LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Charles Mooney <charliemooney@google.com>
Cc: Ming Lei <ming.lei@canonical.com>,
	Dmitry Torokhov <dtor@chromium.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] firmware_class: Add firmware filename overrides
Date: Thu, 5 Mar 2015 09:39:35 -0800	[thread overview]
Message-ID: <9E515131-187A-4083-8054-A415B0E51105@holtmann.org> (raw)
In-Reply-To: <CAJ34Pp4UmqR2H02G+cngGcDoLEnFKNCAc-0L_NXARgEL5TRApg@mail.gmail.com>

Hi Charles,

> Specifically this was motivated by a situation where we have one
> device with a dual-sourced touchscreen. Both use the same driver but
> have different hardware & fw. Our FW updating software therefore,
> needs to be able to update with the correct FW and detect all this at
> runtime due to a read-only partition (so moving the firmware binaries
> around isn't really an option)
> Here the device has only one touchscreen at a time, but it isn't known
> until run-time which will be present.
> 
> So in this case the driver is serving the same function in each
> situation (running a touchscreen) but may be working with different
> hardware.
> 
> Another situation where I've personally wanted this functionality is
> on a device that uses the same touch driver for both a touchscreen and
> a touchpad on the same device. If the driver only grabs a copy of FW
> from, say, /lib/firmware/touch_fw.bin then you either need to move the
> firmware binaries around on disk to update either device, or have a
> change like this that allows you to override which filename it loads.
> The moving option is not viable if you're using a RO filesystem.

what is the actual problem here? We have drivers that load multiple firmware files and we have drivers that pick a different firmware depending on some parameters it reads from the device.

Seems this is all possible already at the moment with the existing framework. You just need to update the drivers to operate properly.

Regards

Marcel


  reply	other threads:[~2015-03-05 17:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 23:25 Charlie Mooney
2015-03-04 23:57 ` Greg KH
2015-03-05  0:48   ` Dmitry Torokhov
2015-03-05  8:14     ` Ming Lei
2015-03-05 17:29       ` Charles Mooney
2015-03-05 17:39         ` Marcel Holtmann [this message]
2015-03-05 17:52           ` Charles Mooney
2015-03-05 18:13             ` Marcel Holtmann
2015-03-05 18:20               ` Dmitry Torokhov
2015-03-05 19:11                 ` Marcel Holtmann
2015-03-05 19:14                   ` Dmitry Torokhov
2015-03-05 22:12                     ` Marcel Holtmann
2015-03-05 22:36                       ` Dmitry Torokhov
2015-03-06  1:27                         ` Ming Lei
2015-03-06 22:50                           ` Charles Mooney
2015-03-06 23:33                             ` Marcel Holtmann
2015-03-10 15:51                               ` Charles Mooney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9E515131-187A-4083-8054-A415B0E51105@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=charliemooney@google.com \
    --cc=dtor@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@canonical.com \
    --subject='Re: [PATCH] firmware_class: Add firmware filename overrides' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).