linux-kernel - Re: [PATCH RESEND v3] leds: flash: leds-qcom-flash: limit LED current based on thermal condition

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <b2c4d8da-780b-470d-87ee-263cafb050e8@quicinc.com>
Date: Tue, 23 Jul 2024 11:15:26 +0800
From: Fenglin Wu <quic_fenglinw@...cinc.com>
To: <kernel@...cinc.com>, <linux-arm-msm@...r.kernel.org>,
        Pavel Machek
	<pavel@....cz>, Lee Jones <lee@...nel.org>
CC: <linux-leds@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        "David
 Collins" <quic_collinsd@...cinc.com>,
        Subbaraman Narayanamurthy
	<quic_subbaram@...cinc.com>
Subject: Re: [PATCH RESEND v3] leds: flash: leds-qcom-flash: limit LED current
 based on thermal condition



On 7/5/2024 3:55 PM, Fenglin Wu via B4 Relay wrote:
> From: Fenglin Wu <quic_fenglinw@...cinc.com>
> 
> The flash module has status bits to indicate different thermal
> conditions which are called as OTSTx. For each OTSTx status,
> there is a recommended total flash current for all channels to
> prevent the flash module entering into higher thermal level.
> For example, the total flash current should be limited to 1000mA/500mA
> respectively when the HW reaches the OTST1/OTST2 thermal level.
> 
> Signed-off-by: Fenglin Wu <quic_fenglinw@...cinc.com>
> ---
> Changes in v3:
> - Fix coding style issues to address review comments in v2.
> - Link to v2: https://lore.kernel.org/r/20240513-qcom_flash_thermal_derating-v2-1-e41a07d0eb83@quicinc.com
> 
> Changes in v2:
> - Update thermal threshold level 2 register definition for mvflash_4ch_regs.
>      Mvflash_4ch module thermal threshold level 2 configuration register
>      offset is 0x78, not succeeding from thermal threshold level 1 register 0x7a.
>      Hence it is not appropriate to use REG_FIELD_ID to define thermal threshold
>      register fileds like mvflash_3ch. Update to use REG_FIELD instead.
> - Link to v1: https://lore.kernel.org/r/20240509-qcom_flash_thermal_derating-v1-1-1d5e68e5d71c@quicinc.com
> ---

Hi Jones,

Can you help to review the change again when you are available?

Fenglin
> 
> Best regards,