From: Jean-Jacques Hiblot <jjhiblot@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] dm: Add a No-op uclass
Date: Mon, 1 Apr 2019 13:32:08 +0200 [thread overview]
Message-ID: <94e5e0c9-1e8c-8074-45d2-ee6ed5c4b793@ti.com> (raw)
In-Reply-To: <CAPnjgZ2F5MdbfW2CoJrPgonm6As0HGr-tVJLOtPwhbk24Hx7xg@mail.gmail.com>
Hi Simon,
On 30/03/2019 22:18, Simon Glass wrote:
> Hi Jean-Jacques,
>
> On Fri, 22 Mar 2019 at 10:44, Jean-Jacques Hiblot <jjhiblot@ti.com> wrote:
>> This uclass is intended for devices that do not need any features from the
>> uclass, including binding children.
>> This will typically be used by devices that are used to bind child devices
>> but do not use dm_scan_fdt_dev() to do it.
>>
> Can you expand this motivation a little? I am not sure why calling
> dm_scan_fdt_dev() would be problematic.
In the case of the USB wrappers, there are 2 children nodes: one for
peripheral and one for host. The wrapper binds only one of them.
dm_scan_fdt_dev() would bind both.
>
> Also if you do add a new uclass it should have a sandbox driver and test.
There isn't much to test, except to check that the uclass is present.
The UCLASS itself does not provide any feature.
JJ
>
> Regards,
> Simon
>
next prev parent reply other threads:[~2019-04-01 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 16:44 [U-Boot] [PATCH] dm: Add a No-op uclass Jean-Jacques Hiblot
2019-03-22 17:39 ` Sergey Kubushyn
2019-03-25 11:24 ` Jean-Jacques Hiblot
2019-03-30 21:18 ` Simon Glass
2019-04-01 11:32 ` Jean-Jacques Hiblot [this message]
2019-04-01 16:18 ` Simon Glass
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=94e5e0c9-1e8c-8074-45d2-ee6ed5c4b793@ti.com \
--to=jjhiblot@ti.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.