From: Wolfram Sang <wsa@the-dreams.de>
To: Pavel Machek <pavel@denx.de>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
pantelis.antoniou@konsulko.com, grant.likely@linaro.org,
robh+dt@kernel.org
Subject: Re: spurious warning from of_i2c_register_device with fixed_regulator?
Date: Wed, 16 Mar 2016 12:20:16 +0100 [thread overview]
Message-ID: <20160316112016.GC1542@katana> (raw)
In-Reply-To: <20160316110156.GC21259@amd>
[-- Attachment #1: Type: text/plain, Size: 200 bytes --]
> But we have fixed regulator there, it does not have "reg" property.
The fixed regulator doesn't even use I2C. So, you need to debug why it
calls I2C. Your information given is not enough for me.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-16 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 11:01 spurious warning from of_i2c_register_device with fixed_regulator? Pavel Machek
2016-03-16 11:20 ` Wolfram Sang [this message]
2016-03-23 11:34 ` Pavel Machek
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=20160316112016.GC1542@katana \
--to=wsa@the-dreams.de \
--cc=grant.likely@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=pavel@denx.de \
--cc=robh+dt@kernel.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).