From: Bo Shen <voice.shen@atmel.com>
To: "Matteo Fortini" <matteo.fortini@gmail.com>,
"Raphaël Poggi" <raphio98@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: atmel_nand pmecc on 8k page [RFC]
Date: Mon, 16 Jun 2014 15:19:44 +0800 [thread overview]
Message-ID: <539E9A90.4010808@atmel.com> (raw)
In-Reply-To: <539AF326.7010504@gmail.com>
Hi Matteo,
On 06/13/2014 08:48 PM, Matteo Fortini wrote:
> Hi all,
> glad you found my patch useful. Sascha rejected it because he sees it
> more fit to separate the initialization of sama5d3 and sam9 since they
> are quite different.
>
> I started, as advised by Sascha, to create into sam9_smc.c the function
>
> void sama5d3_smc_configure(int id, int cs, struct sama5d3_smc_config
> *config)
>
> but this brings on some other changes to keep the same structure of
> functions, i.e. we would need to implement
>
> static void sama5d3_smc_cs_configure(void __iomem *base, struct
> sama5d3_smc_config *config)
>
> and all the related functions, since the argument changes from struct
> sam9_smc_config * to struct sama5d3_smc_config *
>
> Now I'm asking you all for a comment: should we go ahead and create a
> new sama5d3_smc.c file with all the functions (some will unfortunately
> be a duplicate of those present in sam9_smc.c), or should I do a partial
> hack to insert sama5d3 specific functions into sam9_smc.c (like, for
> example, playing with config structures so that the sam9 one is just the
> head of the sama5d3)?
I think we'd better to create a new sama5d3_smc.c. This will be more
readable, and also benefit for the new coming SoC.
> Thank you in advance for your comments, I ask Raphaël to wait until this
> patch is settled to send in his changes. They will be very useful for
> me, too (I had to deactivate PMECC to use my NAND...)
>
> M
Best Regards,
Bo Shen
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-06-16 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 12:28 atmel_nand pmecc on 8k page Raphaël Poggi
2014-06-13 1:26 ` Bo Shen
2014-06-13 8:48 ` Raphaël Poggi
2014-06-13 12:48 ` atmel_nand pmecc on 8k page [RFC] Matteo Fortini
2014-06-16 7:19 ` Bo Shen [this message]
2014-06-19 4:31 ` Jean-Christophe PLAGNIOL-VILLARD
2014-06-19 5:27 ` Bo Shen
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=539E9A90.4010808@atmel.com \
--to=voice.shen@atmel.com \
--cc=barebox@lists.infradead.org \
--cc=matteo.fortini@gmail.com \
--cc=raphio98@gmail.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