diff options
| author | Sven Eckelmann <sven.eckelmann@openmesh.com> | 2018-04-16 13:51:15 +0200 |
|---|---|---|
| committer | Mathias Kresin <dev@kresin.me> | 2018-04-23 22:07:22 +0200 |
| commit | c6aac196b80039ae1716b9af635c06992e62171f (patch) | |
| tree | 95cde348a802030474f4f67eef32e09a207a2d57 /scripts/om-fwupgradecfg-gen.sh | |
| parent | e6bd568051c7ca77a59783fe50203f6e2a427f19 (diff) | |
| download | mtk-20170518-c6aac196b80039ae1716b9af635c06992e62171f.zip mtk-20170518-c6aac196b80039ae1716b9af635c06992e62171f.tar.gz mtk-20170518-c6aac196b80039ae1716b9af635c06992e62171f.tar.bz2 | |
ipq40xx: fix gpio-hog related boot issues
The pinctrl initialization fails with the MSM pinctrl code and gpio-hogs
because either the gpio ranges are not yet initialized (missing gpio-range
in DT) or that the msm driver unconditionally tries to re-initializes the
ranges (gpio-range in DT).
To allow gpio-hogs and similar early-boot gpio code, the gpio-ranges must
be in the device tree and the pinctrl-msm code must check whether the range
was already initialized by the DT.
Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
[drop changes to unrelated dtsi files, refresh patches]
Signed-off-by: Mathias Kresin <dev@kresin.me>
Diffstat (limited to 'scripts/om-fwupgradecfg-gen.sh')
0 files changed, 0 insertions, 0 deletions