<div dir="ltr"><div dir="ltr"> </div> <div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Mar 6, 2025 at 12:26 PM Tejas Vipin <<a href="mailto:tejasvipin76@gmail.com">tejasvipin76@gmail.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> On 3/6/25 9:03 PM, Anusha Srivatsa wrote: > On Thu, Mar 6, 2025 at 11:29 AM Dmitry Baryshkov < > <a href="mailto:dmitry.baryshkov@linaro.org" target="_blank">dmitry.baryshkov@linaro.org</a>> wrote: > >> On Thu, 6 Mar 2025 at 17:10, Anusha Srivatsa <<a href="mailto:asrivats@redhat.com" target="_blank">asrivats@redhat.com</a>> wrote: >>> >>> >>> >>> On Thu, Mar 6, 2025 at 4:31 AM Maxime Ripard <<a href="mailto:mripard@kernel.org" target="_blank">mripard@kernel.org</a>> wrote: >>>> >>>> Hi Anusha, >>>> >>>> On Wed, Mar 05, 2025 at 07:01:41PM -0500, Anusha Srivatsa wrote: >>>>> Move away from using deprecated API and use _multi >>>>> variants if available. Use mipi_dsi_msleep() >>>>> and mipi_dsi_usleep_range() instead of msleep() >>>>> and usleep_range() respectively. >>>>> >>>>> Used Coccinelle to find the multiple occurences. >>>>> SmPl patch: >>>>> @rule@ >>>>> identifier dsi_var; >>>>> identifier r; >>>>> identifier func; >>>>> type t; >>>>> position p; >>>>> expression dsi_device; >>>>> expression list es; >>>>> @@ >>>>> t func(...) { >>>>> ... >>>>> struct mipi_dsi_device *dsi_var = dsi_device; >>>>> +struct mipi_dsi_multi_context dsi_ctx = { .dsi = dsi_var }; >>>>> <+... >>>>> ( >>>>> -mipi_dsi_dcs_write_seq(dsi_var,es)@p; >>>>> +mipi_dsi_dcs_write_seq_multi(&dsi_ctx,es); >>>>> | >>>>> -mipi_dsi_generic_write_seq(dsi_var,es)@p; >>>>> +mipi_dsi_generic_write_seq_multi(&dsi_ctx,es); >>>>> | >>>>> -mipi_dsi_generic_write(dsi_var,es)@p; >>>>> +mipi_dsi_generic_write_multi(&dsi_ctx,es); >>>>> | >>>>> -r = mipi_dsi_dcs_nop(dsi_var)@p; >>>>> +mipi_dsi_dcs_nop_multi(&dsi_ctx); >>>>> | >>>>> ....rest of API >>>>> .. >>>>> ) >>>>> -if(r < 0) { >>>>> -... >>>>> -} >>>>> ...+> >>>> >>>> The point of sending a single patch was to review the coccinelle script, >>>> so you must put the entire script you used here. >>>> >>> >>> I was actually thinking of sending patches per driver this time around >> since Tejas also seems to be looking into similar parts....Thoughts? >> >> Have you discussed it with Tejas? What is his next target? >> >> I was hoping he will have some feedback on this patch and we could take it > from there..... > It *should* be okay for me to send all changes in a single series... > > Anusha > There's 5 more panels that use dcs/generic write_seq(). Maybe I could work on those (himax-hx8394, samsung-sofef00, samsung-s6d7aa0, boe-bf060y8m-aj0, jdi-lpm102a188a) while you work on transitioning the rest of the panels (excluding these) that use other functions in the old API? When either of us finishes before the other we could have another discussion about splitting work if necessary. I'm open to other suggestions too </blockquote><div> </div><div>Like the suggestion! Thanks Tejas. </div><div> </div><div>Anusha </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> >>>>> Cc: Maxime Ripard <<a href="mailto:maxime.ripard@bootlin.com" target="_blank">maxime.ripard@bootlin.com</a>> >>>> >>>> That hasn't been my email address for 6 years :) >>>> >>> My bad. Will change this. >> >> >> >> -- >> With best wishes >> Dmitry >> >> > -- Tejas Vipin </blockquote></div></div>