From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Michael Lawnick <ml.lawnick-Mmb7MZpHnFY@public.gmane.org>
Cc: Ben Dooks <ben.dooks-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
SH-Linux <linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: rcar-i2c: always reads a byte
Date: Mon, 5 May 2014 15:21:11 +0200 [thread overview]
Message-ID: <20140505132111.GA13467@katana> (raw)
In-Reply-To: <53201A83.7040605-Mmb7MZpHnFY@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
> >I have noticed the following behaviour with the i2c-rcar driver
> >with the following single i2c_msg structure:
> >
> > msg[0].addr = 0x12;
> > msg[0].flags = I2C_M_RD;
> > msg[0].len = 0;
> > msg[0].buf = data;
>
> isn't this illegal?
> This should lead to 50% chance of blocked bus: After sending
> read-bit the slave ACK's and puts first data bit onto SDL.
It is not illegal, SMBUS_QUICK is described in the SMBus specs and can
bee seen as a kind of 1-bit transfer. Yet, you should only issue it for
devices which require exactly this kind of transfer. Which is true for
most I2C transaction types.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-05-05 13:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 16:15 rcar-i2c: always reads a byte Ben Dooks
2014-03-11 16:40 ` Wolfram Sang
2014-03-11 16:41 ` Ben Dooks
2014-03-11 16:47 ` Wolfram Sang
2014-03-11 17:10 ` Ben Dooks
2014-05-05 15:51 ` Wolfram Sang
2014-03-11 17:24 ` Wolfram Sang
2014-03-11 17:31 ` Ben Dooks
2014-03-11 17:46 ` Wolfram Sang
[not found] ` <531F3686.7050808-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>
2014-03-12 8:27 ` Michael Lawnick
2014-03-12 8:39 ` Paul Carpenter
2014-03-12 9:00 ` Michael Lawnick
[not found] ` <53201A83.7040605-Mmb7MZpHnFY@public.gmane.org>
2014-05-05 13:21 ` Wolfram Sang [this message]
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=20140505132111.GA13467@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=ben.dooks-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ml.lawnick-Mmb7MZpHnFY@public.gmane.org \
/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).