Re: [RFC V2] mfd: da9063: Add support for production silicon variant code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Am Freitag, den 14.02.2014, 16:43 +0000 schrieb Lee Jones:
> > From: Opensource [Steve Twiss] <stwiss.opensource@xxxxxxxxxxx>
> > 
> > Add the correct silicon variant code ID (0x5) to the driver. This
> > new code is the 'production' variant code ID for DA9063.
> > 
> > This patch will remove the older variant code ID which matches the
> > pre-production silicon ID (0x3) for the DA9063 chip.
> > 
> > There is also some small amount of correction done in this patch:
> > it splits the revision code and correctly names it according to
> > the hardware specification and moves the dev_info() call before
> > the variant ID test.
> > 
> > Signed-off-by: Opensource [Steve Twiss] <stwiss.opensource@xxxxxxxxxxx>
> 
> Applied, thanks.

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.

regards
Philipp

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/




[Index of Archives]

  Powered by Linux

[Older Kernel Discussion]     [Yosemite National Park Forum]     [Large Format Photos]     [Gimp]     [Yosemite Photos]     [Stuff]     [Index of Other Archives]