From: Florian Fainelli <f.fainelli@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
"open list:BROADCOM BCM5301X ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: BCM5301X: Enable SPI-NOR on dual flash devices
Date: Wed, 1 Jun 2016 12:26:33 -0700 [thread overview]
Message-ID: <574F36E9.6030400@gmail.com> (raw)
In-Reply-To: <1461740704-21501-1-git-send-email-zajec5@gmail.com>
On 04/27/2016 12:05 AM, Rafał Miłecki wrote:
> Commit 1b47b98acce2 ("ARM: BCM5301X: Add DT entry for SPI controller and
> NOR flash") enabled SPI-NOR device on routers using serial flash only.
> However there are also devices with two flash memories:
> 1) Small SPI attached flash used mostly for booting
> 2) Bigger NAND used mostly for storing firmware
> On such devices we still need SPI-NOR e.g. to access NVRAM data.
>
> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
Applied, thanks!
--
Florian
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
"open list:BROADCOM BCM5301X ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: BCM5301X: Enable SPI-NOR on dual flash devices
Date: Wed, 1 Jun 2016 12:26:33 -0700 [thread overview]
Message-ID: <574F36E9.6030400@gmail.com> (raw)
In-Reply-To: <1461740704-21501-1-git-send-email-zajec5@gmail.com>
On 04/27/2016 12:05 AM, Rafał Miłecki wrote:
> Commit 1b47b98acce2 ("ARM: BCM5301X: Add DT entry for SPI controller and
> NOR flash") enabled SPI-NOR device on routers using serial flash only.
> However there are also devices with two flash memories:
> 1) Small SPI attached flash used mostly for booting
> 2) Bigger NAND used mostly for storing firmware
> On such devices we still need SPI-NOR e.g. to access NVRAM data.
>
> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
Applied, thanks!
WARNING: multiple messages have this Message-ID (diff)
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: BCM5301X: Enable SPI-NOR on dual flash devices
Date: Wed, 1 Jun 2016 12:26:33 -0700 [thread overview]
Message-ID: <574F36E9.6030400@gmail.com> (raw)
In-Reply-To: <1461740704-21501-1-git-send-email-zajec5@gmail.com>
On 04/27/2016 12:05 AM, Rafa? Mi?ecki wrote:
> Commit 1b47b98acce2 ("ARM: BCM5301X: Add DT entry for SPI controller and
> NOR flash") enabled SPI-NOR device on routers using serial flash only.
> However there are also devices with two flash memories:
> 1) Small SPI attached flash used mostly for booting
> 2) Bigger NAND used mostly for storing firmware
> On such devices we still need SPI-NOR e.g. to access NVRAM data.
>
> Signed-off-by: Rafa? Mi?ecki <zajec5@gmail.com>
Applied, thanks!
--
Florian
next prev parent reply other threads:[~2016-06-01 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 7:05 [PATCH] ARM: BCM5301X: Enable SPI-NOR on dual flash devices Rafał Miłecki
2016-04-27 7:05 ` Rafał Miłecki
2016-04-27 7:05 ` Rafał Miłecki
2016-06-01 19:26 ` Florian Fainelli [this message]
2016-06-01 19:26 ` Florian Fainelli
2016-06-01 19:26 ` Florian Fainelli
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=574F36E9.6030400@gmail.com \
--to=f.fainelli@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=hauke@hauke-m.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=zajec5@gmail.com \
/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.