From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: i.MX6: add more chip revision support
Date: Mon, 21 Jul 2014 15:06:48 +0800 [thread overview]
Message-ID: <20140721070647.GK8537@dragon> (raw)
In-Reply-To: <20140721063520.GR23235@pengutronix.de>
On Mon, Jul 21, 2014 at 08:35:20AM +0200, Sascha Hauer wrote:
> On Mon, Jul 21, 2014 at 01:38:11PM +0800, Shawn Guo wrote:
> > From: Jason Liu <r64343@freescale.com>
> >
> > Add more revision support for the new i.MX6DQ tap-out (TO1.5). This
> > TO1.5 is the Rev 1.3 as documented in i.MX6DQ data sheet, because TO1.3
> > and TO1.4 are never revealed.
>
> So the chip identifies itself as 1.5 but the data sheet refers to it as
> 1.3. Is there a way to make that clear somewhere? Otherwise it's really
> confusing.
I can add a note about that in the code, but I'm not really sure if
there is a better way to pass such info to end users. Suggestions are
welcomed.
Shawn
next prev parent reply other threads:[~2014-07-21 7:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 5:38 [PATCH] ARM: i.MX6: add more chip revision support Shawn Guo
2014-07-21 6:35 ` Sascha Hauer
2014-07-21 6:41 ` Uwe Kleine-König
2014-07-21 7:01 ` Shawn Guo
2014-07-21 7:06 ` Shawn Guo [this message]
2014-07-21 8:21 ` Sascha Hauer
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=20140721070647.GK8537@dragon \
--to=shawn.guo@freescale.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