All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Amit Sunil Dhamne" <amitsd@google.com>
Cc: linux-usb@vger.kernel.org, robh@kernel.org,
	devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: connector: Add time property for tSenderResponse
Date: Sat, 10 Oct 2026 01:40:41 +0000	[thread overview]
Message-ID: <sashiko-outbox-166207@kernel.org> (raw)
In-Reply-To: <20261010-tcpm-sender-response-time-v2-1-67ea364a21d7@google.com>

> From: Amit Sunil Dhamne <amitsd@google.com>
> 
> Add the sender-response-time-ms property to allow platforms to specify
> the tSenderResponse timer value, i.e. the max time a port waits for the
> port partner to respond to a message that requires a response.
> 
> As per the PD specifications, the tSenderResponse values are:
> 
> +--------+----------+----------+
> | Spec   | Min (ms) | Max (ms) |
> +--------+----------+----------+
> | PD 2.0 | 24       | 30       |
> | PD 3.2 | 27       | 33       |
> +--------+----------+----------+
> 
> Set the minimum value to 24 ms (the lowest minimum across the PD
> specifications). Both the default and maximum values are intentionally
> relaxed to 60 ms to maintain interoperability with slower port partners,
> while allowing platforms to configure stricter spec-compliant timeouts.
> 
> Also update the max33359 example to showcase the new property.
> 
> Assisted-by: LLM
> Signed-off-by: Amit Sunil Dhamne <amitsd@google.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261010-tcpm-sender-response-time-v2-0-67ea364a21d7@google.com?part=1


  reply	other threads:[~2026-10-10  1:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10  1:37 [PATCH v2 0/2] usb: typec: tcpm: Make tSenderResponse timer configurable Amit Sunil Dhamne via B4 Relay
2026-10-10  1:37 ` Amit Sunil Dhamne
2026-10-10  1:37 ` [PATCH v2 1/2] dt-bindings: connector: Add time property for tSenderResponse Amit Sunil Dhamne via B4 Relay
2026-10-10  1:37   ` Amit Sunil Dhamne
2026-10-10  1:40   ` sashiko-bot [this message]
2026-10-10  1:37 ` [PATCH v2 2/2] usb: typec: tcpm: Allow configuring tSenderResponse via fwnode Amit Sunil Dhamne via B4 Relay
2026-10-10  1:37   ` Amit Sunil Dhamne
2026-10-10  1:43   ` sashiko-bot

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=sashiko-outbox-166207@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=amitsd@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.