From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] nand: lpc32xx: add SLC NAND controller support
Date: Wed, 15 Jul 2015 22:21:05 +0200 [thread overview]
Message-ID: <20150715222105.5283cc3a@lilith> (raw)
In-Reply-To: <4F172219764C784B84C2C1FF44E7DFB102FF1324@003FCH1MPN2-042.003f.mgd2.msft.net>
Hello SYLVAIN,
On Wed, 15 Jul 2015 19:23:33 +0000, LEMIEUX, SYLVAIN
<slemieux@Tycoint.com> wrote:
> Hi Vladimir and Albert,
>
> During this merge window (once our issues with our exchange server
> are resolve), we were planning on submitting a few patches for the
> LPC32xx.
>
> Some of the patches are the porting of the legacy NXP BSP (u-boot)
> drivers into the latest version; the drivers are the DMA, the SLC
> NAND and the USB.
>
> This original NXP implementation of the SLC NAND was using the DMA. I
> am also planning on testing this patch to compare the flashing time,
> with and without the DMA.
>
> I have two questions:
> 1) How do you suggest to approach this, as some patches may be
> similar or conflicting with what Vladimir is planning on submitting?
That question is for you and Vladimir to discuss.
> 2) For submitting legacy NXP BSP driver porting patch, would you like
> to see a 3 patches series (original driver, checkpatch script fix and
> the update for latest u-boot) to have history of the change or a
> single patch with the final result?
Single patch with the final result.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2015-07-15 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 20:23 [U-Boot] [PATCH] nand: lpc32xx: add SLC NAND controller support Vladimir Zapolskiy
2015-07-15 7:05 ` Albert ARIBAUD
2015-07-15 8:49 ` Vladimir Zapolskiy
2015-07-15 9:21 ` Albert ARIBAUD
2015-07-15 19:23 ` LEMIEUX, SYLVAIN
2015-07-15 20:21 ` Albert ARIBAUD [this message]
2015-07-16 0:19 ` Vladimir Zapolskiy
2015-07-16 19:38 ` LEMIEUX, SYLVAIN
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=20150715222105.5283cc3a@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.