From: Wolfram Sang <wsa@the-dreams.de>
To: Bryan Evenson <bevenson@melinkcorp.com>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
Ludovic Desroches <ludovic.desroches@atmel.com>
Subject: Re: Error using at91-i2c driver in kernel 4.4.x
Date: Thu, 25 May 2017 01:07:08 +0200 [thread overview]
Message-ID: <20170524230708.GA1456@katana> (raw)
In-Reply-To: <DM5PR05MB29541B7EC525C8438538352ABBFE0@DM5PR05MB2954.namprd05.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
> As usual, five minutes after I ask a question I get further. I tried
> changing the ioctl to I2C_SLAVE_FORCE, and now I can talk to my
> EEPROM. I'm happy it's now working, but I'm concerned about why I now
> need to force the slave address. Is this because I now need to set
> things up differently, or is it a problem with the driver?
From userspace, you cannot access an I2C client which has a kernel
driver bound to it unless you use I2C_SLAVE_FORCE. And you really should
not do that because you could confuse the kernel driver.
Your old kernel probably did not bind a driver to the EEPROM, so you
could access it from userspace.
Since your DT now describes the EEPROM, why don't you simply access the
'eeprom' file in sysfs?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-05-24 23:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 18:18 Error using at91-i2c driver in kernel 4.4.x Bryan Evenson
2017-05-24 18:35 ` Bryan Evenson
2017-05-24 23:07 ` Wolfram Sang [this message]
2017-05-25 14:23 ` Bryan Evenson
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=20170524230708.GA1456@katana \
--to=wsa@the-dreams.de \
--cc=bevenson@melinkcorp.com \
--cc=linux-i2c@vger.kernel.org \
--cc=ludovic.desroches@atmel.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