linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
To: "robh@kernel.org" <robh@kernel.org>, "krzk@kernel.org" <krzk@kernel.org>
Cc: "linux-imx@nxp.com" <linux-imx@nxp.com>,
	"robert.chiras@nxp.com" <robert.chiras@nxp.com>,
	"etnaviv@lists.freedesktop.org" <etnaviv@lists.freedesktop.org>,
	"l.stach@pengutronix.de" <l.stach@pengutronix.de>,
	"daniel@ffwll.ch" <daniel@ffwll.ch>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"leoyang.li@nxp.com" <leoyang.li@nxp.com>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"christian.gmeiner@gmail.com" <christian.gmeiner@gmail.com>,
	"linux+etnaviv@armlinux.org.uk" <linux+etnaviv@armlinux.org.uk>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"airlied@linux.ie" <airlied@linux.ie>,
	"lee.jones@linaro.org" <lee.jones@linaro.org>,
	"sam@ravnborg.org" <sam@ravnborg.org>,
	"festevam@gmail.com" <festevam@gmail.com>
Subject: Re: [PATCH 06/13] dt-bindings: mfd: rohm,bd71837-pmic: Add common properties
Date: Tue, 15 Sep 2020 06:34:46 +0000	[thread overview]
Message-ID: <6bfa15383657ca38a28edac38b5e8adf891865e7.camel@fi.rohmeurope.com> (raw)
In-Reply-To: <20200914224407.GA388924@bogus>


Hello All,

On Mon, 2020-09-14 at 16:44 -0600, Rob Herring wrote:
> On Fri, Sep 04, 2020 at 04:53:05PM +0200, Krzysztof Kozlowski wrote:
> > Add common properties appearing in DTSes (clock-names,
> > clock-output-names) to fix dtbs_check warnings like:
> > 
> >   arch/arm64/boot/dts/freescale/imx8mq-librem5-r2.dt.yaml:
> >     pmic@4b: 'clock-names', 'clock-output-names', do not match any
> > of the regexes: 'pinctrl-[0-9]+'
> > 
> > Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> > ---
> >  .../devicetree/bindings/mfd/rohm,bd71837-pmic.yaml          | 6
> > ++++++
> >  1 file changed, 6 insertions(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/mfd/rohm,bd71837-
> > pmic.yaml b/Documentation/devicetree/bindings/mfd/rohm,bd71837-
> > pmic.yaml
> > index 65018a019e1d..ecce0d5e3a95 100644
> > --- a/Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.yaml
> > +++ b/Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.yaml
> > @@ -32,9 +32,15 @@ properties:
> >    clocks:
> >      maxItems: 1
> >  
> > +  clock-names:
> > +    maxItems: 1
> 
> Needs to define what the name is.

Someone once told me that "naming is hard".
Do we have some good common convention for 32K oscillator input naming?
Or should it just be dropped?

> 
> > +
> >    "#clock-cells":
> >      const: 0
> >  
> > +  clock-output-names:
> > +    maxItems: 1
> 
> Ideally this one too, but we've been more flexible on it.

Data-sheet for BD71837 uses pin name "C32k_OUT". So maybe this would be
good?

BD71838 uses "bd71828-32k-out" . so we could also go with this same
convention and use "bd71837-32k-out". Or - we could take a risk and
*assume* typical use case for this clk (as this is typically used with
i.MX8 I'd guess the 32k is used for RTC) and name it accordingly.

Br,
	Matti Vaittinen

--
Matti Vaittinen, Linux device drivers
ROHM Semiconductors, Finland
SWDC
Kiviharjunlenkki 1E
90220 OULU
FINLAND

~~~ "I don't think so," said Rene Descartes. Just then he vanished ~~~

Simon says - in Latin please.
"non cogito me" dixit Rene Descarte, deinde evanescavit

(Thanks for the translation Simon)


  reply	other threads:[~2020-09-15  6:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04 14:52 [PATCH 00/13] iMX 8 - Another round of cleanups Krzysztof Kozlowski
2020-09-04 14:53 ` [PATCH 01/13] dt-bindings: power: fsl,imx-gpcv2: Document interrupt controller properties Krzysztof Kozlowski
2020-09-04 14:58   ` Lucas Stach
2020-09-14 22:31   ` [PATCH 01/13] dt-bindings: power: fsl, imx-gpcv2: " Rob Herring
2020-09-04 14:53 ` [PATCH 02/13] dt-bindings: display: bridge: nwl-dsi: Add common properties Krzysztof Kozlowski
2020-09-14 22:31   ` Rob Herring
2020-09-04 14:53 ` [PATCH 03/13] dt-bindings: arm: fsl: Fix matching Purism Librem5 phones Krzysztof Kozlowski
2020-09-14 22:33   ` Rob Herring
2020-09-16  6:38     ` Krzysztof Kozlowski
2020-09-21 13:09   ` Shawn Guo
2020-09-04 14:53 ` [PATCH 04/13] dt-bindings: gpu: vivante,gc: Add common properties Krzysztof Kozlowski
2020-09-04 14:59   ` Lucas Stach
2020-09-14 22:34   ` Rob Herring
2020-09-04 14:53 ` [PATCH 05/13] dt-bindings: gpu: vivante,gc: Remove trailing whitespace Krzysztof Kozlowski
2020-09-04 14:59   ` Lucas Stach
2020-09-14 22:34   ` [PATCH 05/13] dt-bindings: gpu: vivante, gc: " Rob Herring
2020-09-04 14:53 ` [PATCH 06/13] dt-bindings: mfd: rohm,bd71837-pmic: Add common properties Krzysztof Kozlowski
2020-09-14 22:44   ` Rob Herring
2020-09-15  6:34     ` Vaittinen, Matti [this message]
2020-09-15 14:38       ` Rob Herring
2020-09-04 14:53 ` [PATCH 07/13] dt-bindings: mfd: rohm,bd71847-pmic: Add common clock-names Krzysztof Kozlowski
2020-09-14 22:44   ` Rob Herring
2020-09-04 14:53 ` [PATCH 08/13] arm64: dts: imx8mm-var-som-symphony: Use newer interrupts property Krzysztof Kozlowski
2020-09-13  1:19   ` Shawn Guo
2020-09-04 14:53 ` [PATCH 09/13] arm64: dts: imx8mp-evk: Align pin configuration group names with schema Krzysztof Kozlowski
2020-09-04 14:59   ` Lucas Stach
2020-09-04 14:53 ` [PATCH 10/13] arm64: dts: imx8mq: Add missing interrupts to GPC Krzysztof Kozlowski
2020-09-04 15:04   ` Lucas Stach
2020-09-04 14:53 ` [PATCH 11/13] arm64: dts: imx8mq-librem5: Align regulator names with schema Krzysztof Kozlowski
2020-09-04 14:53 ` [PATCH 12/13] arm64: dts: imx8mq-librem5: Drop interrupt-names in PMIC Krzysztof Kozlowski
2020-09-04 14:53 ` [PATCH 13/13] arm64: dts: imx8mq-librem5: Add interrupt-names to ti,tps6598x Krzysztof Kozlowski

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=6bfa15383657ca38a28edac38b5e8adf891865e7.camel@fi.rohmeurope.com \
    --to=matti.vaittinen@fi.rohmeurope.com \
    --cc=airlied@linux.ie \
    --cc=christian.gmeiner@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=etnaviv@lists.freedesktop.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk@kernel.org \
    --cc=l.stach@pengutronix.de \
    --cc=lee.jones@linaro.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux+etnaviv@armlinux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.chiras@nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sam@ravnborg.org \
    --cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).