From: David Brownell <david-b@pacbell.net>
To: "Pandita, Vikram" <vikram.pandita@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [patch FYI] twl4030 dumps revision info
Date: Thu, 16 Oct 2008 17:16:58 -0700 [thread overview]
Message-ID: <200810161716.58536.david-b@pacbell.net> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC35608702396893F7@dbde02.ent.ti.com>
On Thursday 16 October 2008, Pandita, Vikram wrote:
> >The main curiousity we've uncovered is that TWL5030 ES1.0
> >mis-identifies itself as TWL4030 ES1.0 ... unclear just now
> >whether that's also true of ES1.1 and later parts.
>
> As per TRM,
> the idcode for TWL5030 should be: 0x0009802F
>
> is it not what you are observing? Or was it the , bug !!
On one part labeled tps65950, it was 00009002F.
On one labeled as a twl5030, ditto.
On one labeled as a twl4030, it was 5009002f.
Ergo the observation that the TWL5030 ES1.0
parts seem to mis-identify themselves.
- Dave
next prev parent reply other threads:[~2008-10-17 0:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 4:23 [patch FYI] twl4030 dumps revision info David Brownell
2008-10-16 23:19 ` Pandita, Vikram
2008-10-16 23:27 ` Pandita, Vikram
2008-10-17 0:16 ` David Brownell [this message]
2008-10-17 8:31 ` Pakaravoor, Jagadeesh
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=200810161716.58536.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=vikram.pandita@ti.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