From: "Cousson, Benoit" <b-cousson@ti.com>
To: Omar Ramirez Luna <omar.luna@linaro.org>
Cc: Tony Lindgren <tony@atomide.com>,
Russell King <linux@arm.linux.org.uk>,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 0/2] OMAP: mailbox initial device tree support
Date: Wed, 26 Sep 2012 16:27:25 -0700 [thread overview]
Message-ID: <50638F5D.8070508@ti.com> (raw)
In-Reply-To: <CALLhW=4d8zxekkeGr1S52aGbufyk-vGeE9REYhDSt8pnap_Dxw@mail.gmail.com>
Hi Omar,
On 9/26/2012 3:21 PM, Omar Ramirez Luna wrote:
> Hi Benoit,
>
> On 12 September 2012 19:08, Omar Ramirez Luna <omar.luna@linaro.org> wrote:
>> To allow mailbox driver to function with device tree.
>>
>> Tested in OMAP4 and OMAP3. OMAP2 untested.
>>
>> Patch: arm/dts: OMAP2+: Add mailbox nodes, was Acked by Benoit
>> however it seems it wasn't picked up, so resend.
>>
>> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg69121.html
>>
>> Patch: OMAP: mailbox: add device tree support, there wasn't an
>> opposition other than to cleanup the driver too, however I got
>> quite some patches to send before continuing the cleanup.
>>
>> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg69338.html
>>
>> Omar Ramirez Luna (2):
>> OMAP: mailbox: add device tree support
>> arm/dts: OMAP2+: Add mailbox nodes
>>
>> .../devicetree/bindings/arm/omap/mailbox.txt | 9 +++++++++
>> arch/arm/boot/dts/omap2.dtsi | 5 +++++
>> arch/arm/boot/dts/omap3.dtsi | 5 +++++
>> arch/arm/boot/dts/omap4.dtsi | 5 +++++
>> arch/arm/mach-omap2/devices.c | 3 +++
>> arch/arm/mach-omap2/mailbox.c | 12 ++++++++++++
>> 6 files changed, 39 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/arm/omap/mailbox.txt
>
> Ping. I'm in the understanding that these go through your tree, am I right?
Since it is too late for 3.7, you should probably do two more things:
- move the mailbox driver outside mach-omap2
- move the nr_mbox information in the driver as well instead of the
hwmod for the DT boot.
Regards,
Benoit
WARNING: multiple messages have this Message-ID (diff)
From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] OMAP: mailbox initial device tree support
Date: Wed, 26 Sep 2012 16:27:25 -0700 [thread overview]
Message-ID: <50638F5D.8070508@ti.com> (raw)
In-Reply-To: <CALLhW=4d8zxekkeGr1S52aGbufyk-vGeE9REYhDSt8pnap_Dxw@mail.gmail.com>
Hi Omar,
On 9/26/2012 3:21 PM, Omar Ramirez Luna wrote:
> Hi Benoit,
>
> On 12 September 2012 19:08, Omar Ramirez Luna <omar.luna@linaro.org> wrote:
>> To allow mailbox driver to function with device tree.
>>
>> Tested in OMAP4 and OMAP3. OMAP2 untested.
>>
>> Patch: arm/dts: OMAP2+: Add mailbox nodes, was Acked by Benoit
>> however it seems it wasn't picked up, so resend.
>>
>> http://www.mail-archive.com/linux-omap at vger.kernel.org/msg69121.html
>>
>> Patch: OMAP: mailbox: add device tree support, there wasn't an
>> opposition other than to cleanup the driver too, however I got
>> quite some patches to send before continuing the cleanup.
>>
>> http://www.mail-archive.com/linux-omap at vger.kernel.org/msg69338.html
>>
>> Omar Ramirez Luna (2):
>> OMAP: mailbox: add device tree support
>> arm/dts: OMAP2+: Add mailbox nodes
>>
>> .../devicetree/bindings/arm/omap/mailbox.txt | 9 +++++++++
>> arch/arm/boot/dts/omap2.dtsi | 5 +++++
>> arch/arm/boot/dts/omap3.dtsi | 5 +++++
>> arch/arm/boot/dts/omap4.dtsi | 5 +++++
>> arch/arm/mach-omap2/devices.c | 3 +++
>> arch/arm/mach-omap2/mailbox.c | 12 ++++++++++++
>> 6 files changed, 39 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/arm/omap/mailbox.txt
>
> Ping. I'm in the understanding that these go through your tree, am I right?
Since it is too late for 3.7, you should probably do two more things:
- move the mailbox driver outside mach-omap2
- move the nr_mbox information in the driver as well instead of the
hwmod for the DT boot.
Regards,
Benoit
WARNING: multiple messages have this Message-ID (diff)
From: "Cousson, Benoit" <b-cousson@ti.com>
To: Omar Ramirez Luna <omar.luna@linaro.org>
Cc: Tony Lindgren <tony@atomide.com>,
Russell King <linux@arm.linux.org.uk>,
<devicetree-discuss@lists.ozlabs.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-omap@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] OMAP: mailbox initial device tree support
Date: Wed, 26 Sep 2012 16:27:25 -0700 [thread overview]
Message-ID: <50638F5D.8070508@ti.com> (raw)
In-Reply-To: <CALLhW=4d8zxekkeGr1S52aGbufyk-vGeE9REYhDSt8pnap_Dxw@mail.gmail.com>
Hi Omar,
On 9/26/2012 3:21 PM, Omar Ramirez Luna wrote:
> Hi Benoit,
>
> On 12 September 2012 19:08, Omar Ramirez Luna <omar.luna@linaro.org> wrote:
>> To allow mailbox driver to function with device tree.
>>
>> Tested in OMAP4 and OMAP3. OMAP2 untested.
>>
>> Patch: arm/dts: OMAP2+: Add mailbox nodes, was Acked by Benoit
>> however it seems it wasn't picked up, so resend.
>>
>> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg69121.html
>>
>> Patch: OMAP: mailbox: add device tree support, there wasn't an
>> opposition other than to cleanup the driver too, however I got
>> quite some patches to send before continuing the cleanup.
>>
>> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg69338.html
>>
>> Omar Ramirez Luna (2):
>> OMAP: mailbox: add device tree support
>> arm/dts: OMAP2+: Add mailbox nodes
>>
>> .../devicetree/bindings/arm/omap/mailbox.txt | 9 +++++++++
>> arch/arm/boot/dts/omap2.dtsi | 5 +++++
>> arch/arm/boot/dts/omap3.dtsi | 5 +++++
>> arch/arm/boot/dts/omap4.dtsi | 5 +++++
>> arch/arm/mach-omap2/devices.c | 3 +++
>> arch/arm/mach-omap2/mailbox.c | 12 ++++++++++++
>> 6 files changed, 39 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/arm/omap/mailbox.txt
>
> Ping. I'm in the understanding that these go through your tree, am I right?
Since it is too late for 3.7, you should probably do two more things:
- move the mailbox driver outside mach-omap2
- move the nr_mbox information in the driver as well instead of the
hwmod for the DT boot.
Regards,
Benoit
next prev parent reply other threads:[~2012-09-26 23:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 0:08 [PATCH v2 0/2] OMAP: mailbox initial device tree support Omar Ramirez Luna
2012-09-13 0:08 ` Omar Ramirez Luna
[not found] ` <1347494898-16671-1-git-send-email-omar.luna-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-09-13 0:08 ` [PATCH v2 1/2] OMAP: mailbox: add " Omar Ramirez Luna
2012-09-13 0:08 ` Omar Ramirez Luna
2012-09-13 0:08 ` Omar Ramirez Luna
2012-09-13 0:08 ` [PATCH v2 2/2] arm/dts: OMAP2+: Add mailbox nodes Omar Ramirez Luna
2012-09-13 0:08 ` Omar Ramirez Luna
2012-09-13 0:08 ` [PATCH v2 0/2] OMAP: mailbox initial device tree support Omar Ramirez Luna
2012-09-13 0:08 ` Omar Ramirez Luna
2012-09-26 22:21 ` Omar Ramirez Luna
2012-09-26 22:21 ` Omar Ramirez Luna
2012-09-26 23:27 ` Cousson, Benoit [this message]
2012-09-26 23:27 ` Cousson, Benoit
2012-09-26 23:27 ` Cousson, Benoit
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=50638F5D.8070508@ti.com \
--to=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=omar.luna@linaro.org \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.