From: Arnd Bergmann <arnd@arndb.de>
To: Pratyush Anand <panand@redhat.com>
Cc: mohit.kumar@st.com, jg1.han@samsung.com, l.stach@pengutronix.de,
shawn.guo@freescale.com, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org,
Kishon Vijay Abraham I <kishon@ti.com>,
Sean Cross <xobs@kosagi.com>,
Murali Karicheri <m-karicheri2@ti.com>,
Minghuan Lian <Minghuan.Lian@freescale.com>
Subject: Re: [PATCH] PCIe: Designware: Do not allow config space through ranges
Date: Tue, 23 Dec 2014 21:31:01 +0100 [thread overview]
Message-ID: <3330424.GRa0M3NfZG@wuerfel> (raw)
In-Reply-To: <5498D97A.8030105@redhat.com>
On Tuesday 23 December 2014 08:24:50 Pratyush Anand wrote:
> On Monday 22 December 2014 02:00 PM, Arnd Bergmann wrote:
> > On Monday 22 December 2014 12:09:04 Pratyush Anand wrote:
> >> diff --git a/drivers/pci/host/pcie-designware.c b/drivers/pci/host/pcie-designware.c
> >> index df781cdf13c1..0b22b42e1ff9 100644
> >> --- a/drivers/pci/host/pcie-designware.c
> >> +++ b/drivers/pci/host/pcie-designware.c
> >> @@ -409,19 +409,6 @@ int __init dw_pcie_host_init(struct pcie_port *pp)
> >> pp->mem_mod_base = of_read_number(parser.range -
> >> parser.np + na, ns);
> >> }
> >> - if (restype == 0) {
> >> - of_pci_range_to_resource(&range, np, &pp->cfg);
> >> - pp->cfg0_size = resource_size(&pp->cfg)/2;
> >> - pp->cfg1_size = resource_size(&pp->cfg)/2;
> >> - pp->cfg0_base = pp->cfg.start;
> >> - pp->cfg1_base = pp->cfg.start + pp->cfg0_size;
> >> -
> >> - /* Find the untranslated configuration space address */
> >> - pp->cfg0_mod_base = of_read_number(parser.range -
> >> - parser.np + na, ns);
> >> - pp->cfg1_mod_base = pp->cfg0_mod_base +
> >> - pp->cfg0_size;
> >> - }
> >> }
> >
> > Since we've allowed this for so long, it may be better to leave this
> > in for compatibility with old dts files. It would however be good to
> > print a warning message. We could also limit it to those machines that
> > are known to have been used with this property in the past.
>
> I think, only imx6 is using "config from ranges", for which I made the
> change in this patch. Modification need to be tested and acked by IMX6
> maintainers.
> I do not see any other driver using it. However, I have kept all
> designware user in CC here.
The change to look at the 'reg' property for config space was introduced
in 4dd964df36d ("PCI: designware: Look for configuration space in 'reg',
not 'ranges'"), and at the time, we had Exynos5440 and i.MX as users,
which is only a small subset of what we have now. If we are sure that
on both architectures we don't need to support backwards compatibility
for the existing dtbs, then we can do it, but that would be hard to
prove, unless we know for sure that the platforms are already broken
for any user that has old dtb files.
Arnd
next prev parent reply other threads:[~2014-12-23 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 6:39 [PATCH] PCIe: Designware: Do not allow config space through ranges Pratyush Anand
2014-12-22 8:30 ` Arnd Bergmann
2014-12-23 2:54 ` Pratyush Anand
2014-12-23 20:31 ` Arnd Bergmann [this message]
2015-01-05 9:39 ` Lucas Stach
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=3330424.GRa0M3NfZG@wuerfel \
--to=arnd@arndb.de \
--cc=Minghuan.Lian@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=jg1.han@samsung.com \
--cc=kishon@ti.com \
--cc=l.stach@pengutronix.de \
--cc=linux-pci@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=mohit.kumar@st.com \
--cc=panand@redhat.com \
--cc=shawn.guo@freescale.com \
--cc=xobs@kosagi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox