[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9ec3c26a-3b85-4bea-5a5b-de9ac570cfca@canonical.com>
Date: Tue, 15 Mar 2022 12:22:22 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Lee Jones <lee.jones@...aro.org>
Cc: Stephen Boyd <swboyd@...omium.org>,
Benson Leung <bleung@...omium.org>,
linux-kernel@...r.kernel.org, chrome-platform@...ts.linux.dev,
Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
Guenter Roeck <groeck@...omium.org>,
Douglas Anderson <dianders@...omium.org>,
Craig Hesling <hesling@...omium.org>,
Tom Hughes <tomhughes@...omium.org>,
Alexandru M Stan <amstan@...omium.org>
Subject: Re: [PATCH 1/2] dt-bindings: mfd: Add ChromeOS fingerprint binding
On 15/03/2022 12:10, Lee Jones wrote:
> On Tue, 15 Mar 2022, Krzysztof Kozlowski wrote:
>
>> On 15/03/2022 00:22, Stephen Boyd wrote:
>>> Add a binding to describe the fingerprint processor found on Chromeboks
>>> with a fingerprint sensor.
>>>
>>> Cc: Rob Herring <robh+dt@...nel.org>
>>> Cc: <devicetree@...r.kernel.org>
>>> Cc: Guenter Roeck <groeck@...omium.org>
>>> Cc: Douglas Anderson <dianders@...omium.org>
>>> Cc: Craig Hesling <hesling@...omium.org>
>>> Cc: Tom Hughes <tomhughes@...omium.org>
>>> Cc: Alexandru M Stan <amstan@...omium.org>
>>> Signed-off-by: Stephen Boyd <swboyd@...omium.org>
>>> ---
>>> .../bindings/mfd/google,cros-ec-fp.yaml | 89 +++++++++++++++++++
>>> 1 file changed, 89 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/mfd/google,cros-ec-fp.yaml
>>>
>>> diff --git a/Documentation/devicetree/bindings/mfd/google,cros-ec-fp.yaml b/Documentation/devicetree/bindings/mfd/google,cros-ec-fp.yaml
>>> new file mode 100644
>>> index 000000000000..05d2b2b9b713
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/mfd/google,cros-ec-fp.yaml
>>> @@ -0,0 +1,89 @@
>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>> +%YAML 1.2
>>> +---
>>> +$id: http://devicetree.org/schemas/mfd/google,cros-ec-fp.yaml#
>>
>> Why is this in the MFD directory? Is it really a Multi Function Device?
>> Description is rather opposite. You also did not CC MFD maintainer.
>
> A lot of the ChromeOS Embedded Controller support used to be located
> in MFD. There are still remnants, but most was moved to
> drivers/platform IIRC.
>
> Please see: drivers/mfd/cros_ec_dev.c
Yes, I know, that part is a MFD. But why the fingerprint controller part
is MFD? To me it is closer to input device.
Best regards,
Krzysztof
Powered by blists - more mailing lists