From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konrad.dybcio@linaro.org>,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Mark Gross" <markgross@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
platform-driver-x86@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 2/3] usb: typec: change altmode SVID to u16 entry
Date: Wed, 15 Nov 2023 09:27:16 +0200 [thread overview]
Message-ID: <ZVRy1L5JEN3Nda81@kuha.fi.intel.com> (raw)
In-Reply-To: <20231113221528.749481-3-dmitry.baryshkov@linaro.org>
On Tue, Nov 14, 2023 at 12:13:28AM +0200, Dmitry Baryshkov wrote:
> As stated in the changelog for the commit 7b458a4c5d73 ("usb: typec: Add
> typec_port_register_altmodes()"), the code should be adjusted according
> to the AltMode bindings. As the SVID is 16 bits wide (according to the
> USB PD Spec), use fwnode_property_read_u16() to read it.
>
> Acked-by: Hans de Goede <hdegoede@redhat.com>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> drivers/platform/x86/intel/chtwc_int33fe.c | 2 +-
> drivers/usb/typec/class.c | 5 +++--
> 2 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/platform/x86/intel/chtwc_int33fe.c b/drivers/platform/x86/intel/chtwc_int33fe.c
> index 848baecc1bb0..93f75ba1dafd 100644
> --- a/drivers/platform/x86/intel/chtwc_int33fe.c
> +++ b/drivers/platform/x86/intel/chtwc_int33fe.c
> @@ -136,7 +136,7 @@ static const struct software_node altmodes_node = {
> };
>
> static const struct property_entry dp_altmode_properties[] = {
> - PROPERTY_ENTRY_U32("svid", 0xff01),
> + PROPERTY_ENTRY_U16("svid", 0xff01),
> PROPERTY_ENTRY_U32("vdo", 0x0c0086),
> { }
> };
> diff --git a/drivers/usb/typec/class.c b/drivers/usb/typec/class.c
> index 6ec2a94e6fad..4251d44137b6 100644
> --- a/drivers/usb/typec/class.c
> +++ b/drivers/usb/typec/class.c
> @@ -2238,7 +2238,8 @@ void typec_port_register_altmodes(struct typec_port *port,
> struct typec_altmode_desc desc;
> struct typec_altmode *alt;
> size_t index = 0;
> - u32 svid, vdo;
> + u16 svid;
> + u32 vdo;
> int ret;
>
> altmodes_node = device_get_named_child_node(&port->dev, "altmodes");
> @@ -2246,7 +2247,7 @@ void typec_port_register_altmodes(struct typec_port *port,
> return; /* No altmodes specified */
>
> fwnode_for_each_child_node(altmodes_node, child) {
> - ret = fwnode_property_read_u32(child, "svid", &svid);
> + ret = fwnode_property_read_u16(child, "svid", &svid);
> if (ret) {
> dev_err(&port->dev, "Error reading svid for altmode %s\n",
> fwnode_get_name(child));
> --
> 2.42.0
--
heikki
next prev parent reply other threads:[~2023-11-15 7:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 22:13 [PATCH v2 0/3] dt-bindings: connector: usb: provide bindings for altmodes Dmitry Baryshkov
2023-11-13 22:13 ` [PATCH v2 1/3] dt-bindings: connector: usb: add altmodes description Dmitry Baryshkov
2023-11-16 18:38 ` Rob Herring
2023-11-16 20:48 ` Dmitry Baryshkov
2023-11-13 22:13 ` [PATCH v2 2/3] usb: typec: change altmode SVID to u16 entry Dmitry Baryshkov
2023-11-15 7:27 ` Heikki Krogerus [this message]
2023-11-13 22:13 ` [PATCH v2 3/3] arm64: dts: qcom: qrb5165-rb5: use u16 for DP altmode svid Dmitry Baryshkov
2023-11-15 16:17 ` Konrad Dybcio
2023-11-16 18:36 ` [PATCH v2 0/3] dt-bindings: connector: usb: provide bindings for altmodes Rob Herring
2023-11-16 20:39 ` Dmitry Baryshkov
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=ZVRy1L5JEN3Nda81@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).