mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Baruch Siach <baruch@tkos.co.il>
Cc: "Mainz, Roland" <R.Mainz@eckelmann.de>, barebox@lists.infradead.org
Subject: Re: Question about barebox*/drivers/mfd/mc34704.c and ACCURATE I²C mode ...
Date: Tue, 17 Apr 2018 08:43:20 +0200	[thread overview]
Message-ID: <20180417064320.hw3helj6mtr5a3v4@pengutronix.de> (raw)
In-Reply-To: <20180416101939.yggybypgs3ahr76b@sapphire.tkos.co.il>

Hi Roland,

On Mon, Apr 16, 2018 at 01:19:39PM +0300, Baruch Siach wrote:
> 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 ?

I never heard of "accurate I²C", it must be something the chip designers
have invented. Also there is no support for it neither in the mc34704
driver nor in the generic I²C support.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2018-04-17  6:43 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
2018-04-17  6:43   ` Sascha Hauer [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=20180417064320.hw3helj6mtr5a3v4@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=R.Mainz@eckelmann.de \
    --cc=barebox@lists.infradead.org \
    --cc=baruch@tkos.co.il \
    /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