From: Lee Jones <lee.jones@linaro.org>
To: Prashant Malani <pmalani@chromium.org>
Cc: enric.balletbo@collabora.com, groeck@chromium.org,
bleung@chromium.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] mfd: cros_ec: Add cros-usbpd-notify subdevice
Date: Thu, 16 Jan 2020 13:28:48 +0000 [thread overview]
Message-ID: <20200116132848.GM325@dell> (raw)
In-Reply-To: <20200114031056.44502-2-pmalani@chromium.org>
On Mon, 13 Jan 2020, Prashant Malani wrote:
> Add the cros-usbpd-notify driver as a subdevice on platforms that
> support the EC_FEATURE_USB_PD EC feature flag and don't have the
> ACPI PD notification device defined.
>
> This driver allows other cros-ec devices to receive PD event
> notifications from the Chrome OS Embedded Controller (EC) via a
> notification chain.
>
> Signed-off-by: Prashant Malani <pmalani@chromium.org>
> ---
>
> Changes in v5:
> - Updated the IS_ENABLED() check to check for CONFIG_OF instead of
> !CONFIG_ACPI according to upstream comments.
>
> Changes in v4:
> - Removed #ifndef usage; instead, moved cros-usbpd-notify to a separate
> mfd_cell and used an IS_ENABLED() check.
> - Changed commit title and description slightly to reflect change in
> code.
>
> drivers/mfd/cros_ec_dev.c | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
Looks okay to me, but I would like more Chromium reviews please.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2020-01-16 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 3:10 [PATCH v5 1/2] platform: chrome: Add cros-usbpd-notify driver Prashant Malani
2020-01-14 3:10 ` [PATCH v5 2/2] mfd: cros_ec: Add cros-usbpd-notify subdevice Prashant Malani
2020-01-16 13:28 ` Lee Jones [this message]
2020-01-14 17:07 ` [PATCH v5 1/2] platform: chrome: Add cros-usbpd-notify driver Enric Balletbo i Serra
2020-01-14 19:23 ` Prashant Malani
2020-01-14 20:29 ` Enric Balletbo i Serra
2020-01-14 21:02 ` 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=20200116132848.GM325@dell \
--to=lee.jones@linaro.org \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmalani@chromium.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