netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sagi Maimon <maimon.sagi@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>, netdev@vger.kernel.org
Cc: Richard Cochran <richardcochran@gmail.com>,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	Sagi Maimon <maimon.sagi@gmail.com>
Subject: Re: [PATCH net-next v13 1/2] ptp: ocp: add TAP CPLD access for ADVA TimeCard X1
Date: Mon, 14 Sep 2026 10:23:28 +0300	[thread overview]
Message-ID: <20260914072328.12824-1-maimon.sagi@gmail.com> (raw)
In-Reply-To: <20260911165243.53764253@kernel.org>

On Fri, 11 Sep 2026 16:52:43 -0700 Jakub Kicinski wrote:
> > +               done=<0|1> busy=<0|1> failed=<0|1>  
> 
> I think the sysfs rules are "one value per file"
> We can stretch it a bit and say that this file contains flags
> 
> So format like done or busy or failed or multiple eg "busy failed"
> But the X=[0|1] is too much

Changed for v14.  The file now contains the names of the flags that are
set, space separated, and an empty line when none is:

  # cat cpld_status
  done

  # cat cpld_status     # during programming
  busy

The ABI entry lists the three names and what each means.

> Also I think the AI is right this one commit does too many things.

Split for v14.  The two pre-existing fixes that were buried in it are
separate patches now, with Fixes: tags:

  1/4 ptp: ocp: unregister devlink before detach on probe error
  2/4 ptp: ocp: fix dpll cleanup on probe error
  3/4 ptp: ocp: add TAP CPLD access for ADVA TimeCard X1
  4/4 ptp: ocp: add TAP CPLD flashing via devlink

2/4 is a second bug in the same error path, found while looking at the
first: out_dpll never called dpll_device_unregister(), so a failing
dpll_pin_get() or dpll_pin_register() left the dpll device registered
with a priv pointer into storage devlink_free() releases a few lines
later, and a failing dpll_device_register() leaked the reference
dpll_device_get() had taken.

1 and 2 fix 09eeb3aecc6c, which is in released kernels, but they only
trigger when probe fails, so I did not mark them for stable.  They are in
this series because 3/4 adds a mutex that ptp_ocp_detach() destroys, so
devlink has to be unregistered first.

If you would rather see 3/4 split further - the bus arbitration alone,
then the two read-only interfaces on top - I am happy to do that.

v14 posted at: https://lore.kernel.org/netdev/20260914071531.11640-1-maimon.sagi@gmail.com/T/#u

Thanks for the review,
Sagi

  reply	other threads:[~2026-09-14  7:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 12:23 [PATCH net-next v13 0/2] ptp: ocp: add TAP CPLD support for ADVA TimeCard X1 Sagi Maimon
2026-09-08 12:23 ` [PATCH net-next v13 1/2] ptp: ocp: add TAP CPLD access " Sagi Maimon
2026-09-10 15:23   ` netdev-bot+sashiko
2026-09-11 23:52   ` Jakub Kicinski
2026-09-14  7:23     ` Sagi Maimon [this message]
2026-09-08 12:23 ` [PATCH net-next v13 2/2] ptp: ocp: add TAP CPLD firmware upload " Sagi Maimon
2026-09-10 15:23   ` netdev-bot+sashiko
2026-09-11 23:51   ` Jakub Kicinski
2026-09-14  7:24     ` Sagi Maimon

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=20260914072328.12824-1-maimon.sagi@gmail.com \
    --to=maimon.sagi@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=vadim.fedorenko@linux.dev \
    /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).