From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Hans de Goede <hdegoede@redhat.com>, Li Jun <jun.li@nxp.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, support.opensource@diasemi.com
Subject: [3/3] usb: typec: fusb302: Populate tcpc fwnode for TCPM property handling
Date: Tue, 21 Aug 2018 16:22:27 +0300 [thread overview]
Message-ID: <20180821132227.GB31230@kuha.fi.intel.com> (raw)
On Tue, Aug 21, 2018 at 01:28:23PM +0100, Adam Thomson wrote:
> This update populates the tcpc handle's fwnode pointer with the
> child usb-connector node, if it exists, so that TCPM can perform
> generic property handling to define the ports capabilities.
>
> Signed-off-by: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> drivers/usb/typec/fusb302/fusb302.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/usb/typec/fusb302/fusb302.c b/drivers/usb/typec/fusb302/fusb302.c
> index 82bed98..1b464c9 100644
> --- a/drivers/usb/typec/fusb302/fusb302.c
> +++ b/drivers/usb/typec/fusb302/fusb302.c
> @@ -1736,6 +1736,9 @@ static int fusb302_probe(struct i2c_client *client,
> chip->tcpc_dev.config = &chip->tcpc_config;
> mutex_init(&chip->lock);
>
> + chip->tcpc_dev.fwnode =
> + device_get_named_child_node(dev, "connector");
> +
> if (!device_property_read_u32(dev, "fcs,operating-sink-microwatt", &v))
> chip->tcpc_config.operating_snk_mw = v / 1000;
Thanks,
WARNING: multiple messages have this Message-ID (diff)
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Hans de Goede <hdegoede@redhat.com>, Li Jun <jun.li@nxp.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, support.opensource@diasemi.com
Subject: Re: [PATCH 3/3] usb: typec: fusb302: Populate tcpc fwnode for TCPM property handling
Date: Tue, 21 Aug 2018 16:22:27 +0300 [thread overview]
Message-ID: <20180821132227.GB31230@kuha.fi.intel.com> (raw)
In-Reply-To: <5ab35968fea28abb54326423523af38dd887ddcc.1534853047.git.Adam.Thomson.Opensource@diasemi.com>
On Tue, Aug 21, 2018 at 01:28:23PM +0100, Adam Thomson wrote:
> This update populates the tcpc handle's fwnode pointer with the
> child usb-connector node, if it exists, so that TCPM can perform
> generic property handling to define the ports capabilities.
>
> Signed-off-by: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> drivers/usb/typec/fusb302/fusb302.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/usb/typec/fusb302/fusb302.c b/drivers/usb/typec/fusb302/fusb302.c
> index 82bed98..1b464c9 100644
> --- a/drivers/usb/typec/fusb302/fusb302.c
> +++ b/drivers/usb/typec/fusb302/fusb302.c
> @@ -1736,6 +1736,9 @@ static int fusb302_probe(struct i2c_client *client,
> chip->tcpc_dev.config = &chip->tcpc_config;
> mutex_init(&chip->lock);
>
> + chip->tcpc_dev.fwnode =
> + device_get_named_child_node(dev, "connector");
> +
> if (!device_property_read_u32(dev, "fcs,operating-sink-microwatt", &v))
> chip->tcpc_config.operating_snk_mw = v / 1000;
Thanks,
--
heikki
next reply other threads:[~2018-08-21 13:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 13:22 Heikki Krogerus [this message]
2018-08-21 13:22 ` [PATCH 3/3] usb: typec: fusb302: Populate tcpc fwnode for TCPM property handling Heikki Krogerus
-- strict thread matches above, loose matches on Subject: below --
2018-09-11 14:37 [3/3] " Heikki Krogerus
2018-09-10 12:19 Opensource [Adam Thomson]
2018-08-31 12:17 [2/3] dt-bindings: usb: fusb302: Use usb-connector bindings for configuration Rob Herring
2018-08-31 12:17 ` [PATCH 2/3] " Rob Herring
2018-08-31 12:16 [1/3] dt-bindings: connector: Add support for USB-PD PPS APDOs to bindings Rob Herring
2018-08-31 12:16 ` [PATCH 1/3] " Rob Herring
2018-08-21 14:03 [3/3] usb: typec: fusb302: Populate tcpc fwnode for TCPM property handling Guenter Roeck
2018-08-21 14:03 ` [PATCH 3/3] " Guenter Roeck
2018-08-21 12:28 [3/3] " Opensource [Adam Thomson]
2018-08-21 12:28 ` [PATCH 3/3] " Adam Thomson
2018-08-21 12:28 ` Adam Thomson
2018-08-21 12:28 [2/3] dt-bindings: usb: fusb302: Use usb-connector bindings for configuration Opensource [Adam Thomson]
2018-08-21 12:28 ` [PATCH 2/3] " Adam Thomson
2018-08-21 12:28 ` Adam Thomson
2018-08-21 12:28 [1/3] dt-bindings: connector: Add support for USB-PD PPS APDOs to bindings Opensource [Adam Thomson]
2018-08-21 12:28 ` [PATCH 1/3] " Adam Thomson
2018-08-21 12:28 ` Adam Thomson
2018-08-21 12:28 [PATCH 0/3] dt-bindings: connector: Add USB-PD PPS APDO support Adam Thomson
2018-08-21 12:28 ` Adam Thomson
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=20180821132227.GB31230@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=jun.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=support.opensource@diasemi.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 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.