From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
jose.abreu@synopsys.com, nelson.costa@synopsys.com,
shawn.wen@rock-chips.com, nicolas.dufresne@collabora.com,
kernel@collabora.com, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v2] media: synopsys: hdmirx: Detect broken interrupt
Date: Thu, 2 Oct 2025 18:50:41 +0300 [thread overview]
Message-ID: <169cf964-85a7-4f96-9a0c-0f06c7bfa012@collabora.com> (raw)
In-Reply-To: <wrzkhnslrwnpsv7gbdcvxobahun7l6foftftk676hxinfeqwjr@v3di5okva7co>
On 10/2/25 18:33, Sebastian Reichel wrote:
> Hello Dmitry,
>
> On Thu, Oct 02, 2025 at 05:07:50PM +0300, Dmitry Osipenko wrote:
>> Downstream version of RK3588 U-Boot uses customized TF-A that remaps
>> HDMIRX hardware interrupt, routing it via firmware that isn't supported
>> by upstream driver.
>>
>> Detect broken interrupt and print a clarifying error message about a need
>> to use open-source TF-A with this driver.
>>
>> Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
>> ---
>> Changelog:
>>
>> v2: - Added PHY r/w lock and moved the clarifying error message as
>> was suggested by Sebastian Reichel.
>>
>> .../platform/synopsys/hdmirx/snps_hdmirx.c | 90 ++++++++++++++++++-
>> .../platform/synopsys/hdmirx/snps_hdmirx.h | 2 +
>> 2 files changed, 90 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c b/drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c
>> index b7d278b3889f..e6456352dfa5 100644
>> --- a/drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c
>> +++ b/drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c
>
> #include <linux/cleanup.h>
>
> Otherwise LGTM and hopefully helps people to figure out the root
> cause of their problems:
>
> Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Thanks for the review. The cleanup.h always included by mutex/spinlock
headers, there is no need to include it explicitly.
--
Best regards,
Dmitry
prev parent reply other threads:[~2025-10-02 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 14:07 [PATCH v2] media: synopsys: hdmirx: Detect broken interrupt Dmitry Osipenko
2025-10-02 15:33 ` Sebastian Reichel
2025-10-02 15:50 ` Dmitry Osipenko [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=169cf964-85a7-4f96-9a0c-0f06c7bfa012@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=jose.abreu@synopsys.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=nelson.costa@synopsys.com \
--cc=nicolas.dufresne@collabora.com \
--cc=sebastian.reichel@collabora.com \
--cc=shawn.wen@rock-chips.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