From: d-gerlach@ti•com (Dave Gerlach)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 4/4] ARM: dts: AM4372: Add the wkup_m3_ipc node
Date: Mon, 18 Jan 2016 14:17:47 -0600 [thread overview]
Message-ID: <569D486B.6080000@ti.com> (raw)
In-Reply-To: <20150805103155.GB16878@atomide.com>
Hi Tony,
On 08/05/2015 05:31 AM, Tony Lindgren wrote:
> * Dave Gerlach <d-gerlach@ti•com> [150717 14:10]:
>> From: Suman Anna <s-anna@ti•com>
>>
>> Add the Wakeup M3 IPC device node for the wkup_m3_ipc driver on
>> AM4372 SoC. This node uses the IPC registers, part of the Control
>> Module, and is therefore added as a child of the scm node.
>
> Applying the last two patches in this series into omap-for-v4.3/dt
> thanks.
>
> Probably the send-no-irq quirk you can do in the driver based
> on the compatible flag like I suggested in the related mailbox
> thread so not applying those until that's been discussed.
Now that this compatible flag for the mbox driver has been accepted
here: 8e3c5952144f ("mailbox/omap: Add ti,mbox-send-noirq quirk to fix
AM33xx CPU Idle") can the first two patches in this series get picked
up. I tested applying to v4.4 and they still apply cleanly.
Regards,
Dave
>
> Regards,
>
> Tony
>
next prev parent reply other threads:[~2016-01-18 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 21:08 [PATCH 0/4] ARM: dts: am335x/am43xx: wkup_m3_ipc support patches Dave Gerlach
2015-07-17 21:08 ` [PATCH 1/4] ARM: dts: AM33xx: Add ti, mbox-send-noirq to wkup_m3 mailbox Dave Gerlach
2015-07-17 21:08 ` [PATCH 2/4] ARM: dts: AM4372: " Dave Gerlach
2015-07-17 21:08 ` [PATCH 3/4] ARM: dts: AM33xx: Add the wkup_m3_ipc node Dave Gerlach
2015-07-17 21:08 ` [PATCH 4/4] ARM: dts: AM4372: " Dave Gerlach
2015-08-05 10:31 ` Tony Lindgren
2016-01-18 20:17 ` Dave Gerlach [this message]
2016-01-21 21:55 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=569D486B.6080000@ti.com \
--to=d-gerlach@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox