From: Sascha Hauer <s.hauer@pengutronix.de>
To: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/3] nvmem: ocotp: Elongate OCOTP_CTRL_ADDR field
Date: Tue, 11 Jun 2019 10:30:29 +0200 [thread overview]
Message-ID: <20190611083029.bm2h6ubz4qfzpgh7@pengutronix.de> (raw)
In-Reply-To: <20190611064906.8938-1-r.czerwinski@pengutronix.de>
On Tue, Jun 11, 2019 at 08:49:05AM +0200, Rouven Czerwinski wrote:
> Port of patch from linux-arm-kernel:
> | From: Bryan O'Donoghue <pure.logic@nexus-software.ie>
> |
> | nvmem: imx-ocotp: Elongate OCOTP_CTRL ADDR field to eight bits
> |
> | i.MX6 defines OCOTP_CTRLn:ADDR as seven bit address-field with a one bit
> | RSVD0 field, i.MX7 defines OCOTP_CTRLn:ADDR as a four bit address-field
> | with a four bit RSVD0 field.
> |
> | i.MX8 defines the OCOTP_CTRLn:ADDR bit-field as a full range eight bits.
> |
> | i.MX6 and i.MX7 should return zero for their respective RSVD0 bits and
> | ignore a write-back of zero where i.MX8 will make use of the full range.
> |
> | This patch expands the bit-field definition for all users to eight bits,
> | which is safe due to RSVD0 being a no-op for the i.MX6 and i.MX7.
>
> Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
> ---
> drivers/nvmem/ocotp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-06-11 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 6:49 Rouven Czerwinski
2019-06-11 8:30 ` Sascha Hauer [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=20190611083029.bm2h6ubz4qfzpgh7@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=r.czerwinski@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox