From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Ramuthevar,Vadivel MuruganX"
<vadivel.muruganx.ramuthevar@linux.intel.com>
Cc: cw00.choi@samsung.com, linux-kernel@vger.kernel.org,
vijaikumar.kanagarajan@gmail.com, myungjoo.ham@samsung.com,
cheol.yong.kim@intel.com, qi-ming.wu@intel.com,
yin1.li@intel.com
Subject: Re: [PATCH v1 1/1] extcon: ptn5150: Add usb-typec support for Intel LGM SoC
Date: Tue, 25 Aug 2020 10:40:53 +0200 [thread overview]
Message-ID: <20200825084053.GA13905@kozik-lap> (raw)
In-Reply-To: <20200825083147.25270-2-vadivel.muruganx.ramuthevar@linux.intel.com>
On Tue, Aug 25, 2020 at 04:31:47PM +0800, Ramuthevar,Vadivel MuruganX wrote:
> From: Ramuthevar Vadivel Murugan <vadivel.muruganx.ramuthevar@linux.intel.com>
>
> Add usb-typec detection support for Intel LGM SoC based
> boards.
>
> Signed-off-by: Ramuthevar Vadivel Murugan <vadivel.muruganx.ramuthevar@linux.intel.com>
> ---
> drivers/extcon/extcon-ptn5150.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/extcon/extcon-ptn5150.c b/drivers/extcon/extcon-ptn5150.c
> index 8ba706fad887..60355a1b5cb2 100644
> --- a/drivers/extcon/extcon-ptn5150.c
> +++ b/drivers/extcon/extcon-ptn5150.c
> @@ -300,6 +300,8 @@ static int ptn5150_i2c_probe(struct i2c_client *i2c)
> return ret;
> }
>
> + extcon_set_property_capability(info->edev, EXTCON_USB_HOST,
> + EXTCON_PROP_USB_TYPEC_POLARITY);
Hi,
I think you need the same for EXTCON_USB.
Although extcon_set_property_capability() error should not be fatal, but
printing a warn message would be useful.
Best regards,
Krzysztof
> /* Initialize PTN5150 device and print vendor id and version id */
> ret = ptn5150_init_dev_type(info);
> if (ret)
> --
> 2.11.0
>
next prev parent reply other threads:[~2020-08-25 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 8:31 [PATCH v1 0/1] " Ramuthevar,Vadivel MuruganX
2020-08-25 8:31 ` [PATCH v1 1/1] " Ramuthevar,Vadivel MuruganX
2020-08-25 8:40 ` Krzysztof Kozlowski [this message]
2020-08-25 9:16 ` Ramuthevar, Vadivel MuruganX
2020-08-25 10:46 ` Chanwoo Choi
2020-08-26 3:32 ` Ramuthevar, Vadivel MuruganX
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=20200825084053.GA13905@kozik-lap \
--to=krzk@kernel.org \
--cc=cheol.yong.kim@intel.com \
--cc=cw00.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=qi-ming.wu@intel.com \
--cc=vadivel.muruganx.ramuthevar@linux.intel.com \
--cc=vijaikumar.kanagarajan@gmail.com \
--cc=yin1.li@intel.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
Powered by JetHome