From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 1/2] pci: Support parsing PCI controller DT subnodes
Date: Thu, 30 Aug 2018 15:42:40 +0200 [thread overview]
Message-ID: <02bb72fd-eef5-c7ca-e546-4b1c2343afbc@gmail.com> (raw)
In-Reply-To: <CAEUhbmVgi+bbwsFZGHZEvZis93veVLo+Su2CZf2a=20M5qJK9A@mail.gmail.com>
On 08/30/2018 03:32 PM, Bin Meng wrote:
> Hi Marek,
>
> On Thu, Aug 30, 2018 at 1:07 AM Marek Vasut <marek.vasut@gmail.com> wrote:
>>
>> On 08/29/2018 05:15 PM, Bin Meng wrote:
>>> +Simon
>>>
>>> Hi Marek,
>>>
>>> On Wed, Aug 29, 2018 at 10:22 PM Marek Vasut <marek.vasut@gmail.com> wrote:
>>>>
>>>> On 08/24/2018 08:27 PM, Marek Vasut 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>
>>>>> Cc: Tom Rini <trini@konsulko.com>
>>>>
>>>> Well, bump ?
>>>>
>>>> This is the only missing patch to get my hardware working properly.
>>>
>>> I don't think we ever had an agreement on the v1 patch. Simon had a
>>> long email that pointed out what Linux does seems like a 'fallback' to
>>> find a node with no compatible string.
>>>
>>> Back to this, if we have to go with this way, please create a test
>>> case to cover this scenario.
>>
>> The fact that it works on a particular board is not tested enough?
>> Do we need a custom, special, synthetic test ?
>>
>
> I believe that's always been the requirement against the DM code
> changes. I was requested in the past when I changed something in the
> DM and I see other people were asked to do so. Like Alex said, it does
> not mean this patch was not tested enough, but to ensure future
> commits won't break this.
So, do you have any suggestion how to implement this test ? It seems
Alex posed the same question. It doesn't seem to be trivial in the
context of sandbox.
>> Anyway, any feedback on the patch ? Did you test it ? I again only see
>> "do this random stuff and that random stuff" , but zero actual feedback.
>>
>
> If "this and that random stuff" means test case I asked for, please
> check my proposal on the v1 patch thread which indicated that a proper
> test case should be created. You seems to have missed that.
So, any feedback on this actual patch ?
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-08-30 13:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 18:27 [U-Boot] [PATCH V2 1/2] pci: Support parsing PCI controller DT subnodes Marek Vasut
2018-08-24 18:27 ` [U-Boot] [PATCH V2 2/2] pci: Update documentation to make 'compatible' string optional Marek Vasut
2018-08-30 0:29 ` Simon Glass
2018-08-30 10:20 ` Marek Vasut
2018-09-01 21:45 ` Simon Glass
2018-09-01 22:41 ` Marek Vasut
2018-09-02 1:07 ` Simon Glass
2018-09-02 18:26 ` Marek Vasut
2018-09-02 23:34 ` Simon Glass
2018-08-29 14:21 ` [U-Boot] [PATCH V2 1/2] pci: Support parsing PCI controller DT subnodes Marek Vasut
2018-08-29 15:15 ` Bin Meng
2018-08-29 17:07 ` Marek Vasut
2018-08-29 21:56 ` Alexander Graf
2018-08-30 13:32 ` Bin Meng
2018-08-30 13:42 ` Marek Vasut [this message]
2018-09-01 21:50 ` Simon Glass
2018-09-01 22:45 ` Marek Vasut
2018-09-02 1:07 ` Simon Glass
2018-09-09 23:38 ` Marek Vasut
2018-09-14 4:41 ` Simon Glass
2018-09-18 11:36 ` Marek Vasut
2018-09-18 13:52 ` Bin Meng
2018-09-19 8:19 ` Marek Vasut
2018-09-19 9:25 ` Bin Meng
2018-09-18 13:52 ` Simon Glass
2018-09-19 8:21 ` Marek Vasut
2018-09-19 9:26 ` Bin Meng
2018-09-19 9:34 ` Marek Vasut
2018-09-19 9:41 ` Bin Meng
2018-09-19 13:23 ` Marek Vasut
2018-09-20 1:47 ` Bin Meng
2018-09-20 23:56 ` Marek Vasut
2018-09-26 5:42 ` Simon Glass
2018-09-26 15:03 ` 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=02bb72fd-eef5-c7ca-e546-4b1c2343afbc@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 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.