All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Dave Airlie <airlied@redhat.com>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 05/33] drm: Pass the drm_dp_aux->hw_mutex to i2c for its locking
Date: Fri, 3 Jun 2016 18:11:11 +0300	[thread overview]
Message-ID: <20160603151111.GB4329@intel.com> (raw)
In-Reply-To: <1464964636-3877-6-git-send-email-chris@chris-wilson.co.uk>

On Fri, Jun 03, 2016 at 03:36:48PM +0100, Chris Wilson wrote:
> Rather than have both drm_dp_aux lock within its transfer, and i2c to
> lock around the transfer, use the same lock by filling in the locking
> callbacks that i2c wants to use. We require our own hw_mutex as we
> bypass i2c_transfer for drm_dp_dpcd_access().
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Dave Airlie <airlied@redhat.com>
> Cc: Rafael Antognolli <rafael.antognolli@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: dri-devel@lists.freedesktop.org
> ---
>  drivers/gpu/drm/drm_dp_helper.c | 28 ++++++++++++++++++++++++----
>  1 file changed, 24 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_dp_helper.c b/drivers/gpu/drm/drm_dp_helper.c
> index eeaf5a7c3aa7..4b088afa21b2 100644
> --- a/drivers/gpu/drm/drm_dp_helper.c
> +++ b/drivers/gpu/drm/drm_dp_helper.c
> @@ -708,8 +708,6 @@ static int drm_dp_i2c_xfer(struct i2c_adapter *adapter, struct i2c_msg *msgs,
>  
>  	memset(&msg, 0, sizeof(msg));
>  
> -	mutex_lock(&aux->hw_mutex);
> -
>  	for (i = 0; i < num; i++) {
>  		msg.address = msgs[i].addr;
>  		drm_dp_i2c_msg_set_request(&msg, &msgs[i]);
> @@ -764,8 +762,6 @@ static int drm_dp_i2c_xfer(struct i2c_adapter *adapter, struct i2c_msg *msgs,
>  	msg.size = 0;
>  	(void)drm_dp_i2c_do_msg(aux, &msg);
>  
> -	mutex_unlock(&aux->hw_mutex);
> -
>  	return err;
>  }

AFAICS the only functional difference will be that we'll hold the lock
across the retries performed by the core. Looks like we set the retry
count to 3 for whatever reason, but I'm not seeing that we'd ever
actually return -EAGAIN so I guess the core will neever retry.
Oh, actually if we ever end up in the trylock path
(in_atomic||irqs_disabled) then the core would retry. But I don't think
we should ever do that.

Patch seems OK to me:
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

>  
> @@ -774,6 +770,26 @@ static const struct i2c_algorithm drm_dp_i2c_algo = {
>  	.master_xfer = drm_dp_i2c_xfer,
>  };
>  
> +static struct drm_dp_aux *i2c_to_aux(struct i2c_adapter *i2c)
> +{
> +	return container_of(i2c, struct drm_dp_aux, ddc);
> +}
> +
> +static void lock_bus(struct i2c_adapter *i2c, unsigned int flags)
> +{
> +	mutex_lock(&i2c_to_aux(i2c)->hw_mutex);
> +}
> +
> +static int trylock_bus(struct i2c_adapter *i2c, unsigned int flags)
> +{
> +	return mutex_trylock(&i2c_to_aux(i2c)->hw_mutex);
> +}
> +
> +static void unlock_bus(struct i2c_adapter *i2c, unsigned int flags)
> +{
> +	mutex_unlock(&i2c_to_aux(i2c)->hw_mutex);
> +}
> +
>  /**
>   * drm_dp_aux_register() - initialise and register aux channel
>   * @aux: DisplayPort AUX channel
> @@ -790,6 +806,10 @@ int drm_dp_aux_register(struct drm_dp_aux *aux)
>  	aux->ddc.algo_data = aux;
>  	aux->ddc.retries = 3;
>  
> +	aux->ddc.lock_bus = lock_bus;
> +	aux->ddc.trylock_bus = trylock_bus;
> +	aux->ddc.unlock_bus = unlock_bus;
> +
>  	aux->ddc.class = I2C_CLASS_DDC;
>  	aux->ddc.owner = THIS_MODULE;
>  	aux->ddc.dev.parent = aux->dev;
> -- 
> 2.8.1

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-06-03 15:11 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03 14:36 BAT regression bug 95634, take 3 Chris Wilson
2016-06-03 14:36 ` [PATCH v3 01/33] drm: Export drm_dev_init() for subclassing Chris Wilson
2016-06-03 14:36 ` [PATCH v3 02/33] drm: Add a callback from connector registering Chris Wilson
2016-06-03 14:36 ` [PATCH v3 03/33] drm: Make drm_connector_register() safe against multiple calls Chris Wilson
2016-06-03 14:36 ` [PATCH v3 04/33] drm: Automatically unregister the connector during cleanup Chris Wilson
2016-06-03 14:36 ` [PATCH v3 05/33] drm: Pass the drm_dp_aux->hw_mutex to i2c for its locking Chris Wilson
2016-06-03 15:11   ` Ville Syrjälä [this message]
2016-06-03 14:36 ` [PATCH v3 06/33] drm: Minimally initialise drm_dp_aux Chris Wilson
2016-06-03 14:59   ` Ville Syrjälä
2016-06-09 20:57     ` Chris Wilson
2016-06-10 10:26       ` Ville Syrjälä
2016-06-10 10:50         ` Chris Wilson
2016-06-03 14:36 ` [PATCH v3 07/33] drm/i915: Perform async fbdev initialisation much later Chris Wilson
2016-06-03 14:36 ` [PATCH v3 08/33] drm/i915: Make panel/backlight safe to setup/cleanup multiple times Chris Wilson
2016-06-03 14:36 ` [PATCH v3 09/33] drm/i915: Move panel's pipe from backlight setup to init Chris Wilson
2016-06-03 15:04   ` Ville Syrjälä
2016-06-03 15:22     ` Chris Wilson
2016-06-03 14:36 ` [PATCH v3 10/33] drm/i915: Move intel_connector->unregister to connector->early_unregister Chris Wilson
2016-06-03 14:36 ` [PATCH v3 11/33] drm/i915: Move backlight unregistration to connector unregistration Chris Wilson
2016-06-03 14:36 ` [PATCH v3 12/33] drm/i915: Move registration actions to connector->late_register Chris Wilson
2016-06-03 14:36 ` [PATCH v3 13/33] drm/i915/dp: Free the drm_dp_aux along with the encoder Chris Wilson
2016-06-03 14:36 ` [PATCH v3 14/33] drm/i915: Move backlight setup to connector registration Chris Wilson
2016-06-03 14:36 ` [PATCH v3 15/33] drm/i915: Move backlight registration " Chris Wilson
2016-06-03 14:36 ` [PATCH v3 16/33] drm/i915: Move connector registration to driver registration Chris Wilson
2016-06-03 14:37 ` [PATCH v3 17/33] drm/i915: Register debugfs interface last Chris Wilson
2016-06-03 14:37 ` [PATCH v3 18/33] drm/i915: Demidlayer driver loading Chris Wilson
2016-06-03 14:37 ` [PATCH v3 19/33] drm/i915: Demidlayer driver unloading Chris Wilson
2016-06-03 14:37 ` [PATCH v3 20/33] drm/i915: Start exploiting drm_device subclassing Chris Wilson
2016-06-03 14:37 ` [PATCH v3 21/33] drm/i915: Merge i915_dma.c into i915_drv.c Chris Wilson
2016-06-03 14:37 ` [PATCH v3 22/33] drm/i915: Split out the PCI driver interface to i915_pci.c Chris Wilson
2016-06-03 14:37 ` [PATCH v3 23/33] drm/i915: Move module init/exit " Chris Wilson
2016-06-08  8:57   ` Joonas Lahtinen
2016-06-03 14:37 ` [PATCH v3 24/33] drm/i915: Skip idling an idle engine Chris Wilson
2016-06-03 14:37 ` [PATCH v3 25/33] drm/i915: Move legacy kernel context pinning to intel_ringbuffer.c Chris Wilson
2016-06-03 14:37 ` [PATCH v3 26/33] drm/i915: Treat kernel context as initialised Chris Wilson
2016-06-07  9:23   ` Joonas Lahtinen
2016-06-03 14:37 ` [PATCH v3 27/33] drm/i915: Mark all default contexts as uninitialised after context loss Chris Wilson
2016-06-03 14:37 ` [PATCH v3 28/33] drm/i915: No need to wait for idle on L3 remap Chris Wilson
2016-06-03 14:37 ` [PATCH v3 29/33] drm/i915: Split idling from forcing context switch Chris Wilson
2016-06-08  9:02   ` Joonas Lahtinen
2016-06-08 10:56     ` Chris Wilson
2016-06-03 14:37 ` [PATCH v3 30/33] drm/i915: Only switch to default context when evicting from GGTT Chris Wilson
2016-06-03 14:37 ` [PATCH v3 31/33] drm/i915: Preserve current RPS frequency Chris Wilson
2016-06-03 14:37 ` [PATCH v3 32/33] drm/i915: Remove superfluous powersave work flushing Chris Wilson
2016-06-03 14:37 ` [PATCH v3 33/33] drm/i915: Defer enabling rc6 til after we submit the first batch/context Chris Wilson
2016-06-03 15:17 ` ✗ Ro.CI.BAT: warning for series starting with [v3,01/33] drm: Export drm_dev_init() for subclassing Patchwork

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=20160603151111.GB4329@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=airlied@redhat.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    /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.