From: Richard Cochran <richardcochran@gmail.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: devicetree@vger.kernel.org, Wingman Kwok <w-kwok2@ti.com>,
netdev@vger.kernel.org, Sekhar Nori <nsekhar@ti.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Murali Karicheri <m-karicheri2@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net-next 00/10] net: ethernet: ti: netcp: update and enable cpts support
Date: Sun, 2 Jun 2019 12:52:49 -0700 [thread overview]
Message-ID: <20190602195129.hjx5qyzqxyirdkx7@localhost> (raw)
In-Reply-To: <20190601104534.25790-1-grygorii.strashko@ti.com>
On Sat, Jun 01, 2019 at 01:45:24PM +0300, Grygorii Strashko wrote:
> The Keystone 2 66AK2HK/E/L 1G Ethernet Switch Subsystems contains The
> Common Platform Time Sync (CPTS) module which is in general compatible with
> CPTS module found on TI AM3/4/5 SoCs. So, the basic support for
> Keystone 2 CPTS is available by default, but not documented and has never been
> enabled inconfig files.
>
> The Keystone 2 CPTS module supports also some additional features like time
> sync reference (RFTCLK) clock selection through CPTS_RFTCLK_SEL register
> (offset: x08) in CPTS module, which can modelled as multiplexer clock
> (this was discussed some time ago [1]).
>
> This series adds missed binding documentation for Keystone 2 66AK2HK/E/L
> CPTS module and enables CPTS for TI Keystone 2 66AK2HK/E/L SoCs with possiblity
> to select CPTS reference clock.
For the series:
Acked-by: Richard Cochran <richardcochran@gmail.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-06-02 19:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 10:45 [PATCH net-next 00/10] net: ethernet: ti: netcp: update and enable cpts support Grygorii Strashko
2019-06-01 10:45 ` [PATCH net-next 01/10] dt-bindings: doc: net: keystone-netcp: document cpts Grygorii Strashko
2019-06-01 10:45 ` [PATCH net-next 02/10] net: ethernet: ti: cpts: use devm_get_clk_from_child Grygorii Strashko
2019-06-01 10:45 ` [PATCH net-next 03/10] net: ethernet: ti: netcp_ethss: add support for child cpts node Grygorii Strashko
2019-06-01 10:45 ` [PATCH net-next 04/10] net: ethernet: ti: cpts: add support for rftclk selection Grygorii Strashko
2019-06-03 22:13 ` David Miller
2019-06-01 10:45 ` [PATCH net-next 05/10] ARM: dts: keystone-clocks: add input fixed clocks Grygorii Strashko
2019-06-01 10:45 ` [PATCH net-next 06/10] ARM: dts: k2e-clocks: add input ext. fixed clocks tsipclka/b Grygorii Strashko
2019-06-01 10:45 ` [PATCH net-next 07/10] ARM: dts: k2e-netcp: add cpts refclk_mux node Grygorii Strashko
2019-06-01 10:45 ` [PATCH net-next 08/10] ARM: dts: k2hk-netcp: " Grygorii Strashko
2019-06-01 10:45 ` [PATCH net-next 09/10] ARM: dts: k2l-netcp: " Grygorii Strashko
2019-06-01 10:45 ` [PATCH net-next 10/10] ARM: configs: keystone: enable cpts Grygorii Strashko
2019-06-02 19:52 ` Richard Cochran [this message]
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=20190602195129.hjx5qyzqxyirdkx7@localhost \
--to=richardcochran@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=w-kwok2@ti.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