From: "Rob Herring (Arm)" <robh@kernel.org>
To: Amit Sunil Dhamne <amitsd@google.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kyle Tso <kyletso@google.com>,
Badhri Jagan Sridharan <badhri@google.com>,
linux-kernel@vger.kernel.org, RD Babiera <rdbabiera@google.com>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: connector: Add pd-revision property
Date: Tue, 17 Dec 2024 07:44:09 -0600 [thread overview]
Message-ID: <173444304922.1440983.3295876849064154968.robh@kernel.org> (raw)
In-Reply-To: <20241210-get_rev_upstream-v2-1-d0094e52d48f@google.com>
On Tue, 10 Dec 2024 19:07:07 -0800, Amit Sunil Dhamne wrote:
> Add pd-revision property definition, to specify the maximum Power
> Delivery Revision and Version supported by the connector.
>
> Signed-off-by: Amit Sunil Dhamne <amitsd@google.com>
> ---
> Documentation/devicetree/bindings/connector/usb-connector.yaml | 7 +++++++
> Documentation/devicetree/bindings/usb/maxim,max33359.yaml | 1 +
> 2 files changed, 8 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2024-12-17 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 3:07 [PATCH v2 0/3] Add support for responding to Get_Revision request Amit Sunil Dhamne via B4 Relay
2024-12-11 3:07 ` [PATCH v2 1/3] dt-bindings: connector: Add pd-revision property Amit Sunil Dhamne via B4 Relay
2024-12-17 13:44 ` Rob Herring (Arm) [this message]
2024-12-11 3:07 ` [PATCH v2 2/3] usb: typec: tcpm: Add support for parsing pd-revision DT property Amit Sunil Dhamne via B4 Relay
2024-12-11 3:07 ` [PATCH v2 3/3] usb: typec: tcpm: Add new AMS for Get_Revision response Amit Sunil Dhamne via B4 Relay
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=173444304922.1440983.3295876849064154968.robh@kernel.org \
--to=robh@kernel.org \
--cc=amitsd@google.com \
--cc=badhri@google.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=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
all inboxes | Powered by JetHome®