All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Chunyan Zhang <zhang.lyra@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, Baolin Wang <baolin.wang7@gmail.com>,
	Orson Zhai <orsonzhai@gmail.com>,
	Chunyan Zhang <chunyan.zhang@unisoc.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] dt-bindings: regulator: Add bindings for Unisoc's SC2730 regulator
Date: Fri, 12 Nov 2021 13:46:38 +0000	[thread overview]
Message-ID: <YY5wPh0rwRvFjSRG@sirena.org.uk> (raw)
In-Reply-To: <20211008031953.339461-3-zhang.lyra@gmail.com>

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

On Fri, Oct 08, 2021 at 11:19:53AM +0800, Chunyan Zhang wrote:

> +properties:
> +  compatible:
> +    const: sprd,sc2730-regulator

I still don't understand why this MFD subfunction for a specific device
is a separate binding with a separate compatible string, the issues I
mentioned previously with this just encoding current Linux internals
into the DT rather than describing the device still apply.

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

  reply	other threads:[~2021-11-12 13:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08  3:19 [PATCH v2 0/2] Add Unisoc's SC2730 regulator support Chunyan Zhang
2021-10-08  3:19 ` [PATCH v2 1/2] regulator: Add Unisoc's SC2730 regulator driver Chunyan Zhang
2021-10-08  3:19 ` [PATCH v2 2/2] dt-bindings: regulator: Add bindings for Unisoc's SC2730 regulator Chunyan Zhang
2021-11-12 13:46   ` Mark Brown [this message]
2022-09-22  8:25     ` Chunyan Zhang
2022-09-22 10:19       ` Lee Jones
2022-09-22 11:43         ` Mark Brown
2022-09-26  6:59           ` Lee Jones
2022-09-28 17:27             ` Mark Brown

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=YY5wPh0rwRvFjSRG@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=baolin.wang7@gmail.com \
    --cc=chunyan.zhang@unisoc.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=orsonzhai@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=zhang.lyra@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.