From: "Andreas Färber" <afaerber@suse.de>
To: James Tai <james.tai@realtek.com>
Cc: linux-realtek-soc@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/2] dt-bindings: arm: realtek: Document RTD1319 and Realtek PymParticle EVB
Date: Mon, 13 Apr 2020 02:17:04 +0200 [thread overview]
Message-ID: <bf55ccbe-cbdf-7ba7-d701-aa84c20204e3@suse.de> (raw)
In-Reply-To: <20200204145207.28622-2-james.tai@realtek.com>
Hi James,
Am 04.02.20 um 15:52 schrieb James Tai:
> Define compatible strings for Realtek RTD1319 SoC and Realtek PymParticle
> EVB.
>
> Signed-off-by: James Tai <james.tai@realtek.com>
> ---
> v2 -> v3: Unchanged
>
> v1 -> v2:
> * Put string in alphabetical order
>
> Documentation/devicetree/bindings/arm/realtek.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/realtek.yaml b/Documentation/devicetree/bindings/arm/realtek.yaml
> index 845f9c76d6f7..3b48ae71fdd8 100644
> --- a/Documentation/devicetree/bindings/arm/realtek.yaml
> +++ b/Documentation/devicetree/bindings/arm/realtek.yaml
> @@ -42,6 +42,12 @@ properties:
> - synology,ds418 # Synology DiskStation DS418
> - const: realtek,rtd1296
>
> + # RTD1319 SoC based boards
> + - items:
> + - enum:
> + - realtek,pymparticle # Realtek PymParticle EVB
The board seems labelled "PYM_PARTICLES".
While Wikipedia has nothing on that, I found this explanation:
https://marvel.fandom.com/wiki/Pym_Particles
So, are you sure it's PymParticle and not "Pym Particle" with space or
"Pym Particles" with space and plural S? The S would affect also the
.dts filename. For the compatible string the question is pymparticle or
pym-particle.
By comparison, LION-SKIN was named lion-skin in the compatible and
spelled Lion Skin in textual form. If you believe that should be fixed,
now would be the time to revisit those patches that didn't make v5.7.
Thanks,
Andreas
> + - const: realtek,rtd1319
> +
> # RTD1395 SoC based boards
> - items:
> - enum:
--
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer
HRB 36809 (AG Nürnberg)
next prev parent reply other threads:[~2020-04-13 0:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 14:52 [PATCH v3 0/2] Initial RTD1319 SoC and Realtek PymParticle EVB support James Tai
2020-02-04 14:52 ` [PATCH v3 1/2] dt-bindings: arm: realtek: Document RTD1319 and Realtek PymParticle EVB James Tai
2020-02-05 16:47 ` Rob Herring
2020-02-07 2:53 ` James Tai [戴志峰]
2020-04-13 0:17 ` Andreas Färber [this message]
2020-04-15 8:58 ` James Tai [戴志峰]
2020-04-15 9:19 ` Andreas Färber
2020-02-04 14:52 ` [PATCH v3 2/2] arm64: dts: realtek: Add RTD1319 SoC " James Tai
2020-04-15 11:41 ` Andreas Färber
2020-04-16 8:47 ` James Tai [戴志峰]
2020-04-16 9:45 ` Robin Murphy
2020-04-16 15:00 ` James Tai [戴志峰]
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=bf55ccbe-cbdf-7ba7-d701-aa84c20204e3@suse.de \
--to=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=james.tai@realtek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=mark.rutland@arm.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