From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: christian.ruppert@alitech.com
Cc: Christian Ruppert <christian.ruppert@abilis.com>,
Fabio Mello <fabio.mello@intel.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
linux-i2c@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Lucas De Marchi <lucas.de.marchi@gmail.com>,
Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH] i2c: designware: use enable on resume instead initialization
Date: Thu, 11 Jun 2015 12:38:08 +0300 [thread overview]
Message-ID: <20150611093808.GS1478@lahna.fi.intel.com> (raw)
In-Reply-To: <OF847FFF39.1FF5F96A-ONC1257E60.00506AFD-C1257E60.0052A8CE@alitech.com>
On Wed, Jun 10, 2015 at 05:05:16PM +0200, christian.ruppert@alitech.com wrote:
> We should understand why the controller was disabled after successful
> transfers in the first place, however. Maybe some quirk with older
> versions of the hardware? Mika, do you have any memories about this?
I think it was in the original driver even before I did Intel specific
changes to that. I have no idea why it is done. Probably, like you said,
because some older version of the hardware needed it.
next prev parent reply other threads:[~2015-06-11 9:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 17:50 [PATCH] i2c: designware: use enable on resume instead initialization lucas.de.marchi
2015-06-09 8:51 ` Mika Westerberg
2015-06-09 18:29 ` Lucas De Marchi
2015-06-10 7:07 ` Mika Westerberg
[not found] ` <OF847FFF39.1FF5F96A-ONC1257E60.00506AFD-C1257E60.0052A8CE@alitech.com>
2015-06-11 9:38 ` Mika Westerberg [this message]
2015-06-11 14:48 ` Lucas De Marchi
[not found] ` <OF847FFF39.1FF5F96A-ONC1257E60.00506AFD-C1257E60.0052A8CE@LocalDomain>
2015-06-23 16:45 ` christian.ruppert
2015-06-23 17:02 ` Lucas De Marchi
2015-06-24 7:36 ` christian.ruppert
2015-06-24 11:27 ` Mika Westerberg
2015-06-24 12:56 ` De Marchi, Lucas
2015-06-24 13:18 ` mika.westerberg
2015-06-24 14:06 ` christian.ruppert
2015-06-10 7:55 ` Mika Westerberg
2015-06-12 22:45 ` Lucas De Marchi
2015-06-15 9:29 ` Mika Westerberg
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=20150611093808.GS1478@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=christian.ruppert@abilis.com \
--cc=christian.ruppert@alitech.com \
--cc=fabio.mello@intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=lucas.demarchi@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