public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Naga Sureshkumar Relli <nagasure@xilinx.com>
Cc: Helmut Grohne <h.grohne@intenta.de>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"Boris Brezillon" <Boris.Brezillon@bootlin.com>
Subject: Re: [LINUX, v8, 2/2] mtd: rawnand: pl353: Add basic driver for arm pl353 smc nand interface
Date: Thu, 17 May 2018 15:24:02 +0200	[thread overview]
Message-ID: <20180517152402.50187702@xps13> (raw)
In-Reply-To: <DM2PR02MB1418743DD67EAB0DBBA180D0AF860@DM2PR02MB1418.namprd02.prod.outlook.com>

Hi Naga,

On Fri, 4 May 2018 06:46:50 +0000, Naga Sureshkumar Relli
<nagasure@xilinx.com> wrote:

> Hi Miquel & Helmut,
> 
> Thanks for updating the latest changes.
> 
> > -----Original Message-----
> > From: Miquel Raynal [mailto:miquel.raynal@bootlin.com]
> > Sent: Thursday, May 3, 2018 7:56 PM
> > To: Helmut Grohne <h.grohne@intenta.de>
> > Cc: Naga Sureshkumar Relli <nagasure@xilinx.com>; linux-mtd@lists.infradead.org; Boris
> > Brezillon <Boris.Brezillon@bootlin.com>
> > Subject: Re: [LINUX, v8, 2/2] mtd: rawnand: pl353: Add basic driver for arm pl353 smc nand
> > interface
> > 
> > Hi Naga,
> > 
> > On Thu, 3 May 2018 14:56:01 +0200, Helmut Grohne <h.grohne@intenta.de>
> > wrote:
> >   
> > > On Wed, Mar 14, 2018 at 04:18:25PM +0530, Naga Sureshkumar Relli wrote:  
> > > > +	xnand->row_addr_cycles = nand_chip->onfi_params.addr_cycles & 0xF;
> > > > +	xnand->col_addr_cycles =
> > > > +				(nand_chip->onfi_params.addr_cycles >> 4) & 0xF;  
> > >
> > > Meanwhile onfi_params have been removed from the mainline and this
> > > patch no longer builds against v4.17-rc3. Can you resend a version
> > > that builds against with more recent kernels?  
> > 
> > Actually I'm not sure you need addr_cycles from the ONFI param page. What about non-
> > ONFI chips? Anyway you won't find this entry anymore as the param page is now freed after
> > probe.
> > 
> > I don't get why you need this though?
> > Maybe you should have a look at the NAND_ROW_ADDR_3 flag?  
> 
> The arm SMC pl353 controller operates in cmd phase and data phase.
> In cmd phase it requires number of address cycles, hence we are using this
> By reading from parameter page.
> DOC: http://infocenter.arm.com/help/topic/com.arm.doc.ddi0380g/DDI0380G_smc_pl350_series_r2p1_trm.pdf
> if you see table2-2 NAND AXI address setup, it describes the usage of cmd
> and data phases.
> If we remove this onfi_params, is there an alternative to write the number of address cycles filed in
> Cmd phase register? 
> Or can I use max value?, that means as per spec it supports max of 7 address cycles(it is a 3bit value).

In ->exec_op():
If your operation contains address cycles, you'll get the number with
nand_subop_get_num_addr_cyc(subop, op_id). You already retrieve
correctly that number from your ->exec_op() implementation. I don't
think you need anything else.

In ->ecc.read/write*() helpers:
The number of column cycles is 1 if mtd->writesize <= 512, otherwise
it is 2. The number of row cycles is 3 if the NAND_ROW_ADDR_3 flag is
present in chip->options, otherwise it is 2 (it won't change, just
check it once at probe time).

Thanks,
Miquèl

  reply	other threads:[~2018-05-17 13:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14 10:48 [LINUX PATCH v8 2/2] mtd: rawnand: pl353: Add basic driver for arm pl353 smc nand interface nagasureshkumarrelli
2018-03-19 22:37 ` Miquel Raynal
2018-03-23 14:58   ` Naga Sureshkumar Relli
2018-03-26 21:53     ` Miquel Raynal
2018-03-27  4:02       ` Naga Sureshkumar Relli
     [not found]     ` <a84185e1-2f67-7d15-209d-bd70d31f0ea4@ni.com>
2018-04-22 15:17       ` Miquel Raynal
2018-04-24 10:18         ` Naga Sureshkumar Relli
2018-05-03 12:56 ` [LINUX, v8, " Helmut Grohne
2018-05-03 14:25   ` Miquel Raynal
2018-05-04  6:46     ` Naga Sureshkumar Relli
2018-05-17 13:24       ` Miquel Raynal [this message]
2018-05-18  7:33         ` Naga Sureshkumar Relli

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=20180517152402.50187702@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=Boris.Brezillon@bootlin.com \
    --cc=h.grohne@intenta.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nagasure@xilinx.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