From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/4] soc: ti: add firmware file name as part of the driver
Date: Tue, 13 Oct 2015 16:32:43 +0200 [thread overview]
Message-ID: <5984319.ffuyRPpBNk@wuerfel> (raw)
In-Reply-To: <1444679211-823-3-git-send-email-m-karicheri2@ti.com>
On Monday 12 October 2015 15:46:49 Murali Karicheri wrote:
> Currently firmware file name is included in the DTS. This is not scalable
> as user has to change the DTS if they need upgrade to a new firmware.
> Instead, add the firmware file name in the driver itself. As long as there
> is no API change, new firmware upgrade is easy and require no driver
> change. User is expected to copy the firmware image to the file system
> and add a sym link to the new firmware for doing an upgrade. Driver add
> a array of firmware file names to search for the available firmware blobs.
> This scheme also prepare the driver for future changes to API if ever
> happens. In such case it is assumed that driver needs to change to
> accommodate the new firmware and new firmware file name will get added to
> the array.
>
> Also update the DT document to remove the firmware attribute and add
> description about firmware in the driver documentation.
>
> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Looks good.
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Murali Karicheri <m-karicheri2@ti.com>
Cc: corbet@lwn.net, ssantosh@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/4] soc: ti: add firmware file name as part of the driver
Date: Tue, 13 Oct 2015 16:32:43 +0200 [thread overview]
Message-ID: <5984319.ffuyRPpBNk@wuerfel> (raw)
In-Reply-To: <1444679211-823-3-git-send-email-m-karicheri2@ti.com>
On Monday 12 October 2015 15:46:49 Murali Karicheri wrote:
> Currently firmware file name is included in the DTS. This is not scalable
> as user has to change the DTS if they need upgrade to a new firmware.
> Instead, add the firmware file name in the driver itself. As long as there
> is no API change, new firmware upgrade is easy and require no driver
> change. User is expected to copy the firmware image to the file system
> and add a sym link to the new firmware for doing an upgrade. Driver add
> a array of firmware file names to search for the available firmware blobs.
> This scheme also prepare the driver for future changes to API if ever
> happens. In such case it is assumed that driver needs to change to
> accommodate the new firmware and new firmware file name will get added to
> the array.
>
> Also update the DT document to remove the firmware attribute and add
> description about firmware in the driver documentation.
>
> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Looks good.
next prev parent reply other threads:[~2015-10-13 14:32 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 19:46 [PATCH v2 0/4] soc: ti: knav_qmss: enable accumulator queue support Murali Karicheri
2015-10-12 19:46 ` Murali Karicheri
2015-10-12 19:46 ` Murali Karicheri
2015-10-12 19:46 ` [PATCH 1/4] Documentation: dt: soc: move driver description to a separate document Murali Karicheri
2015-10-12 19:46 ` Murali Karicheri
2015-10-12 19:46 ` Murali Karicheri
2015-10-13 14:42 ` Rob Herring
2015-10-13 14:42 ` Rob Herring
2015-10-13 15:44 ` Murali Karicheri
2015-10-13 15:44 ` Murali Karicheri
2015-10-13 17:28 ` Murali Karicheri
2015-10-13 17:28 ` Murali Karicheri
2015-10-13 17:28 ` Murali Karicheri
2015-10-13 18:01 ` Rob Herring
2015-10-13 18:01 ` Rob Herring
2015-10-13 18:21 ` Murali Karicheri
2015-10-13 18:21 ` Murali Karicheri
2015-10-12 19:46 ` [PATCH v2 2/4] soc: ti: add firmware file name as part of the driver Murali Karicheri
2015-10-12 19:46 ` Murali Karicheri
2015-10-12 19:46 ` Murali Karicheri
2015-10-13 14:32 ` Arnd Bergmann [this message]
2015-10-13 14:32 ` Arnd Bergmann
2015-10-13 14:38 ` Rob Herring
2015-10-12 19:46 ` [PATCH v2 3/4] ARM: dts: keystone: enable accumulator channels Murali Karicheri
2015-10-12 19:46 ` Murali Karicheri
2015-10-12 19:46 ` Murali Karicheri
2015-10-12 19:46 ` [PATCH 4/4] soc: ti: qmss: make acc queue support optional in the driver Murali Karicheri
2015-10-12 19:46 ` Murali Karicheri
2015-10-12 19:46 ` Murali Karicheri
2015-10-12 19:54 ` [PATCH v2 0/4] soc: ti: knav_qmss: enable accumulator queue support Murali Karicheri
2015-10-12 19:54 ` Murali Karicheri
2015-10-12 19:54 ` Murali Karicheri
2015-10-13 13:56 ` Murali Karicheri
2015-10-13 13:56 ` Murali Karicheri
2015-10-13 13:56 ` Murali Karicheri
2015-10-13 16:01 ` santosh shilimkar
2015-10-13 16:01 ` santosh shilimkar
2015-10-13 16:14 ` Murali Karicheri
2015-10-13 16:14 ` Murali Karicheri
2015-10-13 16:14 ` Murali Karicheri
2015-10-13 16:21 ` santosh shilimkar
2015-10-13 16:21 ` santosh shilimkar
2015-10-13 16:42 ` Murali Karicheri
2015-10-13 16:42 ` Murali Karicheri
2015-10-13 16:42 ` Murali Karicheri
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=5984319.ffuyRPpBNk@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.