>
> On Tue, 2015-06-02 at 10:12 -0500, "Stéphane Viau" wrote:
>> Hi Ivan,
>>
>> > Hi Stephane,
>> >
>> > On Mon, 2015-06-01 at 16:28 -0400, Stephane Viau wrote:
>> > > Some targets (eg: msm8994) use the pinctrl framework to configure
>> > > interface pins. This change adds support for initializati
On Tue, 2015-06-02 at 10:12 -0500, "Stéphane Viau" wrote:
> Hi Ivan,
>
> > Hi Stephane,
> >
> > On Mon, 2015-06-01 at 16:28 -0400, Stephane Viau wrote:
> > > Some targets (eg: msm8994) use the pinctrl framework to configure
> > > interface pins. This change adds support for initialization and
>
Hi Ivan,
>
> Hi Stephane,
>
> On Mon, 2015-06-01 at 16:28 -0400, Stephane Viau wrote:
>> Some targets (eg: msm8994) use the pinctrl framework to configure
>> interface pins. This change adds support for initialization and
>> pinctrl active/sleep state control for the HDMI driver.
>>
>> Signed-off-
Hi Stephane,
On Mon, 2015-06-01 at 16:28 -0400, Stephane Viau wrote:
> Some targets (eg: msm8994) use the pinctrl framework to configure
> interface pins. This change adds support for initialization and
> pinctrl active/sleep state control for the HDMI driver.
>
> Signed-off-by: Stephane Viau
Some targets (eg: msm8994) use the pinctrl framework to configure
interface pins. This change adds support for initialization and
pinctrl active/sleep state control for the HDMI driver.
Signed-off-by: Stephane Viau
---
v2:
- Add devicetree binding documentation for pinctrl property [Ivan]
- Use
5 matches
Mail list logo