mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Joshua Henderson <joshua.henderson@microchip.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-mips@linux-mips.org>,
	<ralf@linux-mips.org>, Rob Herring <robh+dt@kernel.org>,
	Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 05/14] dt/bindings: Add bindings for PIC32/MZDA platforms
Date: Fri, 8 Jan 2016 13:37:39 +0300	[thread overview]
Message-ID: <20160108133739.9a9c63c18fee346098354b21@gmail.com> (raw)
In-Reply-To: <1452211389-31025-6-git-send-email-joshua.henderson@microchip.com>

On Thu, 7 Jan 2016 17:00:20 -0700
Joshua Henderson <joshua.henderson@microchip.com> wrote:

> This adds support for the Microchip PIC32 platform along with the
> specific variant PIC32MZDA on a PIC32MZDA Starter Kit.
> 
> Signed-off-by: Joshua Henderson <joshua.henderson@microchip.com>
> Cc: Ralf Baechle <ralf@linux-mips.org>
> Acked-by: Rob Herring <robh@kernel.org>
> ---
>  .../bindings/mips/pic32/microchip,pic32mzda.txt    |   33 ++++++++++++++++++++
>  1 file changed, 33 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/mips/pic32/microchip,pic32mzda.txt
> 
> diff --git a/Documentation/devicetree/bindings/mips/pic32/microchip,pic32mzda.txt b/Documentation/devicetree/bindings/mips/pic32/microchip,pic32mzda.txt
> new file mode 100644
> index 0000000..bcf3e04
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mips/pic32/microchip,pic32mzda.txt
> @@ -0,0 +1,33 @@
> +* Microchip PIC32MZDA Platforms
> +
> +PIC32MZDA Starter Kit
> +Required root node properties:
> +    - compatible = "microchip,pic32mzda-sk", "microchip,pic32mzda"
> +
> +CPU nodes:
> +----------
> +A "cpus" node is required.  Required properties:
> + - #address-cells: Must be 1.
> + - #size-cells: Must be 0.
> +A CPU sub-node is also required.  Required properties:
> + - device_type: Must be "cpu".
> + - compatible: Must be "mti,mips14KEc".
> +Example:
> +	cpus {
> +		#address-cells = <1>;
> +		#size-cells = <0>;
> +
> +		cpu0: cpu@0 {
> +			device_type = "cpu";
> +			compatible = "mti,mips14KEc";
> +		};
> +	};
> +
> +Boot protocol
> +--------------
> +In accordance with the MIPS UHI specification[1], the bootloader must pass the
> +following arguments to the kernel:
> + - $a0: -2.
> + - $a1: KSEG0 address of the flattened device-tree blob.
> +
> +[1] http://prplfoundation.org/wiki/MIPS_documentation

At the moment the link [1] does not work. It is redirected to nonexisting "http://wiki.prplfoundation.org//MIPS_documentation" (prplfoundation.org site problem?).

The http://wiki.prplfoundation.org/wiki/MIPS_documentation URL works.

The "MIPS documentation" wiki page contains many documents so can we use 
more accurate URL, e.g. http://wiki.prplfoundation.org/wiki/MIPS_documentation#Unified_Hosting_Interface ?

Can we use more strict name for "MIPS UHI specification", e.g. "Unified Hosting Interface Reference Manual (MD01069)"?

-- 
Best regards,
  Antony Pavlov

  reply	other threads:[~2016-01-08 10:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08  0:00 [PATCH v3 00/14] Initial Microchip PIC32MZDA Support Joshua Henderson
2016-01-08  0:00 ` [PATCH v3 01/14] dt/bindings: Add bindings for PIC32 interrupt controller Joshua Henderson
2016-01-08  0:00 ` [PATCH v3 02/14] irqchip: irq-pic32-evic: Add support " Joshua Henderson
2016-01-08 19:04   ` Thomas Gleixner
2016-01-08 22:52     ` Joshua Henderson
2016-01-10 10:09       ` Thomas Gleixner
2016-01-12 19:39         ` Joshua Henderson
2016-01-08  0:00 ` [PATCH v3 03/14] dt/bindings: Add PIC32 clock binding documentation Joshua Henderson
2016-01-08  0:00 ` [PATCH v3 04/14] clk: clk-pic32: Add PIC32 clock driver Joshua Henderson
2016-01-08  0:00 ` [PATCH v3 05/14] dt/bindings: Add bindings for PIC32/MZDA platforms Joshua Henderson
2016-01-08 10:37   ` Antony Pavlov [this message]
2016-01-09  0:35     ` Joshua Henderson
2016-01-08  0:00 ` [PATCH v3 06/14] MIPS: Add support for PIC32MZDA platform Joshua Henderson
2016-01-08  0:00 ` [PATCH v3 07/14] dt/bindings: Add bindings for PIC32 pin control and GPIO Joshua Henderson
2016-01-08  0:00 ` [PATCH v3 08/14] pinctrl: pinctrl-pic32: Add PIC32 pin control driver Joshua Henderson
2016-01-08  0:00 ` [PATCH v3 09/14] dt/bindings: Add bindings for PIC32 UART driver Joshua Henderson
2016-01-08  0:00 ` [PATCH v3 10/14] serial: pic32_uart: Add " Joshua Henderson
2016-01-08  0:00 ` [PATCH v3 11/14] dt/bindings: Add bindings for PIC32 SDHCI host controller Joshua Henderson
2016-01-08  0:00 ` [PATCH v3 12/14] mmc: sdhci-pic32: Add PIC32 SDHCI host controller driver Joshua Henderson
2016-01-08  0:00 ` [PATCH v3 13/14] MIPS: dts: Add initial DTS for the PIC32MZDA Starter Kit Joshua Henderson
2016-01-08  0:00 ` [PATCH v3 14/14] MIPS: pic32mzda: Add initial PIC32MZDA Starter Kit defconfig Joshua Henderson

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=20160108133739.9a9c63c18fee346098354b21@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=joshua.henderson@microchip.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=ralf@linux-mips.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

all inboxes | Powered by JetHome®