From: Francesco Dolcini <francesco@dolcini.it>
To: Frank Li <Frank.li@nxp.com>, rafael.beims@toradex.com
Cc: Francesco Dolcini <francesco@dolcini.it>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 4/4] arm64: dts: imx8-ss-conn: add PPS channel to the FEC nodes
Date: Wed, 7 Aug 2024 19:51:48 +0200 [thread overview]
Message-ID: <20240807175148.GA299582@francesco-nb> (raw)
In-Reply-To: <ZrOUGLJPYC/K4MlP@lizhi-Precision-Tower-5810>
Hello Frank,
+Rafael
On Wed, Aug 07, 2024 at 11:34:48AM -0400, Frank Li wrote:
> On Wed, Aug 07, 2024 at 04:43:49PM +0200, Francesco Dolcini wrote:
> > From: Francesco Dolcini <francesco.dolcini@toradex.com>
> >
> > On i.MX8 the FEC PPS channel is routed to the instance 1, not to the
> > default 0.
>
> According to my understand, it should be board level configuration. FEC
> support output pps to any one. choose which one by board design.
This seems different from the information we got from NXP some time ago,
unfortunately this was happening over some private email exchange and
not documented anywhere public. But the message was about SoC internal
routing, not something at the board level, at least for i.MX8 SoCs that
is what this patch is changing.
For example to use PPS on i.MX8QXP we need to have this
IMX8QM_ENET0_REFCLK_125M_25M_CONN_ENET0_PPS 0x06000020
pinctrl configuration _and_ use PPS channel 1. Same is for i.MX8QP.
Maybe Rafael can provide you some more details and the name of the
person that provided this information.
And maybe you can also try to double check this internally within NXP.
Depending on what we find out we can decide if this patch needs to be
dropped or not.
Francesco
next prev parent reply other threads:[~2024-08-07 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 14:43 [PATCH v1 0/4] net: fec: add PPS channel configuration Francesco Dolcini
2024-08-07 14:43 ` [PATCH v1 1/4] dt-bindings: net: fec: add pps channel property Francesco Dolcini
2024-08-07 14:43 ` [PATCH v1 4/4] arm64: dts: imx8-ss-conn: add PPS channel to the FEC nodes Francesco Dolcini
2024-08-07 15:34 ` Frank Li
2024-08-07 17:51 ` Francesco Dolcini [this message]
2024-08-07 19:48 ` Rafael Beims
2024-08-07 20:25 ` Frank Li
2024-08-08 6:30 ` Francesco Dolcini
2024-08-08 21:57 ` [PATCH v1 0/4] net: fec: add PPS channel configuration Francesco Dolcini
2024-08-09 2:58 ` Jakub Kicinski
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=20240807175148.GA299582@francesco-nb \
--to=francesco@dolcini.it \
--cc=Frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.beims@toradex.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).