From: Fabio Estevam <festevam@gmail.com>
To: broonie@kernel.org
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
robh+dt@kernel.org, Fabio Estevam <festevam@gmail.com>,
jee.heng.sia@intel.com
Subject: [PATCH] ASoC: dt-bindings: keembay-i2s: Fix reg descriptions
Date: Tue, 30 Jun 2020 19:44:59 -0300 [thread overview]
Message-ID: <20200630224459.27174-1-festevam@gmail.com> (raw)
intel,keembay-i2s has two register regions:
- I2S registers
- I2S gen configuration
Describe these regions accordingly to fix the following warning seen
with 'make dt_binding_check':
Documentation/devicetree/bindings/sound/intel,keembay-i2s.example.dt.yaml: example-0: i2s@20140000:reg:0: [538181632, 512, 539623588, 4] is too long
Signed-off-by: Fabio Estevam <festevam@gmail.com>
---
.../devicetree/bindings/sound/intel,keembay-i2s.yaml | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/sound/intel,keembay-i2s.yaml b/Documentation/devicetree/bindings/sound/intel,keembay-i2s.yaml
index 175e4fb0c315..2e0bbc1c868a 100644
--- a/Documentation/devicetree/bindings/sound/intel,keembay-i2s.yaml
+++ b/Documentation/devicetree/bindings/sound/intel,keembay-i2s.yaml
@@ -23,7 +23,8 @@ properties:
reg:
items:
- - description: I2S configuration
+ - description: I2S registers
+ - description: I2S gen configuration
reg-names:
items:
@@ -60,7 +61,8 @@ examples:
i2s3: i2s@20140000 {
compatible = "intel,keembay-i2s";
#sound-dai-cells = <0>;
- reg = <0x20140000 0x200 0x202a00a4 0x4>;
+ reg = <0x20140000 0x200>, /* I2S registers */
+ <0x202a00a4 0x4>; /* I2S gen configuration */
reg-names = "i2s-regs", "i2s_gen_cfg";
interrupts = <GIC_SPI 120 IRQ_TYPE_LEVEL_HIGH>;
clock-names = "osc", "apb_clk";
--
2.17.1
next reply other threads:[~2020-06-30 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 22:44 Fabio Estevam [this message]
2020-07-01 22:23 ` [PATCH] ASoC: dt-bindings: keembay-i2s: Fix reg descriptions 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=20200630224459.27174-1-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jee.heng.sia@intel.com \
--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).