Hi Stephen,
On 27 April 2016 at 11:16, Stephen Warren wrote:
> On 04/27/2016 10:58 AM, Simon Glass wrote:
>>
>> Hi Stephen,
>>
>> On 27 April 2016 at 10:24, Stephen Warren wrote:
>>>
>>> On 04/27/2016 09:12 AM, Simon Glass wrote:
Hi Stephen,
On 19 April 2016 at 14:59, St
On 04/27/2016 10:58 AM, Simon Glass wrote:
Hi Stephen,
On 27 April 2016 at 10:24, Stephen Warren wrote:
On 04/27/2016 09:12 AM, Simon Glass wrote:
Hi Stephen,
On 19 April 2016 at 14:59, Stephen Warren wrote:
From: Stephen Warren
Remove funcmux calls from the Tegra I2C driver. Knowledge
Hi Stephen,
On 27 April 2016 at 10:24, Stephen Warren wrote:
> On 04/27/2016 09:12 AM, Simon Glass wrote:
>>
>> Hi Stephen,
>>
>> On 19 April 2016 at 14:59, Stephen Warren wrote:
>>>
>>> From: Stephen Warren
>>>
>>> Remove funcmux calls from the Tegra I2C driver. Knowledge of pinmux
>>> setup m
On 04/27/2016 09:12 AM, Simon Glass wrote:
Hi Stephen,
On 19 April 2016 at 14:59, Stephen Warren wrote:
From: Stephen Warren
Remove funcmux calls from the Tegra I2C driver. Knowledge of pinmux
setup must come from either board files or DT; it should not be embedded
into board-agnostic driver
Hi Stephen,
On 19 April 2016 at 14:59, Stephen Warren wrote:
> From: Stephen Warren
>
> Remove funcmux calls from the Tegra I2C driver. Knowledge of pinmux
> setup must come from either board files or DT; it should not be embedded
> into board-agnostic driver code. The DT pinmux bindings do not
From: Stephen Warren
Remove funcmux calls from the Tegra I2C driver. Knowledge of pinmux
setup must come from either board files or DT; it should not be embedded
into board-agnostic driver code. The DT pinmux bindings do not allow
drivers to derive funcmux-style information, since the DT bindings
6 matches
Mail list logo