On Fri, Nov 07, 2014 at 04:40:52PM +0100, Ivan T. Ivanov wrote: > On Fri, 2014-11-07 at 17:33 +0200, Ivan T. Ivanov wrote: > > On Thu, 2014-11-06 at 08:55 -0800, Bjorn Andersson wrote: > > > On Wed, Nov 5, 2014 at 11:54 PM, Ivan T. Ivanov <iivanov@xxxxxxxxxx> wrote: > > > > On Wed, 2014-11-05 at 17:36 -0800, Bjorn Andersson wrote: [...] > > > > > Could you be a little bit more elaborate on what you're trying to do > > > > > and which child devices that might be? > > > > > > > > For example ADC drivers are required temperature compensation based > > > > on PMIC variant and chip manufacturer. > > > > > > > > > > I see, is that compensation of any practical value? Or is the > > > compensation of academic proportions? > > > > It depends of what you mean by academic :-). Attached file have test > > application which dump difference between non compensated and compensated > > values for different temperature, manufacture and input value. > > [...] > Forgot to add. PMIC subtype and version are used also in charger and BMS > drivers to workaround hardware issues. All of the blocks on the PM8x41 series have their own version numbers. There's no need to look at the chip revision. In fact, the SMBB (charger) documentation (80-NA555-12) specifically refers to the SMBB_MISC block revision registers as the method for determining the hardware version. The "qpnp-charger" SMBB driver in the CAF 3.4 & 3.10 trees utilizes block specific revision numbers, as do the "qpnp-bms" BMS driver, the "qpnp-adc-current" IADC driver, and the "qpnp-adc-voltage" VADC driver. The revision of the PMIC itself should be completely irrelevant to any of the software interfacing with it. -Courtney -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
