From: Philippe De Muyter <phdm@macq.eu>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: Jean-Baptiste Maneyrol <JManeyrol@invensense.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: invensense mpu9250 ak8963 and devicetree
Date: Tue, 9 Mar 2021 11:11:26 +0100 [thread overview]
Message-ID: <20210309101126.GA11691@frolo.macqel> (raw)
In-Reply-To: <20210308172427.000032d2@Huawei.com>
Hello Jonathan,
Thank you for your answer that led me to the explanation.
On Mon, Mar 08, 2021 at 05:24:27PM +0000, Jonathan Cameron wrote:
>
> That's odd because you should get a stub regulator... For simple cases
> where the regulator is always on, there is no need to specify a regulator,
> you can just rely on the regulator framework giving you one that basically
> does nothing.
>
> Could you have a look at why you aren't getting a dummy_regulator from the code
> just below here?
>
> https://elixir.bootlin.com/linux/latest/source/drivers/regulator/core.c#L1948
>
I use a kernel provided by nvidia that is called tegra-l4t-r32.3.1, but
is based on v4.9.
Although the patch that provides automatically stub regulators
4ddfebd3b "regulator: core: Provide a dummy regulator with full constraints"
is older than v3.13, I have found in the commits of my kernel on top of
v4.9, this one
commit 7f25dfa01aafe3d3ac1983a0d0f895775a80c005
Author: Laxman Dewangan <ldewangan@nvidia.com>
Date: Tue Aug 11 18:28:53 2015 +0530
regulator: core: do not allow dummy regulator if config not selected
Do not allow dummy regulator if DUMMY REGULATOR not selected from
config.
Bug 200223300
Change-Id: I672fb4f9d70f05bf3044b63c904be54e19c8ab36
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-on: http://git-master/r/781784
(cherry picked from commit 4e11e2b997d315587956e8537064277c5687bf70)
Reviewed-on: http://git-master/r/1195179
Signed-off-by: Venkat Reddy Talla <vreddytalla@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1550248
Tested-by: Ujwal Patel <ujwalp@nvidia.com>
Reviewed-by: svc-mobile-coverity <svc-mobile-coverity@nvidia.com>
Reviewed-by: svccoveritychecker <svccoveritychecker@nvidia.com>
Reviewed-by: Shardar Mohammed <smohammed@nvidia.com>
Tested-by: Shardar Mohammed <smohammed@nvidia.com>
GVS: Gerrit_Virtual_Submit
And CONFIG_REGULATOR_DUMMY is disabled in the default kernel configuration
provided by nvidia :(
Philippe
next prev parent reply other threads:[~2021-03-09 10:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 15:31 invensense mpu9250 ak8963 and devicetree Philippe De Muyter
2021-03-04 9:12 ` Jean-Baptiste Maneyrol
2021-03-04 9:31 ` Philippe De Muyter
[not found] ` <BL0PR12MB501190F3812AA541BDBEF625C4979@BL0PR12MB5011.namprd12.prod.outlook.com>
2021-03-08 13:06 ` Philippe De Muyter
2021-03-08 17:24 ` Jonathan Cameron
2021-03-09 10:11 ` Philippe De Muyter [this message]
2021-03-09 10:46 ` Lars-Peter Clausen
2021-03-09 10:59 ` Philippe De Muyter
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=20210309101126.GA11691@frolo.macqel \
--to=phdm@macq.eu \
--cc=JManeyrol@invensense.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=linux-iio@vger.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