[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a3bf69f3-6500-4e45-ba34-8ba24312938a@kernel.org>
Date: Thu, 5 Jun 2025 14:13:29 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
Renjiang Han <quic_renjiang@...cinc.com>
Cc: Vikash Garodia <quic_vgarodia@...cinc.com>,
Dikshita Agarwal <quic_dikshita@...cinc.com>,
Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, linux-media@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, Nicolas Dufresne <nicolas.dufresne@...labora.com>
Subject: Re: [PATCH v8 0/3] media: venus: enable venus on qcs615
On 02/06/2025 08:16, Dmitry Baryshkov wrote:
> On Sat, May 31, 2025 at 08:05:24AM +0800, Renjiang Han wrote:
>>
>> On 5/31/2025 4:27 AM, Dmitry Baryshkov wrote:
>>> On Fri, May 30, 2025 at 09:32:12AM +0530, Renjiang Han wrote:
>>>> QCS615 uses the same video core as SC7180, so reuse the same resource
>>>> data of SC7180 for QCS615 to enable video functionality.
>>>>
>>>> There are no resources for the video-decoder and video-encoder nodes
>>>> in the device tree, so remove these two nodes from the device tree. In
>>>> addition, to ensure that the video codec functions properly, use [3]
>>>> to add encoder and decoder node entries in the venus driver.
>>>>
>>>> Validated this series on QCS615 and SC7180.
>>>>
>>>> Note:
>>>> This series consist of DT patches and a venus driver patch. The patch
>>>> 1/3, which is venus driver patch, can be picked independently without
>>>> having any functional dependency. But patch 2/3 & patch 3/3, which are
>>>> DT patches, still depend on [1].
>>> I'd say 2/3 and 3/3 still depend on 1/3, otherwise we can get video core
>>> on QCS615 over(?)clocked.
>> Agree, so we need to make sure that the driver patch is not picked after the
>> DT patch.
>
> Worse: we need to make sure that the driver patch is present in the
> branch which picks up DT patches. Otherwise building & testing that
Well, that's a NAK then (although depends what you mean by DT).
Best regards,
Krzysztof
Powered by blists - more mailing lists