From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Dongcheng Yan <dongcheng.yan@intel.com>,
linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
ricardo.ribalda@gmail.com, bingbu.cao@linux.intel.com,
tomi.valkeinen@ideasonboard.com, jacopo.mondi@ideasonboard.com,
daxing.li@intel.com, dongcheng.yan@linux.intel.com,
ong.hock.yu@intel.com, balamurugan.c@intel.com,
wei.a.fu@intel.com
Subject: Re: [PATCH v5] media: i2c: add lt6911uxe hdmi bridge driver
Date: Wed, 26 Feb 2025 11:36:09 +0000 [thread overview]
Message-ID: <Z778qdS_4fkIm3dk@kekkonen.localdomain> (raw)
In-Reply-To: <Z778R0tL-2knQOwd@kekkonen.localdomain>
On Wed, Feb 26, 2025 at 11:34:31AM +0000, Sakari Ailus wrote:
> Hi Hans,
>
> On Wed, Feb 26, 2025 at 11:51:48AM +0100, Hans Verkuil wrote:
> > On 10/02/2025 07:09, Dongcheng Yan wrote:
> > > +static int lt6911uxe_s_dv_timings(struct v4l2_subdev *sd, unsigned int pad,
> > > + struct v4l2_dv_timings *timings)
> > > +{
> > > + struct lt6911uxe *lt6911uxe = to_lt6911uxe(sd);
> > > + struct v4l2_subdev_state *state;
> > > +
> > > + state = v4l2_subdev_lock_and_get_active_state(sd);
> > > + if (v4l2_match_dv_timings(<6911uxe->timings, timings, 0, false))
> >
> > You're not unlocking the state here.
>
> I think the driver needs to do that as it's using the state lock to
> serialise access to its own device context data structure as well.
Oops. I misread the comment and the code. Please ignore.
--
Sakari Ailus
next prev parent reply other threads:[~2025-02-26 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 6:09 [PATCH v5] media: i2c: add lt6911uxe hdmi bridge driver Dongcheng Yan
2025-02-10 8:59 ` Yan, Dongcheng
2025-02-10 12:31 ` kernel test robot
2025-02-10 13:58 ` kernel test robot
2025-02-10 19:45 ` kernel test robot
2025-02-26 10:51 ` Hans Verkuil
2025-02-26 11:34 ` Sakari Ailus
2025-02-26 11:36 ` Sakari Ailus [this message]
2025-02-27 9:04 ` Yan, Dongcheng
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=Z778qdS_4fkIm3dk@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=balamurugan.c@intel.com \
--cc=bingbu.cao@linux.intel.com \
--cc=daxing.li@intel.com \
--cc=dongcheng.yan@intel.com \
--cc=dongcheng.yan@linux.intel.com \
--cc=hverkuil@xs4all.nl \
--cc=jacopo.mondi@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=ong.hock.yu@intel.com \
--cc=ricardo.ribalda@gmail.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=wei.a.fu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.