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

2014-03-20 Thread Robert Schwebel
Hi Steve,

On Wed, Mar 19, 2014 at 05:14:54PM +, 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- |
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


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

2014-03-20 Thread Robert Schwebel
Hi Steve,

On Wed, Mar 19, 2014 at 05:14:54PM +, 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- |
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


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

2014-03-19 Thread Opensource [Steve Twiss]
On 17 March 2014 08:34, Steve Twiss wrote:

>On 14 March 2014 14:37 Philipp Zabel wrote:
>>Am Freitag, den 14.02.2014, 16:43 + schrieb Lee Jones:
>>> > From: Opensource [Steve Twiss] 
>>> >
>>> > 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] 
>>>
>>> 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.
>
>I will speak with our AEs this morning and try and get an answer to this one.

Hi Philipp,

Phytec informs us that you already asked them for this and have confirmed
that you should have all necessary information now

Best regards,
Steve



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

2014-03-19 Thread Opensource [Steve Twiss]
On 17 March 2014 08:34, Steve Twiss wrote:

On 14 March 2014 14:37 Philipp Zabel wrote:
Am Freitag, den 14.02.2014, 16:43 + schrieb Lee Jones:
  From: Opensource [Steve Twiss] stwiss.opensou...@diasemi.com
 
  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.opensou...@diasemi.com

 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.

I will speak with our AEs this morning and try and get an answer to this one.

Hi Philipp,

Phytec informs us that you already asked them for this and have confirmed
that you should have all necessary information now

Best regards,
Steve



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

2014-03-17 Thread Opensource [Steve Twiss]
On 14 March 2014 14:37 Philipp Zabel wrote:

>Hi,
>
>Am Freitag, den 14.02.2014, 16:43 + schrieb Lee Jones:
>> > From: Opensource [Steve Twiss] 
>> >
>> > 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] 
>>
>> 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.

I will speak with our AEs this morning and try and get an answer to this one.

>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,
Steve

N�r��yb�X��ǧv�^�)޺{.n�+{zX����ܨ}���Ơz�:+v���zZ+��+zf���h���~i���z��w���?�&�)ߢf��^jǫy�m��@A�a���
0��h���i

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

2014-03-17 Thread Opensource [Steve Twiss]
On 14 March 2014 14:37 Philipp Zabel wrote:

Hi,

Am Freitag, den 14.02.2014, 16:43 + schrieb Lee Jones:
  From: Opensource [Steve Twiss] stwiss.opensou...@diasemi.com
 
  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.opensou...@diasemi.com

 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.

I will speak with our AEs this morning and try and get an answer to this one.

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,
Steve

N�r��yb�X��ǧv�^�)޺{.n�+{zX����ܨ}���Ơz�j:+v���zZ+��+zf���h���~i���z��w���?��)ߢf��^jǫy�m��@A�a���
0��h���i

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

2014-03-14 Thread Philipp Zabel
Hi,

Am Freitag, den 14.02.2014, 16:43 + schrieb Lee Jones:
> > From: Opensource [Steve Twiss] 
> > 
> > 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] 
> 
> 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 majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


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

2014-03-14 Thread Philipp Zabel
Hi,

Am Freitag, den 14.02.2014, 16:43 + schrieb Lee Jones:
  From: Opensource [Steve Twiss] stwiss.opensou...@diasemi.com
  
  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.opensou...@diasemi.com
 
 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 majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


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

2014-02-14 Thread Lee Jones
> From: Opensource [Steve Twiss] 
> 
> 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] 

Applied, thanks.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


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

2014-02-14 Thread Lee Jones
 From: Opensource [Steve Twiss] stwiss.opensou...@diasemi.com
 
 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.opensou...@diasemi.com

Applied, thanks.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/