From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Mugunthan V N <mugunthanvnm@ti.com>,
devicetree@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, bcousson@baylibre.com,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH 1/1] arm: dts: am33xx: correcting dt node unit address for usb
Date: Thu, 13 Mar 2014 13:30:09 -0700 [thread overview]
Message-ID: <20140313203009.GE5981@atomide.com> (raw)
In-Reply-To: <20140306152637.GB25648@saruman.home>
* Felipe Balbi <balbi@ti.com> [140306 07:33]:
> On Thu, Mar 06, 2014 at 06:01:34PM +0530, Mugunthan V N wrote:
> > DT node's unit address should be its own register offset address to make it a
> > unique across the system. This patch corrects the incorrect USB entries with
> > correct register offset for unit address.
> >
> > Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> > Cc: Felipe Balbi <balbi@ti.com>
> > Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com>
>
> Acked-by: Felipe Balbi <balbi@ti.com>
Applying into omap-for-v3.15/fixes with cc stable v3.12+. If somebody
wants it in earlier kernels it needs to be updated and posted
to the lists.
Regards,
Tony
> > This patch was posted long back (Aug. 30, 2013), below is the archive of the
> > orginal patch.
> > https://patchwork.kernel.org/patch/2852163/
> >
> > ---
> > arch/arm/boot/dts/am33xx.dtsi | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> > index 7073429..9770e35 100644
> > --- a/arch/arm/boot/dts/am33xx.dtsi
> > +++ b/arch/arm/boot/dts/am33xx.dtsi
> > @@ -453,7 +453,7 @@
> > ti,hwmods = "usb_otg_hs";
> > status = "disabled";
> >
> > - usb_ctrl_mod: control@44e10000 {
> > + usb_ctrl_mod: control@44e10620 {
> > compatible = "ti,am335x-usb-ctrl-module";
> > reg = <0x44e10620 0x10
> > 0x44e10648 0x4>;
> > @@ -556,7 +556,7 @@
> > "tx14", "tx15";
> > };
> >
> > - cppi41dma: dma-controller@07402000 {
> > + cppi41dma: dma-controller@47402000 {
> > compatible = "ti,am3359-cppi41";
> > reg = <0x47400000 0x1000
> > 0x47402000 0x1000
> > --
> > 1.9.0
> >
>
> --
> balbi
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 1/1] arm: dts: am33xx: correcting dt node unit address for usb
Date: Thu, 13 Mar 2014 13:30:09 -0700 [thread overview]
Message-ID: <20140313203009.GE5981@atomide.com> (raw)
In-Reply-To: <20140306152637.GB25648@saruman.home>
* Felipe Balbi <balbi@ti.com> [140306 07:33]:
> On Thu, Mar 06, 2014 at 06:01:34PM +0530, Mugunthan V N wrote:
> > DT node's unit address should be its own register offset address to make it a
> > unique across the system. This patch corrects the incorrect USB entries with
> > correct register offset for unit address.
> >
> > Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> > Cc: Felipe Balbi <balbi@ti.com>
> > Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com>
>
> Acked-by: Felipe Balbi <balbi@ti.com>
Applying into omap-for-v3.15/fixes with cc stable v3.12+. If somebody
wants it in earlier kernels it needs to be updated and posted
to the lists.
Regards,
Tony
> > This patch was posted long back (Aug. 30, 2013), below is the archive of the
> > orginal patch.
> > https://patchwork.kernel.org/patch/2852163/
> >
> > ---
> > arch/arm/boot/dts/am33xx.dtsi | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> > index 7073429..9770e35 100644
> > --- a/arch/arm/boot/dts/am33xx.dtsi
> > +++ b/arch/arm/boot/dts/am33xx.dtsi
> > @@ -453,7 +453,7 @@
> > ti,hwmods = "usb_otg_hs";
> > status = "disabled";
> >
> > - usb_ctrl_mod: control at 44e10000 {
> > + usb_ctrl_mod: control at 44e10620 {
> > compatible = "ti,am335x-usb-ctrl-module";
> > reg = <0x44e10620 0x10
> > 0x44e10648 0x4>;
> > @@ -556,7 +556,7 @@
> > "tx14", "tx15";
> > };
> >
> > - cppi41dma: dma-controller at 07402000 {
> > + cppi41dma: dma-controller at 47402000 {
> > compatible = "ti,am3359-cppi41";
> > reg = <0x47400000 0x1000
> > 0x47402000 0x1000
> > --
> > 1.9.0
> >
>
> --
> balbi
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2014-03-13 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 12:31 [RESEND PATCH 1/1] arm: dts: am33xx: correcting dt node unit address for usb Mugunthan V N
2014-03-06 12:31 ` Mugunthan V N
2014-03-06 12:31 ` Mugunthan V N
2014-03-06 12:42 ` Sebastian Andrzej Siewior
2014-03-06 12:42 ` Sebastian Andrzej Siewior
2014-03-06 15:26 ` Felipe Balbi
2014-03-06 15:26 ` Felipe Balbi
2014-03-06 15:26 ` Felipe Balbi
2014-03-13 20:30 ` Tony Lindgren [this message]
2014-03-13 20:30 ` 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=20140313203009.GE5981@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=bcousson@baylibre.com \
--cc=bigeasy@linutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mugunthanvnm@ti.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.