All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ulrich Hecht <uli+renesas@fpond.eu>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Linux I2C <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH] i2c: sh_mobile: implement atomic transfers
Date: Mon, 15 Jun 2020 15:12:56 +0200	[thread overview]
Message-ID: <20200615131256.GE4423@kunai> (raw)
In-Reply-To: <CAMuHMdWbZ8Bs84naNtoPk6N3itXABwwE2KGVG3k4dbw_5+Qm7A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 822 bytes --]

On Mon, Jun 15, 2020 at 02:58:59PM +0200, Geert Uytterhoeven wrote:
> Hi Wolfram,
> 
> On Mon, Jun 15, 2020 at 2:48 PM Wolfram Sang <wsa@the-dreams.de> wrote:
> > > Uli: can you check if atomic transfers work with the touchscreen or
> > > codec on Armadillo-800-EVA?
> >
> > Atmoic transfers are used for very late communication (e.g. PMIC).
> > Touchscreens and codecs should be already down, then.
> 
> So how to test atomic transfers are working if the I2C controller is part of
> a real power domain? Add a fake PMIC?

Hack something like this into a driver which is executed late:

	struct i2c_msg simple_msg = { ... }

	adap = i2c_get_adapter(0); // or whatever number
	i2c_transfer(adap, simple_msg, 1);

You don't need client struct, you can hardcode some address into
simple_msg directly.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-06-15 13:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10 19:33 [PATCH] i2c: sh_mobile: implement atomic transfers Ulrich Hecht
2020-06-14  9:31 ` Wolfram Sang
2020-06-15 10:01   ` Geert Uytterhoeven
2020-06-15 12:48     ` Wolfram Sang
2020-06-15 12:58       ` Geert Uytterhoeven
2020-06-15 13:12         ` Wolfram Sang [this message]
2020-06-18  9:53   ` Ulrich Hecht
2020-06-15  9:41 ` Geert Uytterhoeven
2020-06-15 12:50   ` Wolfram Sang
2020-06-15 12:57     ` Geert Uytterhoeven
2020-06-15 13:08       ` Wolfram Sang

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=20200615131256.GE4423@kunai \
    --to=wsa@the-dreams.de \
    --cc=geert@linux-m68k.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=uli+renesas@fpond.eu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.