From: Bjorn Helgaas <helgaas@kernel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Hanjie Lin <hanjie.lin@amlogic.com>,
Yixun Lan <yixun.lan@amlogic.com>, Rob Herring <robh@kernel.org>,
Jianxin Pan <jianxin.pan@amlogic.com>,
Kevin Hilman <khilman@baylibre.com>,
Shawn Lin <shawn.lin@rock-chips.com>,
Philippe Ombredanne <pombredanne@nexb.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Yue Wang <yue.wang@amlogic.com>,
Qiufang Dai <qiufang.dai@amlogic.com>,
Jian Hu <jian.hu@amlogic.com>,
Liang Yang <liang.yang@amlogic.com>,
Cyrille Pitchen <cyrille.pitchen@free-electrons.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Carlo Caione <carlo@caione.org>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH v6 2/2] PCI: amlogic: Add the Amlogic Meson PCIe controller driver
Date: Mon, 3 Dec 2018 16:57:31 -0600 [thread overview]
Message-ID: <20181203225731.GE207198@google.com> (raw)
In-Reply-To: <20181203164150.GA11855@e107981-ln.cambridge.arm.com>
On Mon, Dec 03, 2018 at 04:41:50PM +0000, Lorenzo Pieralisi wrote:
> On Thu, Nov 22, 2018 at 04:53:54PM +0800, Hanjie Lin wrote:
>
> [...]
>
> > +static int meson_pcie_rd_own_conf(struct pcie_port *pp, int where, int size,
> > + u32 *val)
> > +{
> > + struct dw_pcie *pci = to_dw_pcie_from_pp(pp);
> > +
> > + /*
> > + * there is a bug of MESON AXG pcie controller that software can not
> > + * programe PCI_CLASS_DEVICE register, so we must return a fake right
> > + * value to ensure driver could probe successfully.
> > + */
> > + if (where == PCI_CLASS_REVISION) {
> > + *val = readl(pci->dbi_base + PCI_CLASS_REVISION);
> > + /* keep revision id */
> > + *val &= PCI_CLASS_REVISION_MASK;
> > + *val |= PCI_CLASS_BRIDGE_PCI << 16;
> > + return PCIBIOS_SUCCESSFUL;
> > + }
>
> As I said before, this looks broken. If this code (or other drivers with
> the same broken assumptions, eg dwc/pcie-qcom.c) carries out a, say,
> byte sized config access of eg PCI_CLASS_DEVICE you will get junk out of
> it according to your comment above.
>
> I would like to pick Bjorn's brain on this to see what we can really do
> to fix this (and other) drivers.
- Check to see whether you're reading anything in the 32-bit dword at
offset 0x08.
- Do the 32-bit readl().
- Insert the correct Sub-Class and Base Class code (you also throw
away the Programming Interface; not sure why that is)
- If you're reading something smaller than 32 bits, mask & shift as
needed. pci_bridge_emul_conf_read() does something similar that
you might be able to copy.
Out of curiosity, what code depends on PCI_CLASS_BRIDGE_PCI? There
are several places in the kernel that currently depend on it, but I
think several of them *should* be checking dev->hdr_type to identify a
type 1 header instead.
Bjorn
next prev parent reply other threads:[~2018-12-03 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 8:53 [PATCH v6 0/2] add the Amlogic Meson PCIe controller driver Hanjie Lin
2018-11-22 8:53 ` [PATCH v6 1/2] dt-bindings: PCI: meson: add DT bindings for Amlogic Meson PCIe controller Hanjie Lin
2018-11-22 8:53 ` [PATCH v6 2/2] PCI: amlogic: Add the Amlogic Meson PCIe controller driver Hanjie Lin
2018-11-29 9:03 ` Dan Carpenter
2018-11-29 12:08 ` Hanjie Lin
2018-11-29 12:20 ` Dan Carpenter
2018-12-03 16:41 ` Lorenzo Pieralisi
2018-12-03 22:57 ` Bjorn Helgaas [this message]
2018-12-04 10:40 ` Hanjie Lin
2018-12-04 12:00 ` Lorenzo Pieralisi
2018-12-05 9:55 ` Hanjie Lin
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=20181203225731.GE207198@google.com \
--to=helgaas@kernel.org \
--cc=carlo@caione.org \
--cc=cyrille.pitchen@free-electrons.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=hanjie.lin@amlogic.com \
--cc=jbrunet@baylibre.com \
--cc=jian.hu@amlogic.com \
--cc=jianxin.pan@amlogic.com \
--cc=khilman@baylibre.com \
--cc=liang.yang@amlogic.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=pombredanne@nexb.com \
--cc=qiufang.dai@amlogic.com \
--cc=robh@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=yixun.lan@amlogic.com \
--cc=yue.wang@amlogic.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;
as well as URLs for NNTP newsgroup(s).