From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] mtd: nand: squash struct nand_buffers into struct nand_chip
Date: Tue, 5 Dec 2017 12:57:11 +0100 [thread overview]
Message-ID: <20171205125711.74158b3b@bbrezillon> (raw)
In-Reply-To: <CAK7LNATKBO=eNHdL_P2MOh7+uRcCjkq+v8+O3DXC5UF3-NGh2Q@mail.gmail.com>
On Tue, 5 Dec 2017 20:49:28 +0900
Masahiro Yamada <yamada.masahiro@socionext.com> wrote:
> 2017-12-05 17:47 GMT+09:00 Masahiro Yamada <yamada.masahiro@socionext.com>:
> > struct nand_buffers is malloc'ed in nand_scan_tail() just for
> > containing three pointers. Squash this struct into nand_chip.
> >
> > Move and rename as follows:
> >
> > chip->buffers->ecccalc -> chip->ecc.calc_buf
> > chip->buffers->ecccode -> chip->ecc.code_buf
> > chip->buffers->databuf -> chip->data_buf
> >
> > Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> > ---
> >
>
>
>
>
> > diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
> > index dad438c..7870cb1 100644
> > --- a/drivers/mtd/nand/omap2.c
> > +++ b/drivers/mtd/nand/omap2.c
> > @@ -1530,7 +1530,7 @@ static int omap_write_page_bch(struct mtd_info *mtd, struct nand_chip *chip,
> > const uint8_t *buf, int oob_required, int page)
> > {
> > int ret;
> > - uint8_t *ecc_calc = chip->buffers->ecccalc;
> > + uint8_t *ecc_calc = chip->ecccalc;
> >
> > /* Enable GPMC ecc engine */
> > chip->ecc.hwctl(mtd, NAND_ECC_WRITE);
> > @@ -1568,7 +1568,7 @@ static int omap_write_subpage_bch(struct mtd_info *mtd,
> > u32 data_len, const u8 *buf,
> > int oob_required, int page)
> > {
> > - u8 *ecc_calc = chip->buffers->ecccalc;
> > + u8 *ecc_calc = chip->ecccalc;
> > int ecc_size = chip->ecc.size;
> > int ecc_bytes = chip->ecc.bytes;
> > int ecc_steps = chip->ecc.steps;
> > @@ -1605,7 +1605,7 @@ static int omap_write_subpage_bch(struct mtd_info *mtd,
> >
> > /* copy calculated ECC for whole page to chip->buffer->oob */
> > /* this include masked-value(0xFF) for unwritten subpages */
> > - ecc_calc = chip->buffers->ecccalc;
> > + ecc_calc = chip->ecccalc;
> > ret = mtd_ooblayout_set_eccbytes(mtd, ecc_calc, chip->oob_poi, 0,
> > chip->ecc.total);
> > if (ret)
> > @@ -1635,8 +1635,8 @@ static int omap_write_subpage_bch(struct mtd_info *mtd,
> > static int omap_read_page_bch(struct mtd_info *mtd, struct nand_chip *chip,
> > uint8_t *buf, int oob_required, int page)
> > {
> > - uint8_t *ecc_calc = chip->buffers->ecccalc;
> > - uint8_t *ecc_code = chip->buffers->ecccode;
> > + uint8_t *ecc_calc = chip->ecccalc;
> > + uint8_t *ecc_code = chip->ecccode;
> > int stat, ret;
> > unsigned int max_bitflips = 0;
> >
>
>
>
> Sorry, I missed to update omap2.c
>
> I will send v3.
No need to send a v3, I already fixed it when applying [1].
[1]https://github.com/bbrezillon/linux-0day/commit/59a7bfff7103d48713b2125c3844400301a3d028
next prev parent reply other threads:[~2017-12-05 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1512463636-28934-1-git-send-email-yamada.masahiro@socionext.com>
2017-12-05 8:47 ` [PATCH v2 3/3] mtd: nand: squash struct nand_buffers into struct nand_chip Masahiro Yamada
2017-12-05 11:49 ` Masahiro Yamada
2017-12-05 11:57 ` Boris Brezillon [this message]
2017-12-05 12:28 ` Masahiro Yamada
2017-12-05 13:30 ` 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=20171205125711.74158b3b@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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