On 11/17/2017 03:42 PM, Stephen Boyd wrote:
Patch 1 prevents gpiolib from accessing GPIOs that haven't been
properly requested.
Patch 2 adds an infrastructure for sparse GPIO maps
Patch 3 updates pinctrl-msm to use that expose that new infrastructure
Patch 4 updates pinctrl-qdf2xxx to work with the new feature in pinctrl-msm
Ok. What path doesn't request the gpio though? If we don't have a
path that fails to request the gpio before using it then I don't
see the need for this patch.
Sorry, I don't understand your question. Patches 2-4 are all about
creating a sparse GPIO map. All patch 1 does is stop initializing all
the GPIOs with an initial direction.
--
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
