On 09/03/2018 01:35 AM, Simon Glass wrote:
> Hi Marek,
>
> On 2 September 2018 at 12:24, Marek Vasut wrote:
>> On 09/02/2018 03:07 AM, Simon Glass wrote:
>>> Hi Marek,
>>>
>>> On 1 September 2018 at 16:43, Marek Vasut wrote:
On 09/01/2018 11:45 PM, Simon Glass wrote:
> Hi Marek,
>
Hi Marek,
On 2 September 2018 at 12:24, Marek Vasut wrote:
> On 09/02/2018 03:07 AM, Simon Glass wrote:
>> Hi Marek,
>>
>> On 1 September 2018 at 16:43, Marek Vasut wrote:
>>> On 09/01/2018 11:45 PM, Simon Glass wrote:
Hi Marek,
On 30 August 2018 at 03:25, Marek Vasut wrote:
On 09/02/2018 03:07 AM, Simon Glass wrote:
> Hi Marek,
>
> On 1 September 2018 at 16:43, Marek Vasut wrote:
>> On 09/01/2018 11:45 PM, Simon Glass wrote:
>>> Hi Marek,
>>>
>>> On 30 August 2018 at 03:25, Marek Vasut wrote:
On 08/30/2018 02:29 AM, Simon Glass wrote:
> Hi Marek,
Hi Marek,
On 1 September 2018 at 16:43, Marek Vasut wrote:
> On 09/01/2018 11:45 PM, Simon Glass wrote:
>> Hi Marek,
>>
>> On 30 August 2018 at 03:25, Marek Vasut wrote:
>>>
>>> On 08/30/2018 02:29 AM, Simon Glass wrote:
Hi Marek,
>>>
>>> Hi,
>>>
>>> [...]
>>>
>> If you have both EHCI
On 09/01/2018 11:45 PM, Simon Glass wrote:
> Hi Marek,
>
> On 30 August 2018 at 03:25, Marek Vasut wrote:
>>
>> On 08/30/2018 02:29 AM, Simon Glass wrote:
>>> Hi Marek,
>>
>> Hi,
>>
>> [...]
>>
> If you have both EHCI and a xHCI controller which can occupy the same
> BFD, then how would
Hi Marek,
On 30 August 2018 at 03:25, Marek Vasut wrote:
>
> On 08/30/2018 02:29 AM, Simon Glass wrote:
> > Hi Marek,
>
> Hi,
>
> [...]
>
> >>> If you have both EHCI and a xHCI controller which can occupy the same
> >>> BFD, then how would you supply in the DT options needed by the
> >>>
On 08/30/2018 02:29 AM, Simon Glass wrote:
> Hi Marek,
Hi,
[...]
>>> If you have both EHCI and a xHCI controller which can occupy the same
>>> BFD, then how would you supply in the DT options needed by the
>>> controller itself? Don't you need two nodes in that case?
>>
>> For the PHY case,
Hi Marek,
On 23 August 2018 at 06:58, Marek Vasut wrote:
> On 08/23/2018 12:45 PM, Simon Glass wrote:
> [...]
Why is pci_bus_find_devfn() failing?
>>>
>>> Because this function is a hack to force-bind drivers to PCI devices
>>> which are described in the DT with a compatible string. This
On 08/23/2018 12:45 PM, Simon Glass wrote:
[...]
>>> Why is pci_bus_find_devfn() failing?
>>
>> Because this function is a hack to force-bind drivers to PCI devices
>> which are described in the DT with a compatible string. This does not
>> apply to this case.
>
> pci_bus_find_devfn() does not
Hi Marek,
On 22 August 2018 at 14:19, Marek Vasut wrote:
> On 08/22/2018 08:08 PM, Simon Glass wrote:
> [...]
>>> This is explained in the patch description and the thread again. Please
>>> read the thread before replying. Take a look at the r8a7794.dtsi and its
>>> PCI bindings, there are PCI
On 08/23/2018 04:11 AM, Bin Meng wrote:
> Hi Marek,
Hello Bin,
> On Wed, Aug 22, 2018 at 5:57 PM, Marek Vasut wrote:
>> On 08/22/2018 04:14 AM, Bin Meng wrote:
>> [...]
>> I said in the previous discussion I am willing to update the
>> documentation to match the implementation, but
Hi Marek,
On Wed, Aug 22, 2018 at 5:57 PM, Marek Vasut wrote:
> On 08/22/2018 04:14 AM, Bin Meng wrote:
> [...]
> I said in the previous discussion I am willing to update the
> documentation to match the implementation, but that's about it.
>
>> So far almost all PCI device
On 08/22/2018 08:08 PM, Simon Glass wrote:
[...]
>> This is explained in the patch description and the thread again. Please
>> read the thread before replying. Take a look at the r8a7794.dtsi and its
>> PCI bindings, there are PCI controller subnodes which add extra
>> information for PCI devices
Hi Marek,
On 20 August 2018 at 14:15, Marek Vasut wrote:
>
> On 08/20/2018 09:29 PM, Simon Glass wrote:
> [...]
>
> > So what is the conclusion here ? Patch the design document and apply
> > this patch as is ?
> >
>
> I think we should see Simon's comments before we move
On 08/22/2018 04:14 AM, Bin Meng wrote:
[...]
I said in the previous discussion I am willing to update the
documentation to match the implementation, but that's about it.
> So far almost all PCI device drivers in U-Boot supports both
> scenarios, except PCI UART which
Hi Marek,
On Tue, Aug 21, 2018 at 6:28 PM, Marek Vasut wrote:
> On 08/21/2018 09:16 AM, Bin Meng wrote:
>> Hi Marek,
>>
>> On Tue, Aug 21, 2018 at 1:43 PM, Marek Vasut wrote:
>>> On 08/21/2018 06:56 AM, Bin Meng wrote:
>>> [...]
The proposal I made is:
* Keep
On 08/21/2018 08:29 PM, Simon Glass wrote:
> Hi Marek,
>
> On 21 August 2018 at 12:26, Marek Vasut wrote:
>>
>> On 08/21/2018 07:32 PM, Simon Glass wrote:
>>> Hi Bin,
>>>
>>> On 20 August 2018 at 21:46, Bin Meng wrote:
Hi Simon,
On Tue, Aug 21, 2018 at 3:29 AM, Simon Glass
Hi Marek,
On 21 August 2018 at 12:26, Marek Vasut wrote:
>
> On 08/21/2018 07:32 PM, Simon Glass wrote:
> > Hi Bin,
> >
> > On 20 August 2018 at 21:46, Bin Meng wrote:
> >> Hi Simon,
> >>
> >> On Tue, Aug 21, 2018 at 3:29 AM, Simon Glass wrote:
> >>> Hi Marek,
> >>>
> >>> On 20 August 2018 at
On 08/21/2018 07:32 PM, Simon Glass wrote:
> Hi Bin,
>
> On 20 August 2018 at 21:46, Bin Meng wrote:
>> Hi Simon,
>>
>> On Tue, Aug 21, 2018 at 3:29 AM, Simon Glass wrote:
>>> Hi Marek,
>>>
>>> On 20 August 2018 at 12:42, Marek Vasut wrote:
On 08/20/2018 06:57 PM, Simon Glass wrote:
Hi Bin,
On 20 August 2018 at 21:46, Bin Meng wrote:
> Hi Simon,
>
> On Tue, Aug 21, 2018 at 3:29 AM, Simon Glass wrote:
>> Hi Marek,
>>
>> On 20 August 2018 at 12:42, Marek Vasut wrote:
>>>
>>> On 08/20/2018 06:57 PM, Simon Glass wrote:
>>> > Hi Bin,
>>> >
>>> > On 16 August 2018 at 19:51, Bin
On 08/21/2018 09:16 AM, Bin Meng wrote:
> Hi Marek,
>
> On Tue, Aug 21, 2018 at 1:43 PM, Marek Vasut wrote:
>> On 08/21/2018 06:56 AM, Bin Meng wrote:
>> [...]
>>> The proposal I made is:
>>>
>>> * Keep pci-uclass driver's post_bind() and child_post_bind() only for
>>> Sandbox
Hi Marek,
On Tue, Aug 21, 2018 at 1:43 PM, Marek Vasut wrote:
> On 08/21/2018 06:56 AM, Bin Meng wrote:
> [...]
>> The proposal I made is:
>>
>> * Keep pci-uclass driver's post_bind() and child_post_bind() only for
>> Sandbox configuration
>> * Keep the call to
On 08/21/2018 06:56 AM, Bin Meng wrote:
[...]
> The proposal I made is:
>
> * Keep pci-uclass driver's post_bind() and child_post_bind() only for
> Sandbox configuration
> * Keep the call to pci_bus_find_devfn() in pci_bind_bus_devices() only
> for Sandbox configuration
Hi Marek,
On Tue, Aug 21, 2018 at 12:30 PM, Marek Vasut wrote:
> On 08/21/2018 06:15 AM, Bin Meng wrote:
> [...]
>
>>> From what I understand, Marek and Bin are discussing whether a
>>> compatible string is needed to bind a driver.
>>>
>>> Generally it is. But with PCI and USB we
On 08/21/2018 06:15 AM, Bin Meng wrote:
[...]
>> From what I understand, Marek and Bin are discussing whether a
>> compatible string is needed to bind a driver.
>>
>> Generally it is. But with PCI and USB we have a search mechanism which
>> can be used instead.
>>
>>
Hi Marek,
On Tue, Aug 21, 2018 at 12:02 PM, Marek Vasut wrote:
> On 08/21/2018 05:46 AM, Bin Meng wrote:
>> Hi Simon,
>>
>> On Tue, Aug 21, 2018 at 3:29 AM, Simon Glass wrote:
>>> Hi Marek,
>>>
>>> On 20 August 2018 at 12:42, Marek Vasut wrote:
On 08/20/2018 06:57 PM, Simon Glass
On 08/21/2018 05:46 AM, Bin Meng wrote:
> Hi Simon,
>
> On Tue, Aug 21, 2018 at 3:29 AM, Simon Glass wrote:
>> Hi Marek,
>>
>> On 20 August 2018 at 12:42, Marek Vasut wrote:
>>>
>>> On 08/20/2018 06:57 PM, Simon Glass wrote:
Hi Bin,
On 16 August 2018 at 19:51, Bin Meng wrote:
Hi Simon,
On Tue, Aug 21, 2018 at 3:29 AM, Simon Glass wrote:
> Hi Marek,
>
> On 20 August 2018 at 12:42, Marek Vasut wrote:
>>
>> On 08/20/2018 06:57 PM, Simon Glass wrote:
>> > Hi Bin,
>> >
>> > On 16 August 2018 at 19:51, Bin Meng wrote:
>> >> Hi Marek,
>> >>
>> >> On Thu, Aug 16, 2018 at
On 08/20/2018 09:29 PM, Simon Glass wrote:
[...]
> So what is the conclusion here ? Patch the design document and apply
> this patch as is ?
>
I think we should see Simon's comments before we move forward. The
proposal I made before should come in a series, not just
Hi Marek,
On 20 August 2018 at 12:42, Marek Vasut wrote:
>
> On 08/20/2018 06:57 PM, Simon Glass wrote:
> > Hi Bin,
> >
> > On 16 August 2018 at 19:51, Bin Meng wrote:
> >> Hi Marek,
> >>
> >> On Thu, Aug 16, 2018 at 7:47 PM, Marek Vasut wrote:
> >>> On 08/15/2018 01:25 PM, Tom Rini wrote:
>
On 08/20/2018 06:57 PM, Simon Glass wrote:
> Hi Bin,
>
> On 16 August 2018 at 19:51, Bin Meng wrote:
>> Hi Marek,
>>
>> On Thu, Aug 16, 2018 at 7:47 PM, Marek Vasut wrote:
>>> On 08/15/2018 01:25 PM, Tom Rini wrote:
On Wed, Aug 15, 2018 at 06:19:25PM +0800, Bin Meng wrote:
> Hi Marek,
Hi Bin,
On 16 August 2018 at 19:51, Bin Meng wrote:
> Hi Marek,
>
> On Thu, Aug 16, 2018 at 7:47 PM, Marek Vasut wrote:
>> On 08/15/2018 01:25 PM, Tom Rini wrote:
>>> On Wed, Aug 15, 2018 at 06:19:25PM +0800, Bin Meng wrote:
Hi Marek,
On Wed, Aug 15, 2018 at 5:22 PM, Marek Vasut
On 08/20/2018 09:18 AM, Bin Meng wrote:
> Hi Marek,
>
> On Fri, Aug 17, 2018 at 6:27 PM, Marek Vasut wrote:
>> On 08/17/2018 03:51 AM, Bin Meng wrote:
>>> Hi Marek,
>>>
>>> On Thu, Aug 16, 2018 at 7:47 PM, Marek Vasut wrote:
On 08/15/2018 01:25 PM, Tom Rini wrote:
> On Wed, Aug 15,
Hi Marek,
On Fri, Aug 17, 2018 at 6:27 PM, Marek Vasut wrote:
> On 08/17/2018 03:51 AM, Bin Meng wrote:
>> Hi Marek,
>>
>> On Thu, Aug 16, 2018 at 7:47 PM, Marek Vasut wrote:
>>> On 08/15/2018 01:25 PM, Tom Rini wrote:
On Wed, Aug 15, 2018 at 06:19:25PM +0800, Bin Meng wrote:
> Hi
On 08/17/2018 03:51 AM, Bin Meng wrote:
> Hi Marek,
>
> On Thu, Aug 16, 2018 at 7:47 PM, Marek Vasut wrote:
>> On 08/15/2018 01:25 PM, Tom Rini wrote:
>>> On Wed, Aug 15, 2018 at 06:19:25PM +0800, Bin Meng wrote:
Hi Marek,
On Wed, Aug 15, 2018 at 5:22 PM, Marek Vasut wrote:
>
Hi Marek,
On Thu, Aug 16, 2018 at 7:47 PM, Marek Vasut wrote:
> On 08/15/2018 01:25 PM, Tom Rini wrote:
>> On Wed, Aug 15, 2018 at 06:19:25PM +0800, Bin Meng wrote:
>>> Hi Marek,
>>>
>>> On Wed, Aug 15, 2018 at 5:22 PM, Marek Vasut wrote:
On 08/14/2018 11:40 AM, Bin Meng wrote:
> Hi
On 08/15/2018 01:25 PM, Tom Rini wrote:
> On Wed, Aug 15, 2018 at 06:19:25PM +0800, Bin Meng wrote:
>> Hi Marek,
>>
>> On Wed, Aug 15, 2018 at 5:22 PM, Marek Vasut wrote:
>>> On 08/14/2018 11:40 AM, Bin Meng wrote:
Hi Marek,
On Tue, Aug 14, 2018 at 4:55 PM, Marek Vasut wrote:
On 08/15/2018 12:19 PM, Bin Meng wrote:
> Hi Marek,
>
> On Wed, Aug 15, 2018 at 5:22 PM, Marek Vasut wrote:
>> On 08/14/2018 11:40 AM, Bin Meng wrote:
>>> Hi Marek,
>>>
>>> On Tue, Aug 14, 2018 at 4:55 PM, Marek Vasut wrote:
On 08/14/2018 03:46 AM, Bin Meng wrote:
> Hi Marek,
>
On Wed, Aug 15, 2018 at 06:19:25PM +0800, Bin Meng wrote:
> Hi Marek,
>
> On Wed, Aug 15, 2018 at 5:22 PM, Marek Vasut wrote:
> > On 08/14/2018 11:40 AM, Bin Meng wrote:
> >> Hi Marek,
> >>
> >> On Tue, Aug 14, 2018 at 4:55 PM, Marek Vasut wrote:
> >>> On 08/14/2018 03:46 AM, Bin Meng wrote:
>
Hi Marek,
On Wed, Aug 15, 2018 at 5:22 PM, Marek Vasut wrote:
> On 08/14/2018 11:40 AM, Bin Meng wrote:
>> Hi Marek,
>>
>> On Tue, Aug 14, 2018 at 4:55 PM, Marek Vasut wrote:
>>> On 08/14/2018 03:46 AM, Bin Meng wrote:
Hi Marek,
On Mon, Aug 13, 2018 at 9:46 PM, Marek Vasut
On 08/14/2018 11:40 AM, Bin Meng wrote:
> Hi Marek,
>
> On Tue, Aug 14, 2018 at 4:55 PM, Marek Vasut wrote:
>> On 08/14/2018 03:46 AM, Bin Meng wrote:
>>> Hi Marek,
>>>
>>> On Mon, Aug 13, 2018 at 9:46 PM, Marek Vasut wrote:
On 08/13/2018 04:24 AM, Bin Meng wrote:
> Hi Marek,
>
On 08/14/2018 11:35 AM, Bin Meng wrote:
[...]
>> I think knowing where Linux does this
>> would be instructive to figure out where we need to have some additional
>> logic added OR we can make some cost/benefit analysis to see if it makes
>> more sense overall to add compatibles
On Tue, Aug 14, 2018 at 10:34:23AM +0800, Bin Meng wrote:
> Hi Tom,
>
> On Tue, Aug 14, 2018 at 1:16 AM, Tom Rini wrote:
> > On Mon, Aug 13, 2018 at 06:07:14PM +0200, Marek Vasut wrote:
> >> On 08/13/2018 03:39 PM, Tom Rini wrote:
> >> [...]
> >>
> >> Next step is to upstream the DT
> >>
Hi Marek,
On Tue, Aug 14, 2018 at 4:55 PM, Marek Vasut wrote:
> On 08/14/2018 03:46 AM, Bin Meng wrote:
>> Hi Marek,
>>
>> On Mon, Aug 13, 2018 at 9:46 PM, Marek Vasut wrote:
>>> On 08/13/2018 04:24 AM, Bin Meng wrote:
Hi Marek,
On Fri, Aug 10, 2018 at 8:38 PM, Marek Vasut
Hi Marek,
On Tue, Aug 14, 2018 at 4:54 PM, Marek Vasut wrote:
> On 08/14/2018 04:34 AM, Bin Meng wrote:
>> Hi Tom,
>>
>> On Tue, Aug 14, 2018 at 1:16 AM, Tom Rini wrote:
>>> On Mon, Aug 13, 2018 at 06:07:14PM +0200, Marek Vasut wrote:
On 08/13/2018 03:39 PM, Tom Rini wrote:
[...]
On 08/14/2018 04:34 AM, Bin Meng wrote:
> Hi Tom,
>
> On Tue, Aug 14, 2018 at 1:16 AM, Tom Rini wrote:
>> On Mon, Aug 13, 2018 at 06:07:14PM +0200, Marek Vasut wrote:
>>> On 08/13/2018 03:39 PM, Tom Rini wrote:
>>> [...]
>>>
>>> Next step is to upstream the DT
>>> changes to Linux
On 08/14/2018 03:46 AM, Bin Meng wrote:
> Hi Marek,
>
> On Mon, Aug 13, 2018 at 9:46 PM, Marek Vasut wrote:
>> On 08/13/2018 04:24 AM, Bin Meng wrote:
>>> Hi Marek,
>>>
>>> On Fri, Aug 10, 2018 at 8:38 PM, Marek Vasut wrote:
On 08/10/2018 02:01 PM, Tom Rini wrote:
> On Wed, Aug 08,
Hi Tom,
On Tue, Aug 14, 2018 at 1:16 AM, Tom Rini wrote:
> On Mon, Aug 13, 2018 at 06:07:14PM +0200, Marek Vasut wrote:
>> On 08/13/2018 03:39 PM, Tom Rini wrote:
>> [...]
>>
>> Next step is to upstream the DT
>> changes to Linux kernel, then sync the changes to U-Boot to satisfy
>>
Hi Marek,
On Mon, Aug 13, 2018 at 9:46 PM, Marek Vasut wrote:
> On 08/13/2018 04:24 AM, Bin Meng wrote:
>> Hi Marek,
>>
>> On Fri, Aug 10, 2018 at 8:38 PM, Marek Vasut wrote:
>>> On 08/10/2018 02:01 PM, Tom Rini wrote:
On Wed, Aug 08, 2018 at 09:37:25PM +0200, Marek Vasut wrote:
> On
On Mon, Aug 13, 2018 at 06:07:14PM +0200, Marek Vasut wrote:
> On 08/13/2018 03:39 PM, Tom Rini wrote:
> [...]
>
> Next step is to upstream the DT
> changes to Linux kernel, then sync the changes to U-Boot to satisfy
> this obsession - using exactly the same DT as Linux.
> >>>
>
On 08/13/2018 03:39 PM, Tom Rini wrote:
[...]
Next step is to upstream the DT
changes to Linux kernel, then sync the changes to U-Boot to satisfy
this obsession - using exactly the same DT as Linux.
>>>
>>> This is not gonna happen.
>>>
>>> Sorry, you're really just wasting my time
On 08/13/2018 04:24 AM, Bin Meng wrote:
> Hi Marek,
>
> On Fri, Aug 10, 2018 at 8:38 PM, Marek Vasut wrote:
>> On 08/10/2018 02:01 PM, Tom Rini wrote:
>>> On Wed, Aug 08, 2018 at 09:37:25PM +0200, Marek Vasut wrote:
On 08/08/2018 05:32 PM, Bin Meng wrote:
> Hi Marek,
>
> On Wed,
On 08/13/2018 04:07 AM, Bin Meng wrote:
[...]
> Sorry this is terribly wrong. Imagine someone
> writes another OS, and all he has is the device tree spec. He follows
> the spec and writes some codes to parse a valid DT, and it's done. How
> his OS makes use of the DT is his
On Mon, Aug 13, 2018 at 10:07:03AM +0800, Bin Meng wrote:
> Hi Marek,
>
> On Fri, Aug 10, 2018 at 6:32 PM, Marek Vasut wrote:
> > On 08/10/2018 05:42 AM, Bin Meng wrote:
> >> Hi Marek,
> >>
> >> On Thu, Aug 9, 2018 at 6:25 PM, Marek Vasut wrote:
> >>> On 08/09/2018 11:41 AM, Bin Meng wrote:
>
Hi Marek,
On Fri, Aug 10, 2018 at 8:38 PM, Marek Vasut wrote:
> On 08/10/2018 02:01 PM, Tom Rini wrote:
>> On Wed, Aug 08, 2018 at 09:37:25PM +0200, Marek Vasut wrote:
>>> On 08/08/2018 05:32 PM, Bin Meng wrote:
Hi Marek,
On Wed, Aug 8, 2018 at 10:33 PM, Marek Vasut wrote:
>
Hi Marek,
On Fri, Aug 10, 2018 at 6:32 PM, Marek Vasut wrote:
> On 08/10/2018 05:42 AM, Bin Meng wrote:
>> Hi Marek,
>>
>> On Thu, Aug 9, 2018 at 6:25 PM, Marek Vasut wrote:
>>> On 08/09/2018 11:41 AM, Bin Meng wrote:
>>>
>>> [...]
>>>
Sorry this is a hack to current U-Boot
On 08/10/2018 02:01 PM, Tom Rini wrote:
> On Wed, Aug 08, 2018 at 09:37:25PM +0200, Marek Vasut wrote:
>> On 08/08/2018 05:32 PM, Bin Meng wrote:
>>> Hi Marek,
>>>
>>> On Wed, Aug 8, 2018 at 10:33 PM, Marek Vasut wrote:
On 08/08/2018 03:39 PM, Bin Meng wrote:
> Hi Marek,
>
> On
On Wed, Aug 08, 2018 at 09:37:25PM +0200, Marek Vasut wrote:
> On 08/08/2018 05:32 PM, Bin Meng wrote:
> > Hi Marek,
> >
> > On Wed, Aug 8, 2018 at 10:33 PM, Marek Vasut wrote:
> >> On 08/08/2018 03:39 PM, Bin Meng wrote:
> >>> Hi Marek,
> >>>
> >>> On Wed, Aug 8, 2018 at 9:24 PM, Marek Vasut
On 08/10/2018 05:42 AM, Bin Meng wrote:
> Hi Marek,
>
> On Thu, Aug 9, 2018 at 6:25 PM, Marek Vasut wrote:
>> On 08/09/2018 11:41 AM, Bin Meng wrote:
>>
>> [...]
>>
>>> Sorry this is a hack to current U-Boot implementation, not fix.
>>
>> I am waiting for a better solution or
Hi Marek,
On Thu, Aug 9, 2018 at 6:25 PM, Marek Vasut wrote:
> On 08/09/2018 11:41 AM, Bin Meng wrote:
>
> [...]
>
>> Sorry this is a hack to current U-Boot implementation, not fix.
>
> I am waiting for a better solution or suggestion ...
>
>> The fix should be adding
On 08/09/2018 11:41 AM, Bin Meng wrote:
[...]
> Sorry this is a hack to current U-Boot implementation, not fix.
I am waiting for a better solution or suggestion ...
> The fix should be adding "ehci-pci" compatible string in the r8a7794.dtsi.
Wrong. The DT is
Hi Marek,
On Thu, Aug 9, 2018 at 3:54 PM, Marek Vasut wrote:
> On 08/09/2018 04:37 AM, Bin Meng wrote:
>> Hi Marek,
>>
>> On Thu, Aug 9, 2018 at 8:36 AM, Marek Vasut wrote:
>>> On 08/09/2018 01:24 AM, Bin Meng wrote:
Hi Marek,
On Thu, Aug 9, 2018 at 3:37 AM, Marek Vasut wrote:
On 08/09/2018 04:37 AM, Bin Meng wrote:
> Hi Marek,
>
> On Thu, Aug 9, 2018 at 8:36 AM, Marek Vasut wrote:
>> On 08/09/2018 01:24 AM, Bin Meng wrote:
>>> Hi Marek,
>>>
>>> On Thu, Aug 9, 2018 at 3:37 AM, Marek Vasut wrote:
On 08/08/2018 05:32 PM, Bin Meng wrote:
> Hi Marek,
>
>
Hi Marek,
On Thu, Aug 9, 2018 at 8:36 AM, Marek Vasut wrote:
> On 08/09/2018 01:24 AM, Bin Meng wrote:
>> Hi Marek,
>>
>> On Thu, Aug 9, 2018 at 3:37 AM, Marek Vasut wrote:
>>> On 08/08/2018 05:32 PM, Bin Meng wrote:
Hi Marek,
On Wed, Aug 8, 2018 at 10:33 PM, Marek Vasut wrote:
On 08/09/2018 01:24 AM, Bin Meng wrote:
> Hi Marek,
>
> On Thu, Aug 9, 2018 at 3:37 AM, Marek Vasut wrote:
>> On 08/08/2018 05:32 PM, Bin Meng wrote:
>>> Hi Marek,
>>>
>>> On Wed, Aug 8, 2018 at 10:33 PM, Marek Vasut wrote:
On 08/08/2018 03:39 PM, Bin Meng wrote:
> Hi Marek,
>
Hi Marek,
On Thu, Aug 9, 2018 at 3:37 AM, Marek Vasut wrote:
> On 08/08/2018 05:32 PM, Bin Meng wrote:
>> Hi Marek,
>>
>> On Wed, Aug 8, 2018 at 10:33 PM, Marek Vasut wrote:
>>> On 08/08/2018 03:39 PM, Bin Meng wrote:
Hi Marek,
On Wed, Aug 8, 2018 at 9:24 PM, Marek Vasut wrote:
On 08/08/2018 05:32 PM, Bin Meng wrote:
> Hi Marek,
>
> On Wed, Aug 8, 2018 at 10:33 PM, Marek Vasut wrote:
>> On 08/08/2018 03:39 PM, Bin Meng wrote:
>>> Hi Marek,
>>>
>>> On Wed, Aug 8, 2018 at 9:24 PM, Marek Vasut wrote:
On 08/08/2018 03:14 PM, Bin Meng wrote:
> Hi Marek,
>
Hi Marek,
On Wed, Aug 8, 2018 at 10:33 PM, Marek Vasut wrote:
> On 08/08/2018 03:39 PM, Bin Meng wrote:
>> Hi Marek,
>>
>> On Wed, Aug 8, 2018 at 9:24 PM, Marek Vasut wrote:
>>> On 08/08/2018 03:14 PM, Bin Meng wrote:
Hi Marek,
On Wed, Aug 8, 2018 at 9:03 PM, Marek Vasut wrote:
On 08/08/2018 03:39 PM, Bin Meng wrote:
> Hi Marek,
>
> On Wed, Aug 8, 2018 at 9:24 PM, Marek Vasut wrote:
>> On 08/08/2018 03:14 PM, Bin Meng wrote:
>>> Hi Marek,
>>>
>>> On Wed, Aug 8, 2018 at 9:03 PM, Marek Vasut wrote:
The PCI controller can have DT subnodes describing extra properties
Hi Marek,
On Wed, Aug 8, 2018 at 9:24 PM, Marek Vasut wrote:
> On 08/08/2018 03:14 PM, Bin Meng wrote:
>> Hi Marek,
>>
>> On Wed, Aug 8, 2018 at 9:03 PM, Marek Vasut wrote:
>>> The PCI controller can have DT subnodes describing extra properties
>>> of particular PCI devices, ie. a PHY attached
On 08/08/2018 03:14 PM, Bin Meng wrote:
> Hi Marek,
>
> On Wed, Aug 8, 2018 at 9:03 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
Hi Marek,
On Wed, Aug 8, 2018 at 9:03 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
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.
73 matches
Mail list logo