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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 20 Jun 2012 16:04:26 +0800
From:	Danny Huang <dahuang@...dia.com>
To:	Axel Lin <axel.lin@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:	Mike Rapoport <mike@...pulab.co.il>, Liam Girdwood <lrg@...com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Subject: RE: regulator: tps6586x: What is the meaning of
 TPS6586X_SLEW_RATE_SET setting?

Hi Axel,

The TPS6586X_SLEW_RATE_SET is not related with hardware register.
It was used to make sure that the slew rate won't be changed by accident.

Thanks,
Danny

-----Original Message-----
From: Axel Lin [mailto:axel.lin@...il.com] 
Sent: Tuesday, June 19, 2012 19:15
To: linux-kernel@...r.kernel.org
Cc: Mike Rapoport; Danny Huang; Liam Girdwood; Mark Brown
Subject: regulator: tps6586x: What is the meaning of TPS6586X_SLEW_RATE_SET setting?

Hi Mike,
While looking at the datasheet (tps65860 and tps65862),
I don't understand why we have TPS6586X_SLEW_RATE_SET (0x08) in the code.

According to the datasheet, BIT3 of SM1SL/SM0SL is not used:

SM1SL [Addr 0x25]
SM0SL [Addr 0x28]
        BIT[2:0] SM0/SM1 SUPPLY RAMP RATE
        BIT[7:3] NOT USED

So why we need to check the "unused bit" in tps6586x_regulator_set_slew_rate()?

        if (!(setting->slew_rate & TPS6586X_SLEW_RATE_SET))
                return 0;

Regards,
Axel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ