On Tue, Jan 11, 2022 at 11:05 PM Douglas Anderson <dianders@xxxxxxxxxxxx> wrote: > If the drive-strength isn't specified in the device tree then it > doesn't actually default to 2. Instead, it defaults to whatever the > heck the BIOS left it at. If the BIOS doesn't touch it then that means > it's whatever the heck the initial state of the pin was when the SoC > booted. > > Reported-by: Matthias Kaehlcke <mka@xxxxxxxxxxxx> > Signed-off-by: Douglas Anderson <dianders@xxxxxxxxxxxx> Patch applied. Yours, Linus Walleij
Re: [PATCH] dt-bindings: pinctrl: drive-strength doesn't default to 2 if unspecified
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] dt-bindings: pinctrl: drive-strength doesn't default to 2 if unspecified
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Sun, 16 Jan 2022 01:58:43 +0100
- In-reply-to: <20220111140519.1.Ie2662d6289af1e9758b14b37149703c846d5f509@changeid>
- References: <20220111140519.1.Ie2662d6289af1e9758b14b37149703c846d5f509@changeid>
- References:
- [PATCH] dt-bindings: pinctrl: drive-strength doesn't default to 2 if unspecified
- From: Douglas Anderson
- [PATCH] dt-bindings: pinctrl: drive-strength doesn't default to 2 if unspecified
- Prev by Date: Re: [PATCH v2 24/28] dt-bindings: pinctrl: samsung: convert to dtschema
- Next by Date: Re: [PATCH] pinctrl: cherryview: Trigger hwirq0 for interrupt-lines without a mapping
- Previous by thread: Re: [PATCH] dt-bindings: pinctrl: drive-strength doesn't default to 2 if unspecified
- Next by thread: [GIT PULL] pin control changes for v5.17
- Index(es):
 |