* [PATCH] ARM: dts: omap3: Fix ISP syscon register offset
@ 2016-04-16 6:20 Ivaylo Dimitrov
[not found] ` <1460787628-17316-1-git-send-email-ivo.g.dimitrov.75-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
0 siblings, 1 reply; 4+ messages in thread
From: Ivaylo Dimitrov @ 2016-04-16 6:20 UTC (permalink / raw)
To: tony, bcousson
Cc: robh+dt, pawel.moll, mark.rutland, ijc+devicetree, galak, linux,
linux-omap, devicetree, linux-arm-kernel, linux-kernel,
Ivaylo Dimitrov
According to the TRM, SCM CONTROL_CSIRXFE register is on offset 0x6c
Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
---
arch/arm/boot/dts/omap34xx.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap34xx.dtsi b/arch/arm/boot/dts/omap34xx.dtsi
index 5cdba1f..e446562 100644
--- a/arch/arm/boot/dts/omap34xx.dtsi
+++ b/arch/arm/boot/dts/omap34xx.dtsi
@@ -46,7 +46,7 @@
0x480bd800 0x017c>;
interrupts = <24>;
iommus = <&mmu_isp>;
- syscon = <&scm_conf 0xdc>;
+ syscon = <&scm_conf 0x6c>;
ti,phy-type = <OMAP3ISP_PHY_TYPE_COMPLEX_IO>;
#clock-cells = <1>;
ports {
--
1.9.1
^ permalink raw reply related [flat|nested] 4+ messages in thread[parent not found: <1460787628-17316-1-git-send-email-ivo.g.dimitrov.75-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]
* Re: [PATCH] ARM: dts: omap3: Fix ISP syscon register offset [not found] ` <1460787628-17316-1-git-send-email-ivo.g.dimitrov.75-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> @ 2016-04-22 4:34 ` Ivaylo Dimitrov [not found] ` <5719A9E3.1000902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 0 siblings, 1 reply; 4+ messages in thread From: Ivaylo Dimitrov @ 2016-04-22 4:34 UTC (permalink / raw) To: tony-4v6yS6AI5VpBDgjK7y7TUQ, bcousson-rdvid1DuHRBWk0Htik3J/w Cc: robh+dt-DgEjT+Ai2ygdnm+yROfE0A, pawel.moll-5wv7dgnIgG8, mark.rutland-5wv7dgnIgG8, ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg, galak-sgV2jX0FEOL9JmXXK+q4OQ, linux-lFZ/pmaqli7XmaaqVzeoHQ, linux-omap-u79uwXL29TY76Z2rM5mHXA, devicetree-u79uwXL29TY76Z2rM5mHXA, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r, linux-kernel-u79uwXL29TY76Z2rM5mHXA, Sebastian Reichel On 16.04.2016 09:20, Ivaylo Dimitrov wrote: > According to the TRM, SCM CONTROL_CSIRXFE register is on offset 0x6c > > Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov.75-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> > --- > arch/arm/boot/dts/omap34xx.dtsi | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/arch/arm/boot/dts/omap34xx.dtsi b/arch/arm/boot/dts/omap34xx.dtsi > index 5cdba1f..e446562 100644 > --- a/arch/arm/boot/dts/omap34xx.dtsi > +++ b/arch/arm/boot/dts/omap34xx.dtsi > @@ -46,7 +46,7 @@ > 0x480bd800 0x017c>; > interrupts = <24>; > iommus = <&mmu_isp>; > - syscon = <&scm_conf 0xdc>; > + syscon = <&scm_conf 0x6c>; > ti,phy-type = <OMAP3ISP_PHY_TYPE_COMPLEX_IO>; > #clock-cells = <1>; > ports { > Anyone going to review that? -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <5719A9E3.1000902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]
* Re: [PATCH] ARM: dts: omap3: Fix ISP syscon register offset [not found] ` <5719A9E3.1000902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> @ 2016-04-22 13:16 ` Sebastian Reichel 2016-04-26 17:12 ` Tony Lindgren 0 siblings, 1 reply; 4+ messages in thread From: Sebastian Reichel @ 2016-04-22 13:16 UTC (permalink / raw) To: Ivaylo Dimitrov Cc: tony-4v6yS6AI5VpBDgjK7y7TUQ, bcousson-rdvid1DuHRBWk0Htik3J/w, robh+dt-DgEjT+Ai2ygdnm+yROfE0A, pawel.moll-5wv7dgnIgG8, mark.rutland-5wv7dgnIgG8, ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg, galak-sgV2jX0FEOL9JmXXK+q4OQ, linux-lFZ/pmaqli7XmaaqVzeoHQ, linux-omap-u79uwXL29TY76Z2rM5mHXA, devicetree-u79uwXL29TY76Z2rM5mHXA, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r, linux-kernel-u79uwXL29TY76Z2rM5mHXA [-- Attachment #1: Type: text/plain, Size: 1209 bytes --] Hi, On Fri, Apr 22, 2016 at 07:34:43AM +0300, Ivaylo Dimitrov wrote: > On 16.04.2016 09:20, Ivaylo Dimitrov wrote: > >According to the TRM, SCM CONTROL_CSIRXFE register is on offset 0x6c > > > >Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov.75-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> > >--- > > arch/arm/boot/dts/omap34xx.dtsi | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > >diff --git a/arch/arm/boot/dts/omap34xx.dtsi b/arch/arm/boot/dts/omap34xx.dtsi > >index 5cdba1f..e446562 100644 > >--- a/arch/arm/boot/dts/omap34xx.dtsi > >+++ b/arch/arm/boot/dts/omap34xx.dtsi > >@@ -46,7 +46,7 @@ > > 0x480bd800 0x017c>; > > interrupts = <24>; > > iommus = <&mmu_isp>; > >- syscon = <&scm_conf 0xdc>; > >+ syscon = <&scm_conf 0x6c>; > > ti,phy-type = <OMAP3ISP_PHY_TYPE_COMPLEX_IO>; > > #clock-cells = <1>; > > ports { > > You may want to add the hint, that 0xdc (the old, wrong "offset") represents the last few bits of the register address. I guess somebody didn't notice, that scm_conf does not start at a register address ending with 00 (like most other modules). Reviewed-By: Sebastian Reichel <sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> -- Sebastian [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] ARM: dts: omap3: Fix ISP syscon register offset 2016-04-22 13:16 ` Sebastian Reichel @ 2016-04-26 17:12 ` Tony Lindgren 0 siblings, 0 replies; 4+ messages in thread From: Tony Lindgren @ 2016-04-26 17:12 UTC (permalink / raw) To: Sebastian Reichel Cc: Ivaylo Dimitrov, bcousson-rdvid1DuHRBWk0Htik3J/w, robh+dt-DgEjT+Ai2ygdnm+yROfE0A, pawel.moll-5wv7dgnIgG8, mark.rutland-5wv7dgnIgG8, ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg, galak-sgV2jX0FEOL9JmXXK+q4OQ, linux-lFZ/pmaqli7XmaaqVzeoHQ, linux-omap-u79uwXL29TY76Z2rM5mHXA, devicetree-u79uwXL29TY76Z2rM5mHXA, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r, linux-kernel-u79uwXL29TY76Z2rM5mHXA * Sebastian Reichel <sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> [160422 06:17]: > Hi, > > On Fri, Apr 22, 2016 at 07:34:43AM +0300, Ivaylo Dimitrov wrote: > > On 16.04.2016 09:20, Ivaylo Dimitrov wrote: > > >According to the TRM, SCM CONTROL_CSIRXFE register is on offset 0x6c > > > > > >Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov.75-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> > > >--- > > > arch/arm/boot/dts/omap34xx.dtsi | 2 +- > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > > >diff --git a/arch/arm/boot/dts/omap34xx.dtsi b/arch/arm/boot/dts/omap34xx.dtsi > > >index 5cdba1f..e446562 100644 > > >--- a/arch/arm/boot/dts/omap34xx.dtsi > > >+++ b/arch/arm/boot/dts/omap34xx.dtsi > > >@@ -46,7 +46,7 @@ > > > 0x480bd800 0x017c>; > > > interrupts = <24>; > > > iommus = <&mmu_isp>; > > >- syscon = <&scm_conf 0xdc>; > > >+ syscon = <&scm_conf 0x6c>; > > > ti,phy-type = <OMAP3ISP_PHY_TYPE_COMPLEX_IO>; > > > #clock-cells = <1>; > > > ports { > > > > > You may want to add the hint, that 0xdc (the old, wrong "offset") > represents the last few bits of the register address. I guess > somebody didn't notice, that scm_conf does not start at a register > address ending with 00 (like most other modules). > > Reviewed-By: Sebastian Reichel <sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> Applying into omap-for-v4.6/fixes-rc5 thanks. Tony -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-04-26 17:12 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-04-16 6:20 [PATCH] ARM: dts: omap3: Fix ISP syscon register offset Ivaylo Dimitrov
[not found] ` <1460787628-17316-1-git-send-email-ivo.g.dimitrov.75-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-22 4:34 ` Ivaylo Dimitrov
[not found] ` <5719A9E3.1000902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-22 13:16 ` Sebastian Reichel
2016-04-26 17:12 ` Tony Lindgren
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).