From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Daniel Scally <djrscally@gmail.com>,
Hans de Goede <hdegoede@redhat.com>,
platform-driver-x86@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
laurent.pinchart@ideasonboard.com, hverkuil@xs4all.nl,
linux-media@vger.kernel.org
Subject: Re: [PATCH v5 2/3] platform/x86: int3472: Call "reset" GPIO "enable" for INT347E
Date: Mon, 3 Feb 2025 10:26:29 +0200 (EET) [thread overview]
Message-ID: <acc436c0-2aad-2ce3-d1ba-f6fd40cf1fc0@linux.intel.com> (raw)
In-Reply-To: <Z6B8WWwNwxS42ARa@kekkonen.localdomain>
[-- Attachment #1: Type: text/plain, Size: 4623 bytes --]
On Mon, 3 Feb 2025, Sakari Ailus wrote:
> Hi Ilpo,
>
> On Mon, Feb 03, 2025 at 10:03:14AM +0200, Ilpo Järvinen wrote:
> > On Fri, 31 Jan 2025, Sakari Ailus wrote:
> >
> > > The DT bindings for ov7251 specify "enable" GPIO (xshutdown in
> > > documentation) but the int3472 indiscriminately provides this as a "reset"
> > > GPIO to sensor drivers. Take this into account by assigning it as "enable"
> > > with active high polarity for INT347E devices, i.e. ov7251. "reset" with
> > > active low polarity remains the default GPIO name for other devices.
> > >
> > > Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> > > Reviewed-by: Hans de Goede <hdegoede@redhat.com>
> > > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > ---
> > > drivers/platform/x86/intel/int3472/discrete.c | 47 +++++++++++++++++--
> > > 1 file changed, 43 insertions(+), 4 deletions(-)
> > >
> > > diff --git a/drivers/platform/x86/intel/int3472/discrete.c b/drivers/platform/x86/intel/int3472/discrete.c
> > > index 3f7624714869..529ea2d08a21 100644
> > > --- a/drivers/platform/x86/intel/int3472/discrete.c
> > > +++ b/drivers/platform/x86/intel/int3472/discrete.c
> > > @@ -2,6 +2,7 @@
> > > /* Author: Dan Scally <djrscally@gmail.com> */
> > >
> > > #include <linux/acpi.h>
> > > +#include <linux/array_size.h>
> > > #include <linux/bitfield.h>
> > > #include <linux/device.h>
> > > #include <linux/gpio/consumer.h>
> > > @@ -122,10 +123,48 @@ skl_int3472_gpiod_get_from_temp_lookup(struct int3472_discrete_device *int3472,
> > > return desc;
> > > }
> > >
> > > -static void int3472_get_func_and_polarity(u8 type, const char **func,
> > > - unsigned long *gpio_flags)
> > > +/**
> > > + * struct int3472_gpio_map - Map GPIOs to whatever is expected by the
> > > + * sensor driver (as in DT bindings)
> > > + * @hid: The ACPI HID of the device without the instance number e.g. INT347E
> > > + * @type_from: The GPIO type from ACPI ?SDT
> > > + * @type_to: The assigned GPIO type, typically same as @type_from
> > > + * @func: The function, e.g. "enable"
> > > + * @polarity_low: GPIO_ACTIVE_LOW true if the @polarity_low is true,
> > > + * GPIO_ACTIVE_HIGH otherwise
> > > + */
> > > +struct int3472_gpio_map {
> > > + const char *hid;
> > > + u8 type_from;
> > > + u8 type_to;
> > > + bool polarity_low;
> > > + const char *func;
> > > +};
> > > +
> > > +static const struct int3472_gpio_map int3472_gpio_map[] = {
> > > + { "INT347E", INT3472_GPIO_TYPE_RESET, INT3472_GPIO_TYPE_RESET, false, "enable" },
> > > +};
> > > +
> > > +static void int3472_get_func_and_polarity(struct acpi_device *adev, u8 *type,
> > > + const char **func, unsigned long *gpio_flags)
> > > {
> > > - switch (type) {
> > > + unsigned int i;
> > > +
> > > + for (i = 0; i < ARRAY_SIZE(int3472_gpio_map); i++) {
> > > + if (*type != int3472_gpio_map[i].type_from)
> > > + continue;
> > > +
> > > + if (!acpi_dev_hid_uid_match(adev, int3472_gpio_map[i].hid, NULL))
> > > + continue;
> > > +
> > > + *type = int3472_gpio_map[i].type_to;
> > > + *gpio_flags = int3472_gpio_map[i].polarity_low ?
> > > + GPIO_ACTIVE_LOW : GPIO_ACTIVE_HIGH;
> >
> > Don't start this continuation line left of = sign unless you really
> > really have to do that, and it's not such a case here!
>
> Why? The documentation says the subsequent lines should be aligned
> "substantially" (I believe a tab stop qualifies), except in cases of
> arguments in parentheses just right of the opening parenthesis but that's
> not the case here.
Because I say so, it's not substancial to me when it's left of =. This is
not negotiable.
--
i.
> I can submit v6 with that if others agree.
>
> >
> > Either put GPIO_ACTIVE_LOW on the first line and align the defines, or
> > align the second line as it is with int3472_gpio_map[...].
> >
> > > + *func = int3472_gpio_map[i].func;
> > > + return;
> > > + }
> > > +
> > > + switch (*type) {
> > > case INT3472_GPIO_TYPE_RESET:
> > > *func = "reset";
> > > *gpio_flags = GPIO_ACTIVE_LOW;
> > > @@ -218,7 +257,7 @@ static int skl_int3472_handle_gpio_resources(struct acpi_resource *ares,
> > >
> > > type = FIELD_GET(INT3472_GPIO_DSM_TYPE, obj->integer.value);
> > >
> > > - int3472_get_func_and_polarity(type, &func, &gpio_flags);
> > > + int3472_get_func_and_polarity(int3472->sensor, &type, &func, &gpio_flags);
> > >
> > > pin = FIELD_GET(INT3472_GPIO_DSM_PIN, obj->integer.value);
> > > if (pin != agpio->pin_table[0])
> > >
>
>
next prev parent reply other threads:[~2025-02-03 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 12:01 [PATCH v5 0/3] int3472: Support GPIO con_id based on _HID Sakari Ailus
2025-01-31 12:01 ` [PATCH v5 1/3] platform/x86: int3472: Use correct type for "polarity", call it gpio_flags Sakari Ailus
2025-01-31 12:01 ` [PATCH v5 2/3] platform/x86: int3472: Call "reset" GPIO "enable" for INT347E Sakari Ailus
2025-01-31 17:18 ` Andy Shevchenko
2025-02-03 7:42 ` Sakari Ailus
2025-02-03 8:52 ` Andy Shevchenko
2025-02-03 8:03 ` Ilpo Järvinen
2025-02-03 8:20 ` Sakari Ailus
2025-02-03 8:26 ` Ilpo Järvinen [this message]
2025-01-31 12:01 ` [PATCH v5 3/3] platform/x86: int3472: Call "func" "con_id" instead Sakari Ailus
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=acc436c0-2aad-2ce3-d1ba-f6fd40cf1fc0@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=djrscally@gmail.com \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox