linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rongrong Zou <zourongrong@gmail.com>
To: baruch@tkos.co.il
Cc: linux-i2c@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: mutex_lock in designware-i2c
Date: Mon, 11 Jan 2016 19:12:10 +0800	[thread overview]
Message-ID: <56938E0A.5080303@gmail.com> (raw)

Hi, baruch

I found a mutex lock in dw_i2c_dev for each adapter,
struct dw_i2c_dev {
         struct device           *dev;
         void __iomem            *base;
         struct completion       cmd_complete;
         struct mutex            lock;
         struct clk              *clk;

but there is another lock: adapter->bus_lock, this lock is also
for each adapter, why we need both of them ?

Regards,

Rongrong

             reply	other threads:[~2016-01-11 11:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 11:12 Rongrong Zou [this message]
2016-01-11 21:39 ` mutex_lock in designware-i2c Baruch Siach

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=56938E0A.5080303@gmail.com \
    --to=zourongrong@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=baruch@tkos.co.il \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mika.westerberg@linux.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;
as well as URLs for NNTP newsgroup(s).