Hi,
On 22/09/2022 20:23, Stephan Gerhold wrote:
Hi Dmitry,
On Sat, Sep 10, 2022 at 03:46:51PM +0300, Dmitry Baryshkov wrote:
Historically the tsens driver fetches the calibration data as a blob and
then parses the blob on its own. This results in semi-duplicated code
spreading over the platform-specific functions.
This patch series changes tsens calibration code to use pre-parsed nvmem
cells rather than parsing the blob in the driver. For backwards
compatibility the old code is left in place for msm8916 and qcs404, two
platforms which have in-tree DT files. For msm8974 the original function
is left intact, since it differs significantly (and I can not test the
code on msm8974). For all other affected platforms the old parsing code
has been dropped as a part of this RFC.
The code was tested on msm8916 and qcs404 only, thus it is being sent as
an RFC.
Thanks a lot for working on this!
After thinking about this for a while I wonder if we can go even a step
further: Can we drop SoC-specific code entirely for 8939 and 9607 and
match the generic compatible (qcom,tsens-v0_1)? This would allow most
v0.1 plaforms to use generic code like for qcom,tsens-v2.
While this idea looks appealing, I think it's a bit against our custom
to put hardware details into the driver rather than putting them into
the DT. So, I think, the 8939 will have to stay as is, while for the
9607 and maybe several other devices it should be possible to create a
fallback entry.
AFAICT with your changes only the following remains SoC-specific:
- hw_ids (actually only needed for 8939 since 9607 has standard IDs)
As I wrote, I wouldn't put this into DT.
While two other things are already handled:
- num_sensors (the driver supports "#qcom,sensors" in DT already)
- tsens_calibrate_nvmem() shift (AFAICT in downstream msm-tsens.c
everything except 8916 uses shift = 2. 8916 needs special handling
anyway for the backwards compatibility)
Having the generic compatible would allow me to add MSM8909 without any
code changes at all (just DT schema addition).
For 8939 we could read the hw_ids from the DT with something like:
qcom,sensors = <0 1 2 3 5 6 7 8 9 10>;
And actually there are two revisions of 8939, the older one has one
sensor less (msm-3.10: msm8939-common.dtsi vs msm8939-v3.0.dtsi).
This could also be easily handled from the DT without any code changes:
qcom,sensors = <0 1 2 3 5 6 7 8 9>;
Usually we only care about the latest revision of the chip, earlier
revisions typically correspond to engineering samples, never hitting the
actual consumer devices.
The diff could be something like the following (I did not test it yet).
What do you think?
I'd like to sort the calibration data for 8976 first. At this moment I'm
waiting for the 8976 data to be tested. Also it would be nice to be able
to cleanup the 8976 calibration code.
--
With best wishes
Dmitry
