mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: David Airlie <airlied@linux.ie>,
	DRI devel <dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/i2c: tda998x: Fix lockdep warning about possible circular dependency
Date: Thu, 20 Jul 2017 15:19:10 +0100	[thread overview]
Message-ID: <20170720141910.GC3532@e110455-lin.cambridge.arm.com> (raw)
In-Reply-To: <20170720130829.GY31807@n2100.armlinux.org.uk>

On Thu, Jul 20, 2017 at 02:08:29PM +0100, Russell King - ARM Linux wrote:
> On Thu, Jul 20, 2017 at 01:54:04PM +0100, Liviu Dudau wrote:
> > On Thu, Jul 20, 2017 at 12:44:49PM +0100, Russell King - ARM Linux wrote:
> > > Actually, scrub that idea - drm_helper_probe_single_connector_modes()
> > > calls drm_edid_to_eld() for these cases anyway, so we must call
> > > drm_helper_probe_single_connector_modes() with the audio_mutex held.
> > 
> > OK, so the lockdep warning is spurious?
> 
> I don't think so.  I think there's two ways to solve this:
> 
> 1. replace the audio_mutex in tda998x_audio_get_eld() and
>    tda998x_connector_fill_modes() with a new mutex (eld_mutex) to
>    protect just the ELD.
> 
> 2. remove the mutex from these two functions, and take the connection_mutex
>    modeset lock in tda998x_audio_get_eld().
> 
> However, I don't have a view on which would be best.

If you don't mind, I took the liberty of picking option 2, just because
I don't like adding new locks when existing ones might do the job.

v2 patch on the way shortly.

Best regards,
Liviu

> 
> -- 
> RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
> FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
> according to speedtest.net.

-- 
====================
| I would like to |
| fix the world,  |
| but they're not |
| giving me the   |
 \ source code!  /
  ---------------
    ¯\_(ツ)_/¯

  reply	other threads:[~2017-07-20 14:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20 11:04 Liviu Dudau
2017-07-20 11:38 ` Russell King - ARM Linux
2017-07-20 11:44   ` Russell King - ARM Linux
2017-07-20 12:54     ` Liviu Dudau
2017-07-20 13:08       ` Russell King - ARM Linux
2017-07-20 14:19         ` Liviu Dudau [this message]
2017-07-20 14:24           ` Russell King - ARM Linux
2017-07-20 14:40             ` Liviu Dudau
2017-07-20 14:57               ` Daniel Vetter
2017-07-20 15:06                 ` Liviu Dudau

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=20170720141910.GC3532@e110455-lin.cambridge.arm.com \
    --to=liviu.dudau@arm.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    /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

Powered by JetHome