From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] pci: Support parsing PCI controller DT subnodes
Date: Wed, 8 Aug 2018 16:33:24 +0200 [thread overview]
Message-ID: <1858e8ca-9374-be2d-e102-1defeacbad8c@gmail.com> (raw)
In-Reply-To: <CAEUhbmXebG=ZAXZXnypo_m9Fs1APMa9rvbcbd-2wG0Gcp2nqDA@mail.gmail.com>
On 08/08/2018 03:39 PM, Bin Meng wrote:
> Hi Marek,
>
> On Wed, Aug 8, 2018 at 9:24 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
>> On 08/08/2018 03:14 PM, Bin Meng wrote:
>>> Hi Marek,
>>>
>>> On Wed, Aug 8, 2018 at 9:03 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
>>>> The PCI controller can have DT subnodes describing extra properties
>>>> of particular PCI devices, ie. a PHY attached to an EHCI controller
>>>> on a PCI bus. This patch parses those DT subnodes and assigns a node
>>>> to the PCI device instance, so that the driver can extract details
>>>> from that node and ie. configure the PHY using the PHY subsystem.
>>>>
>>>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>>>> Cc: Simon Glass <sjg@chromium.org>
>>>> ---
>>>> drivers/pci/pci-uclass.c | 14 ++++++++++++++
>>>> 1 file changed, 14 insertions(+)
>>>>
>>>> diff --git a/drivers/pci/pci-uclass.c b/drivers/pci/pci-uclass.c
>>>> index 46e9c71bdf..306bea0dbf 100644
>>>> --- a/drivers/pci/pci-uclass.c
>>>> +++ b/drivers/pci/pci-uclass.c
>>>> @@ -662,6 +662,8 @@ static int pci_find_and_bind_driver(struct udevice *parent,
>>>> for (id = entry->match;
>>>> id->vendor || id->subvendor || id->class_mask;
>>>> id++) {
>>>> + ofnode node;
>>>> +
>>>> if (!pci_match_one_id(id, find_id))
>>>> continue;
>>>>
>>>> @@ -691,6 +693,18 @@ static int pci_find_and_bind_driver(struct udevice *parent,
>>>> goto error;
>>>> debug("%s: Match found: %s\n", __func__, drv->name);
>>>> dev->driver_data = find_id->driver_data;
>>>> +
>>>> + dev_for_each_subnode(node, parent) {
>>>> + phys_addr_t df, size;
>>>> + df = ofnode_get_addr_size(node, "reg", &size);
>>>> +
>>>> + if (PCI_FUNC(df) == PCI_FUNC(bdf) &&
>>>> + PCI_DEV(df) == PCI_DEV(bdf)) {
>>>> + dev->node = node;
>>>> + break;
>>>> + }
>>>
>>> The function pci_find_and_bind_driver() is supposed to bind devices
>>> that are NOT in the device tree. Adding device tree access in this
>>> routine is quite odd. You can add the EHCI controller that need such
>>> PHY subnodes in the device tree and there is no need to modify
>>> anything I believe. If you are looking for an example, please check
>>> pciuart0 in arch/x86/dts/crownbay.dts.
>>
>> Well this does not work for me, the EHCI PCI doesn't get a DT node
>> assigned, check r8a7794.dtsi for the PCI devices I use.
>>
>
> I think that's because you don't specify a "compatible" string for
> these two EHCI PCI nodes.
That's perfectly fine, why should I specify it ? Linux has no problem
with it either.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-08-08 14:33 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 13:03 [U-Boot] [PATCH] pci: Support parsing PCI controller DT subnodes Marek Vasut
2018-08-08 13:14 ` Bin Meng
2018-08-08 13:24 ` Marek Vasut
2018-08-08 13:39 ` Bin Meng
2018-08-08 14:33 ` Marek Vasut [this message]
2018-08-08 15:32 ` Bin Meng
2018-08-08 19:37 ` Marek Vasut
2018-08-08 23:24 ` Bin Meng
2018-08-09 0:36 ` Marek Vasut
2018-08-09 2:37 ` Bin Meng
2018-08-09 7:54 ` Marek Vasut
2018-08-09 9:41 ` Bin Meng
2018-08-09 10:25 ` Marek Vasut
2018-08-10 3:42 ` Bin Meng
2018-08-10 10:32 ` Marek Vasut
2018-08-13 2:07 ` Bin Meng
2018-08-13 13:39 ` Tom Rini
2018-08-13 16:07 ` Marek Vasut
2018-08-13 17:16 ` Tom Rini
2018-08-14 2:34 ` Bin Meng
2018-08-14 8:54 ` Marek Vasut
2018-08-14 9:35 ` Bin Meng
2018-08-15 9:20 ` Marek Vasut
2018-08-14 19:39 ` Tom Rini
2018-08-13 13:43 ` Marek Vasut
2018-08-10 12:01 ` Tom Rini
2018-08-10 12:38 ` Marek Vasut
2018-08-13 2:24 ` Bin Meng
2018-08-13 13:46 ` Marek Vasut
2018-08-14 1:46 ` Bin Meng
2018-08-14 8:55 ` Marek Vasut
2018-08-14 9:40 ` Bin Meng
2018-08-15 9:22 ` Marek Vasut
2018-08-15 10:19 ` Bin Meng
2018-08-15 10:27 ` Marek Vasut
2018-08-15 11:25 ` Tom Rini
2018-08-16 11:47 ` Marek Vasut
2018-08-17 1:51 ` Bin Meng
2018-08-17 10:27 ` Marek Vasut
2018-08-20 7:18 ` Bin Meng
2018-08-20 8:09 ` Marek Vasut
2018-08-20 16:57 ` Simon Glass
2018-08-20 18:42 ` Marek Vasut
2018-08-20 19:29 ` Simon Glass
2018-08-20 20:15 ` Marek Vasut
2018-08-22 18:08 ` Simon Glass
2018-08-22 20:19 ` Marek Vasut
2018-08-23 10:45 ` Simon Glass
2018-08-23 12:58 ` Marek Vasut
2018-08-30 0:29 ` Simon Glass
2018-08-30 9:25 ` Marek Vasut
2018-09-01 21:45 ` Simon Glass
2018-09-01 22:43 ` Marek Vasut
2018-09-02 1:07 ` Simon Glass
2018-09-02 18:24 ` Marek Vasut
2018-09-02 23:35 ` Simon Glass
2018-09-03 0:53 ` Marek Vasut
2018-08-21 3:46 ` Bin Meng
2018-08-21 4:02 ` Marek Vasut
2018-08-21 4:15 ` Bin Meng
2018-08-21 4:30 ` Marek Vasut
2018-08-21 4:56 ` Bin Meng
2018-08-21 5:43 ` Marek Vasut
2018-08-21 7:16 ` Bin Meng
2018-08-21 10:28 ` Marek Vasut
2018-08-22 2:14 ` Bin Meng
2018-08-22 9:57 ` Marek Vasut
2018-08-23 2:11 ` Bin Meng
2018-08-23 7:42 ` Marek Vasut
2018-08-21 17:32 ` Simon Glass
2018-08-21 18:26 ` Marek Vasut
2018-08-21 18:29 ` Simon Glass
2018-08-21 18:56 ` Marek Vasut
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=1858e8ca-9374-be2d-e102-1defeacbad8c@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox