public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Alexey Charkov <alchark@flipper.net>
Cc: Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Chris Morgan <macromorgan@hotmail.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Sebastian Reichel <sre@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sebastian Reichel <sebastian.reichel@collabora.com>,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 04/11] regulator: bq257xx: Make OTG enable GPIO really optional
Date: Fri, 6 Mar 2026 19:36:28 +0000	[thread overview]
Message-ID: <aassvAsgFTlFnD8M@sirena.co.uk> (raw)
In-Reply-To: <20260306-bq25792-v2-4-6595249d6e6f@flipper.net>

[-- Attachment #1: Type: text/plain, Size: 401 bytes --]

On Fri, Mar 06, 2026 at 06:33:04PM +0400, Alexey Charkov wrote:
> The bindings describe the OTG enable GPIO as optional, but the driver
> gets upset if it's not provided in the device tree.
> 
> Make the driver accept the absence of the GPIO, and just use register
> writes to handle OTG mode in that case, skipping the error message for
> -ENOENT.

Acked-by: Mark Brown <broonie@kernel.org>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2026-03-06 19:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 14:33 [PATCH v2 00/11] Add support for the TI BQ25792 battery charger Alexey Charkov
2026-03-06 14:33 ` [PATCH v2 01/11] dt-bindings: mfd: ti,bq25703a: Expand to include BQ25792 Alexey Charkov
2026-03-07 15:06   ` Krzysztof Kozlowski
2026-03-06 14:33 ` [PATCH v2 02/11] regulator: bq257xx: Remove reference to the parent MFD's dev Alexey Charkov
2026-03-06 19:33   ` Mark Brown
2026-03-06 14:33 ` [PATCH v2 03/11] regulator: bq257xx: Drop the regulator_dev from the driver data Alexey Charkov
2026-03-06 19:33   ` Mark Brown
2026-03-06 14:33 ` [PATCH v2 04/11] regulator: bq257xx: Make OTG enable GPIO really optional Alexey Charkov
2026-03-06 19:36   ` Mark Brown [this message]
2026-03-06 14:33 ` [PATCH v2 05/11] power: supply: bq257xx: Fix VSYSMIN clamping logic Alexey Charkov
2026-03-06 14:33 ` [PATCH v2 06/11] power: supply: bq257xx: Make the default current limit a per-chip attribute Alexey Charkov
2026-03-06 14:33 ` [PATCH v2 07/11] power: supply: bq257xx: Consistently use indirect get/set helpers Alexey Charkov
2026-03-06 14:33 ` [PATCH v2 08/11] power: supply: bq257xx: Add fields for 'charging' and 'overvoltage' states Alexey Charkov
2026-03-06 14:33 ` [PATCH v2 09/11] mfd: bq257xx: Add BQ25792 support Alexey Charkov
2026-03-06 14:33 ` [PATCH v2 10/11] regulator: bq257xx: Add support for BQ25792 Alexey Charkov
2026-03-06 19:38   ` Mark Brown
2026-03-06 14:33 ` [PATCH v2 11/11] power: supply: " Alexey Charkov
2026-03-09 21:53 ` [PATCH v2 00/11] Add support for the TI BQ25792 battery charger Chris Morgan

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=aassvAsgFTlFnD8M@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=alchark@flipper.net \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=macromorgan@hotmail.com \
    --cc=robh@kernel.org \
    --cc=sebastian.reichel@collabora.com \
    --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