From: Jakub Kicinski <kuba@kernel.org>
To: Wei Fang <wei.fang@nxp.com>
Cc: "Buday Csaba" <buday.csaba@prolan.hu>,
"Frank Li" <frank.li@nxp.com>,
"Shenwei Wang" <shenwei.wang@nxp.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Richard Cochran" <richardcochran@gmail.com>,
"Bence Csókás" <bence98@sch.bme.hu>,
"Francesco Dolcini" <francesco.dolcini@toradex.com>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v2 1/1] net: fec: fix the PTP periodic output sysfs interface
Date: Mon, 23 Mar 2026 17:28:42 -0700 [thread overview]
Message-ID: <20260323172842.7a62979d@kernel.org> (raw)
In-Reply-To: <PAXPR04MB8510889775D757361CEAFA39884BA@PAXPR04MB8510.eurprd04.prod.outlook.com>
On Mon, 23 Mar 2026 12:54:46 +0000 Wei Fang wrote:
> > When the PPS channel configuration was implemented, the number of
> > supported periodic outputs (`n_per_out`) was left at 1.
> >
> > This prohibits using channels 1..3 from the sysfs interface, since
> > period_store() rejects channel numbers greater than `n_per_out`.
> >
> > Fix by increasing `n_per_out` to the number of channels supported
> > by the hardware.
> >
> > Fixes: 566c2d83887f ("net: fec: make PPS channel configurable")
> > Signed-off-by: Buday Csaba <buday.csaba@prolan.hu>
> > ---
> > drivers/net/ethernet/freescale/fec_ptp.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/ethernet/freescale/fec_ptp.c
> > b/drivers/net/ethernet/freescale/fec_ptp.c
> > index 4b7bad9a485d..1a7aa280e7f6 100644
> > --- a/drivers/net/ethernet/freescale/fec_ptp.c
> > +++ b/drivers/net/ethernet/freescale/fec_ptp.c
> > @@ -756,7 +756,7 @@ void fec_ptp_init(struct platform_device *pdev, int
> > irq_idx)
> > fep->ptp_caps.max_adj = 250000000;
> > fep->ptp_caps.n_alarm = 0;
> > fep->ptp_caps.n_ext_ts = 0;
> > - fep->ptp_caps.n_per_out = 1;
> > + fep->ptp_caps.n_per_out = 4;
> > fep->ptp_caps.n_pins = 0;
> > fep->ptp_caps.pps = 1;
> > fep->ptp_caps.adjfine = fec_ptp_adjfine;
> >
> Reviewed-by: Wei Fang <wei.fang@nxp.com>
I don't understand why you think that we should be exposing 4 channels
to the user when they can only use one. And have the user guess which
one should be programmed. Please explain (and Buday will have to update
the commit message), to me v1 looked like a much better fix.
--
pw-bot: cr
next prev parent reply other threads:[~2026-03-24 0:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 15:59 [PATCH net v2 1/1] net: fec: fix the PTP periodic output sysfs interface Buday Csaba
2026-03-23 12:54 ` Wei Fang
2026-03-24 0:28 ` Jakub Kicinski [this message]
2026-03-24 2:36 ` Wei Fang
2026-03-24 3:26 ` Jakub Kicinski
2026-03-24 6:15 ` Wei Fang
2026-03-24 9:07 ` Buday Csaba
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=20260323172842.7a62979d@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bence98@sch.bme.hu \
--cc=buday.csaba@prolan.hu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=francesco.dolcini@toradex.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=shenwei.wang@nxp.com \
--cc=wei.fang@nxp.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