From: Chanwoo Choi <cw00.choi@samsung.com>
To: Roger Quadros <rogerq@ti.com>, linux-kernel@vger.kernel.org
Cc: k.kozlowski@samsung.com, ckeepax@opensource.wolfsonmicro.com,
gregkh@linuxfoundation.org, ramakrishna.pallala@intel.com,
patches@opensource.wolfsonmicro.com, myungjoo.ham@samsung.com
Subject: Re: [PATCH 2/2] extcon: Add the support of EXTCON_CHG_USB when SDP port is attached or detached
Date: Tue, 06 Oct 2015 21:28:59 +0900 [thread overview]
Message-ID: <5613BE8B.3030403@samsung.com> (raw)
In-Reply-To: <5613BD10.3070300@ti.com>
Roger,
On 2015년 10월 06일 21:22, Roger Quadros wrote:
> Chanwoo,
>
> On 06/10/15 15:12, Chanwoo Choi wrote:
>> Roger,
>>
>> On 2015년 10월 06일 20:49, Roger Quadros wrote:
>>> Hi,
>>>
>>> On 06/10/15 14:21, Chanwoo Choi wrote:
>>>> The SDP (Standard Downstream Port) is one of various USB Charging ports. The SDP
>>>> supports both the data transmission and the charging through USB connector at
>>>> the same time. So, the EXTCON framework defines two connector type for USB SDP
>>>> connector as following:
>>>> - EXTCON_USB means the USB cable for data transmission.
>>>> - EXTCON_CHG_USB means the USB charger cable for battery charging.
>>>>
>>>> This patch add the support of EXTCON_CHG_USB when USB SDP is attached or
>>>> detached.
>>>
>>> I didn't understand why this change is needed. SDP, EXTCON_USB and EXTCON_CHG_USB
>>> are the same thing. no?
>>
>> As you knew, SDP support both data transmission and charging
>> through one port at the same time. Also, On patch1 of this patch-set,
>> I add the prefix to clarify both attribute and meaning of external connector as following:
>> - EXTCON_CHG_* mean the charger connector.
>>
>> So, there are three possible naming approach for USB SDP.
>>
>> Approach 1.
>> - EXTCON_USB /* SDP for both data transmission and charging */
>>
>> Approach 2.
>> - EXTCON_USB /* SDP for data transmission */
>> - EXTCON_CHG_USB /* SDP for charging */
>
> This only adds confusion. There is only one cable that will always do both jobs
> so no point in using 2 names for it.
OK. I'll drop it.
>
>>
>> Approach 3.
>> - EXTCON_CHG_USB /* SDP for both data transmission and charging */
>>
>> It is not fixed about name. I want to discuss what is proper name for USB SDP.
>
> I do not have any preference over 1 or 3.
I'll drop this patch. Also, I'll use only EXTCON_USB and delete the EXTCON_CHG_USB
from patch1 on next version.
Thanks,
Chanwoo Choi
prev parent reply other threads:[~2015-10-06 12:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 11:21 [PATCH v2 0/2] extcon: Modify the name of external connector Chanwoo Choi
2015-10-06 11:21 ` [PATCH 1/2] extcon: Modify the id and " Chanwoo Choi
2015-10-06 11:42 ` Pallala, Ramakrishna
2015-10-06 11:51 ` Chanwoo Choi
2015-10-06 11:57 ` Pallala, Ramakrishna
2015-10-06 11:21 ` [PATCH 2/2] extcon: Add the support of EXTCON_CHG_USB when SDP port is attached or detached Chanwoo Choi
2015-10-06 11:49 ` Roger Quadros
2015-10-06 12:12 ` Chanwoo Choi
2015-10-06 12:22 ` Roger Quadros
2015-10-06 12:28 ` 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=5613BE8B.3030403@samsung.com \
--to=cw00.choi@samsung.com \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=gregkh@linuxfoundation.org \
--cc=k.kozlowski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=ramakrishna.pallala@intel.com \
--cc=rogerq@ti.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).