From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] mtd: nand: sunxi: Replace failsafe timing cfg with calculated value
Date: Thu, 11 Jun 2015 17:11:39 +0200 [thread overview]
Message-ID: <1434035499.20095.1.camel@pengutronix.de> (raw)
In-Reply-To: <20150611165812.5c0e4c7f@bbrezillon>
Am Donnerstag, den 11.06.2015, 16:58 +0200 schrieb Boris Brezillon:
> Hi Roy,
>
> On Thu, 11 Jun 2015 16:50:35 +0200
> Roy Spliet <r.spliet@ultimaker.com> wrote:
>
> > Hello Boris,
> >
> > Op 10-06-15 om 10:59 schreef Boris Brezillon:
> > > Hi Roy,
> > >
> > > On Wed, 10 Jun 2015 10:29:07 +0200
> > > Roy Spliet <r.spliet@ultimaker.com> wrote:
> > >
> > >> Calculates the timing cfg value once when initialising a chip, then sets
> > >> it on chip select. Register definition documented the A83 user manual.
> > > How about rewording the sentence this way:
> > >
> > > "
> > > The TIMING_CFG register was previously statically set to a magic value
> > > (extracted from Allwinner's BSP) when initializing the NAND controller.
> > > Now that we have more details about the TIMING_CFG register layout
> > > (extracted from the A83 user manual) we can dynamically calculate the
> > > appropriate value for each NAND chip and set it when selecting the
> > > chip.
> > > "
> > >
> > >> Signed-off-by: Roy Spliet <r.spliet@ultimaker.com>
> > >>
> > >> V2:
> > >> - Fix crippled comments
> > >>
> > >> V3:
> > >> - Warn for invalid timings
> > >> - Style
> > > Almost right: the changelog should be placed after the '---' line ;-).
> > Git (format-patch, send-email) doesn't let me do that to the best of my
> > knowledge. Other comments I will process, thanks.
>
> Use git format-patch to generate the patches and then add your
> changelog before sending the mails with git send-email.
>
> Or you could generate a cover-letter (pass --cover-letter to
> format-patch) and put your change log in there.
>
Just insert the '---' line after your S-o-B when you write the commit
log. This will do all the right things for you.
Regards,
Lucas
--
Pengutronix e.K. | Lucas Stach |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2015-06-11 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 8:29 [PATCH v3 1/2] mtd: nand: sunxi: Replace failsafe timing cfg with calculated value Roy Spliet
2015-06-10 8:29 ` [PATCH v3 2/2] mtd: nand: sunxi: Set serial access mode correctly Roy Spliet
2015-06-10 11:24 ` Boris Brezillon
2015-06-10 8:59 ` [PATCH v3 1/2] mtd: nand: sunxi: Replace failsafe timing cfg with calculated value Boris Brezillon
2015-06-11 14:50 ` Roy Spliet
2015-06-11 14:58 ` Boris Brezillon
2015-06-11 15:11 ` Lucas Stach [this message]
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=1434035499.20095.1.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--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).