[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdZp2htovazproVH9eeAr6bwE32hP4w2=jV-M68B5p0CNg@mail.gmail.com>
Date: Sun, 24 Jul 2016 16:29:23 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Andrew Duggan <aduggan@...aptics.com>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Linux Input <linux-input@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jiri Kosina <jikos@...nel.org>,
Benjamin Tissoires <benjamin.tissoires@...hat.com>,
Vincent Huang <vincent.huang@...synaptics.com>,
Nick Dyer <nick@...anahar.org>,
Chris Healy <cphealy@...il.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Mark Rutland <mark.rutland@....com>,
Rob Herring <robh@...nel.org>
Subject: Re: [PATCH v3 3/8] Input: synaptics-rmi4: Add dribble and palm
gesture parameters to device tree
On Fri, Jul 22, 2016 at 8:32 PM, Andrew Duggan <aduggan@...aptics.com> wrote:
> If the firmware was configured incorrectly it might just be easier to add a
> device tree entry. This would allow platform owners to make the change
> without having to get Synaptics involved or have access to our tools.
> Customers have also requested using the same module and firmware across
> multiple platforms. Tracking which firmware is on which part would create an
> additional support burden and not all platforms have an automated way of
> checking and updating firmware versions in the event that a system is build
> with a module which has the incorrect firmware.
I think it's a valid argument.
That said, the world needs more of
drivers/scsi/aic7xxx
That driver has the firmware generation, including an assembler, in the
kernel tree. Pretty cool eh?
(I know it is a thick thing to ask, just want to give you an idea of what
is possible...)
Yours,
Linus Walleij
Powered by blists - more mailing lists