From: Philippe De Muyter <phdm@macq.eu>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
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:59:38 +0100 [thread overview]
Message-ID: <20210309105938.GA16399@frolo.macqel> (raw)
In-Reply-To: <c5860a82-e3ba-3409-a711-847c8bcf7e1e@metafoo.de>
Thank you Lars,
On Tue, Mar 09, 2021 at 11:46:54AM +0100, Lars-Peter Clausen wrote:
> On 3/9/21 11:11 AM, Philippe De Muyter wrote:
>> 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
> [...]
>> And CONFIG_REGULATOR_DUMMY is disabled in the default kernel configuration
>> provided by nvidia :(
>
> To work around this you can add a fixed-regulator to your devicetree and
> connect it to the IMU.
> Seehttps://www.kernel.org/doc/Documentation/devicetree/bindings/regulator/fixed-regulator.txt
I have enabled REGULATOR_DUMMY and that solved the problem.
Philippe
prev parent reply other threads:[~2021-03-09 11:00 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
2021-03-09 10:46 ` Lars-Peter Clausen
2021-03-09 10:59 ` Philippe De Muyter [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=20210309105938.GA16399@frolo.macqel \
--to=phdm@macq.eu \
--cc=JManeyrol@invensense.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=lars@metafoo.de \
--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