From: Chanwoo Choi <cw00.choi@samsung.com>
To: Guenter Roeck <groeck@google.com>
Cc: Chris Zhong <zyw@rock-chips.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
"cpgs (cpgs@samsung.com)" <cpgs@samsung.com>,
Guenter Roeck <groeck@chromium.org>
Subject: Re: [PATCH] extcon: Introduce EXTCON_PROP_DISP_HPD property
Date: Mon, 12 Sep 2016 11:40:16 +0900 [thread overview]
Message-ID: <57D61590.1030307@samsung.com> (raw)
In-Reply-To: <CABXOdTeSEPhn-MjQcdmMXBzpQnrLLQDe=Oq23ip+YLHpS+9HQw@mail.gmail.com>
Hi Guenter,
On 2016년 09월 12일 11:29, Guenter Roeck wrote:
> On Sun, Sep 11, 2016 at 7:23 PM, Chanwoo Choi <cw00.choi@samsung.com> wrote:
>> Hi Chris,
>>
>> On 2016년 09월 12일 10:03, Chanwoo Choi wrote:
>>> Hi Chris,
>>>
>>> On 2016년 09월 10일 09:33, Chris Zhong wrote:
>>>> EXTCON_PROP_DISP_HPD is need by display port, if the system has no hpd
>>>> interrupt, this property can be used.
>>>
>>> What is meaning of HPD? So, you need to add the
>>> description and reference for HPD in commit message.
>>>
>>> For example,
>>> When adding EXTCON_PROP_USB_SS property[1],
>>> the commit message included the reference for USB SuperSpeed.
>>> [1] https://git.kernel.org/cgit/linux/kernel/git/chanwoo/extcon.git/commit/?h=extcon-next&id=8457a1b49a2af0a0e71f80afed9f7c80de361610
>>>
>>>>
>>>> Change-Id: I8b3eb78429126eaa369b10711b7f857b0a3df8ed
>>>
>>> You have to remove the 'Change-Id'.
>>>
>>>> Signed-off-by: Chris Zhong <zyw@rock-chips.com>
>>>> ---
>>>> include/linux/extcon.h | 14 +++++++++++++-
>>>> 1 file changed, 13 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/include/linux/extcon.h b/include/linux/extcon.h
>>>> index 9147c42..4411893 100644
>>>> --- a/include/linux/extcon.h
>>>> +++ b/include/linux/extcon.h
>>>> @@ -131,9 +131,21 @@
>>>> #define EXTCON_PROP_JACK_MAX 100
>>>> #define EXTCON_PROP_JACK_CNT (EXTCON_PROP_JACK_MAX - EXTCON_PROP_JACK_MIN + 1)
>>>>
>>>> +/*
>>>> + * Properties of EXTCON_TYPE_DISP.
>>>> + *
>>>> + * - EXTCON_PROP_DISP_HPD
>>>
>>> You should add the full name of 'HPD'.
>>
>> On previous mail, I replied ambiguous comment.
>>
>> I mean that you better to add the property name with full name as following:
>>
>> EXTCON_PROP_DISP_HPD ( Hxxx Pxxx Dxxx)
>
> What do you prefer ?
>
> HOTPLUGDETECT ? HOT_PLUG_DETECT ? HOTPLUG_DETECT ?
I prefer to add 'HPD (Hot Plug Detect)'.
>
> The term "HPD" seems to be quite common in the DisplayPort world; in
> most presentations it isn't even explained. Personally I would prefer
> to stick with HPD and explain it in the comments.
People who are unfamiliar with DisplayPort world
need the explanation and full name of HPD.
Basically, all abbreviation should show the full name.
--
Best Regards,
Chanwoo Choi
prev parent reply other threads:[~2016-09-12 2:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20160910003427epcas1p24ea63646e269802afb56104fd9096471@epcas1p2.samsung.com>
2016-09-10 0:33 ` [PATCH] extcon: Introduce EXTCON_PROP_DISP_HPD property Chris Zhong
2016-09-10 3:07 ` Guenter Roeck
2016-09-12 1:03 ` Chanwoo Choi
2016-09-12 2:23 ` Chanwoo Choi
2016-09-12 2:29 ` Guenter Roeck
2016-09-12 2:40 ` 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=57D61590.1030307@samsung.com \
--to=cw00.choi@samsung.com \
--cc=cpgs@samsung.com \
--cc=groeck@chromium.org \
--cc=groeck@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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