Hi Simon,
On 07/05/2019 05:52, Simon Glass wrote:
Hi Jean-Jacques,
On Fri, 5 Apr 2019 at 06:56, Jean-Jacques Hiblot 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
Hi Jean-Jacques,
On Fri, 5 Apr 2019 at 06:56, Jean-Jacques Hiblot 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
On 5/3/19 11:30 AM, Jean-Jacques Hiblot wrote:
>
> On 29/04/2019 11:56, Marek Vasut wrote:
>> On 4/5/19 2:55 PM, Jean-Jacques Hiblot 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
On 29/04/2019 11:56, Marek Vasut wrote:
On 4/5/19 2:55 PM, Jean-Jacques Hiblot 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
On 4/5/19 2:55 PM, Jean-Jacques Hiblot 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. That is for
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. That is for example the case of
several USB wrappers that have 2
6 matches
Mail list logo
