On 6/16/17 10:55 AM, Bjorn Andersson wrote:
npins are the number of "pins" handles by the TLMM, while ngpios are the
number of GPIO lines. I.e. npins >= ngpios and non platforms where we
control e.g. sdc properties you can see that npins > ngpios.
I'm talking about the 'npins' in struct msm_pingroup:
struct msm_pingroup {
const char *name;
const unsigned *pins;
unsigned npins;
Every client driver of pinctrl-msm sets this value to 1 for every group.
It's not an awesome solution for mobile either. But to solve this we
have two problems to solve;
1) as the XPU configuration isn't fixed we need to be dynamic or
configurable in some sensible way
I was planning on updating the TLMM ACPI node to include a property that
lists the acceptable GPIOs.
2) the pinctrl framework does have some support for sparse pin spaces,
but this would need to be extended to allow us to (easily) register a
sparse list of pins
I was hoping there would be a way in pinctrl-msm to tell the framework,
"Oh, you want to export this pin? Sorry, I forgot to tell you that it
doesn't exist."
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.
--
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
