On Sat, 8 Jul 2023 12:58:24 +0530 Jishnu Prakash <quic_jprakash@xxxxxxxxxxx> wrote: > PMIC5 Gen3 has a similar ADC architecture to that on PMIC5 Gen2, > with all SW communication to ADC going through PMK8550 which > communicates with other PMICs through PBS. The major difference is > that the register interface used here is that of an SDAM present on > PMK8550, rather than a dedicated ADC peripheral. There may be more than one > SDAM used for ADC5 Gen3. Each ADC SDAM has eight channels, each of which may > be used for either immediate reads (same functionality as previous PMIC5 and > PMIC5 Gen2 ADC peripherals) or recurring measurements (same as PMIC5 and PMIC5 > Gen2 ADC_TM functionality). In this case, we have VADC and ADC_TM functionality > combined into the same driver. > > Patches 1-5 update the name of the previous generation of PMIC5 ADC peripherals > from ADC7 to ADC5 Gen2, as this is the correct name and it makes more sense now > to update it, with the addition of the latest ADC5 Gen3 peripheral support. > > Patches 6 and 7 add bindings and driver support respectively for ADC5 Gen3. > > Patches 8-11 are for an additional change, where the QCOM ADC dt-bindings files > are moved from dt-bindings/iio to dt-bindings/iio/adc folder, as they are > specifically for ADC devices. > This crossed with Dmitry's set... https://patchwork.kernel.org/project/linux-iio/patch/20230707123027.1510723-2-dmitry.baryshkov@xxxxxxxxxx/ which changes a bunch of the includes you are going to rename. I don't mind which order these land (if both go forward) so will leave it up to the two of you to figure that out and tell me ;) Jonathan
