linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Linux I2C <linux-i2c@vger.kernel.org>,
	Christian Fetzer <fetzer.ch@gmail.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH] i2c-piix4: Fix SB800 locking
Date: Tue, 26 Jan 2016 08:04:39 +0100	[thread overview]
Message-ID: <1453791879.4772.2.camel@chaos.site> (raw)
In-Reply-To: <20160126054212.GB1533@katana>

Le Tuesday 26 January 2016 à 06:42 +0100, Wolfram Sang a écrit :
> On Fri, Jan 22, 2016 at 02:12:02PM +0100, Jean Delvare wrote:
> > We need a single mutex for all 4 shared SMBus ports on the SB800. A
> > per-port mutex doesn't protect us from concurrent access.
> > 
> > In theory the mutex should be per PCI device, however in practice we
> > know that there's only ever a single instance of the device in a given
> > system so we can use a global.
> > 
> > Also take the mutex during initialization, as first port may be already
> > in use when second port is initialized.
> > 
> > Signed-off-by: Jean Delvare <jdelvare@suse.de>
> > Cc: Christian Fetzer <fetzer.ch@gmail.com>
> > Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
> > Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Cc: Wolfram Sang <wsa@the-dreams.de>
> 
> Fixed a sparse warning by making the mutex static, took the freedom to
> read Christian's mail as Tested-by and applied to for-current, thanks!

Oh, I thought I had fixed that before submitting but clearly I forgot.
Thanks for doing it :)

I'll send a patch restoring I2C bus names for older devices later today.
I have a few other fixups in mind but the rest isn't as urgent.

-- 
Jean Delvare
SUSE L3 Support

      reply	other threads:[~2016-01-26  7:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 13:12 [PATCH] i2c-piix4: Fix SB800 locking Jean Delvare
2016-01-23 13:26 ` fetzerch
2016-01-25  9:29 ` Mika Westerberg
2016-01-26  5:42 ` Wolfram Sang
2016-01-26  7:04   ` Jean Delvare [this message]

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=1453791879.4772.2.camel@chaos.site \
    --to=jdelvare@suse.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=fetzer.ch@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=wsa@the-dreams.de \
    /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;
as well as URLs for NNTP newsgroup(s).