From: Baruch Siach <baruch@tkos.co.il>
To: "Mainz, Roland" <R.Mainz@eckelmann.de>
Cc: barebox@lists.infradead.org
Subject: Re: Question about barebox*/drivers/mfd/mc34704.c and ACCURATE I²C mode ...
Date: Mon, 16 Apr 2018 13:19:39 +0300 [thread overview]
Message-ID: <20180416101939.yggybypgs3ahr76b@sapphire.tkos.co.il> (raw)
In-Reply-To: <38a86524d3ed4ff2b2306a3bb52fb312@eckelmann.de>
Hi Roland,
On Mon, Apr 16, 2018 at 09:52:14AM +0000, Mainz, Roland wrote:
> Two small questions about drivers/mfd/mc34704.c in the barebox codebase:
> 1. mc34704 has an ACCURATE bit (I2CSET1, see
> https://www.nxp.com/docs/en/data-sheet/MC34704.pdf) which requires that all
> read/write commands are send twice - does the barebox code have any support
> for that in the current versions ?
> 2. Is this "accurate I²C communication mode" enabled by that bit a
> vendor-specific protocol extension or is it part of the I²C standard ?
Please send your Barebox related questions to the barebox mailing list. I
added the list to Cc.
To the best of my knowledge there is no "twice" mode in the I2C standard. The
mc34704 driver does not seem to support this mode.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next parent reply other threads:[~2018-04-16 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <38a86524d3ed4ff2b2306a3bb52fb312@eckelmann.de>
2018-04-16 10:19 ` Baruch Siach [this message]
2018-04-17 6:43 ` Sascha Hauer
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=20180416101939.yggybypgs3ahr76b@sapphire.tkos.co.il \
--to=baruch@tkos.co.il \
--cc=R.Mainz@eckelmann.de \
--cc=barebox@lists.infradead.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