From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: myungjoo.ham@samsung.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 2/2] extcon: arizona: Update device tree binding for mic detect configurations
Date: Mon, 14 Dec 2015 09:18:50 +0000 [thread overview]
Message-ID: <20151214091850.GS6058@localhost.localdomain> (raw)
In-Reply-To: <566E238E.4050007@samsung.com>
On Mon, Dec 14, 2015 at 11:03:58AM +0900, Chanwoo Choi wrote:
> Hi Charles,
>
> On 2015년 12월 11일 02:08, Charles Keepax wrote:
> > Update the device tree binding documentation to include documentation for
> > the wlf,micd-configs property that is used to specify the configurations
> > for headset polarity detection (CTIA / OTMP).
> >
> > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> > ---
> > Documentation/devicetree/bindings/extcon/extcon-arizona.txt | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/extcon/extcon-arizona.txt b/Documentation/devicetree/bindings/extcon/extcon-arizona.txt
> > index 238e10e..fd9b898 100644
> > --- a/Documentation/devicetree/bindings/extcon/extcon-arizona.txt
> > +++ b/Documentation/devicetree/bindings/extcon/extcon-arizona.txt
> > @@ -37,5 +37,13 @@ Optional properties:
> > milliseconds.
> > - wlf,micd-force-micbias : Force MICBIAS continuously on during microphone
> > detection.
> > + - wlf,micd-configs : Headset polarity configurations (generally used for
> > + detection of CTIA / OMTP headsets), the field can be of variable length
> > + but should always be a multiple of 3 cells long, each three cell group
> > + represents one polarity configuration.
> > + The first cell defines the accessory detection pin, zero will use MICDET1
> > + and all other values will use MICDET2.
> > + The second cell represents the MICBIAS to be used.
> > + The third cell represents the value of the micd-pol-gpio pin.
>
> I think that you better to add the example using the 'wlf,micd-configs'
> to improve the understanding of using this property.
> because the number of 'wlf,micd-configs' value is not fixed.
>
> Also,
> How about do you add the real example for all arizona properties on separate patch?
Yeah that seems sensible I will do a patch to add an example to
this file.
Thanks,
Charles
next prev parent reply other threads:[~2015-12-14 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 17:08 [PATCH 1/2] extcon: arizona: Add device bindings for the micd configurations Charles Keepax
2015-12-14 4:11 ` Chanwoo Choi
[not found] ` <1449767299-29691-1-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2015-12-10 17:08 ` [PATCH 2/2] extcon: arizona: Update device tree binding for mic detect configurations Charles Keepax
[not found] ` <1449767299-29691-2-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2015-12-11 3:44 ` Rob Herring
2015-12-14 2:03 ` Chanwoo Choi
2015-12-14 9:18 ` Charles Keepax [this message]
2016-04-24 15:49 ` [PATCH 1/2] extcon: arizona: Add device bindings for the micd configurations Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151214091850.GS6058@localhost.localdomain \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=patches@opensource.wolfsonmicro.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).