Re: Sparse GPIO maps with pinctrl-msm.c?

[Timur Tabi <timur@xxxxxxxxxxxxxx>]

On Tue, Jun 13, 2017 at 6:35 PM, Timur Tabi <timur@xxxxxxxxxxxxxx> wrote:
>
> Is there a way, in pinctrl-msm, to specify a GPIO that doesn't
> actually exist, and therefore should never be exported?

Follow-up question:

In pinctrl-msm, how do pin groups support multiple pins?

struct msm_pingroup {
    const char *name;
    const unsigned *pins;
    unsigned npins;

Here I can specify an array of pins.  However, I can't see from the
code how it would be possible to support more than one pin.  In fact,
all of the drivers that call msm_pinctrl_probe() always set 'npins' to
1 in every group.

Each group represents one GPIO in the TLMM.  All of the TLMM register
definitions are associated with a group, not a pin.  Frankly, it seems
that we should stop pretending that npins can be anything other than
1, and change all the code accordingly.

-- 
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html