From: Martin Kaiser <martin@kaiser.cx>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Boris Brezillon <boris.brezillon@bootlin.com>,
David Woodhouse <dwmw2@infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] mtd: rawnand: mxc: set spare area size register explicitly
Date: Sun, 10 Jun 2018 15:14:40 +0200 [thread overview]
Message-ID: <20180610131440.GA10544@botnar.kaiser.cx> (raw)
In-Reply-To: <20180607171911.7a7ee649@xps13>
Hi Miquel,
Thus wrote Miquel Raynal (miquel.raynal@bootlin.com):
> > Usually, this register is updated from settings in the IIM fuses when
> > the system is booting from nand flash. For other boot media, however,
> s/nand/NAND
ok
> > + /* spare area size in 16bit words */
> I thought I understood the problem with your commit message but
> then I don't get this comment. What's the link between 16-bit buses? Is
> this preset valid for both 8 and 16-bit bus width?
The register value is unrelated to the bus width.
> > + writew(mtd->oobsize >> 1, NFC_V21_RSLTSPARE_AREA);
> > +
> If this is for dividing per two oobsize value,
That's exactly what I wanted to do: mtd->oobsize is in bytes, the
register value must be in 16bit words (the specification uses the term
half-words, I'll update the comment while at it).
> I would really prefer a '/ 2' and let the compiler optimize things.
> Unless the spec is explicit about some shifting of course.
Ok, I'll use / 2 and resend the patch shortly.
Best regards,
Martin
next prev parent reply other threads:[~2018-06-10 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-03 11:31 [PATCH] mtd: rawnand: mxc: set spare area size register explicitly Martin Kaiser
2018-06-04 6:53 ` Sascha Hauer
2018-06-07 15:19 ` Miquel Raynal
2018-06-10 13:14 ` Martin Kaiser [this message]
2018-06-10 13:31 ` [PATCH v2] " Martin Kaiser
2018-06-18 14:06 ` Miquel Raynal
2018-06-18 14:09 ` Boris Brezillon
2018-06-18 20:36 ` Martin Kaiser
2018-06-18 20:41 ` [PATCH v3] " Martin Kaiser
2018-06-19 5:52 ` Boris Brezillon
2018-06-19 9:07 ` Miquel Raynal
2018-06-20 9:41 ` Boris Brezillon
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=20180610131440.GA10544@botnar.kaiser.cx \
--to=martin@kaiser.cx \
--cc=boris.brezillon@bootlin.com \
--cc=dwmw2@infradead.org \
--cc=fabio.estevam@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=s.hauer@pengutronix.de \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).