Linux USB
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: amitsd@google.com
Cc: "Badhri Jagan Sridharan" <badhri@google.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	"André Draszik" <andre.draszik@linaro.org>,
	"RD Babiera" <rdbabiera@google.com>,
	"Kyle Tso" <kyletso@google.com>
Subject: Re: [PATCH v2 3/3] usb: typec: tcpci_maxim: implement get_current_limit
Date: Fri, 9 Oct 2026 13:34:17 +0200	[thread overview]
Message-ID: <asjROWLXYbDhw8Si@black.igk.intel.com> (raw)
In-Reply-To: <20261004-max77759-icl-typec-v2-3-866caf9e7d9a@google.com>

On Sun, Oct 04, 2026 at 03:41:01AM +0000, Amit Sunil Dhamne via B4 Relay wrote:
> From: Amit Sunil Dhamne <amitsd@google.com>
> 
> Implement tcpci_data::get_current_limit for tcpci_maxim driver to report
> a value of 500 mA unconditionally. This is the max current a configured
> USB 2.0 device may draw per the USB Type-C Cable and Connector
> Specification r2.2, Sec. 4.6.2.1. This helps set a current limit and
> thus enable charging for the cases when a port is connected to a non-PD
> Type-C port partner advertising Rp-def. This is until a mechanism for
> USB core to communicate the current limit to the TCPC driver is
> implemented.
> 
> Assisted-by: LLM
> Signed-off-by: Amit Sunil Dhamne <amitsd@google.com>
> Reviewed-by: Badhri Jagan Sridharan <badhri@google.com>

Acked-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>

> ---
>  drivers/usb/typec/tcpm/tcpci_maxim_core.c | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/drivers/usb/typec/tcpm/tcpci_maxim_core.c b/drivers/usb/typec/tcpm/tcpci_maxim_core.c
> index 998693a61839..e6f825931ba0 100644
> --- a/drivers/usb/typec/tcpm/tcpci_maxim_core.c
> +++ b/drivers/usb/typec/tcpm/tcpci_maxim_core.c
> @@ -482,6 +482,20 @@ static bool max_tcpci_attempt_vconn_swap_discovery(struct tcpci *tcpci, struct t
>  	return true;
>  }
>  
> +/*
> + * This callback is used by the TCPM to determine the current limit to set when
> + * Rp-def is advertised on the CC pins. The actual current limit comes from
> + * other subsystems such as the USB gadget/host stack (USB 2.0/USB 3.2) and
> + * BC1.2. As a workaround, report the USB 2.0 current limit of 500 mA to enable
> + * charging when the device is connected to a non-PD source advertising Rp-def.
> + * This can be removed once a mechanism for the USB core to communicate the
> + * current limit to this driver is implemented.
> + */
> +static int max_tcpci_get_current_limit(struct tcpci *tcpci, struct tcpci_data *tdata)
> +{
> +	return 500;
> +}
> +
>  static void max_tcpci_unregister_tcpci_port(void *tcpci)
>  {
>  	tcpci_unregister_port(tcpci);
> @@ -523,6 +537,7 @@ static int max_tcpci_probe(struct i2c_client *client)
>  	chip->data.check_contaminant = max_tcpci_check_contaminant;
>  	chip->data.cable_comm_capable = true;
>  	chip->data.attempt_vconn_swap_discovery = max_tcpci_attempt_vconn_swap_discovery;
> +	chip->data.get_current_limit = max_tcpci_get_current_limit;
>  
>  	max_tcpci_init_regs(chip);
>  	chip->tcpci = tcpci_register_port(chip->dev, &chip->data);
> 
> -- 
> 2.56.0.rc1.315.gc6ed9934b7-goog
> 

-- 
heikki

      reply	other threads:[~2026-10-09 11:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04  3:40 [PATCH v2 0/3] usb: typec: report a current limit for non-PD Rp-def sources Amit Sunil Dhamne via B4 Relay
2026-10-04  3:40 ` [PATCH v2 1/3] usb: typec: tcpm: only call get_current_limit() for cc=Rp-def Amit Sunil Dhamne via B4 Relay
2026-10-09 11:33   ` Heikki Krogerus
2026-10-04  3:41 ` [PATCH v2 2/3] usb: typec: tcpci: implement get_current_limit Amit Sunil Dhamne via B4 Relay
2026-10-09 11:33   ` Heikki Krogerus
2026-10-04  3:41 ` [PATCH v2 3/3] usb: typec: tcpci_maxim: " Amit Sunil Dhamne via B4 Relay
2026-10-09 11:34   ` 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=asjROWLXYbDhw8Si@black.igk.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=amitsd@google.com \
    --cc=andre.draszik@linaro.org \
    --cc=badhri@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kyletso@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rdbabiera@google.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