Re: [alsa-devel] [PATCH v2 2/2] mfd: arizona: Update DT binding to support INn_MODE init_data

[Inha Song]

Hi, Charles.
Thanks for your review.

On Wed, 13 Aug 2014 13:18:14 +0100
Charles Keepax <ckeepax@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

> On Wed, Aug 13, 2014 at 08:54:56PM +0900, Inha Song wrote:
> > This patch update DT binding to support INn_MODE init_data. Each
> > input signal path can be configurated either as a Analogue or
> > Digital using the INn_MODE registers.
> > 
> > Signed-off-by: Inha Song <ideal.song@xxxxxxxxxxx>
> > ---
> >  Documentation/devicetree/bindings/mfd/arizona.txt | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt b/Documentation/devicetree/bindings/mfd/arizona.txt
> > index 5c7e723..b8c131e 100644
> > --- a/Documentation/devicetree/bindings/mfd/arizona.txt
> > +++ b/Documentation/devicetree/bindings/mfd/arizona.txt
> > @@ -42,6 +42,14 @@ Optional properties:
> >      the chip default will be used.  If present exactly five values must
> >      be specified.
> >  
> > +  - wlf,inmode : A list of INn_MODE register values, where n is the number
> > +    of input signal. Each input signal path can be configurated either as a
> > +    Analogue or Digital using the INn_MODE registers. If absent, INn_MODE
> > +    registers set to 0 by default. If present, values must be specified less
> > +    than or equal to the number of input singal. If values less than the
> 
> Typo here should be "input signals".

Oops, Thanks! I will fix this.

Best regards,
Inha Song.

> 
> > +    number of input signal, elements that has not been specifed are set to 0
> > +    by default.
> > +
> >    - DCVDD-supply, MICVDD-supply : Power supplies, only need to be specified if
> >      they are being externally supplied. As covered in
> >      Documentation/devicetree/bindings/regulator/regulator.txt
> > -- 
> > 2.0.0.390.gcb682f8
> > 
> 
> Thanks,
> Charles
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/