From: Brian Norris <briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
To: Lin Huang <hl-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Cc: dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
jikos-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
benjamin.tissoires-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
jani.nikula-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] HID: i2c-hid: add reset gpio property
Date: Mon, 30 Oct 2017 09:57:55 -0700 [thread overview]
Message-ID: <20171030165753.GA10752@google.com> (raw)
In-Reply-To: <1509331789-1949-1-git-send-email-hl-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
+ devicetree list
Hi,
On Mon, Oct 30, 2017 at 10:49:49AM +0800, Lin Huang wrote:
> some i2c hid devices have reset gpio, need to control
> it in the driver.
>
> Change-Id: I87bca954bffc7eb7b35711406f522cb3d0fc2ded
You should be removing these Gerrit ID lines from patches before sending
them to these mailing lists.
> Signed-off-by: Lin Huang <hl-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
> ---
> drivers/hid/i2c-hid/i2c-hid.c | 63 +++++++++++++++++++++++++++--------
> include/linux/platform_data/i2c-hid.h | 4 +++
> 2 files changed, 53 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/hid/i2c-hid/i2c-hid.c b/drivers/hid/i2c-hid/i2c-hid.c
> index 9145c21..a0e3a8e 100644
> --- a/drivers/hid/i2c-hid/i2c-hid.c
> +++ b/drivers/hid/i2c-hid/i2c-hid.c
> @@ -38,6 +38,7 @@
> #include <linux/mutex.h>
> #include <linux/acpi.h>
> #include <linux/of.h>
> +#include <linux/gpio/consumer.h>
> #include <linux/regulator/consumer.h>
>
> #include <linux/platform_data/i2c-hid.h>
> @@ -793,6 +794,34 @@ struct hid_ll_driver i2c_hid_ll_driver = {
> };
> EXPORT_SYMBOL_GPL(i2c_hid_ll_driver);
>
> +static int i2c_hid_hw_power_on(struct i2c_hid *ihid)
> +{
> + int ret;
> +
> + ret = regulator_enable(ihid->pdata.supply);
> + if (ret < 0)
> + return ret;
> +
> + if (ihid->pdata.post_power_delay_ms)
> + msleep(ihid->pdata.post_power_delay_ms);
> +
> + gpiod_set_value_cansleep(ihid->pdata.reset_gpio, 1);
> + usleep_range(ihid->pdata.assert_reset_us,
> + ihid->pdata.assert_reset_us);
What's the point of using the same value on both ends of the range? Does
it make sense to give some padding to this? e.g., from X to X + 10% ?
(Note that reasonable values for this are on the order of a few
milliseconds.)
Also, the above msleep() has a 'if non-zero' condition on it...but
that's not actually necessary now that I look again, since msleep() and
usleep_range() both handle zero times OK... But it feels a little
inconsistent. We should probably change one or the other sometime.
> + gpiod_set_value_cansleep(ihid->pdata.reset_gpio, 0);
> + usleep_range(ihid->pdata.deassert_reset_us,
> + ihid->pdata.deassert_reset_us);
> +
> + return ret;
> +}
> +
> +static int i2c_hid_hw_power_off(struct i2c_hid *ihid)
> +{
> + gpiod_set_value_cansleep(ihid->pdata.reset_gpio, 1);
> +
> + return regulator_disable(ihid->pdata.supply);
> +}
> +
> static int i2c_hid_init_irq(struct i2c_client *client)
> {
> struct i2c_hid *ihid = i2c_get_clientdata(client);
> @@ -934,6 +963,12 @@ static int i2c_hid_of_probe(struct i2c_client *client,
> if (!ret)
> pdata->post_power_delay_ms = val;
>
> + ret = of_property_read_u32(dev->of_node, "assert-reset-us",
> + &pdata->assert_reset_us);
> +
> + ret = of_property_read_u32(dev->of_node, "deassert-reset-us",
> + &pdata->deassert_reset_us);
You need to document these.
Brian
> +
> return 0;
> }
>
> @@ -1002,14 +1037,16 @@ static int i2c_hid_probe(struct i2c_client *client,
> goto err;
> }
>
> - ret = regulator_enable(ihid->pdata.supply);
> + ihid->pdata.reset_gpio = devm_gpiod_get_optional(&client->dev, "reset",
> + GPIOD_OUT_HIGH);
> + if (IS_ERR(ihid->pdata.reset_gpio))
> + goto err;
> +
> + ret = i2c_hid_hw_power_on(ihid);
> if (ret < 0) {
> - dev_err(&client->dev, "Failed to enable regulator: %d\n",
> - ret);
> + dev_err(&client->dev, "Failed to power on: %d\n", ret);
> goto err;
> }
> - if (ihid->pdata.post_power_delay_ms)
> - msleep(ihid->pdata.post_power_delay_ms);
>
> i2c_set_clientdata(client, ihid);
>
> @@ -1086,7 +1123,7 @@ static int i2c_hid_probe(struct i2c_client *client,
> pm_runtime_disable(&client->dev);
>
> err_regulator:
> - regulator_disable(ihid->pdata.supply);
> + i2c_hid_hw_power_off(ihid);
>
> err:
> i2c_hid_free_buffers(ihid);
> @@ -1112,8 +1149,7 @@ static int i2c_hid_remove(struct i2c_client *client)
> if (ihid->bufsize)
> i2c_hid_free_buffers(ihid);
>
> - regulator_disable(ihid->pdata.supply);
> -
> + i2c_hid_hw_power_off(ihid);
> kfree(ihid);
>
> return 0;
> @@ -1165,9 +1201,10 @@ static int i2c_hid_suspend(struct device *dev)
> hid_warn(hid, "Failed to enable irq wake: %d\n",
> wake_status);
> } else {
> - ret = regulator_disable(ihid->pdata.supply);
> + ret = i2c_hid_hw_power_off(ihid);
> if (ret < 0)
> - hid_warn(hid, "Failed to disable supply: %d\n", ret);
> + hid_warn(hid, "Failed to disable hw power: %d\n",
> + ret);
> }
>
> return 0;
> @@ -1182,11 +1219,9 @@ static int i2c_hid_resume(struct device *dev)
> int wake_status;
>
> if (!device_may_wakeup(&client->dev)) {
> - ret = regulator_enable(ihid->pdata.supply);
> + ret = i2c_hid_hw_power_on(ihid);
> if (ret < 0)
> - hid_warn(hid, "Failed to enable supply: %d\n", ret);
> - if (ihid->pdata.post_power_delay_ms)
> - msleep(ihid->pdata.post_power_delay_ms);
> + hid_warn(hid, "Failed to enable hw power: %d\n", ret);
> } else if (ihid->irq_wake_enabled) {
> wake_status = disable_irq_wake(client->irq);
> if (!wake_status)
> diff --git a/include/linux/platform_data/i2c-hid.h b/include/linux/platform_data/i2c-hid.h
> index 1fb0882..3afc781 100644
> --- a/include/linux/platform_data/i2c-hid.h
> +++ b/include/linux/platform_data/i2c-hid.h
> @@ -14,6 +14,7 @@
>
> #include <linux/types.h>
>
> +struct gpio_desc;
> struct regulator;
>
> /**
> @@ -37,6 +38,9 @@ struct i2c_hid_platform_data {
> u16 hid_descriptor_address;
> struct regulator *supply;
> int post_power_delay_ms;
> + struct gpio_desc *reset_gpio;
> + int assert_reset_us;
> + int deassert_reset_us;
> };
>
> #endif /* __LINUX_I2C_HID_H */
> --
> 2.7.4
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Brian Norris <briannorris@chromium.org>
To: Lin Huang <hl@rock-chips.com>
Cc: dmitry.torokhov@gmail.com, jikos@kernel.org,
benjamin.tissoires@redhat.com, jani.nikula@intel.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] HID: i2c-hid: add reset gpio property
Date: Mon, 30 Oct 2017 09:57:55 -0700 [thread overview]
Message-ID: <20171030165753.GA10752@google.com> (raw)
In-Reply-To: <1509331789-1949-1-git-send-email-hl@rock-chips.com>
+ devicetree list
Hi,
On Mon, Oct 30, 2017 at 10:49:49AM +0800, Lin Huang wrote:
> some i2c hid devices have reset gpio, need to control
> it in the driver.
>
> Change-Id: I87bca954bffc7eb7b35711406f522cb3d0fc2ded
You should be removing these Gerrit ID lines from patches before sending
them to these mailing lists.
> Signed-off-by: Lin Huang <hl@rock-chips.com>
> ---
> drivers/hid/i2c-hid/i2c-hid.c | 63 +++++++++++++++++++++++++++--------
> include/linux/platform_data/i2c-hid.h | 4 +++
> 2 files changed, 53 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/hid/i2c-hid/i2c-hid.c b/drivers/hid/i2c-hid/i2c-hid.c
> index 9145c21..a0e3a8e 100644
> --- a/drivers/hid/i2c-hid/i2c-hid.c
> +++ b/drivers/hid/i2c-hid/i2c-hid.c
> @@ -38,6 +38,7 @@
> #include <linux/mutex.h>
> #include <linux/acpi.h>
> #include <linux/of.h>
> +#include <linux/gpio/consumer.h>
> #include <linux/regulator/consumer.h>
>
> #include <linux/platform_data/i2c-hid.h>
> @@ -793,6 +794,34 @@ struct hid_ll_driver i2c_hid_ll_driver = {
> };
> EXPORT_SYMBOL_GPL(i2c_hid_ll_driver);
>
> +static int i2c_hid_hw_power_on(struct i2c_hid *ihid)
> +{
> + int ret;
> +
> + ret = regulator_enable(ihid->pdata.supply);
> + if (ret < 0)
> + return ret;
> +
> + if (ihid->pdata.post_power_delay_ms)
> + msleep(ihid->pdata.post_power_delay_ms);
> +
> + gpiod_set_value_cansleep(ihid->pdata.reset_gpio, 1);
> + usleep_range(ihid->pdata.assert_reset_us,
> + ihid->pdata.assert_reset_us);
What's the point of using the same value on both ends of the range? Does
it make sense to give some padding to this? e.g., from X to X + 10% ?
(Note that reasonable values for this are on the order of a few
milliseconds.)
Also, the above msleep() has a 'if non-zero' condition on it...but
that's not actually necessary now that I look again, since msleep() and
usleep_range() both handle zero times OK... But it feels a little
inconsistent. We should probably change one or the other sometime.
> + gpiod_set_value_cansleep(ihid->pdata.reset_gpio, 0);
> + usleep_range(ihid->pdata.deassert_reset_us,
> + ihid->pdata.deassert_reset_us);
> +
> + return ret;
> +}
> +
> +static int i2c_hid_hw_power_off(struct i2c_hid *ihid)
> +{
> + gpiod_set_value_cansleep(ihid->pdata.reset_gpio, 1);
> +
> + return regulator_disable(ihid->pdata.supply);
> +}
> +
> static int i2c_hid_init_irq(struct i2c_client *client)
> {
> struct i2c_hid *ihid = i2c_get_clientdata(client);
> @@ -934,6 +963,12 @@ static int i2c_hid_of_probe(struct i2c_client *client,
> if (!ret)
> pdata->post_power_delay_ms = val;
>
> + ret = of_property_read_u32(dev->of_node, "assert-reset-us",
> + &pdata->assert_reset_us);
> +
> + ret = of_property_read_u32(dev->of_node, "deassert-reset-us",
> + &pdata->deassert_reset_us);
You need to document these.
Brian
> +
> return 0;
> }
>
> @@ -1002,14 +1037,16 @@ static int i2c_hid_probe(struct i2c_client *client,
> goto err;
> }
>
> - ret = regulator_enable(ihid->pdata.supply);
> + ihid->pdata.reset_gpio = devm_gpiod_get_optional(&client->dev, "reset",
> + GPIOD_OUT_HIGH);
> + if (IS_ERR(ihid->pdata.reset_gpio))
> + goto err;
> +
> + ret = i2c_hid_hw_power_on(ihid);
> if (ret < 0) {
> - dev_err(&client->dev, "Failed to enable regulator: %d\n",
> - ret);
> + dev_err(&client->dev, "Failed to power on: %d\n", ret);
> goto err;
> }
> - if (ihid->pdata.post_power_delay_ms)
> - msleep(ihid->pdata.post_power_delay_ms);
>
> i2c_set_clientdata(client, ihid);
>
> @@ -1086,7 +1123,7 @@ static int i2c_hid_probe(struct i2c_client *client,
> pm_runtime_disable(&client->dev);
>
> err_regulator:
> - regulator_disable(ihid->pdata.supply);
> + i2c_hid_hw_power_off(ihid);
>
> err:
> i2c_hid_free_buffers(ihid);
> @@ -1112,8 +1149,7 @@ static int i2c_hid_remove(struct i2c_client *client)
> if (ihid->bufsize)
> i2c_hid_free_buffers(ihid);
>
> - regulator_disable(ihid->pdata.supply);
> -
> + i2c_hid_hw_power_off(ihid);
> kfree(ihid);
>
> return 0;
> @@ -1165,9 +1201,10 @@ static int i2c_hid_suspend(struct device *dev)
> hid_warn(hid, "Failed to enable irq wake: %d\n",
> wake_status);
> } else {
> - ret = regulator_disable(ihid->pdata.supply);
> + ret = i2c_hid_hw_power_off(ihid);
> if (ret < 0)
> - hid_warn(hid, "Failed to disable supply: %d\n", ret);
> + hid_warn(hid, "Failed to disable hw power: %d\n",
> + ret);
> }
>
> return 0;
> @@ -1182,11 +1219,9 @@ static int i2c_hid_resume(struct device *dev)
> int wake_status;
>
> if (!device_may_wakeup(&client->dev)) {
> - ret = regulator_enable(ihid->pdata.supply);
> + ret = i2c_hid_hw_power_on(ihid);
> if (ret < 0)
> - hid_warn(hid, "Failed to enable supply: %d\n", ret);
> - if (ihid->pdata.post_power_delay_ms)
> - msleep(ihid->pdata.post_power_delay_ms);
> + hid_warn(hid, "Failed to enable hw power: %d\n", ret);
> } else if (ihid->irq_wake_enabled) {
> wake_status = disable_irq_wake(client->irq);
> if (!wake_status)
> diff --git a/include/linux/platform_data/i2c-hid.h b/include/linux/platform_data/i2c-hid.h
> index 1fb0882..3afc781 100644
> --- a/include/linux/platform_data/i2c-hid.h
> +++ b/include/linux/platform_data/i2c-hid.h
> @@ -14,6 +14,7 @@
>
> #include <linux/types.h>
>
> +struct gpio_desc;
> struct regulator;
>
> /**
> @@ -37,6 +38,9 @@ struct i2c_hid_platform_data {
> u16 hid_descriptor_address;
> struct regulator *supply;
> int post_power_delay_ms;
> + struct gpio_desc *reset_gpio;
> + int assert_reset_us;
> + int deassert_reset_us;
> };
>
> #endif /* __LINUX_I2C_HID_H */
> --
> 2.7.4
>
next prev parent reply other threads:[~2017-10-30 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 2:49 [PATCH] HID: i2c-hid: add reset gpio property Lin Huang
[not found] ` <1509331789-1949-1-git-send-email-hl-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-10-30 16:57 ` Brian Norris [this message]
2017-10-30 16:57 ` Brian Norris
[not found] ` <20171030165753.GA10752-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2017-10-30 20:15 ` Rob Herring
2017-10-30 20:15 ` Rob Herring
[not found] ` <CAL_JsqKQw7UubSRALsPMUw7rR16xwcSWUzN5wEAqckN7D61Kkg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-30 21:16 ` Brian Norris
2017-10-30 21:16 ` Brian Norris
2017-11-06 9:30 ` Benjamin Tissoires
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=20171030165753.GA10752@google.com \
--to=briannorris-f7+t8e8rja9g9huczpvpmw@public.gmane.org \
--cc=benjamin.tissoires-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=hl-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=jani.nikula-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=jikos-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.