From: Robert Schwebel <r.schwebel@pengutronix.de>
To: "Opensource [Steve Twiss]" <stwiss.opensource@diasemi.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Liam Girdwood <lgirdwood@gmail.com>,
Lee Jones <lee.jones@linaro.org>, Mark Brown <broonie@kernel.org>,
David Dajun Chen <david.chen@diasemi.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC V2] mfd: da9063: Add support for production silicon variant code
Date: Thu, 20 Mar 2014 16:23:07 +0100 [thread overview]
Message-ID: <20140320152307.GR1629@pengutronix.de> (raw)
In-Reply-To: <6ED8E3B22081A4459DAC7699F3695FB7A18F5A46@SW-EX-MBX02.diasemi.com>
Hi Steve,
On Wed, Mar 19, 2014 at 05:14:54PM +0000, Opensource [Steve Twiss] wrote:
> > > > > This patch will remove the older variant code ID which matches the
> > > > > pre-production silicon ID (0x3) for the DA9063 chip.
[...]
> > > we have a few i.MX6 Modules (imx6q-phytec-pfla02) with DA9063 PMICs that
> > > all report the model/revision ID as 0x61/0x03. Those are marked as
> > > follows:
> > > dialog DA9063 44 1240EHDA
> > > dialog DA9063 44 1312ECAF
> > >
> > > We now have received a report from Phytec that those PMICs were not
> > > marketed as preproduction in any way, but as a normal mask revision.
> > > Their Dialog Semiconductor contact talked about AD, BA, and BB silicon
> > > variants. How do those relate to the variant register value and to the
> > > markings on the chips?
> > >
> > > There seems to be a serious miscommunication somewhere.
[...]
> Phytec informs us that you already asked them for this and have
> confirmed that you should have all necessary information now
No, it's completely unclear:
a) You said above that the 0x3 silicon is pre-production and thus you
removed that from the kernel.
b) Phytec says you didn't mark the PMICs as preproduction in any way.
The question is still, which one is correct? If a), I'm wondering why
Phytec didn't get that information. If b), the 0x3 variant must not be
removed from the kernel.
Could you clarify that?
rsc
--
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 |
prev parent reply other threads:[~2014-03-20 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 14:08 [RFC V2] mfd: da9063: Add support for production silicon variant code Opensource [Steve Twiss]
2014-02-14 16:43 ` Lee Jones
2014-03-14 14:37 ` Philipp Zabel
2014-03-17 8:33 ` Opensource [Steve Twiss]
2014-03-19 17:14 ` Opensource [Steve Twiss]
2014-03-20 15:23 ` Robert Schwebel [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=20140320152307.GR1629@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=broonie@kernel.org \
--cc=david.chen@diasemi.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=stwiss.opensource@diasemi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.