linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Davis <afd@ti.com>
To: Lee Jones <lee@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Linus Walleij <linus.walleij@linaro.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Daniel Tang <dt.tangr@gmail.com>,
	Fabian Vogt <fabian@ritter-vogt.de>
Cc: <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, Andrew Davis <afd@ti.com>
Subject: [PATCH v3 1/9] dt-bindings: mfd: syscon: Add TI-Nspire misc registers compatible
Date: Thu, 27 Oct 2022 13:13:29 -0500	[thread overview]
Message-ID: <20221027181337.8651-2-afd@ti.com> (raw)
In-Reply-To: <20221027181337.8651-1-afd@ti.com>

The TI Nspire devices contain a set of registers with a seemingly
miscellaneous set of functionality. This area is known simply as the
"misc" region. As "syscon" nodes like this still need a specific
compatible, document "ti,nspire-misc" here.

Signed-off-by: Andrew Davis <afd@ti.com>
---
 Documentation/devicetree/bindings/mfd/syscon.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/mfd/syscon.yaml b/Documentation/devicetree/bindings/mfd/syscon.yaml
index 4e4baf53796d..37a00532ea79 100644
--- a/Documentation/devicetree/bindings/mfd/syscon.yaml
+++ b/Documentation/devicetree/bindings/mfd/syscon.yaml
@@ -69,6 +69,7 @@ properties:
               - samsung,exynos5433-sysreg
               - samsung,exynos850-sysreg
               - samsung,exynosautov9-sysreg
+              - ti,nspire-misc
 
           - const: syscon
 
-- 
2.37.3


  reply	other threads:[~2022-10-27 18:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27 18:13 [PATCH v3 0/9] TI-Nspire cleanups Andrew Davis
2022-10-27 18:13 ` Andrew Davis [this message]
2022-10-27 19:32   ` [PATCH v3 1/9] dt-bindings: mfd: syscon: Add TI-Nspire misc registers compatible Krzysztof Kozlowski
2022-10-27 18:13 ` [PATCH v3 2/9] ARM: dts: nspire: Use syscon-reboot to handle restart Andrew Davis
2022-10-27 19:33   ` Krzysztof Kozlowski
2022-10-27 21:07     ` Andrew Davis
2022-10-27 21:27       ` Krzysztof Kozlowski
2022-10-31 14:30         ` Andrew Davis
2022-10-31 17:14           ` Rob Herring
2022-11-01 13:04             ` Andrew Davis
2022-10-27 18:13 ` [PATCH v3 3/9] ARM: dts: nspire: Fix cpu node to conform with DT binding Andrew Davis
2022-10-27 18:13 ` [PATCH v3 4/9] ARM: dts: nspire: Fix sram " Andrew Davis
2022-10-27 18:13 ` [PATCH v3 5/9] ARM: dts: nspire: Fix vbus_reg " Andrew Davis
2022-10-27 18:13 ` [PATCH v3 6/9] ARM: dts: nspire: Fix uart " Andrew Davis
2022-10-27 19:34   ` Krzysztof Kozlowski
2022-10-27 18:13 ` [PATCH v3 7/9] ARM: dts: nspire: Use MATRIX_KEY macro for linux,keymap Andrew Davis
2022-10-27 18:13 ` [PATCH v3 8/9] ARM: nspire: Use syscon-reboot to handle restart Andrew Davis
2022-10-27 18:13 ` [PATCH v3 9/9] ARM: nspire: Remove unused header file mmio.h Andrew Davis

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=20221027181337.8651-2-afd@ti.com \
    --to=afd@ti.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dt.tangr@gmail.com \
    --cc=fabian@ritter-vogt.de \
    --cc=geert+renesas@glider.be \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lee@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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).