Messages in this thread | | | Subject | Re: [PATCH v6 0/6] DVFS for IO devices on sdm845 and sc7180 | From | Rajendra Nayak <> | Date | Wed, 1 Jul 2020 16:58:13 +0530 |
| |
Hey Stan,
>> >> Hey Stan, >> >>> On 6/18/20 7:47 AM, Rajendra Nayak wrote: >>>> Hey Matthias, thanks for summarizing this. >>>> >>>> On 6/18/2020 3:45 AM, Matthias Kaehlcke wrote: >>>>> What is the plan for landing these, it seems not all must/should >>>>> go through the QCOM tree. >>>>> >>>>> My guesses: >>>>> >>>>> tty: serial: qcom_geni_serial: Use OPP API to set clk/perf state >>>>> spi: spi-geni-qcom: Use OPP API to set clk/perf state >>>>> QCOM tree due to shared dependency on change in >>>>> include/linux/qcom-geni-se.h >>>> >>>> That's correct, Bjorn/Andy, can these be pulled in now for 5.9? >>>> They have acks from Greg for serial and Mark for the spi patch. >>>> >>>>> drm/msm/dpu: Use OPP API to set clk/perf state >>>>> drm/msm: dsi: Use OPP API to set clk/perf state >>>>> drm/msm tree >>>> >>>> Correct, the dsi patch is still not reviewed by Rob, so once that's >>>> done, >>>> I am guessing Rob would pull both of these. >>>> >>>>> >>>>> media: venus: core: Add support for opp tables/perf voting >>>>> venus tree >>>> >>>> correct, this is pending review/ack from Stan. >>> >>> I tested the changes in the driver, and they looks fine. But when >>> applied the corresponding change in the DT node I see this message when >>> the streaming is stopping: >>> >>> qcom_rpmh TCS Busy, retrying RPMH message send: addr=0x30000 >>> >>> I tested on v5.7 (linaro-integration). Should I be worried ?
I had a look at this message and also spoke to Maulik, and it seems like its fairly harmless. It just suggests we had to wait a while to get a TCS, and then retry, So nothing to worry about.
thanks, Rajendra
-- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
| |