Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Tue, 06 Aug 2019 22:54:48 +0300
User-Agent: K-9 Mail for Android
In-Reply-To: <CACRpkdaTmxQn2Z=vD6nyqk-iXCFrnCG1xpkXwO3-+sazOhGBvw@mail.gmail.com>
References: <20190803133436.15016-1-rfried.dev@gmail.com> <CACRpkdYEdQdk62bWJ2=i2Mbvpz3kwL=9bnMoxksFsTgAHRh68w@mail.gmail.com> <CACRpkdaTmxQn2Z=vD6nyqk-iXCFrnCG1xpkXwO3-+sazOhGBvw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PATCH] gpiolib: Take MUX usage into account
To:     Linus Walleij <linus.walleij@linaro.org>
CC:     Bartosz Golaszewski <bgolaszewski@baylibre.com>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Stefan Wahren <stefan.wahren@i2se.com>
From:   Ramon Fried <rfried.dev@gmail.com>
Message-ID: <2F7B6E95-045E-4F57-B2CB-858BEE298986@gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


On August 6, 2019 4:11:27 PM GMT+03:00, Linus Walleij <linus=2Ewalleij@lin=
aro=2Eorg> wrote:
>On Tue, Aug 6, 2019 at 3:04 PM Linus Walleij <linus=2Ewalleij@linaro=2Eor=
g>
>wrote:
>> On Sat, Aug 3, 2019 at 3:34 PM Ramon Fried <rfried=2Edev@gmail=2Ecom>
>wrote:
>>
>> > From: Stefan Wahren <stefan=2Ewahren@i2se=2Ecom>
>> >
>> > The user space like gpioinfo only see the GPIO usage but not the
>> > MUX usage (e=2Eg=2E I2C or SPI usage) of a pin=2E As a user we want t=
o
>know which
>> > pin is free/safe to use=2E So take the MUX usage of strict pinmux
>controllers
>> > into account to get a more realistic view for ioctl
>GPIO_GET_LINEINFO_IOCTL=2E
>> >
>> > Signed-off-by: Stefan Wahren <stefan=2Ewahren@i2se=2Ecom>
>> > Tested-By: Ramon Fried <rfried=2Edev@gmail=2Ecom>
>> > Signed-off-by: Ramon Fried <rfried=2Edev@gmail=2Ecom>
>> > ---
>> > Sending Stefan's RFC as patch, as I tested it and it seems to work,
>> > additionally, an accompanying fix was made by me to gpiolibd to fix
>a
>> > display error of the actual result:
>> > https://patchwork=2Eozlabs=2Eorg/patch/1139923/
>>
>> This is mostly fine, some style nits so I fixed it up when
>> applying=2E
>
>Ooops no=2E It needs a deeper rework in accordance to my comments
>last time it was posted=2E Please read this reply to Stefan's patch
>and address the comments:
>
NP, I'll try to address these in a new patch=2E=20
Thanks=2E=20
Ramon=20
>https://lore=2Ekernel=2Eorg/linux-gpio/CACRpkdb5DjAMRYkT+b0U6HVk7E6ccLT79=
-LB=3DQGQWWtE17aPUg@mail=2Egmail=2Ecom/
>
>Yours,
>Linus Walleij

--=20
Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E