From: Cory Keitz <ckeitz@amazon.com>
To: Hans de Goede <johannes.goede@oss.qualcomm.com>
Cc: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>,
<linux-media@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] media: qcom: camss: Add "gcc_axi_hf" to 8775p VFE lite clock lists
Date: Thu, 23 Jul 2026 10:42:13 -0700 [thread overview]
Message-ID: <amJPH7TMiMP79mIe@bcd074ae11bb> (raw)
In-Reply-To: <20260723110952.55597-1-johannes.goede@oss.qualcomm.com>
On Thu, Jul 23, 2026 at 01:09:50PM +0200, Hans de Goede wrote:
> The "gcc_axi_hf" clock is correctly listed in the clock list of the
> 8775p 2 main VFE-s, but it is missing from all the VFE-lite clock lists,
> causing these to not work on platforms where the firmware allows turning
> off "gcc_axi_hf".
>
> Add the missing "gcc_axi_hf" to fix the VFE-lite blocks not working on
> these platforms.
Tested-by: Cory Keitz <ckeitz@amazon.com>
prev parent reply other threads:[~2026-07-23 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 11:09 [PATCH v2 1/3] media: qcom: camss: Add "gcc_axi_hf" to 8775p VFE lite clock lists Hans de Goede
2026-07-23 11:09 ` [PATCH v2 2/3] media: qcom: camss: Drop icc_res_qcs8300 resource table Hans de Goede
2026-07-23 11:30 ` Vladimir Zapolskiy
2026-07-23 11:09 ` [PATCH v2 3/3] media: qcom: camss: Drop csiphy_res_8300 phy " Hans de Goede
2026-07-23 11:31 ` Vladimir Zapolskiy
2026-07-23 11:30 ` [PATCH v2 1/3] media: qcom: camss: Add "gcc_axi_hf" to 8775p VFE lite clock lists Vladimir Zapolskiy
2026-07-23 12:50 ` Loic Poulain
2026-07-23 17:42 ` Cory Keitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=amJPH7TMiMP79mIe@bcd074ae11bb \
--to=ckeitz@amazon.com \
--cc=bryan.odonoghue@linaro.org \
--cc=johannes.goede@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=stable@vger.kernel.org \
--cc=vladimir.zapolskiy@linaro.org \
--cc=wenmeng.liu@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).