> Hmm... Should be 0x105, otherwise 2 is an argument. > Can you confirm it's for real 0x205? Ah yes, you're right (I had the 2 in my head having converted it from the decimal 261) > Fixing the driver would be the best. > Thanks for the report, I'm on it! Fantastic, thank you! - Jamie
Re: Specifying a valid pullup value for pinctrl_intel from an ACPI table
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: Specifying a valid pullup value for pinctrl_intel from an ACPI table
- From: "Jamie McClymont" <jamie@xxxxxxxxxx>
- Date: Sat, 10 Oct 2020 11:57:08 +1300
- In-reply-to: <CAHp75Vd-P56=4PibajRcdnniy2pN6ZXoUP=FiJ1enrFzxKkojg@mail.gmail.com>
- References: <7102c0df-8d8b-4ef8-babf-a920ff11bcf8@www.fastmail.com> <CAHp75Vd-P56=4PibajRcdnniy2pN6ZXoUP=FiJ1enrFzxKkojg@mail.gmail.com>
- User-agent: Cyrus-JMAP/3.3.0-407-g461656c-fm-20201004.001-g461656c6
- Follow-Ups:
- Re: Specifying a valid pullup value for pinctrl_intel from an ACPI table
- From: Andy Shevchenko
- Re: Specifying a valid pullup value for pinctrl_intel from an ACPI table
- References:
- Specifying a valid pullup value for pinctrl_intel from an ACPI table
- From: Jamie McClymont
- Re: Specifying a valid pullup value for pinctrl_intel from an ACPI table
- From: Andy Shevchenko
- Specifying a valid pullup value for pinctrl_intel from an ACPI table
- Prev by Date: Re: [GIT PULL] late GPIO fixes for v5.9
- Next by Date: Configuring bias on an APCI GpioInt
- Previous by thread: Re: Specifying a valid pullup value for pinctrl_intel from an ACPI table
- Next by thread: Re: Specifying a valid pullup value for pinctrl_intel from an ACPI table
- Index(es):
 |