From: Manivannan Sadhasivam <mani@kernel.org>
To: Luca Leonardo Scorcia <l.scorcia@gmail.com>
Cc: linux-mediatek@lists.infradead.org,
Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Chunfeng Yun <chunfeng.yun@mediatek.com>,
Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] phy: mediatek: phy-mtk-hdmi: Use regmap to manipulate hdmi registers
Date: Sat, 31 Oct 2026 17:47:39 +0530 [thread overview]
Message-ID: <179344905948.5901.6799097646166176701.b4-reply@b4> (raw)
In-Reply-To: <20261011082042.348422-2-l.scorcia@gmail.com>
On 2026-10-11 10:20 +0200, Luca Leonardo Scorcia wrote:
> Use the regmap primitives to manipulate HDMI registers instead of custom
> helpers from phy-mtk-io.h. No functional changes.
>
> This avoids the following issue with mt8167:
>
> hdmi-phy: error -EBUSY: can't request region for resource
> [mem 0x10018300-0x1001831f]
>
> due to the fact that HDMI PHY registers are actually mapped inside the
> apmixedsys memory space.
>
> The same situation is present on mt8173 too but this SoC does not exhibit
> the issue as its apmixedsys driver uses of_iomap instead of
> devm_platform_ioremap_resource to map its memory space, just like regmap
> does.
>
> Signed-off-by: Luca Leonardo Scorcia <l.scorcia@gmail.com>
Why RFC?
Anyhow, please fix the build errors reported.
- Mani
prev parent reply other threads:[~2026-10-31 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 8:20 [RFC PATCH 0/1] " Luca Leonardo Scorcia
2026-10-11 8:20 ` [RFC PATCH 1/1] " Luca Leonardo Scorcia
2026-10-31 12:17 ` Manivannan Sadhasivam [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=179344905948.5901.6799097646166176701.b4-reply@b4 \
--to=mani@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunfeng.yun@mediatek.com \
--cc=chunkuang.hu@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=l.scorcia@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=neil.armstrong@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=vkoul@kernel.org \
/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
all inboxes | Powered by JetHome®