linux-kernel - Re: [PATCH 1/2] i2c: hisi: Add generic GPIO bus recovery support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5de8e304-05b7-48ec-6b8f-e1f856e86697@huawei.com>
Date:   Tue, 8 Feb 2022 10:15:44 +0800
From:   Yicong Yang <yangyicong@...wei.com>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Yicong Yang <yangyicong@...ilicon.com>
CC:     <jarkko.nikula@...ux.intel.com>, <mika.westerberg@...ux.intel.com>,
        <wsa@...nel.org>, <linux-i2c@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <prime.zeng@...ilicon.com>,
        <linuxarm@...wei.com>, <irina.tirdea@...el.com>,
        <linus.walleij@...aro.org>, <linux-gpio@...r.kernel.org>
Subject: Re: [PATCH 1/2] i2c: hisi: Add generic GPIO bus recovery support

[ +cc pinctrl list for visible ]

Hi Andy,

Thanks for the reply.

On 2022/2/7 19:20, Andy Shevchenko wrote:
> On Mon, Feb 07, 2022 at 01:17:49PM +0200, Andy Shevchenko wrote:
>> On Tue, Jan 25, 2022 at 08:49:29PM +0800, Yicong Yang wrote:
>>> Add generic GPIO bus recovery support for i2c-hisi driver
>>> by registering the recovery information with core provided
>>> i2c_generic_scl_recovery() method.
>>>
>>> As the SCL/SDA pins are multiplexed with GPIO, we need to
>>> switch the pins mux to GPIO before recovery and switch back
>>> after recovery. It's implemented by the ACPI method in
>>> the i2c_bus_recovery_info->{prepare,unprepare}_recovery()
>>> method.
>>
>> NAK.
>>
>> ACPI has its own resources for that. What is missed is the layer between ACPI
>> and pin control.
> 

I think that's where the problem is and why we use this approach. When I looked into
devm_pinctrl_get(), it stops when fails to retrieve the pin info from device tree.
So I cannot use it on our ACPI server for the pinmux.

I looked into the history that Irina raised an RFC for adding the ACPI support in pinctrl[1],
but at that time seems it lacks some standard support. But maybe now we can support it?

But based on the current situation maybe the implementation of this patch suits best.
And currently we don't have a pinctrl driver for doing the multiplexing (though I think it's
easy to add one but maybe only configures 2 pins for now).

[1] https://lore.kernel.org/all/CACRpkdbj==q5wp2Z5-ZXkbfeXa4y+beLF_3YN-vS3CtyAKGwkg@mail.gmail.com/

Thanks,
Yicong

> To be more precise,
> 
> https://uefi.org/specs/ACPI/6.4/19_ASL_Reference/ACPI_Source_Language_Reference.html?highlight=pinfunction#pinconfig-pin-configuration-descriptor-macro
> 
> https://uefi.org/specs/ACPI/6.4/19_ASL_Reference/ACPI_Source_Language_Reference.html?highlight=pinfunction#pinfunction-pin-function-descriptor-macro
> 
> https://uefi.org/specs/ACPI/6.4/19_ASL_Reference/ACPI_Source_Language_Reference.html?highlight=pinfunction#pingroup-pin-group-descriptor-macro
> 
> https://uefi.org/specs/ACPI/6.4/19_ASL_Reference/ACPI_Source_Language_Reference.html?highlight=pinfunction#pingroupconfig-pin-group-configuration-descriptor-macro
>