From: Prashant Malani <pmalani@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: heikki.krogerus@linux.intel.com,
Benson Leung <bleung@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Guenter Roeck <groeck@chromium.org>
Subject: Re: [PATCH v2 1/3] platform/chrome: typec: Use notifier for updates
Date: Thu, 9 Apr 2020 17:19:42 -0700 [thread overview]
Message-ID: <20200410001942.GA201188@google.com> (raw)
In-Reply-To: <20200410000819.198668-2-pmalani@chromium.org>
Hi Enric,
On Thu, Apr 09, 2020 at 05:08:19PM -0700, Prashant Malani wrote:
> Register a listener for the cros-usbpd-notifier, and update port state
> when a notification comes in.
>
> Signed-off-by: Prashant Malani <pmalani@chromium.org>
> ---
>
> Changes in v2:
> - Added Kconfig dependency to CROS_USBPD_NOTIFY.
> - Fixed spacing error.
> - Removed superfluous devm_warn() call.
>
> drivers/platform/chrome/Kconfig | 1 +
> drivers/platform/chrome/cros_ec_typec.c | 23 +++++++++++++++++++++++
> 2 files changed, 24 insertions(+)
>
> diff --git a/drivers/platform/chrome/Kconfig b/drivers/platform/chrome/Kconfig
> index 03ea5129ed0c3..67fc9c567ae6c 100644
> --- a/drivers/platform/chrome/Kconfig
> +++ b/drivers/platform/chrome/Kconfig
> @@ -218,6 +218,7 @@ config CROS_EC_TYPEC
> tristate "ChromeOS EC Type-C Connector Control"
> depends on MFD_CROS_EC_DEV && TYPEC
> default MFD_CROS_EC_DEV
> + depends on CROS_USBPD_NOTIFY
Woops, looks like I got the ordering wrong here. My apologies, I will
send a new version of the series out.
> help
> If you say Y here, you get support for accessing Type C connector
> information from the Chrome OS EC.
> diff --git a/drivers/platform/chrome/cros_ec_typec.c b/drivers/platform/chrome/cros_ec_typec.c
> index 874269c070739..d444dd7422a2a 100644
> --- a/drivers/platform/chrome/cros_ec_typec.c
> +++ b/drivers/platform/chrome/cros_ec_typec.c
> @@ -11,6 +11,7 @@
> #include <linux/of.h>
> #include <linux/platform_data/cros_ec_commands.h>
> #include <linux/platform_data/cros_ec_proto.h>
> +#include <linux/platform_data/cros_usbpd_notify.h>
> #include <linux/platform_device.h>
> #include <linux/usb/typec.h>
>
> @@ -26,6 +27,7 @@ struct cros_typec_data {
> struct typec_port *ports[EC_USB_PD_MAX_PORTS];
> /* Initial capabilities for each port. */
> struct typec_capability *caps[EC_USB_PD_MAX_PORTS];
> + struct notifier_block nb;
> };
>
> static int cros_typec_parse_port_props(struct typec_capability *cap,
> @@ -272,6 +274,22 @@ static int cros_typec_get_cmd_version(struct cros_typec_data *typec)
> return 0;
> }
>
> +static int cros_ec_typec_event(struct notifier_block *nb,
> + unsigned long host_event, void *_notify)
> +{
> + struct cros_typec_data *typec = container_of(nb, struct cros_typec_data,
> + nb);
> + int ret, i;
> +
> + for (i = 0; i < typec->num_ports; i++) {
> + ret = cros_typec_port_update(typec, i);
> + if (ret < 0)
> + dev_warn(typec->dev, "Update failed for port: %d\n", i);
> + }
> +
> + return NOTIFY_OK;
> +}
> +
> #ifdef CONFIG_ACPI
> static const struct acpi_device_id cros_typec_acpi_id[] = {
> { "GOOG0014", 0 },
> @@ -332,6 +350,11 @@ static int cros_typec_probe(struct platform_device *pdev)
> goto unregister_ports;
> }
>
> + typec->nb.notifier_call = cros_ec_typec_event;
> + ret = cros_usbpd_register_notify(&typec->nb);
> + if (ret < 0)
> + goto unregister_ports;
> +
> return 0;
>
> unregister_ports:
> --
> 2.26.0.110.g2183baf09c-goog
>
next prev parent reply other threads:[~2020-04-10 0:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 0:08 [PATCH v2 0/3] platform/chrome: typec: Add port partner registration Prashant Malani
2020-04-10 0:08 ` [PATCH v2 1/3] platform/chrome: typec: Use notifier for updates Prashant Malani
2020-04-10 0:19 ` Prashant Malani [this message]
2020-04-10 0:08 ` [PATCH v2 2/3] platform/chrome: typec: Add struct for port data Prashant Malani
2020-04-10 0:08 ` [PATCH v2 3/3] platform/chrome: typec: Register port partner Prashant Malani
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=20200410001942.GA201188@google.com \
--to=pmalani@chromium.org \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.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
Powered by JetHome