From: Florian Fainelli <f.fainelli@gmail.com>
To: Karl Beldan <karl.beldan@gmail.com>, linux-mtd@lists.infradead.org
Cc: bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org,
Brian Norris <computersforpeace@gmail.com>,
Kamal Dasu <kdasu.kdev@gmail.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Richard Weinberger <richard@nod.at>,
David Woodhouse <dwmw2@infradead.org>,
Marek Vasut <marek.vasut@gmail.com>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
Karl Beldan <karl.beldan+oss@gmail.com>
Subject: Re: [PATCH] brcmnand: Fix up the flash cache register offset for older controllers
Date: Wed, 5 Jul 2017 11:15:01 -0700 [thread overview]
Message-ID: <7f7804da-e431-f197-31b9-c98359b9151a@gmail.com> (raw)
In-Reply-To: <20170705174653.21797-1-karl.beldan+oss@gmail.com>
On 07/05/2017 10:46 AM, Karl Beldan wrote:
> From: Karl Beldan <karl.beldan-ext@sagemcom.com>
>
> Tested on BCM{63138,6838,63268} and cross checked with the various
> *_map_part.h which the brcmnand_regs_v* in brcmnand.c have historically
> been derived from.
BCM63138 is using a 7.0 controller, 6838 uses a 5.0 controller, but has
a separate flash cache register which does indeed end up at 0x400 bytes
off the main FLASH block, and finally 63268 does have a v4.0 controller
and the flash cache is also in a separate register that makes it end up
at 0x400.
Your change, as proposed would break chips like 7425 which use 5.0
controller with the flash cache at 0x200 bytes.
The binding describes an optional flash-cache register cell that you can
specify, so that's probably what you want to do here?
>
> Cc: Brian Norris <computersforpeace@gmail.com>
> Cc: Kamal Dasu <kdasu.kdev@gmail.com>
> Cc: Boris Brezillon <boris.brezillon@free-electrons.com>
> Cc: Richard Weinberger <richard@nod.at>
> Cc: David Woodhouse <dwmw2@infradead.org>
> Cc: Marek Vasut <marek.vasut@gmail.com>
> Cc: Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>
> Signed-off-by: Karl Beldan <karl.beldan-ext@sagemcom.com>
> ---
> drivers/mtd/nand/brcmnand/brcmnand.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mtd/nand/brcmnand/brcmnand.c b/drivers/mtd/nand/brcmnand/brcmnand.c
> index 7419c5c..e6371ff6 100644
> --- a/drivers/mtd/nand/brcmnand/brcmnand.c
> +++ b/drivers/mtd/nand/brcmnand/brcmnand.c
> @@ -250,7 +250,7 @@ static const u16 brcmnand_regs_v40[] = {
> [BRCMNAND_OOB_READ_10_BASE] = 0x130,
> [BRCMNAND_OOB_WRITE_BASE] = 0x30,
> [BRCMNAND_OOB_WRITE_10_BASE] = 0,
> - [BRCMNAND_FC_BASE] = 0x200,
> + [BRCMNAND_FC_BASE] = 0x400,
> };
>
> /* BRCMNAND v5.0 */
> @@ -280,7 +280,7 @@ static const u16 brcmnand_regs_v50[] = {
> [BRCMNAND_OOB_READ_10_BASE] = 0x130,
> [BRCMNAND_OOB_WRITE_BASE] = 0x30,
> [BRCMNAND_OOB_WRITE_10_BASE] = 0x140,
> - [BRCMNAND_FC_BASE] = 0x200,
> + [BRCMNAND_FC_BASE] = 0x400,
> };
>
> /* BRCMNAND v6.0 - v7.1 */
>
--
Florian
next prev parent reply other threads:[~2017-07-05 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 17:46 Karl Beldan
2017-07-05 18:15 ` Florian Fainelli [this message]
2017-07-05 18:18 ` Brian Norris
2017-07-05 20:57 ` Karl Beldan
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=7f7804da-e431-f197-31b9-c98359b9151a@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=karl.beldan+oss@gmail.com \
--cc=karl.beldan@gmail.com \
--cc=kdasu.kdev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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
Powered by JetHome