Hi Stephen,
On 11 May 2016 at 10:52, Stephen Warren wrote:
> On 05/10/2016 08:25 PM, Simon Glass wrote:
>>
>> Hi Stephen,
>>
>> On 4 May 2016 at 12:42, Stephen Warren wrote:
>>>
>>> On 05/01/2016 01:27 PM, Simon Glass wrote:
Hi
On 05/10/2016 08:25 PM, Simon Glass wrote:
Hi Stephen,
On 4 May 2016 at 12:42, Stephen Warren wrote:
On 05/01/2016 01:27 PM, Simon Glass wrote:
Hi Stephen,
On 28 April 2016 at 17:08, Stephen Warren wrote:
From: Stephen Warren
Hi Stephen,
On 4 May 2016 at 12:42, Stephen Warren wrote:
> On 05/01/2016 01:27 PM, Simon Glass wrote:
>>
>> Hi Stephen,
>>
>> On 28 April 2016 at 17:08, Stephen Warren wrote:
>>>
>>> From: Stephen Warren
>>>
>>> This will allow
On 05/04/2016 12:42 PM, Stephen Warren wrote:
On 05/01/2016 01:27 PM, Simon Glass wrote:
Hi Stephen,
On 28 April 2016 at 17:08, Stephen Warren wrote:
From: Stephen Warren
This will allow a driver's bind function to use the driver data. One
example
On 05/01/2016 01:27 PM, Simon Glass wrote:
Hi Stephen,
On 28 April 2016 at 17:08, Stephen Warren wrote:
From: Stephen Warren
This will allow a driver's bind function to use the driver data. One
example is the Tegra186 GPIO driver, which
Hi Stephen,
On 28 April 2016 at 17:08, Stephen Warren wrote:
> From: Stephen Warren
>
> This will allow a driver's bind function to use the driver data. One
> example is the Tegra186 GPIO driver, which instantiates child devices
> for each of its GPIO
From: Stephen Warren
This will allow a driver's bind function to use the driver data. One
example is the Tegra186 GPIO driver, which instantiates child devices
for each of its GPIO ports, yet supports two different HW instances each
with a different set of ports, and
7 matches
Mail list logo