Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Gabor Juhos <juhosg@openwrt.org>
To: John Crispin <blogic@openwrt.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	linux-mips@linux-mips.org, devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH 2/6] DT: add documentation for the Ralink MIPS SoCs
Date: Sun, 14 Apr 2013 11:44:24 +0200	[thread overview]
Message-ID: <516A7A78.7060502@openwrt.org> (raw)
In-Reply-To: <1365843026-11015-2-git-send-email-blogic@openwrt.org>

2013.04.13. 10:50 keltezéssel, John Crispin írta:
> From: Gabor Juhos <juhosg@openwrt.org>
> 
> This patch adds binding documentation for the
> compatible values of the Ralink MIPS SoCs.
> 
> Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
> ---
>  Documentation/devicetree/bindings/mips/ralink.txt |   17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/mips/ralink.txt
> 
> diff --git a/Documentation/devicetree/bindings/mips/ralink.txt b/Documentation/devicetree/bindings/mips/ralink.txt
> new file mode 100644
> index 0000000..43fc03c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mips/ralink.txt
> @@ -0,0 +1,17 @@
> +Ralink MIPS SoC device tree bindings
> +
> +1. SoCs
> +
> +Each device tree must specify a compatible value for the Ralink SoC
> +it uses in the compatible property of the root node. The compatible
> +value must be one of the following values:
> +
> +  ralink,rt2880-soc
> +  ralink,rt3050-soc
> +  ralink,rt3052-soc
> +  ralink,rt3350-soc
> +  ralink,rt3352-soc
> +  ralink,rt3883-soc
> +  ralink,rt5350-soc
> +  ralink,mt7620-soc

It seems that I was wrong here. We should have separate entries for the MT7620A
and for the MT7620N varians.

-Gabor

  reply	other threads:[~2013-04-14  9:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13  8:50 [PATCH 1/6] DT: add vendor prefixes for Ralink John Crispin
2013-04-13  8:50 ` [PATCH 2/6] DT: add documentation for the Ralink MIPS SoCs John Crispin
2013-04-14  9:44   ` Gabor Juhos [this message]
2013-04-13  8:50 ` [PATCH 3/6] DT: MIPS: ralink: extend RT3050 dtsi and dts file John Crispin
2013-04-13 14:49   ` Sergei Shtylyov
2013-04-13 17:59     ` John Crispin
2013-04-14  9:50       ` Gabor Juhos
2013-04-13  8:50 ` [PATCH 4/6] DT: MIPS: ralink: add RT2880 dts files John Crispin
2013-04-14  9:53   ` Gabor Juhos
2013-08-23 18:34   ` Sergei Shtylyov
2013-08-23 18:37     ` Sergei Shtylyov
2013-08-23 18:44     ` David Daney
2013-04-13  8:50 ` [PATCH 5/6] DT: MIPS: ralink: add RT3883 " John Crispin
2013-04-14  9:54   ` Gabor Juhos
2013-04-13  8:50 ` [PATCH 6/6] DT: MIPS: ralink: add MT7620 " John Crispin
2013-04-14 11:41   ` Gabor Juhos

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=516A7A78.7060502@openwrt.org \
    --to=juhosg@openwrt.org \
    --cc=blogic@openwrt.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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