Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Fenglin Wu <quic_fenglinw@quicinc.com>
To: <kernel@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
	Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>
Cc: <linux-leds@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"David Collins" <quic_collinsd@quicinc.com>,
	Subbaraman Narayanamurthy <quic_subbaram@quicinc.com>
Subject: Re: [PATCH RESEND v3] leds: flash: leds-qcom-flash: limit LED current based on thermal condition
Date: Tue, 23 Jul 2024 11:15:26 +0800	[thread overview]
Message-ID: <b2c4d8da-780b-470d-87ee-263cafb050e8@quicinc.com> (raw)
In-Reply-To: <20240705-qcom_flash_thermal_derating-v3-1-8e2e2783e3a6@quicinc.com>



On 7/5/2024 3:55 PM, Fenglin Wu via B4 Relay wrote:
> From: Fenglin Wu <quic_fenglinw@quicinc.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@quicinc.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,

  parent reply	other threads:[~2024-07-23  3:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-05  7:55 [PATCH RESEND v3] leds: flash: leds-qcom-flash: limit LED current based on thermal condition Fenglin Wu via B4 Relay
2024-07-05 14:23 ` Luca Weiss
2024-07-08  2:59   ` Fenglin Wu
2024-07-08  7:39     ` Luca Weiss
2024-07-23  3:15 ` Fenglin Wu [this message]
2024-07-25 16:28 ` (subset) " Lee Jones

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=b2c4d8da-780b-470d-87ee-263cafb050e8@quicinc.com \
    --to=quic_fenglinw@quicinc.com \
    --cc=kernel@quicinc.com \
    --cc=lee@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=quic_collinsd@quicinc.com \
    --cc=quic_subbaram@quicinc.com \
    /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