From: "Franklin S Cooper Jr." <fcooper@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux@arm.linux.org.uk, tony@atomide.com, rogerq@ti.com,
nm@ti.com, lokeshvutla@ti.com
Subject: Re: [PATCH 1/2 v2] ARM: DRA7/335x/437x/OMAP4: hwmod: Remove elm address space from hwmod data
Date: Mon, 26 Oct 2015 09:50:16 -0500 [thread overview]
Message-ID: <562E3DA8.4000006@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1510231858170.9575@utopia.booyaka.com>
On 10/23/2015 02:00 PM, Paul Walmsley wrote:
> On Thu, 15 Oct 2015, Franklin S Cooper Jr wrote:
>
>> ELM address information is provided by device tree. No longer need
>> to include this information within hwmod.
>>
>> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
> The OMAP4 DTS files don't have the ELM address space declared. I'm going
> to drop that portion of your patch. Could you please send a two-patch
> series that first adds the ELM address space to the OMAP4 DTS file and
> then subsequently drops it from the OMAP4 hwmod data file?
Hi Paul,
Sorry about that. I can create the patches but I don't see any board omap4
board that has nand support. So I'm not going to be able to test to insure if
omap_elm.c will work as is.
Should I just drop omap4 from this patchset or should I just add the elm node
to omap4.dtsi and if people report an issue with omap_elm then we can fix it?
>
>
> - Paul
WARNING: multiple messages have this Message-ID (diff)
From: fcooper@ti.com (Franklin S Cooper Jr.)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 v2] ARM: DRA7/335x/437x/OMAP4: hwmod: Remove elm address space from hwmod data
Date: Mon, 26 Oct 2015 09:50:16 -0500 [thread overview]
Message-ID: <562E3DA8.4000006@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1510231858170.9575@utopia.booyaka.com>
On 10/23/2015 02:00 PM, Paul Walmsley wrote:
> On Thu, 15 Oct 2015, Franklin S Cooper Jr wrote:
>
>> ELM address information is provided by device tree. No longer need
>> to include this information within hwmod.
>>
>> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
> The OMAP4 DTS files don't have the ELM address space declared. I'm going
> to drop that portion of your patch. Could you please send a two-patch
> series that first adds the ELM address space to the OMAP4 DTS file and
> then subsequently drops it from the OMAP4 hwmod data file?
Hi Paul,
Sorry about that. I can create the patches but I don't see any board omap4
board that has nand support. So I'm not going to be able to test to insure if
omap_elm.c will work as is.
Should I just drop omap4 from this patchset or should I just add the elm node
to omap4.dtsi and if people report an issue with omap_elm then we can fix it?
>
>
> - Paul
WARNING: multiple messages have this Message-ID (diff)
From: "Franklin S Cooper Jr." <fcooper@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-omap@vger.kernel.org>, <linux@arm.linux.org.uk>,
<tony@atomide.com>, <rogerq@ti.com>, <nm@ti.com>,
<lokeshvutla@ti.com>
Subject: Re: [PATCH 1/2 v2] ARM: DRA7/335x/437x/OMAP4: hwmod: Remove elm address space from hwmod data
Date: Mon, 26 Oct 2015 09:50:16 -0500 [thread overview]
Message-ID: <562E3DA8.4000006@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1510231858170.9575@utopia.booyaka.com>
On 10/23/2015 02:00 PM, Paul Walmsley wrote:
> On Thu, 15 Oct 2015, Franklin S Cooper Jr wrote:
>
>> ELM address information is provided by device tree. No longer need
>> to include this information within hwmod.
>>
>> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
> The OMAP4 DTS files don't have the ELM address space declared. I'm going
> to drop that portion of your patch. Could you please send a two-patch
> series that first adds the ELM address space to the OMAP4 DTS file and
> then subsequently drops it from the OMAP4 hwmod data file?
Hi Paul,
Sorry about that. I can create the patches but I don't see any board omap4
board that has nand support. So I'm not going to be able to test to insure if
omap_elm.c will work as is.
Should I just drop omap4 from this patchset or should I just add the elm node
to omap4.dtsi and if people report an issue with omap_elm then we can fix it?
>
>
> - Paul
next prev parent reply other threads:[~2015-10-26 14:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 16:27 [PATCH 1/2 v2] ARM: DRA7/335x/437x/OMAP4: hwmod: Remove elm address space from hwmod data Franklin S Cooper Jr
2015-10-15 16:27 ` Franklin S Cooper Jr
2015-10-15 16:27 ` [PATCH 2/2 v2] ARM: DRA7/335x/437x: hwmod: Remove gpmc " Franklin S Cooper Jr
2015-10-15 16:27 ` Franklin S Cooper Jr
2015-10-16 7:52 ` Roger Quadros
2015-10-16 7:52 ` Roger Quadros
2015-10-16 7:52 ` Roger Quadros
2015-10-20 7:36 ` Paul Walmsley
2015-10-20 7:36 ` Paul Walmsley
2015-10-23 19:01 ` Paul Walmsley
2015-10-23 19:01 ` Paul Walmsley
2015-10-16 7:51 ` [PATCH 1/2 v2] ARM: DRA7/335x/437x/OMAP4: hwmod: Remove elm " Roger Quadros
2015-10-16 7:51 ` Roger Quadros
2015-10-16 7:51 ` Roger Quadros
2015-10-20 7:36 ` Paul Walmsley
2015-10-20 7:36 ` Paul Walmsley
2015-10-23 19:00 ` Paul Walmsley
2015-10-23 19:00 ` Paul Walmsley
2015-10-26 14:50 ` Franklin S Cooper Jr. [this message]
2015-10-26 14:50 ` Franklin S Cooper Jr.
2015-10-26 14:50 ` Franklin S Cooper Jr.
2015-10-26 17:06 ` Paul Walmsley
2015-10-26 17:06 ` Paul Walmsley
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=562E3DA8.4000006@ti.com \
--to=fcooper@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=rogerq@ti.com \
--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.