Linux USB
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Krishna Kurapati PSSNV <krishna.kurapati@oss.qualcomm.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Biju Das <biju.das.jz@bp.renesas.com>,
	linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] usb: typec: hd3ss3220: Enable VBUS based on ID pin state
Date: Wed, 8 Oct 2025 16:30:14 +0300	[thread overview]
Message-ID: <aOZnZqb1ohI7z2HU@kuha.fi.intel.com> (raw)
In-Reply-To: <1a428b7f-5d20-4d55-aa3a-e4feb580b82e@oss.qualcomm.com>

On Wed, Oct 08, 2025 at 04:45:06PM +0530, Krishna Kurapati PSSNV wrote:
> On 10/8/2025 4:39 PM, Heikki Krogerus wrote:
> > On Thu, Oct 02, 2025 at 10:55:39PM +0530, Krishna Kurapati wrote:
> > > Enable VBUS on HD3SS3220 when the ID pin is low, as required by the Type-C
> > > specification.
> > 
> > There is not ID pin on Type-C connector.
> 
> There is an ID pin coming out from HD3SS3220 controller to SoC that is being
> referred to here.

So please fix the statement. The Type-C specification does not place
any requirements on the ID pin.

> > > The ID pin stays high when VBUS is not at VSafe0V, and goes
> > > low when VBUS is at VSafe0V.
> > > 
> > > Add support to read the ID pin state and enable VBUS accordingly.
> > 
> > I'm a bit confused about this... Why can't you just check the attached
> > state, and if it's DFP, then you drive VBUS?
> > 
> 
> We could, but checking for DFP doesn't ensure VBUS is at VSafe0V as per the
> datasheet. So using the ID pin to enable vbus.

Fair enough.

thanks,

> > > Signed-off-by: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
> > > ---
> > >   drivers/usb/typec/hd3ss3220.c | 58 +++++++++++++++++++++++++++++++++++
> > >   1 file changed, 58 insertions(+)
> > > 
> > > diff --git a/drivers/usb/typec/hd3ss3220.c b/drivers/usb/typec/hd3ss3220.c
> > > index 3ecc688dda82..44ee0be27644 100644
> > > --- a/drivers/usb/typec/hd3ss3220.c
> > > +++ b/drivers/usb/typec/hd3ss3220.c
> > > @@ -54,6 +54,11 @@ struct hd3ss3220 {
> > >   	struct delayed_work output_poll_work;
> > >   	enum usb_role role_state;
> > >   	bool poll;
> > > +
> > > +	struct gpio_desc *id_gpiod;
> > > +	int id_irq;
> > > +
> > > +	struct regulator *vbus;
> > >   };
> > >   static int hd3ss3220_set_power_opmode(struct hd3ss3220 *hd3ss3220, int power_opmode)
> > > @@ -319,6 +324,28 @@ static const struct regmap_config config = {
> > >   	.max_register = 0x0A,
> > >   };
> > > +static irqreturn_t hd3ss3220_id_isr(int irq, void *dev_id)
> > > +{
> > > +	struct hd3ss3220 *hd3ss3220 = dev_id;
> > > +	int ret;
> > > +	int id;
> > > +
> > > +	if (IS_ERR_OR_NULL(hd3ss3220->vbus))
> > > +		return IRQ_HANDLED;
> > > +
> > > +	id = hd3ss3220->id_gpiod ? gpiod_get_value_cansleep(hd3ss3220->id_gpiod) : 1;
> > > +
> > > +	if (!id) {
> > > +		ret = regulator_enable(hd3ss3220->vbus);
> > > +		if (ret)
> > > +			dev_err(hd3ss3220->dev, "enable vbus regulator failed\n");
> > > +	} else {
> > > +		regulator_disable(hd3ss3220->vbus);
> > > +	}
> > > +
> > > +	return IRQ_HANDLED;
> > > +}
> > > +
> > >   static int hd3ss3220_probe(struct i2c_client *client)
> > >   {
> > >   	struct typec_capability typec_cap = { };
> > > @@ -354,6 +381,37 @@ static int hd3ss3220_probe(struct i2c_client *client)
> > >   		hd3ss3220->role_sw = usb_role_switch_get(hd3ss3220->dev);
> > >   	}
> > > +	hd3ss3220->id_gpiod = devm_gpiod_get_optional(hd3ss3220->dev, "id", GPIOD_IN);
> > > +	if (IS_ERR(hd3ss3220->id_gpiod))
> > > +		return PTR_ERR(hd3ss3220->id_gpiod);
> > > +
> > > +	if (hd3ss3220->id_gpiod) {
> > > +		hd3ss3220->id_irq = gpiod_to_irq(hd3ss3220->id_gpiod);
> > > +		if (hd3ss3220->id_irq < 0) {
> > > +			dev_err(hd3ss3220->dev, "failed to get ID IRQ\n");
> > > +			return hd3ss3220->id_irq;
> > > +		}
> > > +
> > > +		ret = devm_request_threaded_irq(hd3ss3220->dev,
> > > +						hd3ss3220->id_irq, NULL,
> > > +						hd3ss3220_id_isr,
> > > +						IRQF_TRIGGER_RISING |
> > > +						IRQF_TRIGGER_FALLING | IRQF_ONESHOT,
> > > +						dev_name(hd3ss3220->dev), hd3ss3220);
> > > +		if (ret < 0) {
> > > +			dev_err(hd3ss3220->dev, "failed to get id irq\n");
> > > +			return ret;
> > > +		}
> > > +	}
> > > +
> > > +	hd3ss3220->vbus = devm_regulator_get_optional(hd3ss3220->dev, "vbus");
> > > +	if (PTR_ERR(hd3ss3220->vbus) == -ENODEV)
> > > +		hd3ss3220->vbus = NULL;
> > > +
> > > +	if (IS_ERR(hd3ss3220->vbus))
> > > +		return dev_err_probe(hd3ss3220->dev,
> > > +				     PTR_ERR(hd3ss3220->vbus), "failed to get vbus\n");
> > > +
> > >   	if (IS_ERR(hd3ss3220->role_sw)) {
> > >   		ret = PTR_ERR(hd3ss3220->role_sw);
> > >   		goto err_put_fwnode;
> > > -- 
> > > 2.34.1
> > 

-- 
heikki

      reply	other threads:[~2025-10-08 13:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 17:25 [PATCH 0/2] Implement vbus support for HD3SS3220 port controller Krishna Kurapati
2025-10-02 17:25 ` [PATCH 1/2] dt-bindings: usb: ti,hd3ss3220: Add support for VBUS based on ID state Krishna Kurapati
2025-10-08 20:53   ` Conor Dooley
2025-10-02 17:25 ` [PATCH 2/2] usb: typec: hd3ss3220: Enable VBUS based on ID pin state Krishna Kurapati
2025-10-03  5:56   ` kernel test robot
2025-10-08 11:09   ` Heikki Krogerus
2025-10-08 11:15     ` Krishna Kurapati PSSNV
2025-10-08 13:30       ` Heikki Krogerus [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=aOZnZqb1ohI7z2HU@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krishna.kurapati@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=robh@kernel.org \
    /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