All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Jean Delvare <jdelvare@suse.de>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-i2c@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [RFC] i2c-stub: make it usable with DT when booting
Date: Thu, 18 May 2017 11:30:54 +0200	[thread overview]
Message-ID: <20170518093054.GA2740@katana> (raw)
In-Reply-To: <20170518105253.058a90a6@endymion>

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

Hi Jean,

> I get the idea and I understand the need to emulate the devices early
> in the boot process. However, how do you deal with the I2C devices
> pre-initialization (setting initial register values)? This is typically
> done in user-space with the i2c-stub-from-dump script, or manual calls
> to i2cset, but that would be too late in your case, wouldn't it?

Yes. In my case, all 0 memory is fine. I needed to check writes which
were enabling "channels" allowing me to do further initialization.

I see the point, though, that we likely want to address your question
before going upstream.

> Code looks sane, but I can't comment on the bindings side of things as
> this isn't my area.

Sure, thanks for checking the code!

Regards,

   Wolfram


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

      reply	other threads:[~2017-05-18  9:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 11:27 [RFC] i2c-stub: make it usable with DT when booting Wolfram Sang
2017-05-18  8:52 ` Jean Delvare
2017-05-18  9:30   ` 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=20170518093054.GA2740@katana \
    --to=wsa@the-dreams.de \
    --cc=jdelvare@suse.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=wsa+renesas@sang-engineering.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 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.