From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Santosh Shilimkar <ssantosh@kernel.org>
Cc: devicetree@vger.kernel.org,
Grygorii Strashko <grygorii.strashko@ti.com>,
Sekhar Nori <nsekhar@ti.com>,
linux-kernel@vger.kernel.org,
Murali Karicheri <m-karicheri2@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH next v2 0/6] ARM: keystone: update dt and enable cpts support
Date: Fri, 5 Jul 2019 18:12:41 +0300 [thread overview]
Message-ID: <20190705151247.30422-1-grygorii.strashko@ti.com> (raw)
Hi Santosh,
This series is set of platform changes required to enable NETCP CPTS reference
clock selection and final patch to enable CPTS for Keystone 66AK2E/L/HK SoCs.
Those patches were posted already [1] together with driver's changes, so this
is re-send of DT/platform specific changes only, as driver's changes have
been merged already.
Patches 1-5: CPTS DT nodes update for TI Keystone 2 66AK2HK/E/L SoCs.
Patch 6: enables CPTS for TI Keystone 2 66AK2HK/E/L SoCs.
[1] https://patchwork.kernel.org/cover/10980037/
Grygorii Strashko (6):
ARM: dts: keystone-clocks: add input fixed clocks
ARM: dts: k2e-clocks: add input ext. fixed clocks tsipclka/b
ARM: dts: k2e-netcp: add cpts refclk_mux node
ARM: dts: k2hk-netcp: add cpts refclk_mux node
ARM: dts: k2l-netcp: add cpts refclk_mux node
ARM: configs: keystone: enable cpts
arch/arm/boot/dts/keystone-clocks.dtsi | 27 ++++++++++++++++++++++
arch/arm/boot/dts/keystone-k2e-clocks.dtsi | 20 ++++++++++++++++
arch/arm/boot/dts/keystone-k2e-netcp.dtsi | 21 +++++++++++++++--
arch/arm/boot/dts/keystone-k2hk-netcp.dtsi | 20 ++++++++++++++--
arch/arm/boot/dts/keystone-k2l-netcp.dtsi | 20 ++++++++++++++--
arch/arm/configs/keystone_defconfig | 1 +
6 files changed, 103 insertions(+), 6 deletions(-)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-07-05 15:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 15:12 Grygorii Strashko [this message]
2019-07-05 15:12 ` [RESEND PATCH next v2 1/6] ARM: dts: keystone-clocks: add input fixed clocks Grygorii Strashko
2019-07-05 15:12 ` [RESEND PATCH next v2 2/6] ARM: dts: k2e-clocks: add input ext. fixed clocks tsipclka/b Grygorii Strashko
2019-07-05 15:12 ` [RESEND PATCH next v2 3/6] ARM: dts: k2e-netcp: add cpts refclk_mux node Grygorii Strashko
2019-07-05 15:12 ` [RESEND PATCH next v2 4/6] ARM: dts: k2hk-netcp: " Grygorii Strashko
2019-07-05 15:12 ` [RESEND PATCH next v2 5/6] ARM: dts: k2l-netcp: " Grygorii Strashko
2019-07-05 15:12 ` [RESEND PATCH next v2 6/6] ARM: configs: keystone: enable cpts Grygorii Strashko
2019-07-05 23:48 ` [RESEND PATCH next v2 0/6] ARM: keystone: update dt and enable cpts support santosh.shilimkar
2019-07-16 10:44 ` grygorii
2019-09-05 19:33 ` Grygorii Strashko
2019-09-06 4:52 ` santosh.shilimkar
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=20190705151247.30422-1-grygorii.strashko@ti.com \
--to=grygorii.strashko@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=nsekhar@ti.com \
--cc=ssantosh@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;
as well as URLs for NNTP newsgroup(s).