From: boris.brezillon@free-electrons.com (Boris BREZILLON)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/3] mtd: nand: gpmi: add gpmi_move_bits function
Date: Tue, 23 Sep 2014 16:58:22 +0200 [thread overview]
Message-ID: <20140923165822.27cfde69@bbrezillon> (raw)
In-Reply-To: <20140923145413.GA1633@localhost.localdomain>
On Tue, 23 Sep 2014 22:54:15 +0800
Huang Shijie <shijie8@gmail.com> wrote:
> On Tue, Sep 23, 2014 at 04:07:34PM +0200, Boris BREZILLON wrote:
> > Add a new function to move bits (not bytes) from a memory region to
> > another one.
> > This function is similar to memmove except it acts at bit level.
> > This function is needed to implement GPMI raw access functions, given the
> > fact that ECC engine does not pad ECC bits to the next byte boundary.
> sorry for not comment your v2 patch set.
>
> >
> > Signed-off-by: Boris BREZILLON <boris.brezillon@free-electrons.com>
> > ---
> > drivers/mtd/nand/gpmi-nand/gpmi-lib.c | 88 ++++++++++++++++++++++++++++++++++
> > drivers/mtd/nand/gpmi-nand/gpmi-nand.h | 4 ++
> > 2 files changed, 92 insertions(+)
> >
> > diff --git a/drivers/mtd/nand/gpmi-nand/gpmi-lib.c b/drivers/mtd/nand/gpmi-nand/gpmi-lib.c
> > index 87e658c..e2f706a 100644
> > --- a/drivers/mtd/nand/gpmi-nand/gpmi-lib.c
> > +++ b/drivers/mtd/nand/gpmi-nand/gpmi-lib.c
> > @@ -1353,3 +1353,91 @@ int gpmi_read_page(struct gpmi_nand_data *this,
> > set_dma_type(this, DMA_FOR_READ_ECC_PAGE);
> > return start_dma_with_bch_irq(this, desc);
> > }
> > +
> > +void gpmi_move_bits(u8 *dst, size_t dst_bit_off,
> > + const u8 *src, size_t src_bit_off,
> > + size_t nbits)
> we can simplify the code.
Any suggestions ?
>
> We could use the bytes to replace the @nbits.
>
> The chunk data is always byte aligned.
This function is also used to store ECC bits in the OOB buffer and
these chunk of data are not byte aligned :-).
>
>
> Btw: please add more comments in this function.
Yep, I should definitely comment it, and I'll do.
Best Regards,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-23 14:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 14:07 [PATCH v3 0/3] mtd: nand: gpmi: add proper raw access support Boris BREZILLON
2014-09-23 14:07 ` [PATCH v3 1/3] mtd: nand: gpmi: add gpmi_move_bits function Boris BREZILLON
2014-09-23 14:54 ` Huang Shijie
2014-09-23 14:58 ` Boris BREZILLON [this message]
2014-09-23 15:04 ` Huang Shijie
2014-09-23 15:20 ` Huang Shijie
2014-09-23 15:25 ` Boris BREZILLON
2014-09-23 14:07 ` [PATCH v3 2/3] mtd: nand: gpmi: add proper raw access support Boris BREZILLON
2014-09-23 15:17 ` Huang Shijie
2014-09-23 15:34 ` Boris BREZILLON
2014-09-23 16:10 ` Huang Shijie
2014-09-23 17:16 ` Boris BREZILLON
2014-09-23 17:21 ` Boris BREZILLON
2014-09-23 14:07 ` [PATCH v3 3/3] mtd: nand: gpmi: add raw oob access functions Boris BREZILLON
2014-09-30 8:07 ` [PATCH v3 0/3] mtd: nand: gpmi: add proper raw access support Boris Brezillon
2014-10-05 2:13 ` Huang Shijie
2014-10-08 14:24 ` Huang Shijie
2014-10-08 15:10 ` Boris Brezillon
2014-10-10 14:42 ` Huang Shijie
2014-10-10 14:53 ` Boris Brezillon
2014-10-14 5:50 ` Iwo Mergler
2014-10-16 15:52 ` Huang Shijie
2014-10-19 2:20 ` Huang Shijie
2014-10-20 5:02 ` Iwo Mergler
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=20140923165822.27cfde69@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;
as well as URLs for NNTP newsgroup(s).