Message ID | 20220924080459.13084-1-krzysztof.kozlowski@linaro.org |
---|---|
Headers | show |
Series | pinctrl/arm64: qcom: continued - fix Qualcomm TLMM pinctrl schema warnings | expand |
On 25/09/2022 16:00, Stephan Gerhold wrote: >> + allOf: >> + - $ref: "qcom,tlmm-common.yaml#/$defs/qcom-tlmm-state" >> + - if: >> + properties: >> + pins: >> + pattern: "^gpio([0-9]|[1-9][0-9]|10[0-9]|11[0-7])$" >> + then: >> + required: >> + - function >> > > Is it possible to place this into qcom,tlmm-common.yaml? If the pattern > is only used to make "function" required for GPIOs, then it should not > matter if it matches just the prefix ("^gpio") or the exact set of > allowed GPIO numbers. The definition of the "pins" property will already > take care of validating those. Hm, very good idea. > > Or are there some Qcom SoCs where a GPIO without "function" is valid? Quick look at drivers says there is no such case. I can try adding it to common schema and look for errors. Best regards, Krzysztof
On Sat, 24 Sep 2022 10:04:40 +0200, Krzysztof Kozlowski wrote: > Certain pins, like SDcard related, do not have functions and such should > not be required. > > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > --- > .../bindings/pinctrl/qcom,msm8226-pinctrl.yaml | 12 ++++++++++-- > 1 file changed, 10 insertions(+), 2 deletions(-) > Reviewed-by: Rob Herring <robh@kernel.org>
On Sat, Sep 24, 2022 at 10:05 AM Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote: > This is the third patchset around Qualcomm pinctrl in recent days: > 1. First round of TLMM fixes: merged > 2. LPASS fixes: https://lore.kernel.org/linux-devicetree/20220922195651.345369-1-krzysztof.kozlowski@linaro.org/T/#t > 3. Second round of TLMM fixes: THIS PATCHSET Same thing with TLMM as LPASS! Stack up the bindings, send me pull requests, because I trust you. Yours, Linus Walleij