public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Aaron Sierra <asierra@xes-inc.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-mtd@lists.infradead.org,
	Brian Norris <computersforpeace@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Prabhakar Kushwaha <prabhakar@freescale.com>
Subject: Re: [PATCH v3] fsl_ifc: Support all 8 IFC chip selects
Date: Tue, 26 Aug 2014 18:21:02 -0500	[thread overview]
Message-ID: <1409095262.6510.104.camel@snotra.buserror.net> (raw)
In-Reply-To: <264587069.465984.1409095113566.JavaMail.zimbra@xes-inc.com>

On Tue, 2014-08-26 at 18:18 -0500, Aaron Sierra wrote:
> Freescale's QorIQ T Series processors support 8 IFC chip selects
> within a memory map backward compatible with previous P Series
> processors which supported only 4 chip selects.
> 
> Signed-off-by: Aaron Sierra <asierra@xes-inc.com>
> ---
>  Note: v1 and v2 patches were submitted to Linux PPC mailing list
> 
>  v3: * IFC version register read only once
>      * fsl_ifc_version and fsl_ifc_bank_count inline functions replaced
>        by version and banks members of struct fsl_ifc_ctrl
>      * IFC version print moved from fsl_ifc_nand.c to fsl_ifc.c
> 
>  drivers/memory/fsl_ifc.c        | 13 +++++++++++--
>  drivers/mtd/nand/fsl_ifc_nand.c | 10 ++++------
>  include/linux/fsl_ifc.h         | 21 ++++++++++++++++-----
>  3 files changed, 31 insertions(+), 13 deletions(-)

Acked-by: Scott Wood <scottwood@freescale.com>

-Scott

  reply	other threads:[~2014-08-26 23:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1560704347.463292.1409093361997.JavaMail.zimbra@xes-inc.com>
2014-08-26 23:18 ` [PATCH v3] fsl_ifc: Support all 8 IFC chip selects Aaron Sierra
2014-08-26 23:21   ` Scott Wood [this message]
2014-11-05 22:54   ` Brian Norris

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=1409095262.6510.104.camel@snotra.buserror.net \
    --to=scottwood@freescale.com \
    --cc=arnd@arndb.de \
    --cc=asierra@xes-inc.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=prabhakar@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox