linux-kernel - Re: [PATCH 2/2] iio: imu: mpu6050: Add support for vdd-supply regulator

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <MN2PR12MB3373846E85AA1A396198F46EC4780@MN2PR12MB3373.namprd12.prod.outlook.com>
Date:   Thu, 7 Nov 2019 13:29:33 +0000
From:   Jean-Baptiste Maneyrol <JManeyrol@...ensense.com>
To:     Stephan Gerhold <stephan@...hold.net>
CC:     Jonathan Cameron <jic23@...nel.org>,
        Hartmut Knaack <knaack.h@....de>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Peter Meerwald-Stadler <pmeerw@...erw.net>,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Linus Walleij <linus.walleij@...aro.org>,
        Brian Masney <masneyb@...tation.org>,
        Jonathan Marek <jonathan@...ek.ca>,
        "linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] iio: imu: mpu6050: Add support for vdd-supply
 regulator

 Hi Stephan,

I think the regulator_bulk usage is good, and the core_enable/disable_regulator functions implemented the way you did is perfect for the init/shutdown phase.

We just need to change the suspend/resume implementation to use something different.

Thanks,
JB


From: linux-iio-owner@...r.kernel.org <linux-iio-owner@...r.kernel.org> on behalf of Stephan Gerhold <stephan@...hold.net>

Sent: Wednesday, November 6, 2019 22:36

To: Jean-Baptiste Maneyrol <JManeyrol@...ensense.com>

Cc: Jonathan Cameron <jic23@...nel.org>; Hartmut Knaack <knaack.h@....de>; Lars-Peter Clausen <lars@...afoo.de>; Peter Meerwald-Stadler <pmeerw@...erw.net>; Rob Herring <robh+dt@...nel.org>; Mark Rutland <mark.rutland@....com>; Linus Walleij <linus.walleij@...aro.org>;
 Brian Masney <masneyb@...tation.org>; Jonathan Marek <jonathan@...ek.ca>; linux-iio@...r.kernel.org <linux-iio@...r.kernel.org>; devicetree@...r.kernel.org <devicetree@...r.kernel.org>; linux-kernel@...r.kernel.org <linux-kernel@...r.kernel.org>

Subject: Re: [PATCH 2/2] iio: imu: mpu6050: Add support for vdd-supply regulator

 


 CAUTION: This email originated from outside of the organization. Please make sure the sender is who they say they are and do not click links or open attachments unless you recognize the sender and know the content is safe.



Hi JB,



On Wed, Nov 06, 2019 at 07:55:20PM +0000, Jean-Baptiste Maneyrol wrote:

> Hello Stephan,

> 

> nice patch but I have an important concern.

> 

> We are calling the core_enable/disable_regulator functions when going into suspend and resume.

> With your changes, we are going to power down the chip when going into suspend and then power it up again.

> This way we will loose all already set configuration, like FSR, sampling rate, init values, ...

> The chip will not be able to work correctly anymore after a suspend-resume cycle.

> 

> You need to change the resume/suspend handlers to only disable/enable the vddio regulator, not the vdd one.



That is a good point, thanks!

I guess we are not able to use the regulator bulk API in this case...



I will send a v2 soon.



Stephan