Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Victor Krawiec <victor.krawiec@arturia.com>,
	Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 1/4] regulator: dt-bindings: Add Silergy SYR82X allowed modes
Date: Sun, 19 Jul 2026 07:58:01 +0200	[thread overview]
Message-ID: <98848a59-6385-48d0-926f-3e78aea9a386@kernel.org> (raw)
In-Reply-To: <c3977e59-951b-4d91-a775-6c96cb84e37c@arturia.com>

On 17/07/2026 16:14, Victor Krawiec wrote:
> 
> 
> On 7/17/26 14:44, Mark Brown wrote:
>> On Fri, Jul 17, 2026 at 02:31:51PM +0200, Krzysztof Kozlowski wrote:
>>
>>> So you are adding constants for one device but used in the bindings and
>>> driver for other? Are they valid there?
>>
>> It's one of these devices that's got a bunch of clones from various
>> manufacturers with minor differences and share a driver.
> 
> I checked the datasheets and all devices share the same 2 modes which
> are Auto-PFM and Forced PWM mode.
> 
> Since devices are all clones and share the same modes the binding part
> can be generic. I plan to rename the header and its macros to use
> FAN53555 name and add this property to the binding:
> 
> regulator-initial-mode:
>     enum:
>       [ 1, 2 ]
>     description:
>       Defined in
>       include/dt-bindings/regulator/fcs,fan53555-regulator.h
> 
> However the implementation I made in the driver is currently
> restricted to SYR82X. I could make it generic but I don't have access
> to the other devices to test it.
> 

Old name of header file is fine, but please explain this in commit msg.

Best regards,
Krzysztof

  reply	other threads:[~2026-07-19  5:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 15:51 [PATCH 0/4] Configure SYR82X regulator modes via device tree Victor Krawiec
2026-07-15 15:51 ` [PATCH 1/4] regulator: dt-bindings: Add Silergy SYR82X allowed modes Victor Krawiec
2026-07-15 16:02   ` sashiko-bot
2026-07-17  9:08   ` Krzysztof Kozlowski
2026-07-17 12:02     ` Victor Krawiec
2026-07-17 12:31       ` Krzysztof Kozlowski
2026-07-17 12:44         ` Mark Brown
2026-07-17 14:14           ` Victor Krawiec
2026-07-19  5:58             ` Krzysztof Kozlowski [this message]
2026-07-15 15:51 ` [PATCH 2/4] arm64: dts: rk3399-rock-4c-plus: Use device tree bindings constants for SYR828 regulator initial mode Victor Krawiec
2026-07-15 15:51 ` [PATCH 3/4] arm64: dts: rockchip: rk3399-hugsun-x99: Update SYR828 regulator initial mode to use device tree bindings constants Victor Krawiec
2026-07-15 15:51 ` [PATCH 4/4] regulator: fan53555: Add support for mode operations on Silergy devices Victor Krawiec
2026-07-15 16:02   ` sashiko-bot

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=98848a59-6385-48d0-926f-3e78aea9a386@kernel.org \
    --to=krzk@kernel.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=victor.krawiec@arturia.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