From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Herring <robherring2@gmail.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Dmitry Krivoschekov <dkrivoschokov@dev.rtsoft.ru>,
Nikita Yushchenko <nyushchenko@dev.rtsoft.ru>,
Thierry Reding <thierry.reding@avionic-design.de>,
linux-kernel@vger.kernel.org,
Grant Likely <grant.likely@linaro.org>,
linuxppc-dev@lists.ozlabs.org,
Alexey Lugovskoy <lugovskoy@dev.rtsoft.ru>
Subject: Re: commit e38c0a1f breaks powerpc boards with uli1575 chip
Date: Thu, 19 Dec 2013 15:24:02 +0100 [thread overview]
Message-ID: <20131219142400.GA13878@ulmo.nvidia.com> (raw)
In-Reply-To: <52B1EC15.5070606@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4008 bytes --]
On Wed, Dec 18, 2013 at 12:40:21PM -0600, Rob Herring wrote:
> [fixed DT maillist address]
>
> On 12/17/2013 01:35 AM, Nikita Yushchenko wrote:
> > Hi
> >
> > While trying to make freescale p2020ds and mpc8572ds boards working with mainline kernel, I faced that commit
> > e38c0a1f (Handle #address-cells > 2 specially) breaks things with these boards.
>
> Good to see this broke in v3.7 and is just now found...
>
> >
> > Both these boards have uli1575 chip.
> > Corresponding part in device tree is something like
> >
> > uli1575@0 {
> > reg = <0x0 0x0 0x0 0x0 0x0>;
> > #size-cells = <2>;
> > #address-cells = <3>;
> > ranges = <0x2000000 0x0 0x80000000
> > 0x2000000 0x0 0x80000000
> > 0x0 0x20000000
> >
> > 0x1000000 0x0 0x0
> > 0x1000000 0x0 0x0
> > 0x0 0x10000>;
> > isa@1e {
> > ...
> >
> > I.e. it has #address-cells = <3>
> >
> >
> > With commit e38c0a1f reverted, devices under uli1575 are registered correctly, e.g. for rtc
> >
> > OF: ** translation for device /pcie@ffe09000/pcie@0/uli1575@0/isa@1e/rtc@70 **
> > OF: bus is isa (na=2, ns=1) on /pcie@ffe09000/pcie@0/uli1575@0/isa@1e
> > OF: translating address: 00000001 00000070
> > OF: parent bus is default (na=3, ns=2) on /pcie@ffe09000/pcie@0/uli1575@0
> > OF: walking ranges...
> > OF: ISA map, cp=0, s=1000, da=70
> > OF: parent translation for: 01000000 00000000 00000000
> > OF: with offset: 70
> > OF: one level translation: 00000000 00000000 00000070
> > OF: parent bus is pci (na=3, ns=2) on /pcie@ffe09000/pcie@0
> > OF: walking ranges...
> > OF: default map, cp=a0000000, s=20000000, da=70
> > OF: default map, cp=0, s=10000, da=70
> > OF: parent translation for: 01000000 00000000 00000000
> > OF: with offset: 70
> > OF: one level translation: 01000000 00000000 00000070
> > OF: parent bus is pci (na=3, ns=2) on /pcie@ffe09000
> > OF: walking ranges...
> > OF: PCI map, cp=0, s=10000, da=70
> > OF: parent translation for: 01000000 00000000 00000000
> > OF: with offset: 70
> > OF: one level translation: 01000000 00000000 00000070
> > OF: parent bus is default (na=2, ns=2) on /
> > OF: walking ranges...
> > OF: PCI map, cp=0, s=10000, da=70
> > OF: parent translation for: 00000000 ffc10000
> > OF: with offset: 70
> > OF: one level translation: 00000000 ffc10070
> > OF: reached root node
> >
> > With commit e38c0a1f in place, address translation fails:
> >
> > OF: ** translation for device /pcie@ffe09000/pcie@0/uli1575@0/isa@1e/rtc@70 **
> > OF: bus is isa (na=2, ns=1) on /pcie@ffe09000/pcie@0/uli1575@0/isa@1e
> > OF: translating address: 00000001 00000070
> > OF: parent bus is default (na=3, ns=2) on /pcie@ffe09000/pcie@0/uli1575@0
> > OF: walking ranges...
> > OF: ISA map, cp=0, s=1000, da=70
> > OF: parent translation for: 01000000 00000000 00000000
> > OF: with offset: 70
> > OF: one level translation: 00000000 00000000 00000070
> > OF: parent bus is pci (na=3, ns=2) on /pcie@ffe09000/pcie@0
> > OF: walking ranges...
> > OF: default map, cp=a0000000, s=20000000, da=70
> > OF: default map, cp=0, s=10000, da=70
> > OF: not found !
> >
> > Either e38c0a1f should be reverted, or uli1575 (and perhaps other similar devices) have to be described in device
> > trees differently.
>
> Reverting would break Tegra PCIe, but you should not have to change the
> DT either. So we need a solution.
We ended up merging a different address representation for Tegra PCIe
and I've confirmed that reverting this commit doesn't cause any obvious
regressions. I think all other drivers in drivers/pci/host ended up
copying what we did on Tegra, so I wouldn't expect any other breakage
either.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Herring <robherring2@gmail.com>
Cc: Nikita Yushchenko <nyushchenko@dev.rtsoft.ru>,
Arnd Bergmann <arnd@arndb.de>,
Thierry Reding <thierry.reding@avionic-design.de>,
Grant Likely <grant.likely@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Kumar Gala <galak@kernel.crashing.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Alexey Lugovskoy <lugovskoy@dev.rtsoft.ru>,
Dmitry Krivoschekov <dkrivoschokov@dev.rtsoft.ru>
Subject: Re: commit e38c0a1f breaks powerpc boards with uli1575 chip
Date: Thu, 19 Dec 2013 15:24:02 +0100 [thread overview]
Message-ID: <20131219142400.GA13878@ulmo.nvidia.com> (raw)
In-Reply-To: <52B1EC15.5070606@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4008 bytes --]
On Wed, Dec 18, 2013 at 12:40:21PM -0600, Rob Herring wrote:
> [fixed DT maillist address]
>
> On 12/17/2013 01:35 AM, Nikita Yushchenko wrote:
> > Hi
> >
> > While trying to make freescale p2020ds and mpc8572ds boards working with mainline kernel, I faced that commit
> > e38c0a1f (Handle #address-cells > 2 specially) breaks things with these boards.
>
> Good to see this broke in v3.7 and is just now found...
>
> >
> > Both these boards have uli1575 chip.
> > Corresponding part in device tree is something like
> >
> > uli1575@0 {
> > reg = <0x0 0x0 0x0 0x0 0x0>;
> > #size-cells = <2>;
> > #address-cells = <3>;
> > ranges = <0x2000000 0x0 0x80000000
> > 0x2000000 0x0 0x80000000
> > 0x0 0x20000000
> >
> > 0x1000000 0x0 0x0
> > 0x1000000 0x0 0x0
> > 0x0 0x10000>;
> > isa@1e {
> > ...
> >
> > I.e. it has #address-cells = <3>
> >
> >
> > With commit e38c0a1f reverted, devices under uli1575 are registered correctly, e.g. for rtc
> >
> > OF: ** translation for device /pcie@ffe09000/pcie@0/uli1575@0/isa@1e/rtc@70 **
> > OF: bus is isa (na=2, ns=1) on /pcie@ffe09000/pcie@0/uli1575@0/isa@1e
> > OF: translating address: 00000001 00000070
> > OF: parent bus is default (na=3, ns=2) on /pcie@ffe09000/pcie@0/uli1575@0
> > OF: walking ranges...
> > OF: ISA map, cp=0, s=1000, da=70
> > OF: parent translation for: 01000000 00000000 00000000
> > OF: with offset: 70
> > OF: one level translation: 00000000 00000000 00000070
> > OF: parent bus is pci (na=3, ns=2) on /pcie@ffe09000/pcie@0
> > OF: walking ranges...
> > OF: default map, cp=a0000000, s=20000000, da=70
> > OF: default map, cp=0, s=10000, da=70
> > OF: parent translation for: 01000000 00000000 00000000
> > OF: with offset: 70
> > OF: one level translation: 01000000 00000000 00000070
> > OF: parent bus is pci (na=3, ns=2) on /pcie@ffe09000
> > OF: walking ranges...
> > OF: PCI map, cp=0, s=10000, da=70
> > OF: parent translation for: 01000000 00000000 00000000
> > OF: with offset: 70
> > OF: one level translation: 01000000 00000000 00000070
> > OF: parent bus is default (na=2, ns=2) on /
> > OF: walking ranges...
> > OF: PCI map, cp=0, s=10000, da=70
> > OF: parent translation for: 00000000 ffc10000
> > OF: with offset: 70
> > OF: one level translation: 00000000 ffc10070
> > OF: reached root node
> >
> > With commit e38c0a1f in place, address translation fails:
> >
> > OF: ** translation for device /pcie@ffe09000/pcie@0/uli1575@0/isa@1e/rtc@70 **
> > OF: bus is isa (na=2, ns=1) on /pcie@ffe09000/pcie@0/uli1575@0/isa@1e
> > OF: translating address: 00000001 00000070
> > OF: parent bus is default (na=3, ns=2) on /pcie@ffe09000/pcie@0/uli1575@0
> > OF: walking ranges...
> > OF: ISA map, cp=0, s=1000, da=70
> > OF: parent translation for: 01000000 00000000 00000000
> > OF: with offset: 70
> > OF: one level translation: 00000000 00000000 00000070
> > OF: parent bus is pci (na=3, ns=2) on /pcie@ffe09000/pcie@0
> > OF: walking ranges...
> > OF: default map, cp=a0000000, s=20000000, da=70
> > OF: default map, cp=0, s=10000, da=70
> > OF: not found !
> >
> > Either e38c0a1f should be reverted, or uli1575 (and perhaps other similar devices) have to be described in device
> > trees differently.
>
> Reverting would break Tegra PCIe, but you should not have to change the
> DT either. So we need a solution.
We ended up merging a different address representation for Tegra PCIe
and I've confirmed that reverting this commit doesn't cause any obvious
regressions. I think all other drivers in drivers/pci/host ended up
copying what we did on Tegra, so I wouldn't expect any other breakage
either.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-19 14:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 7:35 commit e38c0a1f breaks powerpc boards with uli1575 chip Nikita Yushchenko
2013-12-17 7:35 ` Nikita Yushchenko
2013-12-18 18:40 ` Rob Herring
2013-12-18 18:40 ` Rob Herring
2013-12-19 4:42 ` Nikita Yushchenko
2013-12-19 4:42 ` Nikita Yushchenko
2013-12-30 3:13 ` Benjamin Herrenschmidt
2013-12-30 3:13 ` Benjamin Herrenschmidt
2013-12-30 3:13 ` Benjamin Herrenschmidt
2014-01-03 0:04 ` Scott Wood
2014-01-03 0:04 ` Scott Wood
2014-01-03 0:04 ` Scott Wood
2013-12-19 14:24 ` Thierry Reding [this message]
2013-12-19 14:24 ` Thierry Reding
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=20131219142400.GA13878@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=dkrivoschokov@dev.rtsoft.ru \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lugovskoy@dev.rtsoft.ru \
--cc=nyushchenko@dev.rtsoft.ru \
--cc=robherring2@gmail.com \
--cc=thierry.reding@avionic-design.de \
/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.