public inbox for linux-rockchip@lists.infradead.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: "Markus Elfring" <Markus.Elfring@web.de>,
	"Dingxian Wen" <shawn.wen@rock-chips.com>,
	"Shreeya Patel" <shreeya.patel@collabora.com>,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-rockchip@lists.infradead.org,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Hans Verkuil" <hverkuil@xs4all.nl>,
	"Heiko Stübner" <heiko@sntech.de>,
	"Jose Abreu" <Jose.Abreu@synopsys.com>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Nelson Costa" <Nelson.Costa@synopsys.com>,
	"Nicolas Dufresne" <nicolas.dufresne@collabora.com>,
	"Rob Herring" <robh@kernel.org>,
	"Sebastian Reichel" <sebastian.reichel@collabora.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	kernel@collabora.com, Tim Surber <me@timsurber.de>
Subject: Re: [PATCH v7 4/6] media: platform: synopsys: Add support for HDMI input driver
Date: Sun, 23 Feb 2025 00:25:18 +0300	[thread overview]
Message-ID: <dfb0ef63-8867-4d00-abdd-8280623c3405@collabora.com> (raw)
In-Reply-To: <9e46e0f9-ef0d-406f-9fa9-9c4464a8db88@web.de>

On 2/19/25 23:56, Markus Elfring wrote:
> …
>> +++ b/drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c
>> @@ -0,0 +1,2718 @@
> …
>> +static u32 hdmirx_readl(struct snps_hdmirx_dev *hdmirx_dev, int reg)
>> +{
>> +	u32 val;
>> +
>> +	guard(spinlock_irqsave)(&hdmirx_dev->rst_lock);
>> +
>> +	val = readl(hdmirx_dev->regs + reg);
>> +
>> +	return val;
>> +}
> 
> May such a function implementation be simplified?
> 
> {
> 	guard(spinlock_irqsave)(&hdmirx_dev->rst_lock);
> 	return readl(hdmirx_dev->regs + reg);
> }

That will work, thanks.

> …
>> +static int hdmirx_get_detected_timings(struct snps_hdmirx_dev *hdmirx_dev,
>> +				       struct v4l2_dv_timings *timings)
>> +{
> …
>> +	mutex_lock(&hdmirx_dev->work_lock);
>> +retry:
>> +	memset(timings, 0, sizeof(struct v4l2_dv_timings));
> …
>> +	mutex_unlock(&hdmirx_dev->work_lock);
>> +
>> +	return ret;
>> +}
> …
> 
> Would you become interested to apply a statement like “guard(mutex)(&hdmirx_dev->work_lock);”?
> https://elixir.bootlin.com/linux/v6.14-rc3/source/include/linux/mutex.h#L201

That will make code less consistent and less intuitive to me. Anyways,
thanks for the suggestion.

-- 
Best regards,
Dmitry

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2025-02-22 21:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 18:44 [PATCH v7 0/6] Add Synopsys DesignWare HDMI RX Controller Dmitry Osipenko
2025-02-18 18:44 ` [PATCH v7 1/6] MAINTAINERS: Add entry for Synopsys DesignWare HDMI RX Driver Dmitry Osipenko
2025-02-18 18:44 ` [PATCH v7 2/6] dt-bindings: media: Document bindings for HDMI RX Controller Dmitry Osipenko
2025-02-18 18:44 ` [PATCH v7 3/6] arm64: dts: rockchip: Add device tree support " Dmitry Osipenko
2025-02-18 18:44 ` [PATCH v7 4/6] media: platform: synopsys: Add support for HDMI input driver Dmitry Osipenko
2025-02-19  9:11   ` Hans Verkuil
2025-02-19 18:35     ` Dmitry Osipenko
2025-02-20  7:03       ` Hans Verkuil
2025-02-20 12:53         ` Dmitry Osipenko
2025-02-19 20:56   ` Markus Elfring
2025-02-22 21:25     ` Dmitry Osipenko [this message]
2025-02-18 18:44 ` [PATCH v7 5/6] arm64: defconfig: Enable Synopsys HDMI receiver Dmitry Osipenko
2025-02-18 18:44 ` [PATCH v7 6/6] arm64: dts: rockchip: Enable HDMI receiver on rock-5b Dmitry Osipenko

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=dfb0ef63-8867-4d00-abdd-8280623c3405@collabora.com \
    --to=dmitry.osipenko@collabora.com \
    --cc=Jose.Abreu@synopsys.com \
    --cc=Markus.Elfring@web.de \
    --cc=Nelson.Costa@synopsys.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=hverkuil@xs4all.nl \
    --cc=kernel@collabora.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mchehab@kernel.org \
    --cc=me@timsurber.de \
    --cc=nicolas.dufresne@collabora.com \
    --cc=robh@kernel.org \
    --cc=sebastian.reichel@collabora.com \
    --cc=shawn.wen@rock-chips.com \
    --cc=shreeya.patel@collabora.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