public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/3] Keystone SOC driver updates for 4.4
Date: Thu, 08 Oct 2015 17:41:13 +0200	[thread overview]
Message-ID: <5870815.PiO7rCVXjJ@wuerfel> (raw)
In-Reply-To: <1444151960-4941-1-git-send-email-ssantosh@kernel.org>

On Tuesday 06 October 2015 10:19:18 Santosh Shilimkar wrote:
> Couple of patches for ARM Keystone SOC drivers
>         - irq affinity bug fix
>         - display the firmware name
> 
> ----------------------------------------------------------------
> Murali Karicheri (2):
>       soc: ti: reset irq affinity before freeing irq
>       soc: ti: display firmware file name as part of boot log
> 
>  .../bindings/soc/ti/keystone-navigator-qmss.txt      | 20 +++++++++++++++++++-
>  drivers/soc/ti/knav_qmss_acc.c                       |  4 ++++
>  drivers/soc/ti/knav_qmss_queue.c                     |  3 +++
>  3 files changed, 26 insertions(+), 1 deletion(-)

The new text you add to the binding document doesn't really seem to
belong in there, so I'm not pulling this until we've discussed how
this should be better handled.

Ideally, the firmware should just get merged into the linux-firmware.git
tree.

Regarding the method of storing the firmware file name in DT, we
recently had a longer discussion about that and basically concluded
that this doesn't work for most devices, in particular when the
communication between the driver and the firmware uses an interface
that is not 100% stable and can change depending on the firmware
blob.

Can you guarantee that there will never be changes to the interface?
If not, we should try to come up with a better mechanism here, and
only provide the current method for backwards compatibility.

	Arnd

  parent reply	other threads:[~2015-10-08 15:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 17:19 [GIT PULL 1/3] Keystone SOC driver updates for 4.4 Santosh Shilimkar
2015-10-06 17:19 ` [GIT PULL 2/3] Keystone config " Santosh Shilimkar
2015-10-08 15:34   ` Arnd Bergmann
2015-10-06 17:19 ` [GIT PULL 3/3] Kestone DTS " Santosh Shilimkar
2015-10-08 15:31   ` Arnd Bergmann
2015-10-08 15:41 ` Arnd Bergmann [this message]
2015-10-08 16:25   ` [GIT PULL 1/3] Keystone SOC driver " santosh.shilimkar at oracle.com
2015-10-08 18:50     ` Arnd Bergmann
2015-10-08 19:20       ` santosh.shilimkar at oracle.com
2015-10-08 19:29         ` Arnd Bergmann
2015-10-08 20:35           ` santosh shilimkar
2015-10-08 16:47   ` Murali Karicheri
2015-10-08 19:16     ` Arnd Bergmann
2015-10-09 14:48       ` Karicheri, Muralidharan
2015-10-09 15:09       ` Karicheri, Muralidharan
2015-10-09 15:21         ` Arnd Bergmann
2015-10-09 15:32           ` santosh shilimkar
2015-10-09 18:54           ` Karicheri, Muralidharan
2015-10-12 15:06             ` Murali Karicheri
2015-10-12 19:56               ` 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=5870815.PiO7rCVXjJ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox