From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-i2c@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH v1 1/3] i2c: designware-pci: Make bus number allocation robust
Date: Wed, 15 Jun 2016 16:42:54 +0300 [thread overview]
Message-ID: <f2466d99-ca2d-127c-ae90-54ec8a1ae25c@linux.intel.com> (raw)
In-Reply-To: <1465944960-25444-1-git-send-email-andriy.shevchenko@linux.intel.com>
On 06/15/2016 01:55 AM, Andy Shevchenko wrote:
> On some platforms, such as Intel Medfield, the I2C slave devices are enumerated
> through SFI tables where bus numbering is expected to be defined in the OS.
> Make the bus number allocation robust for such platforms.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/i2c/busses/i2c-designware-pcidrv.c | 84 ++++++++++++------------------
> 1 file changed, 34 insertions(+), 50 deletions(-)
...
> - [medfield_3] = {
> - .bus_num = 3,
> - .bus_cfg = INTEL_MID_STD_CFG | DW_IC_CON_SPEED_STD,
> - .tx_fifo_depth = 32,
> - .rx_fifo_depth = 32,
> - .clk_khz = 25000,
> - },
> - [medfield_4] = {
> - .bus_num = 4,
> - .bus_cfg = INTEL_MID_STD_CFG | DW_IC_CON_SPEED_FAST,
> - .tx_fifo_depth = 32,
> - .rx_fifo_depth = 32,
> - .clk_khz = 25000,
> - },
> - [medfield_5] = {
> - .bus_num = 5,
> + [medfield] = {
> + .bus_num = -1,
> .bus_cfg = INTEL_MID_STD_CFG | DW_IC_CON_SPEED_FAST,
> .tx_fifo_depth = 32,
> .rx_fifo_depth = 32,
> .clk_khz = 25000,
> + .setup = mfld_setup,
Now bus 3 speed is pumped up to fast speed. Can it cause problems?
--
Jarkko
next prev parent reply other threads:[~2016-06-15 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 22:55 [PATCH v1 1/3] i2c: designware-pci: Make bus number allocation robust Andy Shevchenko
2016-06-14 22:55 ` [PATCH v1 2/3] i2c: designware-pci: Introduce Merrifield support Andy Shevchenko
2016-06-15 13:48 ` Jarkko Nikula
2016-06-15 14:09 ` Andy Shevchenko
2016-06-14 22:56 ` [PATCH v1 3/3] i2c: designware-pci: Sort header block alphabetically Andy Shevchenko
2016-06-15 13:49 ` Jarkko Nikula
2016-06-15 13:42 ` Jarkko Nikula [this message]
2016-06-15 14:15 ` [PATCH v1 1/3] i2c: designware-pci: Make bus number allocation robust Andy Shevchenko
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=f2466d99-ca2d-127c-ae90-54ec8a1ae25c@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.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).