Linux USB
 help / color / mirror / Atom feed
From: "Pandey, Radhey Shyam" <radheys@amd.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
Cc: gregkh@linuxfoundation.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, linux-usb@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] usb: typec: tipd: add TPS66993 support
Date: Wed, 8 Jul 2026 23:04:14 +0530	[thread overview]
Message-ID: <34c3ca72-7327-424d-9da9-63f6542d7472@amd.com> (raw)
In-Reply-To: <akfSnKaxki9FCDww@kuha>

> Hi Radhey,
> 
> On Fri, Jul 03, 2026 at 12:35:27AM +0530, Radhey Shyam Pandey wrote:
>> Derive power status from the STATUS register (0x1A) now that TPS66993
>> deprecates the Power_Status register (0x3F). Add support for the "APP1"
>> mode string. TPS66993 controller is configured in polling mode and only
>> type-c flip orientation feature is supported on AMD Versal AI Edge Gen 2
>> VEK385 Evaluation Kit.
>>
>> Signed-off-by: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
>> ---
>> Changes for v2:
>> - New patch to add TPS66993 driver support.
>> ---
>>   drivers/usb/typec/tipd/core.c | 65 +++++++++++++++++++++++++++++++++--
>>   1 file changed, 63 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/usb/typec/tipd/core.c b/drivers/usb/typec/tipd/core.c
>> index a6cb233a055d..d2394d23a2dc 100644
>> --- a/drivers/usb/typec/tipd/core.c
>> +++ b/drivers/usb/typec/tipd/core.c
>> @@ -130,6 +130,7 @@ enum {
>>   	TPS_MODE_BIST,
>>   	TPS_MODE_DISC,
>>   	TPS_MODE_PTCH,
>> +	TPS_MODE_APP1,
>>   };
>>   
>>   static const char *const modes[] = {
>> @@ -138,6 +139,7 @@ static const char *const modes[] = {
>>   	[TPS_MODE_BIST]	= "BIST",
>>   	[TPS_MODE_DISC]	= "DISC",
>>   	[TPS_MODE_PTCH] = "PTCH",
>> +	[TPS_MODE_APP1]	= "APP1",
>>   };
>>   
>>   /* Unrecognized commands will be replaced with "!CMD" */
>> @@ -631,6 +633,35 @@ static bool tps6598x_read_power_status(struct tps6598x *tps)
>>   	return true;
>>   }
>>   
>> +/*
>> + * TPS66993 deprecated Power_Status register (0x3F). BC1.2 is not supported
>> + * and the remaining bits are redundant with STATUS register (0x1A).
>> + * Synthesize pwr_status from the already-read STATUS register.
>> + */
>> +static bool tps66993_read_power_status(struct tps6598x *tps)
>> +{
>> +	u16 pwr_status = 0;
>> +
>> +	/* Same masks as TPS_POWER_STATUS_CONNECTION() / SOURCESINK() / PWROPMODE() in tps6598x.h */
>> +	if (tps->status & TPS_STATUS_PLUG_PRESENT)
>> +		pwr_status |= FIELD_PREP(TPS_POWER_STATUS_CONNECTION_MASK, 1);
>> +
>> +	/* SOURCESINK: 1=sink; STATUS.PortRole 1=source, opposite convention */
>> +	if (!TPS_STATUS_TO_TYPEC_PORTROLE(tps->status))
>> +		pwr_status |= FIELD_PREP(TPS_POWER_STATUS_SOURCESINK_MASK, 1);
>> +
>> +	if (TPS_STATUS_VBUS_STATUS(tps->status) == TPS_STATUS_VBUS_STATUS_PD)
>> +		pwr_status |= FIELD_PREP(TPS_POWER_STATUS_TYPEC_CURRENT_MASK,
>> +					 TPS_POWER_STATUS_TYPEC_CURRENT_PD);
>> +
>> +	tps->pwr_status = pwr_status;
>> +
>> +	if (tps->data->trace_power_status)
>> +		tps->data->trace_power_status(pwr_status);
> 
> Is the condition necesary? Is it possible to get here without that
> callback?
> 

Thanks for the review . Valid point will remove the if() and call 
trace_power_status() directly and spin out v3 soon.

Thanks,
Radhey> Thanks,
> 
>> +	return true;
>> +}
>> +
>>   static void tps6598x_handle_plug_event(struct tps6598x *tps, u32 status)
>>   {
>>   	int ret;
>> @@ -1026,6 +1057,8 @@ static irqreturn_t tps6598x_interrupt(int irq, void *data)
>>   	if (!tps6598x_read_status(tps, &status))
>>   		goto err_unlock;
>>   
>> +	tps->status = status;
>> +
>>   	if ((event1[0] | event2[0]) & TPS_REG_INT_POWER_STATUS_UPDATE)
>>   		if (!tps->data->read_power_status(tps))
>>   			goto err_unlock;
>> @@ -1034,9 +1067,15 @@ static irqreturn_t tps6598x_interrupt(int irq, void *data)
>>   		if (!tps->data->read_data_status(tps))
>>   			goto err_unlock;
>>   
>> -	/* Handle plug insert or removal */
>> -	if ((event1[0] | event2[0]) & TPS_REG_INT_PLUG_EVENT)
>> +	/*
>> +	 * Refresh power status before connect - needed for TPS66993 which
>> +	 * synthesizes pwr_status from STATUS and never gets POWER_STATUS_UPDATE.
>> +	 */
>> +	if ((event1[0] | event2[0]) & TPS_REG_INT_PLUG_EVENT) {
>> +		if (!tps->data->read_power_status(tps))
>> +			goto err_unlock;
>>   		tps6598x_handle_plug_event(tps, status);
>> +	}
>>   
>>   err_unlock:
>>   	mutex_unlock(&tps->lock);
>> @@ -1072,6 +1111,7 @@ static int tps6598x_check_mode(struct tps6598x *tps)
>>   
>>   	switch (ret) {
>>   	case TPS_MODE_APP:
>> +	case TPS_MODE_APP1:
>>   	case TPS_MODE_PTCH:
>>   		return ret;
>>   	case TPS_MODE_BOOT:
>> @@ -1810,6 +1850,8 @@ static int tps6598x_probe(struct i2c_client *client)
>>   		goto err_clear_mask;
>>   	}
>>   
>> +	tps->status = status;
>> +
>>   	/*
>>   	 * This fwnode has a "compatible" property, but is never populated as a
>>   	 * struct device. Instead we simply parse it to read the properties.
>> @@ -2004,6 +2046,24 @@ static const struct tipd_data tps6598x_data = {
>>   	.connect = tps6598x_connect,
>>   };
>>   
>> +static const struct tipd_data tps66993_data = {
>> +	.irq_handler = tps6598x_interrupt,
>> +	.irq_mask1 = TPS_REG_INT_DATA_STATUS_UPDATE |
>> +		     TPS_REG_INT_PLUG_EVENT,
>> +	.tps_struct_size = sizeof(struct tps6598x),
>> +	.register_port = tps6598x_register_port,
>> +	.unregister_port = tps6598x_unregister_port,
>> +	.trace_data_status = trace_tps6598x_data_status,
>> +	.trace_power_status = trace_tps6598x_power_status,
>> +	.trace_status = trace_tps6598x_status,
>> +	.apply_patch = tps6598x_apply_patch,
>> +	.init = tps6598x_init,
>> +	.read_data_status = tps6598x_read_data_status,
>> +	.read_power_status = tps66993_read_power_status,
>> +	.reset = tps6598x_reset,
>> +	.connect = tps6598x_connect,
>> +};
>> +
>>   static const struct tipd_data tps25750_data = {
>>   	.irq_handler = tps25750_interrupt,
>>   	.irq_mask1 = TPS_REG_INT_POWER_STATUS_UPDATE |
>> @@ -2025,6 +2085,7 @@ static const struct tipd_data tps25750_data = {
>>   
>>   static const struct of_device_id tps6598x_of_match[] = {
>>   	{ .compatible = "ti,tps6598x", &tps6598x_data},
>> +	{ .compatible = "ti,tps66993", &tps66993_data},
>>   	{ .compatible = "apple,cd321x", &cd321x_data},
>>   	{ .compatible = "ti,tps25750", &tps25750_data},
>>   	{}
>> -- 
>> 2.43.0
> 


      reply	other threads:[~2026-07-08 17:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 19:05 [PATCH v2 0/3] usb: typec: tipd: add TPS66993 support Radhey Shyam Pandey
2026-07-02 19:05 ` [PATCH v2 1/3] dt-bindings: usb: ti,tps6598x: add TPS66993 compatible Radhey Shyam Pandey
2026-07-03  7:12   ` Krzysztof Kozlowski
2026-07-02 19:05 ` [PATCH v2 2/3] usb: typec: tipd: add read_power_status callback to tipd_data Radhey Shyam Pandey
2026-07-03 15:14   ` Heikki Krogerus
2026-07-02 19:05 ` [PATCH v2 3/3] usb: typec: tipd: add TPS66993 support Radhey Shyam Pandey
2026-07-03 15:17   ` Heikki Krogerus
2026-07-08 17:34     ` Pandey, Radhey Shyam [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=34c3ca72-7327-424d-9da9-63f6542d7472@amd.com \
    --to=radheys@amd.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=radhey.shyam.pandey@amd.com \
    --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