On Mon, 5 Dec 2022 at 14:42, Bryan O'Donoghue <bryan.odonoghue@xxxxxxxxxx> wrote: > > On 04/12/2022 19:25, Vincent Knecht wrote: > > Le dimanche 04 décembre 2022 à 19:42 +0100, Vincent Knecht a écrit : > >> Le dimanche 04 décembre 2022 à 07:59 +0200, Dmitry Baryshkov a écrit : > >>> There is no dtsi file for msm8939 in the kernel sources. Drop the > >>> compatibility with unofficial dtsi and remove support for handling the > >>> single-cell calibration data on msm8939. > >> > >> Could one invoke a "msm8916-like exemption" here ? Colleagues, I know that it adds a bit of pain on your side, however I'd also kindly ask to rework the dtsi. I'd really like to drop as much of the 'legacy parsing' as possible. The existing code is painful to handle already, it is redundant, self-duplicated, etc. See, how easier is to handle the DT cells + nvmem_cell API vs old shifts and masks code. > > > > Ignore that, guess we'll just have to implement it like there: > > https://lore.kernel.org/linux-arm-msm/20221204055909.1351895-9-dmitry.baryshkov@xxxxxxxxxx/T/#m19cffb13114b6f4f153058e3e7a1943251acaf81 > > > >> Also, msm8939.dtsi was submitted once [1], > >> and if helps we could send a v2 this month... > >> > >> [1] https://lore.kernel.org/linux-arm-msm/20220419010903.3109514-1-bryan.odonoghue@xxxxxxxxxx/ > > > > Offer still stands, the current community one is here: > > https://github.com/msm8916-mainline/linux/blob/msm8916/6.1-rc7/arch/arm64/boot/dts/qcom/msm8939.dtsi > > > > > > > > heh - here's my current > > https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=tracking-qcomlt-msm8939 > > I've been working on clearing out blockages in legacy yaml conversions > > phy > mdss-dsi-ctrl > > which thrown up errors on 8939 > > I took a good bunch of feedback from the list for v1 into that dtsi - > there's not much left blocking v2. > > I'll see if I can get that out this week > > --- > bod > > -- With best wishes Dmitry