public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Christophe Roullier <christophe.roullier@st.com>
Cc: mark.rutland@arm.com, mcoquelin.stm32@gmail.com,
	alexandre.torgue@st.com, peppe.cavallaro@st.com,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH  8/8] dt-bindings: stm32: add compatible for syscon
Date: Tue, 1 May 2018 09:01:24 -0500	[thread overview]
Message-ID: <20180501140124.GA17771@rob-hp-laptop> (raw)
In-Reply-To: <1524582120-4451-9-git-send-email-christophe.roullier@st.com>

On Tue, Apr 24, 2018 at 05:02:00PM +0200, Christophe Roullier wrote:
> This patch describes syscon DT bindings.
> 
> Signed-off-by: Christophe Roullier <christophe.roullier@st.com>
> ---
>  Documentation/devicetree/bindings/arm/stm32.txt | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/arm/stm32.txt b/Documentation/devicetree/bindings/arm/stm32.txt
> index 6808ed9..a871a78 100644
> --- a/Documentation/devicetree/bindings/arm/stm32.txt
> +++ b/Documentation/devicetree/bindings/arm/stm32.txt
> @@ -8,3 +8,10 @@ using one of the following compatible strings:
>    st,stm32f746
>    st,stm32h743
>    st,stm32mp157
> +
> +Required nodes:
> +
> +- syscon: some subnode of the STM32 SoC node must be a
> +  system controller node pointing to the control registers,
> +  with the compatible string set to one of these tuples:
> +  "st,stm32-syscfg", "syscon"

This should be a separate file.

I'd guess the syscfg registers differ from SoC to SoC, so you need more 
specific compatible strings.

Rob

      reply	other threads:[~2018-05-01 14:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 15:01 [PATCH 0/8] net: ethernet: stmmac: add support for stm32mp1 Christophe Roullier
2018-04-24 15:01 ` [PATCH 1/8] net: ethernet: stmmac: add adaptation for stm32mp157c Christophe Roullier
2018-04-24 15:39   ` Andrew Lunn
2018-04-25  7:12     ` Christophe ROULLIER
2018-04-25 12:40       ` Andrew Lunn
2018-04-24 15:01 ` [PATCH 2/8] dt-bindings: stm32-dwmac: add support of MPU families Christophe Roullier
2018-05-01 13:58   ` Rob Herring
2018-05-02  8:15     ` Christophe ROULLIER
2018-04-24 15:01 ` [PATCH 3/8] ARM: dts: stm32: add ethernet pins to stm32mp157c Christophe Roullier
2018-04-25 15:09   ` Rob Herring
2018-04-25 16:22     ` Alexandre Torgue
2018-04-24 15:01 ` [PATCH 4/8] ARM: dts: stm32: Add syscfg on stm32mp1 Christophe Roullier
2018-04-24 15:01 ` [PATCH 5/8] ARM: dts: stm32: Add ethernet dwmac " Christophe Roullier
2018-04-24 15:01 ` [PATCH 6/8] net: stmmac: add dwmac-4.20a compatible Christophe Roullier
2018-04-24 15:01 ` [PATCH 7/8] ARM: dts: stm32: add support of ethernet on stm32mp157c-ev1 Christophe Roullier
2018-04-24 15:02 ` [PATCH 8/8] dt-bindings: stm32: add compatible for syscon Christophe Roullier
2018-05-01 14:01   ` Rob Herring [this message]

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=20180501140124.GA17771@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=alexandre.torgue@st.com \
    --cc=christophe.roullier@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.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