[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD2FfiE+VFa+7sHQg=LGkBy556msNyyFUhmWW_cAfZd0V4DPYQ@mail.gmail.com>
Date: Wed, 8 May 2024 09:39:41 +0100
From: Richard Hughes <hughsient@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>, Jeff LaBundy <jeff@...undy.com>,
Hans de Goede <hdegoede@...hat.com>, Charles Wang <charles.goodix@...il.com>, hadess@...ess.net,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
neil.armstrong@...aro.org
Subject: Re: [PATCH] Input: goodix-berlin - Add sysfs interface for reading
and writing touch IC registers
On Wed, 8 May 2024 at 03:37, Mark Brown <broonie@...nel.org> wrote:
> The other model I've seen used BTW is to expose a MTD device, if the
> device actually looks like a MTD device (perhaps even is just a flash
> that's fairly directly exposed) that minimises the kernel code quite
> well.
If it helps, fwupd already uses mtd for other devices too, although at
the moment we're using it only for system firmware -- e.g. intel-spi
style. The MTD subsystem doesn't give fwupd much info about the
{removable} device itself, and that can pose a problem unless you
start using heuristics about the parent device to match firmware to
the mtd device.
Richard.
Powered by blists - more mailing lists