[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y7Ww67pIyjeLKBE7@smile.fi.intel.com>
Date: Wed, 4 Jan 2023 19:01:31 +0200
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Martin Zaťovič <m.zatovic1@...il.com>
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
mani@...nel.org, hemantk@...eaurora.org, quic_jhugo@...cinc.com,
andersson@...nel.org, Michael.Srba@...nam.cz, arnd@...db.de,
dipenp@...dia.com, bvanassche@....org, iwona.winiarska@...el.com,
ogabbay@...nel.org, tzimmermann@...e.de, fmdefrancesco@...il.com,
jason.m.bills@...ux.intel.com, jae.hyun.yoo@...ux.intel.com,
gregkh@...uxfoundation.org, krzysztof.kozlowski+dt@...aro.org,
robh+dt@...nel.org
Subject: Re: [PATCH 3/3] wiegand: add Wiegand GPIO bit-banged controller
driver
On Wed, Jan 04, 2023 at 06:59:00PM +0200, Andy Shevchenko wrote:
> On Wed, Jan 04, 2023 at 02:34:14PM +0100, Martin Zaťovič wrote:
...
> > +What: /sys/devices/platform/.../wiegand-gpio-attributes/format
> > +What: /sys/devices/platform/.../wiegand-gpio-attributes/payload_len
> Why all these attributes? What is special about them and how they are specific
> to the hardware in question?
>
> To me it all sounds like layering violation: a GPIO driver that has to be
> generic provides a complete custom ABIs which we usually put on the upper
> layer (in the kernel as a child driver or in the user space).
Okay, it seems the consumer driver.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists