devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pankaj Dubey <pankaj.dubey@samsung.com>
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org
Cc: kgene.kim@samsung.com, robh+dt@kernel.org,
	ijc+devicetree@hellion.org.uk, pawel.moll@arm.com,
	thomas.ab@samsung.com
Subject: Re: [PATCH] ARM: samsung: add exynos-chipid binding information
Date: Mon, 05 Jan 2015 15:15:01 +0530	[thread overview]
Message-ID: <54AA5D1D.9000409@samsung.com> (raw)
In-Reply-To: <1417592664-10672-1-git-send-email-pankaj.dubey@samsung.com>

Gentle Ping.

On Wednesday 03 December 2014 01:14 PM, Pankaj Dubey wrote:
> Exynos SoC's DT files are using Chipid device nodes, but it's binding
> information is missing. This patch adds exynos-chipid binding information.
>
> Signed-off-by: Pankaj Dubey <pankaj.dubey@samsung.com>
> ---
>   .../bindings/arm/samsung/exynos-chipid.txt         |   12 ++++++++++++
>   1 file changed, 12 insertions(+)
>   create mode 100644 Documentation/devicetree/bindings/arm/samsung/exynos-chipid.txt
>
> diff --git a/Documentation/devicetree/bindings/arm/samsung/exynos-chipid.txt b/Documentation/devicetree/bindings/arm/samsung/exynos-chipid.txt
> new file mode 100644
> index 0000000..85c5dfd
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/samsung/exynos-chipid.txt
> @@ -0,0 +1,12 @@
> +SAMSUNG Exynos SoCs Chipid driver.
> +
> +Required properties:
> +- compatible : Should at least contain "samsung,exynos4210-chipid".
> +
> +- reg: offset and length of the register set
> +
> +Example:
> +	chipid@10000000 {
> +		compatible = "samsung,exynos4210-chipid";
> +		reg = <0x10000000 0x100>;
> +	};
>

Thanks,
Pankaj Dubey

  reply	other threads:[~2015-01-05  9:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03  7:44 [PATCH] ARM: samsung: add exynos-chipid binding information Pankaj Dubey
2015-01-05  9:45 ` Pankaj Dubey [this message]
2015-01-12  9:14   ` Kukjin Kim

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=54AA5D1D.9000409@samsung.com \
    --to=pankaj.dubey@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=thomas.ab@samsung.com \
    /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).