kernel/linux.git/drivers/pinctrl/intel/pinctrl-intel.h, branch linux-7.0.y

pinctrl: intel: Enable 3-bit PAD_OWN feature

2026-03-19T06:58:53+00:00

Starting from revision 1.1 of the Chassis specification the PAD_OWN is represented by 3 bits instead of 2 bits in the previous revisions. Update the driver to support this feature. Signed-off-by: Andy Shevchenko

pinctrl: intel: Align Copyright note with corporate guidelines

2026-02-06T11:05:29+00:00

The Copyright note must follow the Copyright (C) Intel Corporation template, where (C) is always capitalised and either a single year or a range. Update the Intel pin control drivers to follow. Signed-off-by: Andy Shevchenko Acked-by: Mika Westerberg Signed-off-by: Linus Walleij

pinctrl: intel: Export intel_gpio_add_pin_ranges()

2025-11-18T14:13:59+00:00

Export intel_gpio_add_pin_ranges() for reuse in other drivers. Acked-by: Mika Westerberg Signed-off-by: Andy Shevchenko

pinctrl: intel: Introduce INTEL_GPP() macro

2025-11-05T17:14:36+00:00

A new macro will be used for the further refactoring of the drivers. Signed-off-by: Andy Shevchenko

pinctrl: intel: Constify struct intel_pinctrl parameter

2024-09-05T15:09:28+00:00

There are a few functions that do not and should not change the state of the pin control object. Constify the respective parameter. Signed-off-by: Andy Shevchenko Acked-by: Mika Westerberg

pinctrl: intel: Constify intel_get_community() returned object

2024-08-30T18:44:38+00:00

There is nothing prevents us from constifying intel_get_community() returned object. Do it to make code more robust. Acked-by: Mika Westerberg Signed-off-by: Andy Shevchenko

pinctrl: baytrail: Fix selecting gpio pinctrl state

2024-04-08T14:54:48+00:00

For all the "score" pin-groups all the intel_pingroup-s to select the non GPIO function are re-used for byt_score_gpio_groups[]. But this is incorrect since a pin-group includes the mode setting, which for the non GPIO functions generally is 1, where as to select the GPIO function mode must be set to 0. So the GPIO function needs separate intel_pingroup-s with their own mode value of 0. Add a new PIN_GROUP_GPIO macro which adds a foo_gpio entry to each pin-group defined this way and update byt_score_gpio_groups[] to point to the new foo_gpio entries. The "sus" usb_oc_grp usb_ulpi_grp and pcu_spi_grp pin-groups are special because these have a non 0 mode value to select the GPIO functions and these already have matching foo_gpio pin-groups, leave these are unchanged. The pmu_clk "sus" groups added in commit 2f46d7f7e959 ("pinctrl: baytrail: Add pinconf group + function for the pmu_clk") do need to use the new PIN_GROUP_GPIO macro. Fixes: 2f46d7f7e959 ("pinctrl: baytrail: Add pinconf group + function for the pmu_clk") Signed-off-by: Hans de Goede Signed-off-by: Andy Shevchenko

pinctrl: intel: Revert "Unexport intel_pinctrl_probe()"

2023-11-14T12:09:08+00:00

In order to prepare for a new coming driver export the original intel_pinctrl_probe() again. This reverts commit 0dd519e3784b13befa1cdfeff847a0885b06650f. Signed-off-by: Andy Shevchenko

pinctrl: intel: Make PM ops functions static

2023-11-13T11:33:28+00:00

No more users outside of the main module. Acked-by: Mika Westerberg Acked-by: Linus Walleij Link: https://lore.kernel.org/r/20231030120734.2831419-18-andriy.shevchenko@linux.intel.com Signed-off-by: Andy Shevchenko

pinctrl: intel: Provide Intel pin control wide PM ops structure

2023-11-13T11:33:27+00:00

With the help of EXPORT_NS_GPL_DEV_PM_OPS() and NOIRQ_SYSTEM_SLEEP_PM_OPS() we may convert PM ops functions to become static. This also takes into account the PM configuration options such as CONFIG_PM and CONFIG_PM_SLEEP. Hence the first step is to provide a generic PM ops structure that can be used by drivers directly. Reviewed-by: Jonathan Cameron Acked-by: Mika Westerberg Acked-by: Linus Walleij Link: https://lore.kernel.org/r/20231030120734.2831419-2-andriy.shevchenko@linux.intel.com Signed-off-by: Andy Shevchenko