pinctrl: qcom: add support for sparse GPIOs
Subsystems (5)
v6 cover pinctrl: qcom: add support for sparse GPIOs
A series of patches that add support for GPIO maps that have holes in them. That is, even though a client driver has N consecutive GPIOs, some are just unavailable for whatever reason, and the hardware should not be accessed for those GPIOs.
Frankly, I like V5 of this patchset better, because it uses an existing API (gpiochip_add_pin_range) and is less intrusive.
Timur Tabi (4):
Revert "gpio: set up initial state from .get_direction()"
gpiolib: add bitmask for valid GPIO lines
[v6] pinctrl: qcom: disable GPIO groups with no pins [v3] pinctrl: qcom: qdf2xxx: add support for new ACPI HID QCOM8002
drivers/gpio/gpiolib.c | 74 +++++++++-------- drivers/pinctrl/qcom/pinctrl-msm.c | 48 +++++++++-- drivers/pinctrl/qcom/pinctrl-msm.h | 2 + drivers/pinctrl/qcom/pinctrl-qdf2xxx.c | 145 +++++++++++++++++++++++++-------- include/linux/gpio/driver.h | 2 + 5 files changed, 197 insertions(+), 74 deletions(-)
Signature · 3 lines
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
PATCH v6 1/4 Revert "gpio: set up initial state from .get_direction()"
This reverts commit 72d3200061776264941be1b5a9bb8e926b3b30a5.
We cannot blindly query the direction of all GPIOs when the pins are first registered. The get_direction callback normally triggers a read/write to hardware, but we shouldn't be touching the hardware for an individual GPIO until after it's been properly requested.
--- drivers/gpio/gpiolib.c | 31 +++++++------------------------ 1 file changed, 7 insertions(+), 24 deletions(-)
drivers/gpio/gpiolib.c +7 -24
@@ -1221,31 +1221,14 @@ int gpiochip_add_data(struct gpio_chip *chip, void *data)struct gpio_desc *desc = &gdev->descs[i]; desc->gdev = gdev; -/* -* REVISIT: most hardware initializes GPIOs as inputs -* (often with pullups enabled) so power usage is -* minimized. Linux code should set the gpio direction -* first thing; but until it does, and in case -* chip->get_direction is not set, we may expose the -* wrong direction in sysfs. -*/ - -if (chip->get_direction) { -/* -* If we have .get_direction, set up the initial -* direction flag from the hardware. -*/ -int dir = chip->get_direction (chip, i); -if (!dir) -set_bit (FLAG_IS_OUT , &desc->flags); - }else if (!chip->direction_input) { -/* -* If the chip lacks the .direction_input callback -* we logically assume all lines are outputs. -*/ -set_bit (FLAG_IS_OUT , &desc->flags); - } +/* REVISIT: most hardware initializes GPIOs as inputs (often +* with pullups enabled) so power usage is minimized. Linux +* code should set the gpio direction first thing; but until +* it does, and in case chip->get_direction is not set, we may +* expose the wrong direction in sysfs. +*/ + desc->flags = !chip->direction_input ? (1 <<FLAG_IS_OUT ) :0 ; }#ifdef CONFIG_PINCTRL
Signature · 3 lines
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
PATCH 1/4 Revert "gpio: set up initial state from .get_direction()"
Quoted 16 lines · Timur Tabi
This reverts commit
72d3200061776264941be1b5a9bb8e926b3b30a5.We cannot blindly query the direction of all GPIOs when the pins are first registered. The
get_directioncallback normally triggers a read/write to hardware, but we shouldn't be touching the hardware for an individual GPIO until after it's been properly requested.(quoted diff) +1
-0+ /* REVISIT: most hardware initializes GPIOs as inputs(often
(quoted diff) +1
-0+ * with pullups enabled) so power usage is minimized.Linux
(quoted diff) +1
-0+ * code should set the gpio direction first thing;but until
(quoted diff) +1
-0+ * it does, and in case chip->get_direction is notset, we may
drivers/gpio/gpiolib.c int gpiochip_add_data(struct gpio_chip *chip, void *data) · line 1230
Quoted 2 lines
drivers/gpio/gpiolib.c +2
-0+* expose the wrong direction in sysfs. +*/
Can you preserve the style and indentation of the commit? Does checkpatch warn you about style? (It's apparently not a net subsystem)
Quoted 5 lines
(quoted diff) +1
-0+ desc->flags = !chip->direction_input ? (1 <<
FLAG_IS_OUT) : 0;
}#ifdef
CONFIG_PINCTRL
Signature · 2 lines
Andy Shevchenko <[email protected]> Intel Finland Oy
PATCH v6 1/4 Revert "gpio: set up initial state from .get_direction()"
Quoted 3 lines · Andy Shevchenko
Can you preserve the style and indentation of the commit? Does checkpatch warn you about style? (It's apparently not a net subsystem)
I ran checkpatch on it and it didn't complain.
Also, I don't think that when reverting a patch, I am also supposed to to fix cosmetic changes of the code that existed before the original patch.
Signature · 3 lines
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
PATCH 1/4 Revert "gpio: set up initial state from .get_direction()"
Quoted 1 line · Timur Tabi
I ran checkpatch on it and it didn't complain.
In this case checkpatch should have given you an error due to the missing Signed-off-by tag :-)
PATCH v6 1/4 Revert "gpio: set up initial state from .get_direction()"
Quoted 2 lines · Fabio Estevam
In this case checkpatch should have given you an error due to the missing Signed-off-by tag:-)
Indeed! Something must be broken in my checkpatch invocation. I did think that it was odd that I didn't get any complaints. Thanks.
Signature · 3 lines
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
PATCH 1/4 Revert "gpio: set up initial state from .get_direction()"
In reply to Timur TabiQuoted 6 lines · Timur Tabi
Quoted 3 lines · Andy Shevchenko
Can you preserve the style and indentation of the commit? Does checkpatch warn you about style? (It's apparently not a net subsystem)
I ran checkpatch on it and it didn't complain.
Hmm... Okay.
Quoted 4 lines
Also, I don't think that when reverting a patch, I am also supposed to
to fix cosmetic changes of the code that existed before the original patch.
Point taken. Up to Linus how to proceed, it's indeed cosmetic non-code change.
Signature · 2 lines
Andy Shevchenko <[email protected]> Intel Finland Oy
PATCH v6 2/4 gpiolib: add bitmask for valid GPIO lines
In reply to Timur TabiAdd support for specifying that some GPIOs within a range are unavailable. Some systems have a sparse list of GPIOs, where a range of GPIOs is specified (usually 0 to n-1), but some subset within that range is absent or unavailable for whatever reason.
To support this, allow drivers to specify a bitmask of GPIOs that are present or absent. Gpiolib will then block access to those that are absent.
--- drivers/gpio/gpiolib.c | 43 +++++++++++++++++++++++++++++++++++-------- include/linux/gpio/driver.h | 2 ++ 2 files changed, 37 insertions(+), 8 deletions(-)
drivers/gpio/gpiolib.c +35 -8
@@ -1481,22 +1481,36 @@ static struct gpio_chip *find_chip_by_name(const char *name)static int gpiochip_irqchip_init_valid_mask (struct gpio_chip *gpiochip) { -if (!gpiochip->irq_need_valid_mask) -return 0 ; +if (gpiochip->irq_need_valid_mask) { + gpiochip->irq_valid_mask = +kcalloc (BITS_TO_LONGS (gpiochip->ngpio), +sizeof (long ),GFP_KERNEL ); +if (!gpiochip->irq_valid_mask) +return -ENOMEM ; - gpiochip->irq_valid_mask =kcalloc (BITS_TO_LONGS (gpiochip->ngpio), -sizeof (long ),GFP_KERNEL ); -if (!gpiochip->irq_valid_mask) -return -ENOMEM ; +/* Assume by default all GPIOs are valid */ +bitmap_fill (gpiochip->irq_valid_mask, gpiochip->ngpio); + } -/* Assume by default all GPIOs are valid */ -bitmap_fill (gpiochip->irq_valid_mask, gpiochip->ngpio); +if (gpiochip->line_need_valid_mask) { + gpiochip->line_valid_mask = +kcalloc (BITS_TO_LONGS (gpiochip->ngpio), +sizeof (long ),GFP_KERNEL ); +if (!gpiochip->line_valid_mask) +return -ENOMEM ; + +/* Assume by default all GPIOs are valid */ +bitmap_fill (gpiochip->line_valid_mask, gpiochip->ngpio); + }return 0 ; }static void gpiochip_irqchip_free_valid_mask (struct gpio_chip *gpiochip) { +kfree (gpiochip->line_valid_mask); + gpiochip->line_valid_mask =NULL ; +kfree (gpiochip->irq_valid_mask); gpiochip->irq_valid_mask =NULL ; }
@@ -1510,6 +1524,15 @@ static bool gpiochip_irqchip_irq_valid(const struct gpio_chip *gpiochip,return test_bit (offset, gpiochip->irq_valid_mask); } +static bool gpiochip_irqchip_line_valid (const struct gpio_chip *gpiochip, +unsigned int offset) +{ +/* No mask means all valid */ +if (likely (!gpiochip->line_valid_mask)) +return true; +return test_bit (offset, gpiochip->line_valid_mask); +} +/** * gpiochip_set_cascaded_irqchip() - connects a cascaded irqchip to a gpiochip * @gpiochip: the gpiochip to set the irqchip chain to
@@ -3320,6 +3343,10 @@ struct gpio_desc *__must_check gpiod_get_index(struct device *dev,return desc; } +/* Make sure the GPIO is valid before we request it. */ +if (!gpiochip_irqchip_line_valid (desc->gdev->chip, idx)) +return ERR_PTR (-EACCES ); + status =gpiod_request (desc, con_id);if (status <0 )return ERR_PTR (status);
include/linux/gpio/driver.h +2 -0
@@ -172,6 +172,8 @@ struct gpio_chip {bool irq_nested;bool irq_need_valid_mask;unsigned long *irq_valid_mask; +bool line_need_valid_mask; +unsigned long *line_valid_mask;struct lock_class_key *lock_key;#endif
Signature · 3 lines
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
PATCH 2/4 gpiolib: add bitmask for valid GPIO lines
Quoted 10 lines · Timur Tabi
Add support for specifying that some GPIOs within a range are unavailable.
Some systems have a sparse list of GPIOs, where a range of GPIOs is specified (usually 0 to n-1), but some subset within that range is absent or unavailable for whatever reason.To support this, allow drivers to specify a bitmask of GPIOs that are present or absent. Gpiolib will then block access to those that are absent.
Quoted 7 lines
Signed-off-by Timur Tabi <[email protected]>static int gpiochip_irqchip_init_valid_mask(struct
gpio_chip
*gpiochip)
{
Instead of mangling this function wouldn't be better to introduce a separate one for line and perhaps a third one which calls them both?
Quoted 31 lines
drivers/gpio/gpiolib.c +6
-3-if (!gpiochip->irq_need_valid_mask) -return 0 ; +if (gpiochip->irq_need_valid_mask) { + gpiochip->irq_valid_mask = +kcalloc (BITS_TO_LONGS (gpiochip->ngpio), +sizeof (long ),GFP_KERNEL ); +if (!gpiochip->irq_valid_mask) +return -ENOMEM ; - gpiochip->irq_valid_mask = kcalloc(BITS_TO_LONGS(gpiochip-Quoted 1 line
ngpio),
drivers/gpio/gpiolib.c +2
-3- sizeof(long), GFP_KERNEL); -if (!gpiochip->irq_valid_mask) -return -ENOMEM ; +/* Assume by default all GPIOs are valid */ + bitmap_fill(gpiochip->irq_valid_mask, gpiochip-Quoted 1 line
ngpio);
drivers/gpio/gpiolib.c +10
-2+ } -/* Assume by default all GPIOs are valid */ -bitmap_fill (gpiochip->irq_valid_mask, gpiochip->ngpio); +if (gpiochip->line_need_valid_mask) { + gpiochip->line_valid_mask = +kcalloc (BITS_TO_LONGS (gpiochip->ngpio), +sizeof (long ),GFP_KERNEL ); +if (!gpiochip->line_valid_mask) +return -ENOMEM ; + +/* Assume by default all GPIOs are valid */ + bitmap_fill(gpiochip->line_valid_mask, gpiochip-Quoted 1 line
ngpio);
drivers/gpio/gpiolib.c static struct gpio_chip *find_chip_by_name(const char *name) · line 1507
Quoted 4 lines
drivers/gpio/gpiolib.c +1
-0+ }return 0 ; }
...for my opinion it will drastically increase readability and reduce diff as well (better for review).
Signature · 2 lines
Andy Shevchenko <[email protected]> Intel Finland Oy
PATCH v6 2/4 gpiolib: add bitmask for valid GPIO lines
Quoted 2 lines · Andy Shevchenko
Instead of mangling this function wouldn't be better to introduce a separate one for line and perhaps a third one which calls them both?
The diff is convoluted, but the end result is clean:
static int gpiochip_irqchip_init_valid_mask(struct gpio_chip *gpiochip)
{
if (gpiochip->irq_need_valid_mask) {
gpiochip->irq_valid_mask =
kcalloc(BITS_TO_LONGS(gpiochip->ngpio),
sizeof(long), GFP_KERNEL);
if (!gpiochip->irq_valid_mask)
return -ENOMEM;
/* Assume by default all GPIOs are valid */
bitmap_fill(gpiochip->irq_valid_mask, gpiochip->ngpio);
}
if (gpiochip->line_need_valid_mask) {
gpiochip->line_valid_mask =
kcalloc(BITS_TO_LONGS(gpiochip->ngpio),
sizeof(long), GFP_KERNEL);
if (!gpiochip->line_valid_mask)
return -ENOMEM;
/* Assume by default all GPIOs are valid */
bitmap_fill(gpiochip->line_valid_mask, gpiochip->ngpio);
}
return 0;
}Is this acceptable?
Signature · 3 lines
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
PATCH 2/4 gpiolib: add bitmask for valid GPIO lines
Quoted 7 lines · Timur Tabi
Quoted 2 lines · Andy Shevchenko
Instead of mangling this function wouldn't be better to introduce a separate one for line and perhaps a third one which calls them both?
The diff is convoluted, but the end result is clean:
Is this acceptable?
I also put in the comment the following:
--- 8< --- 8< --- 8< ---
...for my opinion it will drastically increase readability and reduce diff as well (better for review).
--- 8< --- 8< --- 8< ---
The decision is up to Linus. I simple shared my opinion.
Signature · 2 lines
Andy Shevchenko <[email protected]> Intel Finland Oy
PATCH v6 3/4 pinctrl: qcom: disable GPIO groups with no pins
In reply to Timur Tabipinctrl-msm only accepts an array of GPIOs from 0 to n-1, and it expects each group to support have only one pin (npins == 1).
We can support "sparse" GPIO maps if we allow for some groups to have zero pins (npins == 0). These pins are "hidden" from the rest of the driver and gpiolib.
A new boolean 'sparse' indicates whether the GPIO map is sparse. If any GPIO has an 'npins' value of 0, then 'sparse' must be set to True.
Most access to unavailable GPIOs can be blocked via the gpio_chip.request function. The one exception is when gpiochip_add_data() scans all of the GPIOs without "requesting" them. To cover this case, msm_gpio_get_direction() separately checks if the GPIO is available.
--- drivers/pinctrl/qcom/pinctrl-msm.c | 48 +++++++++++++++++++++++++++++++++----- drivers/pinctrl/qcom/pinctrl-msm.h | 2 ++ 2 files changed, 44 insertions(+), 6 deletions(-)
drivers/pinctrl/qcom/pinctrl-msm.c +42 -6
@@ -507,6 +507,11 @@ static void msm_gpio_dbg_show_one(struct seq_file *s, }; g = &pctrl->soc->groups[offset]; + +/* If the GPIO group has no pins, then don't show it. */ +if (!g->npins) +return ; + ctl_reg =readl (pctrl->regs + g->ctl_reg); is_out = !!(ctl_reg &BIT (g->oe_bit));
@@ -516,7 +521,7 @@ static void msm_gpio_dbg_show_one(struct seq_file *s,seq_printf (s," %-8s: %-3s %d" , g->name, is_out ?"out" :"in" , func);seq_printf (s," %dmA" ,msm_regval_to_drive (drive)); -seq_printf (s," %s" , pulls[pull]); +seq_printf (s," %s\n" , pulls[pull]); }static void msm_gpio_dbg_show (struct seq_file *s,struct gpio_chip *chip)
@@ -524,23 +529,36 @@ static void msm_gpio_dbg_show(struct seq_file *s, struct gpio_chip *chip)unsigned gpio = chip->base;unsigned i; -for (i =0 ; i < chip->ngpio; i++, gpio++) { +for (i =0 ; i < chip->ngpio; i++, gpio++) msm_gpio_dbg_show_one(s, NULL, chip, i, gpio); -seq_puts (s,"\n" ); - } }#else #define msm_gpio_dbg_show NULL#endif +/* +* If the requested GPIO has no pins, then treat it as unavailable. +* Otherwise, call the standard request function. +*/ +static int msm_gpio_request (struct gpio_chip *chip,unsigned int offset) +{ +struct msm_pinctrl *pctrl =gpiochip_get_data (chip); +const struct msm_pingroup *g = &pctrl->soc->groups[offset]; + +if (!g->npins) +return -ENODEV ; + +return gpiochip_generic_request (chip, offset); +} +static const struct gpio_chip msm_gpio_template = { .direction_input = msm_gpio_direction_input, .direction_output = msm_gpio_direction_output, .get_direction = msm_gpio_get_direction, .get = msm_gpio_get, .set = msm_gpio_set, - .request = gpiochip_generic_request, + .request = msm_gpio_request, .free = gpiochip_generic_free, .dbg_show = msm_gpio_dbg_show, };
@@ -813,6 +831,8 @@ static int msm_gpio_init(struct msm_pinctrl *pctrl)struct gpio_chip *chip;int ret;unsigned ngpio = pctrl->soc->ngpios; +const struct msm_pingroup *groups = pctrl->soc->groups; +unsigned int i;if (WARN_ON (ngpio >MAX_NR_GPIO ))return -EINVAL ;
@@ -825,13 +845,29 @@ static int msm_gpio_init(struct msm_pinctrl *pctrl) chip->owner =THIS_MODULE ; chip->of_node = pctrl->dev->of_node; +/* If the GPIO map is sparse, then we need to disable specific IRQs */ +if (pctrl->soc->sparse) { + chip->irq_need_valid_mask = true; + chip->line_need_valid_mask = true; + } + ret =gpiochip_add_data (&pctrl->chip, pctrl);if (ret) {dev_err (pctrl->dev,"Failed register gpiochip\n" );return ret; } - ret =gpiochip_add_pin_range (&pctrl->chip,dev_name (pctrl->dev),0 ,0 , chip->ngpio); +if (chip->line_need_valid_mask) { +for (i =0 ; i < ngpio; i++) +if (!groups[i].npins) { +clear_bit (i, pctrl->chip.irq_valid_mask); +clear_bit (i, pctrl->chip.line_valid_mask); + } + } + + ret =gpiochip_add_pin_range (&pctrl->chip,dev_name (pctrl->dev), +0 ,0 , ngpio); +if (ret) {dev_err (pctrl->dev,"Failed to add pin range\n" );gpiochip_remove (&pctrl->chip);
drivers/pinctrl/qcom/pinctrl-msm.h +2 -0
@@ -107,6 +107,7 @@ struct msm_pingroup {* @ngroups: The numbmer of entries in @groups. * @ngpio: The number of pingroups the driver should expose as GPIOs. * @pull_no_keeper: The SoC does not support keeper bias. +* @sparse: The GPIO map is sparse (some GPIOs have npins == 0) */ struct msm_pinctrl_soc_data {const struct pinctrl_pin_desc *pins;
@@ -117,6 +118,7 @@ struct msm_pinctrl_soc_data {unsigned ngroups;unsigned ngpios;bool pull_no_keeper; +bool sparse; }; int msm_pinctrl_probe(struct platform_device *pdev,
Signature · 3 lines
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
PATCH v3 4/4 pinctrl: qcom: qdf2xxx: add support for new ACPI HID QCOM8002
In reply to Timur TabiNewer versions of the firmware for the Qualcomm Datacenter Technologies QDF2400 restricts access to a subset of the GPIOs on the TLMM. To prevent older kernels from accidentally accessing the restricted GPIOs, we change the ACPI HID for the TLMM block from QCOM8001 to QCOM8002, and introduce a new property "gpios". This property is an array of specific GPIOs that are accessible. When an older kernel boots on newer (restricted) firmware, it will fail to probe.
To implement the sparse GPIO map, we register all of the GPIOs, but set the pin count for the unavailable GPIOs to zero. The pinctrl-msm driver will block those unavailable GPIOs from being accessed.
To allow newer kernels to support older firmware, the driver retains support for QCOM8001.
--- drivers/pinctrl/qcom/pinctrl-qdf2xxx.c | 145 +++++++++++++++++++++++++-------- 1 file changed, 109 insertions(+), 36 deletions(-)
drivers/pinctrl/qcom/pinctrl-qdf2xxx.c +109 -36
@@ -38,68 +38,147 @@/* maximum size of each gpio name (enough room for "gpioXXX" + null) */ #define NAME_SIZE 8 +enum { +QDF2XXX_V1 , +QDF2XXX_V2 , +}; + +static const struct acpi_device_id qdf2xxx_acpi_ids[] = { + {"QCOM8001" ,QDF2XXX_V1 }, + {"QCOM8002" ,QDF2XXX_V2 }, + {}, +}; +MODULE_DEVICE_TABLE (acpi, qdf2xxx_acpi_ids); +static int qdf2xxx_pinctrl_probe (struct platform_device *pdev) { +const struct acpi_device_id *id = +acpi_match_device (qdf2xxx_acpi_ids, &pdev->dev);struct pinctrl_pin_desc *pins;struct msm_pingroup *groups;char (*names)[NAME_SIZE ];unsigned int i;u32 num_gpios; +unsigned int avail_gpios;/* The number of GPIOs we support */ +u16 *gpios;/* An array of supported GPIOs */ int ret;/* Query the number of GPIOs from ACPI */ ret =device_property_read_u32 (&pdev->dev,"num-gpios" , &num_gpios);if (ret <0 ) { -dev_warn (&pdev->dev,"missing num-gpios property\n" ); +dev_err (&pdev->dev,"missing 'num-gpios' property\n" );return ret; } -if (!num_gpios || num_gpios >MAX_GPIOS ) { -dev_warn (&pdev->dev,"invalid num-gpios property\n" ); +dev_err (&pdev->dev,"invalid 'num-gpios' property\n" );return -ENODEV ; } +/* +* The QCOM8001 HID contains only the number of GPIOs, and assumes +* that all of them are available. avail_gpios is the same as num_gpios. +* +* The QCOM8002 HID introduces the 'gpios' DSD, which lists +* specific GPIOs that the driver is allowed to access. +* +* The make the common code simpler, in both cases we create an +* array of GPIOs that are accessible. So for QCOM8001, that would +* be all of the GPIOs. +*/ +if (id->driver_data ==QDF2XXX_V1 ) { + avail_gpios = num_gpios; + + gpios =devm_kcalloc (&pdev->dev, avail_gpios,sizeof (gpios[0 ]), +GFP_KERNEL ); +if (!gpios) +return -ENOMEM ; + +for (i =0 ; i < avail_gpios; i++) + gpios[i] = i; + }else { +/* The number of GPIOs in the approved list */ + ret =device_property_read_u16_array (&pdev->dev,"gpios" , +NULL ,0 ); +if (ret <0 ) { +dev_err (&pdev->dev,"missing 'num-gpios' property\n" ); +return ret; + } +if (!ret || ret >MAX_GPIOS ) { +dev_err (&pdev->dev,"invalid 'num-gpios' property\n" ); +return -ENODEV ; + } + avail_gpios = ret; + + gpios =devm_kcalloc (&pdev->dev, avail_gpios,sizeof (gpios[0 ]), +GFP_KERNEL ); +if (!gpios) +return -ENOMEM ; + + ret =device_property_read_u16_array (&pdev->dev,"gpios" , gpios, + avail_gpios); +if (ret <0 ) { +dev_err (&pdev->dev,"could not read list of GPIOs\n" ); +return ret; + } + +/* +* Because we have a specific list of GPIOs, the GPIO map +* is 'sparse'. +*/ + qdf2xxx_pinctrl.sparse = true; + } + pins =devm_kcalloc (&pdev->dev, num_gpios,sizeof (struct pinctrl_pin_desc ),GFP_KERNEL ); groups =devm_kcalloc (&pdev->dev, num_gpios,sizeof (struct msm_pingroup ),GFP_KERNEL ); - names =devm_kcalloc (&pdev->dev, num_gpios,NAME_SIZE ,GFP_KERNEL ); + names =devm_kcalloc (&pdev->dev, avail_gpios,NAME_SIZE ,GFP_KERNEL );if (!pins || !groups || !names)return -ENOMEM ; +/* +* Initialize the array. GPIOs not listed in the 'gpios' array +* still need a number, but nothing else. +*/ for (i =0 ; i < num_gpios; i++) { -snprintf (names[i],NAME_SIZE ,"gpio%u" , i); - pins[i].number = i; - pins[i].name = names[i]; - - groups[i].npins =1 ; - groups[i].name = names[i]; groups[i].pins = &pins[i].number; + } - groups[i].ctl_reg =0x10000 * i; - groups[i].io_reg =0x04 +0x10000 * i; - groups[i].intr_cfg_reg =0x08 +0x10000 * i; - groups[i].intr_status_reg =0x0c +0x10000 * i; - groups[i].intr_target_reg =0x08 +0x10000 * i; - - groups[i].mux_bit =2 ; - groups[i].pull_bit =0 ; - groups[i].drv_bit =6 ; - groups[i].oe_bit =9 ; - groups[i].in_bit =0 ; - groups[i].out_bit =1 ; - groups[i].intr_enable_bit =0 ; - groups[i].intr_status_bit =0 ; - groups[i].intr_target_bit =5 ; - groups[i].intr_target_kpss_val =1 ; - groups[i].intr_raw_status_bit =4 ; - groups[i].intr_polarity_bit =1 ; - groups[i].intr_detection_bit =2 ; - groups[i].intr_detection_width =2 ; +/* Populate the entries that are meant to be exposes as GPIOs. */ +for (i =0 ; i < avail_gpios; i++) { +unsigned int gpio = gpios[i]; + + groups[gpio].npins =1 ; +snprintf (names[i],NAME_SIZE ,"gpio%u" , gpio); + pins[gpio].name = names[i]; + groups[gpio].name = names[i]; + + groups[gpio].ctl_reg =0x10000 * gpio; + groups[gpio].io_reg =0x04 +0x10000 * gpio; + groups[gpio].intr_cfg_reg =0x08 +0x10000 * gpio; + groups[gpio].intr_status_reg =0x0c +0x10000 * gpio; + groups[gpio].intr_target_reg =0x08 +0x10000 * gpio; + + groups[gpio].mux_bit =2 ; + groups[gpio].pull_bit =0 ; + groups[gpio].drv_bit =6 ; + groups[gpio].oe_bit =9 ; + groups[gpio].in_bit =0 ; + groups[gpio].out_bit =1 ; + groups[gpio].intr_enable_bit =0 ; + groups[gpio].intr_status_bit =0 ; + groups[gpio].intr_target_bit =5 ; + groups[gpio].intr_target_kpss_val =1 ; + groups[gpio].intr_raw_status_bit =4 ; + groups[gpio].intr_polarity_bit =1 ; + groups[gpio].intr_detection_bit =2 ; + groups[gpio].intr_detection_width =2 ; } +devm_kfree (&pdev->dev, gpios); + qdf2xxx_pinctrl.pins = pins; qdf2xxx_pinctrl.groups = groups; qdf2xxx_pinctrl.npins = num_gpios;
@@ -109,12 +188,6 @@ static int qdf2xxx_pinctrl_probe(struct platform_device *pdev)return msm_pinctrl_probe (pdev, &qdf2xxx_pinctrl); } -static const struct acpi_device_id qdf2xxx_acpi_ids[] = { - {"QCOM8001" }, - {}, -}; -MODULE_DEVICE_TABLE (acpi, qdf2xxx_acpi_ids); -static struct platform_driver qdf2xxx_pinctrl_driver = { .driver = { .name ="qdf2xxx-pinctrl" ,
Signature · 3 lines
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.