From: Vladimir Zapolskiy <vz@mleia.com>
To: Mike Looijmans <mike.looijmans@topic.nl>, linux-i2c@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, wsa@the-dreams.de,
soren.brinkmann@xilinx.com, michal.simek@xilinx.com
Subject: Re: [PATCH] i2c: i2c-cadence: Don't register the adapter until it's ready
Date: Fri, 6 Jan 2017 23:34:24 +0200 [thread overview]
Message-ID: <428e8fc8-8b23-8e2c-763e-d977aaa98691@mleia.com> (raw)
In-Reply-To: <1483613240-32501-1-git-send-email-mike.looijmans@topic.nl>
Hello Mike,
On 01/05/2017 12:47 PM, Mike Looijmans wrote:
> The driver calls i2c_add_adapter before writing to config registers,
> resulting in dmesg output like this, where devices fail to initialize:
>
> cdns-i2c ff030000.i2c: timeout waiting on completion
> pca953x 1-0041: failed reading register
> pca953x: probe of 1-0041 failed with error -110
> at24 1-0050: 512 byte 24c04 EEPROM, writable, 1 bytes/write
> cdns-i2c ff030000.i2c: 100 kHz mmio ff030000 irq 197
>
> The adapter is being used before it completed the "probe". To fix
> this, make "i2c_add_adapter" the last thing it calls in probe.
> It also makes sense to show the adapter initialization before
> the devices on the bus.
commonly "it also" in a commit message means a change, which should be done
separately, and this is the case here as well.
Because the adapter registration i2c_add_adapter() can fail, information
about the adapter initialization would be expected only in case of
successful registration.
The information sent to the kernel log buffer here is quite trivial,
probably dev_info() can be just removed, but in any case it should be
a separate change.
> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2017-01-06 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 10:47 [PATCH] i2c: i2c-cadence: Don't register the adapter until it's ready Mike Looijmans
2017-01-06 21:34 ` Vladimir Zapolskiy [this message]
2017-01-12 19:22 ` Wolfram Sang
2017-01-13 6:40 ` Mike Looijmans
2017-01-13 8:37 ` Wolfram Sang
2017-01-13 14:52 ` Mike Looijmans
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=428e8fc8-8b23-8e2c-763e-d977aaa98691@mleia.com \
--to=vz@mleia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=mike.looijmans@topic.nl \
--cc=soren.brinkmann@xilinx.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