Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alexey Charkov <alchark@flipper.net>
Cc: "Sebastian Reichel" <sre@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Pali Rohár" <pali@kernel.org>, "Andrew F. Davis" <afd@ti.com>,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: power: supply: bq27xxx: add BQ28Z620
Date: Sat, 3 Oct 2026 16:37:28 +0200	[thread overview]
Message-ID: <20261003-adventurous-attractive-bird-fea9ef@quoll> (raw)
In-Reply-To: <20261002-bq28z620-v1-1-bdcc10d42519@flipper.net>

On Fri, Oct 02, 2026 at 04:02:54PM +0400, Alexey Charkov wrote:
> Add a compatible for the TI BQ28Z620, a firmware derivative of the
> BQ28Z610 that keeps its standard command set but drops the Battery Trip
> Point feature and relocates much of the data flash as a result.
> 
> Keep it standalone rather than falling back to ti,bq28z610, as software
> programming the BQ28Z610 data flash layout would corrupt the
> configuration of a BQ28Z620.
> 
> Link: https://www.ti.com/product/BQ28Z620
> Signed-off-by: Alexey Charkov <alchark@flipper.net>
> ---
>  Documentation/devicetree/bindings/power/supply/bq27xxx.yaml | 2 ++
>  1 file changed, 2 insertions(+)
> 

Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

Best regards,
Krzysztof


  reply	other threads:[~2026-10-03 14:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 12:02 [PATCH 0/2] power: supply: bq27xxx: Add TI BQ28Z620 battery gauge Alexey Charkov
2026-10-02 12:02 ` [PATCH 1/2] dt-bindings: power: supply: bq27xxx: add BQ28Z620 Alexey Charkov
2026-10-03 14:37   ` Krzysztof Kozlowski [this message]
2026-10-02 12:02 ` [PATCH 2/2] power: supply: bq27xxx: add support for BQ28Z620 Alexey Charkov
2026-10-04 17:46 ` [PATCH 0/2] power: supply: bq27xxx: Add TI BQ28Z620 battery gauge Sebastian Reichel

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=20261003-adventurous-attractive-bird-fea9ef@quoll \
    --to=krzk@kernel.org \
    --cc=afd@ti.com \
    --cc=alchark@flipper.net \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pali@kernel.org \
    --cc=robh@kernel.org \
    --cc=sre@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