[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=U5O8aZqQxtx2MGz791SiQtSwMBx2ww3J5qFaG=W9skjA@mail.gmail.com>
Date: Thu, 17 Mar 2022 17:12:25 -0700
From: Doug Anderson <dianders@...omium.org>
To: Vinod Polimera <quic_vpolimer@...cinc.com>
Cc: dri-devel <dri-devel@...ts.freedesktop.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
freedreno <freedreno@...ts.freedesktop.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
Rob Clark <robdclark@...il.com>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
quic_kalyant <quic_kalyant@...cinc.com>
Subject: Re: [PATCH v6 2/5] arm64: dts: qcom: sm7280: remove
assigned-clock-rate property for mdp clk
Hi,
On Mon, Mar 14, 2022 at 7:47 AM Vinod Polimera
<quic_vpolimer@...cinc.com> wrote:
>
> Drop the assigned clock rate property and vote on the mdp clock as per
> calculated value during the usecase.
>
> This patch is dependent on below patch
> https://patchwork.kernel.org/patch/12774067/
Some nits on how you're referring to the dependent patch:
1. In the commit message it's really nice to also include the subject
line of the patch so someone looking at the commit after it lands can
more easily identify the patch you depend on.
2. It's better to use links that have the message ID in them. In the
past patchwork's magic IDs have been list.
So I'd write:
This patch is dependent on the patch ("drm/msm/disp/dpu1: set mdp clk
to the maximum frequency in opp table during probe") [1].
[1] https://lore.kernel.org/r/1647269217-14064-2-git-send-email-quic_vpolimer@quicinc.com/
> Signed-off-by: Vinod Polimera <quic_vpolimer@...cinc.com>
> Reviewed-by: Stephen Boyd <swboyd@...omium.org>
> ---
> arch/arm64/boot/dts/qcom/sc7280.dtsi | 9 ++-------
> 1 file changed, 2 insertions(+), 7 deletions(-)
Reviewed-by: Douglas Anderson <dianders@...omium.org>
Powered by blists - more mailing lists