From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [RESEND] drm/i915/sdvo: use the i2c bus locking functions
Date: Wed, 13 May 2026 17:32:24 +0300 [thread overview]
Message-ID: <agSLeFMnZTpyPVlv@intel.com> (raw)
In-Reply-To: <20260513080103.169402-1-jani.nikula@intel.com>
On Wed, May 13, 2026 at 11:01:03AM +0300, Jani Nikula wrote:
> Use i2c_lock_bus(), i2c_trylock_bus(), and i2c_unlock_bus() instead of
> poking at i2c adapter's lock_ops directly.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_sdvo.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_sdvo.c b/drivers/gpu/drm/i915/display/intel_sdvo.c
> index 23c511a9a2ad..ba54c90828f4 100644
> --- a/drivers/gpu/drm/i915/display/intel_sdvo.c
> +++ b/drivers/gpu/drm/i915/display/intel_sdvo.c
> @@ -3319,7 +3319,7 @@ static void proxy_lock_bus(struct i2c_adapter *adapter,
> struct intel_sdvo_ddc *ddc = adapter->algo_data;
> struct intel_sdvo *sdvo = ddc->sdvo;
>
> - sdvo->i2c->lock_ops->lock_bus(sdvo->i2c, flags);
> + i2c_lock_bus(sdvo->i2c, flags);
> }
>
> static int proxy_trylock_bus(struct i2c_adapter *adapter,
> @@ -3328,7 +3328,7 @@ static int proxy_trylock_bus(struct i2c_adapter *adapter,
> struct intel_sdvo_ddc *ddc = adapter->algo_data;
> struct intel_sdvo *sdvo = ddc->sdvo;
>
> - return sdvo->i2c->lock_ops->trylock_bus(sdvo->i2c, flags);
> + return i2c_trylock_bus(sdvo->i2c, flags);
> }
>
> static void proxy_unlock_bus(struct i2c_adapter *adapter,
> @@ -3337,7 +3337,7 @@ static void proxy_unlock_bus(struct i2c_adapter *adapter,
> struct intel_sdvo_ddc *ddc = adapter->algo_data;
> struct intel_sdvo *sdvo = ddc->sdvo;
>
> - sdvo->i2c->lock_ops->unlock_bus(sdvo->i2c, flags);
> + i2c_unlock_bus(sdvo->i2c, flags);
> }
>
> static const struct i2c_lock_operations proxy_lock_ops = {
> --
> 2.47.3
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2026-05-13 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 8:01 [RESEND] drm/i915/sdvo: use the i2c bus locking functions Jani Nikula
2026-05-13 10:10 ` ✓ i915.CI.BAT: success for drm/i915/sdvo: use the i2c bus locking functions (rev2) Patchwork
2026-05-13 10:10 ` Patchwork
2026-05-13 10:10 ` Patchwork
2026-05-13 14:32 ` Ville Syrjälä [this message]
2026-05-13 17:19 ` [RESEND] drm/i915/sdvo: use the i2c bus locking functions Jani Nikula
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=agSLeFMnZTpyPVlv@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox