public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property
Date: Mon, 4 Jul 2016 11:12:07 -0500	[thread overview]
Message-ID: <20160704161207.GA4592@rob-hp-laptop> (raw)
In-Reply-To: <b18cd232-711a-b617-2f09-09c4bdf2c3c4@broadcom.com>

On Fri, Jul 01, 2016 at 10:17:37AM +0200, Arend Van Spriel wrote:
> 
> 
> On 1-7-2016 4:08, Rob Herring wrote:
> > On Wed, Jun 29, 2016 at 04:04:31PM +0200, Hans de Goede wrote:
> >> Add a brcm,nvram_file_name dt property to allow overruling the default
> >> nvram filename for sdio devices. The idea is that we can specify a
> >> board specific nvram file, e.g. brcmfmac43362-ap6210.txt for boards
> >> with an ap6210 wifi sdio module and ship this in linux-firmware, so
> >> that wifi will work out of the box, without requiring users to find
> >> and then manually install the right nvram file for their board.
> > 
> > What about putting its contents directly into DT? It's just text 
> > key/value pairs so it would match up well.
> 
> It would be an option, but I have no clue how to dig up documentation of
> these key,value pairs. The file is typically obtained from a wifi module
> vendor which would need to be converted to DT format, ie. prefix with
> "brcm," etc. From driver perspective this would mean it need to know
> keys. Currently, it just takes the file contents and sends it to the device.

Okay, if it is opaque, then probably best to treat as firmware and not 
change it.

Rob

      parent reply	other threads:[~2016-07-04 16:12 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 14:04 [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property Hans de Goede
2016-06-29 14:04 ` [PATCH 2/4] ARM: dts: sun7i-a20-cubietruck: Set brcm,nvram_file_name Hans de Goede
2016-06-29 17:01   ` [PATCH 2/4] ARM: dts: sun7i-a20-cubietruck: Set brcm, nvram_file_name Kalle Valo
2016-06-29 18:01     ` [linux-sunxi] Re: [PATCH 2/4] ARM: dts: sun7i-a20-cubietruck: Set brcm,nvram_file_name Hans de Goede
2016-06-29 14:04 ` [PATCH 3/4] ARM: dts: sun7i-a20-wits-pro-a20-dkt: Set brcm, nvram_file_name Hans de Goede
2016-06-29 14:04 ` [PATCH 4/4] ARM: dts: sun5i-a10s-auxtek-t004: " Hans de Goede
2016-06-29 14:42 ` [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property Jonas Gorski
2016-06-29 15:16   ` Hans de Goede
2016-06-29 17:00     ` Kalle Valo
2016-06-29 18:01       ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Hans de Goede
2016-06-29 18:51         ` Arend Van Spriel
2016-06-29 18:57           ` Arend Van Spriel
2016-06-30  8:50             ` Kalle Valo
2016-06-29 19:33           ` Arnd Bergmann
2016-06-29 19:54             ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Priit Laes
2016-06-29 20:07               ` [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm, nvram_file_name " Arnd Bergmann
2016-06-30  9:02               ` Kalle Valo
2016-06-30  9:50                 ` Hans de Goede
2016-06-30  9:58                   ` Kalle Valo
2016-06-30 10:04                     ` Hans de Goede
2016-06-30 10:18                       ` Jonas Gorski
2016-06-30 10:25                         ` Hans de Goede
2016-06-30 11:31                           ` Arnd Bergmann
2016-06-30 19:23                             ` Arend Van Spriel
2016-07-01  8:51                               ` Arnd Bergmann
2016-07-01  8:58                               ` Jonas Gorski
2016-07-02  6:59                                 ` Kalle Valo
2016-07-02 18:20                                 ` Arend Van Spriel
2016-07-02 21:30                                   ` Arnd Bergmann
2016-07-04  8:41                                     ` Arend Van Spriel
2016-07-04  8:55                                       ` Arnd Bergmann
2016-07-04  9:08                                         ` Arend Van Spriel
2016-07-04 14:54                                           ` Arnd Bergmann
2016-07-04 18:36                                             ` Arend van Spriel
2016-07-05 13:43                                               ` Arnd Bergmann
2016-07-06  8:08                                                 ` Arend Van Spriel
2016-07-06 13:42                                                   ` Arnd Bergmann
2016-07-06 19:19                                                     ` Arend Van Spriel
2016-07-07  8:46                                                       ` Arnd Bergmann
2016-07-07  9:16                                                         ` Arend Van Spriel
2016-07-07  9:24                                                           ` Arnd Bergmann
2016-07-17 21:45                                                         ` Rob Herring
2016-07-18  7:51                                                           ` Arend Van Spriel
2016-06-30  8:46           ` Kalle Valo
2016-06-30  9:49             ` Hans de Goede
2016-06-30  9:53           ` Hans de Goede
2016-07-01  2:08 ` [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name " Rob Herring
2016-07-01  8:17   ` Arend Van Spriel
2016-07-01  9:20     ` Arnd Bergmann
2016-07-04 16:12     ` Rob Herring [this message]

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=20160704161207.GA4592@rob-hp-laptop \
    --to=robh@kernel.org \
    --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