From: Chanwoo Choi <cw00.choi@samsung.com>
To: myungjoo.ham@samsung.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "zyw@rock-chips.com" <zyw@rock-chips.com>,
"groeck@chromium.org" <groeck@chromium.org>,
"cwchoi00@gmail.com" <cwchoi00@gmail.com>
Subject: Re: [PATCH 1/6] extcon: Add the extcon_type to group each connector into five category
Date: Wed, 27 Jul 2016 14:35:57 +0900 [thread overview]
Message-ID: <5798483D.2090904@samsung.com> (raw)
In-Reply-To: <757384616.167210.1469593665960.JavaMail.weblogic@ep1ml101a>
Hi Myungjoo,
On 2016년 07월 27일 13:27, MyungJoo Ham wrote:
>> This patch adds the new extcon type to group the each connecotr
>> into following five category. This type would be used to handle
>> the connectors as a group unit instead of a connector unit.
>> - EXTCON_TYPE_USB : USB connector
>> - EXTCON_TYPE_CHG : Charger connector
>> - EXTCON_TYPE_JACK : Jack connector
>
> "Jack" seems to be an internal jargon that many people won't recognize.
> It's, in fact, 3.5-pi, isn't it?
You're right. But, the ALSA framework already used the 'jack' word
for headphone/headset/microphone for a long time. (sound/soc/soc-jack.c)
So, To prevent the confusion, I use the 'jack' word.
>
> Anyway, this is already being used as an enum with drivers,
> I'd suggest to add a comment in extcon.h stating that
> "Jack connector" is usually the 3.5-pi earbud connector.
Additionally, jack means the the LINE_IN/OUT, VIDEO_IN/OUT,
SPDIF_IN/OUT in the extcon.
>
> Anyway, I like the direction of this patch.
Thanks.
>
>
> Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
Regards,
Chanwoo Choi
>
> Cheers,
> MyungJoo
>
>> --- a/include/linux/extcon.h
>> +++ b/include/linux/extcon.h
>> @@ -29,6 +29,15 @@
>> #include <linux/device.h>
>>
>> /*
>> + * Define the type of supported external connectors
>> + */
>> +#define EXTCON_TYPE_USB BIT(0) /* USB connector */
>> +#define EXTCON_TYPE_CHG BIT(1) /* Charger connector */
>> +#define EXTCON_TYPE_JACK BIT(2) /* Jack connector */
> + /* Usually, this is a 3.5-pi earbud conector */
>> +#define EXTCON_TYPE_DISP BIT(3) /* Display connector */
>> +#define EXTCON_TYPE_MISC BIT(4) /* Miscellaneous connector */
>> +
>> +/*
>> * Define the unique id of supported external connectors
>> */
>> #define EXTCON_NONE 0
>> --
>> 1.9.1
>>
prev parent reply other threads:[~2016-07-27 5:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 12:09 [PATCH 0/6] extcon: Add the support for extcon type and property Chanwoo Choi
2016-07-26 12:09 ` [PATCH 1/6] extcon: Add the extcon_type to group each connector into five category Chanwoo Choi
2016-07-26 12:09 ` [PATCH 2/6] extcon: Add the support for extcon property according to extcon type Chanwoo Choi
2016-07-26 22:06 ` Guenter Roeck
[not found] ` <CAGTfZH2rPyhSiXU=62RKTaE40fok5iiWM+G=+V147gGq8wv_Bw@mail.gmail.com>
2016-07-27 1:15 ` Chris Zhong
2016-07-27 1:44 ` Guenter Roeck
2016-07-27 2:09 ` Chris Zhong
2016-07-27 3:42 ` Chanwoo Choi
2016-07-27 3:51 ` Guenter Roeck
2016-07-27 3:57 ` Chanwoo Choi
2016-07-27 4:30 ` Chris Zhong
2016-07-27 17:24 ` Guenter Roeck
2016-07-29 7:02 ` Chanwoo Choi
2016-07-26 12:09 ` [PATCH 3/6] extcon: Add the support for the capability of each property Chanwoo Choi
2016-07-26 12:09 ` [PATCH 4/6] extcon: Rename the extcon_set/get_state() to maintain the function naming pattern Chanwoo Choi
2016-07-26 12:09 ` [PATCH 5/6] extcon: Add the synchronization extcon APIs to support the notification Chanwoo Choi
2016-07-27 7:30 ` Chris Zhong
2016-07-27 7:41 ` Chanwoo Choi
2016-07-26 12:09 ` [PATCH 6/6] extcon: Add EXTCON_DISP_DP and the property for USB Type-C Chanwoo Choi
[not found] ` <CGME20160726120955epcas1p1379233158fe6612133799eb2255a5247@epcas1p1.samsung.com>
2016-07-27 4:27 ` [PATCH 1/6] extcon: Add the extcon_type to group each connector into five category MyungJoo Ham
2016-07-27 5:35 ` Chanwoo Choi [this message]
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=5798483D.2090904@samsung.com \
--to=cw00.choi@samsung.com \
--cc=cwchoi00@gmail.com \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=zyw@rock-chips.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