* [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID
@ 2025-02-11 7:28 Sakari Ailus
2025-02-11 7:28 ` [PATCH v7 1/3] platform/x86: int3472: Use correct type for "polarity", call it gpio_flags Sakari Ailus
` (3 more replies)
0 siblings, 4 replies; 11+ messages in thread
From: Sakari Ailus @ 2025-02-11 7:28 UTC (permalink / raw)
To: Daniel Scally, Hans de Goede, Ilpo Järvinen
Cc: platform-driver-x86, Andy Shevchenko, laurent.pinchart, hverkuil,
linux-media
One patch turned into a set, the second patch being the original one.
since v6:
- Reword the comment regarding GPIO map processing.
Sakari Ailus (3):
platform/x86: int3472: Use correct type for "polarity", call it
gpio_flags
platform/x86: int3472: Call "reset" GPIO "enable" for INT347E
platform/x86: int3472: Call "func" "con_id" instead
drivers/platform/x86/intel/int3472/discrete.c | 105 +++++++++++++-----
1 file changed, 75 insertions(+), 30 deletions(-)
--
2.39.5
^ permalink raw reply [flat|nested] 11+ messages in thread
* [PATCH v7 1/3] platform/x86: int3472: Use correct type for "polarity", call it gpio_flags
2025-02-11 7:28 [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID Sakari Ailus
@ 2025-02-11 7:28 ` Sakari Ailus
2025-02-11 7:28 ` [PATCH v7 2/3] platform/x86: int3472: Call "reset" GPIO "enable" for INT347E Sakari Ailus
` (2 subsequent siblings)
3 siblings, 0 replies; 11+ messages in thread
From: Sakari Ailus @ 2025-02-11 7:28 UTC (permalink / raw)
To: Daniel Scally, Hans de Goede, Ilpo Järvinen
Cc: platform-driver-x86, Andy Shevchenko, laurent.pinchart, hverkuil,
linux-media
Struct gpiod_lookup flags field's type is unsigned long. Thus use unsigned
long for values to be assigned to that field. Similarly, also call the
field gpio_flags which it really is.
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 | 39 ++++++++++---------
1 file changed, 20 insertions(+), 19 deletions(-)
diff --git a/drivers/platform/x86/intel/int3472/discrete.c b/drivers/platform/x86/intel/int3472/discrete.c
index 31015ebe20d8..b891b064fbf7 100644
--- a/drivers/platform/x86/intel/int3472/discrete.c
+++ b/drivers/platform/x86/intel/int3472/discrete.c
@@ -55,7 +55,7 @@ static void skl_int3472_log_sensor_module_name(struct int3472_discrete_device *i
static int skl_int3472_fill_gpiod_lookup(struct gpiod_lookup *table_entry,
struct acpi_resource_gpio *agpio,
- const char *func, u32 polarity)
+ const char *func, unsigned long gpio_flags)
{
char *path = agpio->resource_source.string_ptr;
struct acpi_device *adev;
@@ -70,14 +70,14 @@ static int skl_int3472_fill_gpiod_lookup(struct gpiod_lookup *table_entry,
if (!adev)
return -ENODEV;
- *table_entry = GPIO_LOOKUP(acpi_dev_name(adev), agpio->pin_table[0], func, polarity);
+ *table_entry = GPIO_LOOKUP(acpi_dev_name(adev), agpio->pin_table[0], func, gpio_flags);
return 0;
}
static int skl_int3472_map_gpio_to_sensor(struct int3472_discrete_device *int3472,
struct acpi_resource_gpio *agpio,
- const char *func, u32 polarity)
+ const char *func, unsigned long gpio_flags)
{
int ret;
@@ -87,7 +87,7 @@ static int skl_int3472_map_gpio_to_sensor(struct int3472_discrete_device *int347
}
ret = skl_int3472_fill_gpiod_lookup(&int3472->gpios.table[int3472->n_sensor_gpios],
- agpio, func, polarity);
+ agpio, func, gpio_flags);
if (ret)
return ret;
@@ -100,7 +100,7 @@ static int skl_int3472_map_gpio_to_sensor(struct int3472_discrete_device *int347
static struct gpio_desc *
skl_int3472_gpiod_get_from_temp_lookup(struct int3472_discrete_device *int3472,
struct acpi_resource_gpio *agpio,
- const char *func, u32 polarity)
+ const char *func, unsigned long gpio_flags)
{
struct gpio_desc *desc;
int ret;
@@ -111,7 +111,7 @@ skl_int3472_gpiod_get_from_temp_lookup(struct int3472_discrete_device *int3472,
return ERR_PTR(-ENOMEM);
lookup->dev_id = dev_name(int3472->dev);
- ret = skl_int3472_fill_gpiod_lookup(&lookup->table[0], agpio, func, polarity);
+ ret = skl_int3472_fill_gpiod_lookup(&lookup->table[0], agpio, func, gpio_flags);
if (ret)
return ERR_PTR(ret);
@@ -122,32 +122,33 @@ 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, u32 *polarity)
+static void int3472_get_func_and_polarity(u8 type, const char **func,
+ unsigned long *gpio_flags)
{
switch (type) {
case INT3472_GPIO_TYPE_RESET:
*func = "reset";
- *polarity = GPIO_ACTIVE_LOW;
+ *gpio_flags = GPIO_ACTIVE_LOW;
break;
case INT3472_GPIO_TYPE_POWERDOWN:
*func = "powerdown";
- *polarity = GPIO_ACTIVE_LOW;
+ *gpio_flags = GPIO_ACTIVE_LOW;
break;
case INT3472_GPIO_TYPE_CLK_ENABLE:
*func = "clk-enable";
- *polarity = GPIO_ACTIVE_HIGH;
+ *gpio_flags = GPIO_ACTIVE_HIGH;
break;
case INT3472_GPIO_TYPE_PRIVACY_LED:
*func = "privacy-led";
- *polarity = GPIO_ACTIVE_HIGH;
+ *gpio_flags = GPIO_ACTIVE_HIGH;
break;
case INT3472_GPIO_TYPE_POWER_ENABLE:
*func = "power-enable";
- *polarity = GPIO_ACTIVE_HIGH;
+ *gpio_flags = GPIO_ACTIVE_HIGH;
break;
default:
*func = "unknown";
- *polarity = GPIO_ACTIVE_HIGH;
+ *gpio_flags = GPIO_ACTIVE_HIGH;
break;
}
}
@@ -194,7 +195,7 @@ static int skl_int3472_handle_gpio_resources(struct acpi_resource *ares,
struct gpio_desc *gpio;
const char *err_msg;
const char *func;
- u32 polarity;
+ unsigned long gpio_flags;
int ret;
if (!acpi_gpio_get_io_resource(ares, &agpio))
@@ -217,7 +218,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, &polarity);
+ int3472_get_func_and_polarity(type, &func, &gpio_flags);
pin = FIELD_GET(INT3472_GPIO_DSM_PIN, obj->integer.value);
/* Pin field is not really used under Windows and wraps around at 8 bits */
@@ -227,16 +228,16 @@ static int skl_int3472_handle_gpio_resources(struct acpi_resource *ares,
active_value = FIELD_GET(INT3472_GPIO_DSM_SENSOR_ON_VAL, obj->integer.value);
if (!active_value)
- polarity ^= GPIO_ACTIVE_LOW;
+ gpio_flags ^= GPIO_ACTIVE_LOW;
dev_dbg(int3472->dev, "%s %s pin %d active-%s\n", func,
agpio->resource_source.string_ptr, agpio->pin_table[0],
- str_high_low(polarity == GPIO_ACTIVE_HIGH));
+ str_high_low(gpio_flags == GPIO_ACTIVE_HIGH));
switch (type) {
case INT3472_GPIO_TYPE_RESET:
case INT3472_GPIO_TYPE_POWERDOWN:
- ret = skl_int3472_map_gpio_to_sensor(int3472, agpio, func, polarity);
+ ret = skl_int3472_map_gpio_to_sensor(int3472, agpio, func, gpio_flags);
if (ret)
err_msg = "Failed to map GPIO pin to sensor\n";
@@ -244,7 +245,7 @@ static int skl_int3472_handle_gpio_resources(struct acpi_resource *ares,
case INT3472_GPIO_TYPE_CLK_ENABLE:
case INT3472_GPIO_TYPE_PRIVACY_LED:
case INT3472_GPIO_TYPE_POWER_ENABLE:
- gpio = skl_int3472_gpiod_get_from_temp_lookup(int3472, agpio, func, polarity);
+ gpio = skl_int3472_gpiod_get_from_temp_lookup(int3472, agpio, func, gpio_flags);
if (IS_ERR(gpio)) {
ret = PTR_ERR(gpio);
err_msg = "Failed to get GPIO\n";
--
2.39.5
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [PATCH v7 2/3] platform/x86: int3472: Call "reset" GPIO "enable" for INT347E
2025-02-11 7:28 [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID Sakari Ailus
2025-02-11 7:28 ` [PATCH v7 1/3] platform/x86: int3472: Use correct type for "polarity", call it gpio_flags Sakari Ailus
@ 2025-02-11 7:28 ` Sakari Ailus
2025-02-11 7:28 ` [PATCH v7 3/3] platform/x86: int3472: Call "func" "con_id" instead Sakari Ailus
2025-02-11 10:06 ` [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID Andy Shevchenko
3 siblings, 0 replies; 11+ messages in thread
From: Sakari Ailus @ 2025-02-11 7:28 UTC (permalink / raw)
To: Daniel Scally, Hans de Goede, Ilpo Järvinen
Cc: platform-driver-x86, Andy Shevchenko, laurent.pinchart, hverkuil,
linux-media
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 | 52 +++++++++++++++++--
1 file changed, 48 insertions(+), 4 deletions(-)
diff --git a/drivers/platform/x86/intel/int3472/discrete.c b/drivers/platform/x86/intel/int3472/discrete.c
index b891b064fbf7..092252eb95a8 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,53 @@ 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++) {
+ /*
+ * Map the firmware-provided GPIO to whatever a driver expects
+ * (as in DT bindings). First check if the type matches with the
+ * GPIO map, then further check that the device _HID matches.
+ */
+ 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;
+ *func = int3472_gpio_map[i].func;
+ return;
+ }
+
+ switch (*type) {
case INT3472_GPIO_TYPE_RESET:
*func = "reset";
*gpio_flags = GPIO_ACTIVE_LOW;
@@ -218,7 +262,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);
/* Pin field is not really used under Windows and wraps around at 8 bits */
--
2.39.5
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [PATCH v7 3/3] platform/x86: int3472: Call "func" "con_id" instead
2025-02-11 7:28 [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID Sakari Ailus
2025-02-11 7:28 ` [PATCH v7 1/3] platform/x86: int3472: Use correct type for "polarity", call it gpio_flags Sakari Ailus
2025-02-11 7:28 ` [PATCH v7 2/3] platform/x86: int3472: Call "reset" GPIO "enable" for INT347E Sakari Ailus
@ 2025-02-11 7:28 ` Sakari Ailus
2025-02-11 10:06 ` [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID Andy Shevchenko
3 siblings, 0 replies; 11+ messages in thread
From: Sakari Ailus @ 2025-02-11 7:28 UTC (permalink / raw)
To: Daniel Scally, Hans de Goede, Ilpo Järvinen
Cc: platform-driver-x86, Andy Shevchenko, laurent.pinchart, hverkuil,
linux-media
"con_id" is an established variable name for the GPIO naming for drivers.
Use it instead of "func" in the int3472 driver, too.
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 | 48 +++++++++----------
1 file changed, 24 insertions(+), 24 deletions(-)
diff --git a/drivers/platform/x86/intel/int3472/discrete.c b/drivers/platform/x86/intel/int3472/discrete.c
index 092252eb95a8..30ff8f3ea1f5 100644
--- a/drivers/platform/x86/intel/int3472/discrete.c
+++ b/drivers/platform/x86/intel/int3472/discrete.c
@@ -56,7 +56,7 @@ static void skl_int3472_log_sensor_module_name(struct int3472_discrete_device *i
static int skl_int3472_fill_gpiod_lookup(struct gpiod_lookup *table_entry,
struct acpi_resource_gpio *agpio,
- const char *func, unsigned long gpio_flags)
+ const char *con_id, unsigned long gpio_flags)
{
char *path = agpio->resource_source.string_ptr;
struct acpi_device *adev;
@@ -71,14 +71,14 @@ static int skl_int3472_fill_gpiod_lookup(struct gpiod_lookup *table_entry,
if (!adev)
return -ENODEV;
- *table_entry = GPIO_LOOKUP(acpi_dev_name(adev), agpio->pin_table[0], func, gpio_flags);
+ *table_entry = GPIO_LOOKUP(acpi_dev_name(adev), agpio->pin_table[0], con_id, gpio_flags);
return 0;
}
static int skl_int3472_map_gpio_to_sensor(struct int3472_discrete_device *int3472,
struct acpi_resource_gpio *agpio,
- const char *func, unsigned long gpio_flags)
+ const char *con_id, unsigned long gpio_flags)
{
int ret;
@@ -88,7 +88,7 @@ static int skl_int3472_map_gpio_to_sensor(struct int3472_discrete_device *int347
}
ret = skl_int3472_fill_gpiod_lookup(&int3472->gpios.table[int3472->n_sensor_gpios],
- agpio, func, gpio_flags);
+ agpio, con_id, gpio_flags);
if (ret)
return ret;
@@ -101,7 +101,7 @@ static int skl_int3472_map_gpio_to_sensor(struct int3472_discrete_device *int347
static struct gpio_desc *
skl_int3472_gpiod_get_from_temp_lookup(struct int3472_discrete_device *int3472,
struct acpi_resource_gpio *agpio,
- const char *func, unsigned long gpio_flags)
+ const char *con_id, unsigned long gpio_flags)
{
struct gpio_desc *desc;
int ret;
@@ -112,12 +112,12 @@ skl_int3472_gpiod_get_from_temp_lookup(struct int3472_discrete_device *int3472,
return ERR_PTR(-ENOMEM);
lookup->dev_id = dev_name(int3472->dev);
- ret = skl_int3472_fill_gpiod_lookup(&lookup->table[0], agpio, func, gpio_flags);
+ ret = skl_int3472_fill_gpiod_lookup(&lookup->table[0], agpio, con_id, gpio_flags);
if (ret)
return ERR_PTR(ret);
gpiod_add_lookup_table(lookup);
- desc = devm_gpiod_get(int3472->dev, func, GPIOD_OUT_LOW);
+ desc = devm_gpiod_get(int3472->dev, con_id, GPIOD_OUT_LOW);
gpiod_remove_lookup_table(lookup);
return desc;
@@ -129,7 +129,7 @@ skl_int3472_gpiod_get_from_temp_lookup(struct int3472_discrete_device *int3472,
* @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"
+ * @con_id: The name of the GPIO for the device
* @polarity_low: GPIO_ACTIVE_LOW true if the @polarity_low is true,
* GPIO_ACTIVE_HIGH otherwise
*/
@@ -138,15 +138,15 @@ struct int3472_gpio_map {
u8 type_from;
u8 type_to;
bool polarity_low;
- const char *func;
+ const char *con_id;
};
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)
+static void int3472_get_con_id_and_polarity(struct acpi_device *adev, u8 *type,
+ const char **con_id, unsigned long *gpio_flags)
{
unsigned int i;
@@ -165,33 +165,33 @@ static void int3472_get_func_and_polarity(struct acpi_device *adev, u8 *type,
*type = int3472_gpio_map[i].type_to;
*gpio_flags = int3472_gpio_map[i].polarity_low ?
GPIO_ACTIVE_LOW : GPIO_ACTIVE_HIGH;
- *func = int3472_gpio_map[i].func;
+ *con_id = int3472_gpio_map[i].con_id;
return;
}
switch (*type) {
case INT3472_GPIO_TYPE_RESET:
- *func = "reset";
+ *con_id = "reset";
*gpio_flags = GPIO_ACTIVE_LOW;
break;
case INT3472_GPIO_TYPE_POWERDOWN:
- *func = "powerdown";
+ *con_id = "powerdown";
*gpio_flags = GPIO_ACTIVE_LOW;
break;
case INT3472_GPIO_TYPE_CLK_ENABLE:
- *func = "clk-enable";
+ *con_id = "clk-enable";
*gpio_flags = GPIO_ACTIVE_HIGH;
break;
case INT3472_GPIO_TYPE_PRIVACY_LED:
- *func = "privacy-led";
+ *con_id = "privacy-led";
*gpio_flags = GPIO_ACTIVE_HIGH;
break;
case INT3472_GPIO_TYPE_POWER_ENABLE:
- *func = "power-enable";
+ *con_id = "power-enable";
*gpio_flags = GPIO_ACTIVE_HIGH;
break;
default:
- *func = "unknown";
+ *con_id = "unknown";
*gpio_flags = GPIO_ACTIVE_HIGH;
break;
}
@@ -238,7 +238,7 @@ static int skl_int3472_handle_gpio_resources(struct acpi_resource *ares,
union acpi_object *obj;
struct gpio_desc *gpio;
const char *err_msg;
- const char *func;
+ const char *con_id;
unsigned long gpio_flags;
int ret;
@@ -262,26 +262,26 @@ 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(int3472->sensor, &type, &func, &gpio_flags);
+ int3472_get_con_id_and_polarity(int3472->sensor, &type, &con_id, &gpio_flags);
pin = FIELD_GET(INT3472_GPIO_DSM_PIN, obj->integer.value);
/* Pin field is not really used under Windows and wraps around at 8 bits */
if (pin != (agpio->pin_table[0] & 0xff))
dev_dbg(int3472->dev, FW_BUG "%s %s pin number mismatch _DSM %d resource %d\n",
- func, agpio->resource_source.string_ptr, pin, agpio->pin_table[0]);
+ con_id, agpio->resource_source.string_ptr, pin, agpio->pin_table[0]);
active_value = FIELD_GET(INT3472_GPIO_DSM_SENSOR_ON_VAL, obj->integer.value);
if (!active_value)
gpio_flags ^= GPIO_ACTIVE_LOW;
- dev_dbg(int3472->dev, "%s %s pin %d active-%s\n", func,
+ dev_dbg(int3472->dev, "%s %s pin %d active-%s\n", con_id,
agpio->resource_source.string_ptr, agpio->pin_table[0],
str_high_low(gpio_flags == GPIO_ACTIVE_HIGH));
switch (type) {
case INT3472_GPIO_TYPE_RESET:
case INT3472_GPIO_TYPE_POWERDOWN:
- ret = skl_int3472_map_gpio_to_sensor(int3472, agpio, func, gpio_flags);
+ ret = skl_int3472_map_gpio_to_sensor(int3472, agpio, con_id, gpio_flags);
if (ret)
err_msg = "Failed to map GPIO pin to sensor\n";
@@ -289,7 +289,7 @@ static int skl_int3472_handle_gpio_resources(struct acpi_resource *ares,
case INT3472_GPIO_TYPE_CLK_ENABLE:
case INT3472_GPIO_TYPE_PRIVACY_LED:
case INT3472_GPIO_TYPE_POWER_ENABLE:
- gpio = skl_int3472_gpiod_get_from_temp_lookup(int3472, agpio, func, gpio_flags);
+ gpio = skl_int3472_gpiod_get_from_temp_lookup(int3472, agpio, con_id, gpio_flags);
if (IS_ERR(gpio)) {
ret = PTR_ERR(gpio);
err_msg = "Failed to get GPIO\n";
--
2.39.5
^ permalink raw reply related [flat|nested] 11+ messages in thread
* Re: [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID
2025-02-11 7:28 [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID Sakari Ailus
` (2 preceding siblings ...)
2025-02-11 7:28 ` [PATCH v7 3/3] platform/x86: int3472: Call "func" "con_id" instead Sakari Ailus
@ 2025-02-11 10:06 ` Andy Shevchenko
2025-02-11 10:18 ` Hans de Goede
3 siblings, 1 reply; 11+ messages in thread
From: Andy Shevchenko @ 2025-02-11 10:06 UTC (permalink / raw)
To: Sakari Ailus
Cc: Daniel Scally, Hans de Goede, Ilpo Järvinen,
platform-driver-x86, laurent.pinchart, hverkuil, linux-media
On Tue, Feb 11, 2025 at 09:28:38AM +0200, Sakari Ailus wrote:
> One patch turned into a set, the second patch being the original one.
>
> since v6:
>
> - Reword the comment regarding GPIO map processing.
Hans, Ilpo, I think this is in good enough shape
(the order of the checks I'm still not happy about
we can amend later on if required). Can it be taken?
--
With Best Regards,
Andy Shevchenko
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID
2025-02-11 10:06 ` [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID Andy Shevchenko
@ 2025-02-11 10:18 ` Hans de Goede
2025-02-11 14:32 ` Ilpo Järvinen
0 siblings, 1 reply; 11+ messages in thread
From: Hans de Goede @ 2025-02-11 10:18 UTC (permalink / raw)
To: Andy Shevchenko, Sakari Ailus
Cc: Daniel Scally, Ilpo Järvinen, platform-driver-x86,
laurent.pinchart, hverkuil, linux-media
Hi,
On 11-Feb-25 11:06 AM, Andy Shevchenko wrote:
> On Tue, Feb 11, 2025 at 09:28:38AM +0200, Sakari Ailus wrote:
>> One patch turned into a set, the second patch being the original one.
>>
>> since v6:
>>
>> - Reword the comment regarding GPIO map processing.
>
> Hans, Ilpo, I think this is in good enough shape
> (the order of the checks I'm still not happy about
> we can amend later on if required). Can it be taken?
Yes this looks good to me. Ilpo can you merge these 3 as fixes
for the 6.14 cycle ?
Regards,
Hans
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID
2025-02-11 10:18 ` Hans de Goede
@ 2025-02-11 14:32 ` Ilpo Järvinen
2025-02-11 15:13 ` Andy Shevchenko
2025-02-11 17:12 ` Sakari Ailus
0 siblings, 2 replies; 11+ messages in thread
From: Ilpo Järvinen @ 2025-02-11 14:32 UTC (permalink / raw)
To: Hans de Goede
Cc: Andy Shevchenko, Sakari Ailus, Daniel Scally, platform-driver-x86,
laurent.pinchart, hverkuil, linux-media
On Tue, 11 Feb 2025, Hans de Goede wrote:
> Hi,
>
> On 11-Feb-25 11:06 AM, Andy Shevchenko wrote:
> > On Tue, Feb 11, 2025 at 09:28:38AM +0200, Sakari Ailus wrote:
> >> One patch turned into a set, the second patch being the original one.
> >>
> >> since v6:
> >>
> >> - Reword the comment regarding GPIO map processing.
> >
> > Hans, Ilpo, I think this is in good enough shape
> > (the order of the checks I'm still not happy about
> > we can amend later on if required). Can it be taken?
>
> Yes this looks good to me. Ilpo can you merge these 3 as fixes
> for the 6.14 cycle ?
Currently, these don't appear in lore for some reason (not in
patchwork)...
Sakari, could you please resend the series v7 so that it hopefully gets
picked up by lore and is easier for me to apply them using the normal
tools I've.
The last patch IMO falls outside of even borderline for fixes. I think
I'll put it into for-next after merging the two first ones from fixes
branch into for-next.
--
i.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID
2025-02-11 14:32 ` Ilpo Järvinen
@ 2025-02-11 15:13 ` Andy Shevchenko
2025-02-11 17:12 ` Sakari Ailus
1 sibling, 0 replies; 11+ messages in thread
From: Andy Shevchenko @ 2025-02-11 15:13 UTC (permalink / raw)
To: Ilpo Järvinen
Cc: Hans de Goede, Sakari Ailus, Daniel Scally, platform-driver-x86,
laurent.pinchart, hverkuil, linux-media
On Tue, Feb 11, 2025 at 04:32:12PM +0200, Ilpo Järvinen wrote:
> On Tue, 11 Feb 2025, Hans de Goede wrote:
...
> Currently, these don't appear in lore for some reason (not in
> patchwork)...
FWIW, lore seems down. DDoS on kernel.org? (I dunno)
> Sakari, could you please resend the series v7 so that it hopefully gets
> picked up by lore and is easier for me to apply them using the normal
> tools I've.
Usually lore picks them up when it restores. But it's up to you, of course,
how to proceed. Just my 2c.
--
With Best Regards,
Andy Shevchenko
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID
2025-02-11 14:32 ` Ilpo Järvinen
2025-02-11 15:13 ` Andy Shevchenko
@ 2025-02-11 17:12 ` Sakari Ailus
2025-02-11 17:28 ` Ilpo Järvinen
1 sibling, 1 reply; 11+ messages in thread
From: Sakari Ailus @ 2025-02-11 17:12 UTC (permalink / raw)
To: Ilpo Järvinen
Cc: Hans de Goede, Andy Shevchenko, Daniel Scally,
platform-driver-x86, laurent.pinchart, hverkuil, linux-media
Hi Ilpo,
On Tue, Feb 11, 2025 at 04:32:12PM +0200, Ilpo Järvinen wrote:
> On Tue, 11 Feb 2025, Hans de Goede wrote:
>
> > Hi,
> >
> > On 11-Feb-25 11:06 AM, Andy Shevchenko wrote:
> > > On Tue, Feb 11, 2025 at 09:28:38AM +0200, Sakari Ailus wrote:
> > >> One patch turned into a set, the second patch being the original one.
> > >>
> > >> since v6:
> > >>
> > >> - Reword the comment regarding GPIO map processing.
> > >
> > > Hans, Ilpo, I think this is in good enough shape
> > > (the order of the checks I'm still not happy about
> > > we can amend later on if required). Can it be taken?
> >
> > Yes this looks good to me. Ilpo can you merge these 3 as fixes
> > for the 6.14 cycle ?
>
> Currently, these don't appear in lore for some reason (not in
> patchwork)...
>
> Sakari, could you please resend the series v7 so that it hopefully gets
> picked up by lore and is easier for me to apply them using the normal
> tools I've.
Lore is up again, getting the patches from there should therefore work (I
tried it).
>
> The last patch IMO falls outside of even borderline for fixes. I think
> I'll put it into for-next after merging the two first ones from fixes
> branch into for-next.
Sounds reasonable.
--
Regards,
Sakari Ailus
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID
2025-02-11 17:12 ` Sakari Ailus
@ 2025-02-11 17:28 ` Ilpo Järvinen
2025-02-11 17:45 ` Sakari Ailus
0 siblings, 1 reply; 11+ messages in thread
From: Ilpo Järvinen @ 2025-02-11 17:28 UTC (permalink / raw)
To: Sakari Ailus
Cc: Hans de Goede, Andy Shevchenko, Daniel Scally,
platform-driver-x86, laurent.pinchart, hverkuil, linux-media
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
On Tue, 11 Feb 2025, Sakari Ailus wrote:
> On Tue, Feb 11, 2025 at 04:32:12PM +0200, Ilpo Järvinen wrote:
> > On Tue, 11 Feb 2025, Hans de Goede wrote:
> > > On 11-Feb-25 11:06 AM, Andy Shevchenko wrote:
> > > > On Tue, Feb 11, 2025 at 09:28:38AM +0200, Sakari Ailus wrote:
> > > >> One patch turned into a set, the second patch being the original one.
> > > >>
> > > >> since v6:
> > > >>
> > > >> - Reword the comment regarding GPIO map processing.
> > > >
> > > > Hans, Ilpo, I think this is in good enough shape
> > > > (the order of the checks I'm still not happy about
> > > > we can amend later on if required). Can it be taken?
> > >
> > > Yes this looks good to me. Ilpo can you merge these 3 as fixes
> > > for the 6.14 cycle ?
> >
> > Currently, these don't appear in lore for some reason (not in
> > patchwork)...
> >
> > Sakari, could you please resend the series v7 so that it hopefully gets
> > picked up by lore and is easier for me to apply them using the normal
> > tools I've.
>
> Lore is up again, getting the patches from there should therefore work (I
> tried it).
>
> >
> > The last patch IMO falls outside of even borderline for fixes. I think
> > I'll put it into for-next after merging the two first ones from fixes
> > branch into for-next.
>
> Sounds reasonable.
Patches 1 & 2 are now in the review-ilpo-fixes branch.
--
i.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID
2025-02-11 17:28 ` Ilpo Järvinen
@ 2025-02-11 17:45 ` Sakari Ailus
0 siblings, 0 replies; 11+ messages in thread
From: Sakari Ailus @ 2025-02-11 17:45 UTC (permalink / raw)
To: Ilpo Järvinen
Cc: Hans de Goede, Andy Shevchenko, Daniel Scally,
platform-driver-x86, laurent.pinchart, hverkuil, linux-media
On Tue, Feb 11, 2025 at 07:28:51PM +0200, Ilpo Järvinen wrote:
> Patches 1 & 2 are now in the review-ilpo-fixes branch.
Thank you!
--
Sakari Ailus
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2025-02-11 17:45 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-02-11 7:28 [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID Sakari Ailus
2025-02-11 7:28 ` [PATCH v7 1/3] platform/x86: int3472: Use correct type for "polarity", call it gpio_flags Sakari Ailus
2025-02-11 7:28 ` [PATCH v7 2/3] platform/x86: int3472: Call "reset" GPIO "enable" for INT347E Sakari Ailus
2025-02-11 7:28 ` [PATCH v7 3/3] platform/x86: int3472: Call "func" "con_id" instead Sakari Ailus
2025-02-11 10:06 ` [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID Andy Shevchenko
2025-02-11 10:18 ` Hans de Goede
2025-02-11 14:32 ` Ilpo Järvinen
2025-02-11 15:13 ` Andy Shevchenko
2025-02-11 17:12 ` Sakari Ailus
2025-02-11 17:28 ` Ilpo Järvinen
2025-02-11 17:45 ` Sakari Ailus
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.