devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maciej Purski <m.purski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: Krzysztof Kozlowski <krzk-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Kukjin Kim <kgene-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
	b.zolnierkie-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
	Maciej Purski <m.purski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Subject: [PATCH v2 0/3] Add soc nodes to exynos4 series DTS
Date: Tue, 06 Feb 2018 12:29:39 +0100	[thread overview]
Message-ID: <1517916582-13814-1-git-send-email-m.purski@samsung.com> (raw)
In-Reply-To: CGME20180206113006eucas1p148766268255c129223e32f221afc1b94@eucas1p1.samsung.com

Hi all,

this patchset adds soc node to exynos4, exynos4210 and exynos4412
DTS. The main goal for these changes is unification of all exynos
DTS. Soc nodes are already present in for example exynos5 series.

Best regards,

Maciej Purski

---
Changes in v2:
- rebased onto "ARM: dts: exynos: Use pmu label in exynos4412"
  in order to fix pmu warning
- move "cpu0_opp_table" outside the "soc" node

Maciej Purski (3):
  ARM: dts: exynos: Add soc node to exynos4
  ARM: dts: exynos: Add soc node to exynos4210
  ARM: dts: exynos: Add soc node to exynos4412

 arch/arm/boot/dts/exynos4.dtsi    | 1727 +++++++++++++++++++------------------
 arch/arm/boot/dts/exynos4210.dtsi |  513 +++++------
 arch/arm/boot/dts/exynos4412.dtsi |  772 +++++++++--------
 3 files changed, 1519 insertions(+), 1493 deletions(-)

-- 
2.7.4

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

       reply	other threads:[~2018-02-06 11:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180206113006eucas1p148766268255c129223e32f221afc1b94@eucas1p1.samsung.com>
2018-02-06 11:29 ` Maciej Purski [this message]
     [not found]   ` <CGME20180206113006eucas1p24f4b7fb082527571146f6be2de626dcb@eucas1p2.samsung.com>
     [not found]     ` <1517916582-13814-1-git-send-email-m.purski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2018-02-06 11:29       ` [PATCH v2 1/3] ARM: dts: exynos: Add soc node to exynos4 Maciej Purski
2018-02-07  9:37       ` [PATCH v2 0/3] Add soc nodes to exynos4 series DTS Krzysztof Kozlowski
     [not found]   ` <CGME20180206113007eucas1p258ccf74144c41dc2d4000f59b59eefc9@eucas1p2.samsung.com>
2018-02-06 11:29     ` [PATCH v2 2/3] ARM: dts: exynos: Add soc node to exynos4210 Maciej Purski
     [not found]   ` <CGME20180206113007eucas1p261abf16de0e52e2722441d4abb559c13@eucas1p2.samsung.com>
2018-02-06 11:29     ` [PATCH v2 3/3] ARM: dts: exynos: Add soc node to exynos4412 Maciej Purski
2018-02-13 18:05   ` [PATCH v2 0/3] Add soc nodes to exynos4 series DTS Krzysztof Kozlowski

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=1517916582-13814-1-git-send-email-m.purski@samsung.com \
    --to=m.purski-sze3o3uu22jbdgjk7y7tuq@public.gmane.org \
    --cc=b.zolnierkie-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=kgene-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=krzk-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.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).