public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wei Fang <wei.fang@nxp.com>
To: shenwei.wang@nxp.com, xiaoning.wang@nxp.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, eric@nelint.com,
	richardcochran@gmail.com
Cc: imx@lists.linux.dev, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH net 0/4] net: fec: fix some PTP related issues
Date: Tue, 25 Nov 2025 16:52:06 +0800	[thread overview]
Message-ID: <20251125085210.1094306-1-wei.fang@nxp.com> (raw)

There are some issues which were introduced by the commit 350749b909bf
("net: fec: Add support for periodic output signal of PPS"). See each
patch for more details.

Wei Fang (4):
  net: fec: cancel perout_timer when PEROUT is disabled
  net: fec: do not update PEROUT if it is enabled
  net: fec: do not allow enabling PPS and PEROUT simultaneously
  net: fec: do not register PPS event for PEROUT

 drivers/net/ethernet/freescale/fec.h     |  1 +
 drivers/net/ethernet/freescale/fec_ptp.c | 64 +++++++++++++++++++-----
 2 files changed, 53 insertions(+), 12 deletions(-)

-- 
2.34.1


             reply	other threads:[~2025-11-25  8:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25  8:52 Wei Fang [this message]
2025-11-25  8:52 ` [PATCH net 1/4] net: fec: cancel perout_timer when PEROUT is disabled Wei Fang
2025-11-25  8:52 ` [PATCH net 2/4] net: fec: do not update PEROUT if it is enabled Wei Fang
2025-11-25  8:52 ` [PATCH net 3/4] net: fec: do not allow enabling PPS and PEROUT simultaneously Wei Fang
2025-11-25  8:52 ` [PATCH net 4/4] net: fec: do not register PPS event for PEROUT Wei Fang
2025-11-27 11:00 ` [PATCH net 0/4] net: fec: fix some PTP related issues patchwork-bot+netdevbpf

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=20251125085210.1094306-1-wei.fang@nxp.com \
    --to=wei.fang@nxp.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric@nelint.com \
    --cc=imx@lists.linux.dev \
    --cc=kuba@kernel.org \
    --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=xiaoning.wang@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