linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Zhang, Tianfei" <tianfei.zhang@intel.com>
Cc: Nicolas Pitre <nico@fluxnic.net>,
	Richard Cochran <richardcochran@gmail.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-fpga@vger.kernel.org" <linux-fpga@vger.kernel.org>,
	"ilpo.jarvinen@linux.intel.com" <ilpo.jarvinen@linux.intel.com>,
	"Weight, Russell H" <russell.h.weight@intel.com>,
	"matthew.gerlach@linux.intel.com"
	<matthew.gerlach@linux.intel.com>,
	"pierre-louis.bossart@linux.intel.com" 
	<pierre-louis.bossart@linux.intel.com>,
	"Gomes, Vinicius" <vinicius.gomes@intel.com>,
	"Khadatare,
	RaghavendraX Anand"  <raghavendrax.anand.khadatare@intel.com>
Subject: Re: [PATCH v1] ptp: add ToD device driver for Intel FPGA cards
Date: Tue, 21 Mar 2023 16:40:01 +0200	[thread overview]
Message-ID: <ZBnBwa/MLdH0ep3g@smile.fi.intel.com> (raw)
In-Reply-To: <BN9PR11MB548394F8DCE5AEC4DA553EB6E3819@BN9PR11MB5483.namprd11.prod.outlook.com>

On Tue, Mar 21, 2023 at 02:28:15PM +0000, Zhang, Tianfei wrote:
> > From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Sent: Tuesday, March 21, 2023 9:03 PM
> > To: Nicolas Pitre <nico@fluxnic.net>
> > On Mon, Mar 20, 2023 at 04:53:07PM -0400, Nicolas Pitre wrote:
> > > On Mon, 20 Mar 2023, Richard Cochran wrote:
> > > > On Mon, Mar 20, 2023 at 09:43:30AM -0400, Nicolas Pitre wrote:
> > > >
> > > > > Alternatively the above commit can be reverted if no one else
> > > > > cares. I personally gave up on the idea of a slimmed down Linux
> > > > > kernel a while ago.
> > > >
> > > > Does this mean I can restore the posix clocks back into the core
> > > > unconditionally?
> > >
> > > This only means _I_ no longer care. I'm not speaking for others (e.g.
> > > OpenWRT or the like) who might still rely on splitting it out.
> > > Maybe Andy wants to "fix" it?
> > 
> > I would be a good choice, if I have an access to the hardware at hand to test.
> > That said, I think Richard himself can try to finish that feature (optional PTP) and on
> > my side I can help with reviewing the code (just Cc me when needed).
> 
> Handle NULL as a valid parameter (object) to their respective APIs looks a
> good idea, but this will be a big change and need fully test for all devices,

Since it's core change, so a few devices that cover 100% APIs that should
handle optional PTP. I don't think it requires enormous work.

> we can add it on the TODO list.

It would be a good idea.

> So for this patch, are you agree we continue use the existing
> ptp_clock_register() API, for example, change my driver like below:

The problem is that it will increase the technical debt.
What about sending with NULL handled variant together with an RFC/RFT
that finishes the optional PTP support?

>       dt->ptp_clock = ptp_clock_register(&dt->ptp_clock_ops, dev);

	ret = PTR_ERR_OR_ZERO(...);
	if (ret)
		return ...

?

>       if (IS_ERR_OR_NULL(dt->ptp_clock))
>               return dev_err_probe(dt->dev, IS_ERR_OR_NULL(dt->ptp_clock),
>                                    "Unable to register PTP clock\n");


-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-03-21 14:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13  3:02 [PATCH v1] ptp: add ToD device driver for Intel FPGA cards Tianfei Zhang
2023-03-13 17:50 ` Marco Pagani
2023-03-15  2:59   ` Zhang, Tianfei
2023-03-16 15:03     ` Zhang, Tianfei
2023-03-13 18:49 ` Richard Cochran
2023-03-14  7:16   ` Zhang, Tianfei
2023-03-14 20:01     ` Richard Cochran
2023-03-14 10:47   ` Andy Shevchenko
2023-03-14 19:46     ` Richard Cochran
2023-03-15 13:59       ` Andy Shevchenko
2023-03-15 14:37         ` Nicolas Pitre
2023-03-20 13:20           ` Andy Shevchenko
2023-03-20 13:43             ` Nicolas Pitre
2023-03-20 19:41               ` Richard Cochran
2023-03-20 20:53                 ` Nicolas Pitre
2023-03-21 13:02                   ` Andy Shevchenko
2023-03-21 14:28                     ` Zhang, Tianfei
2023-03-21 14:40                       ` Andy Shevchenko [this message]
2023-03-21 14:52                         ` Zhang, Tianfei
2023-03-22  4:17                           ` Richard Cochran

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=ZBnBwa/MLdH0ep3g@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=matthew.gerlach@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=raghavendrax.anand.khadatare@intel.com \
    --cc=richardcochran@gmail.com \
    --cc=russell.h.weight@intel.com \
    --cc=tianfei.zhang@intel.com \
    --cc=vinicius.gomes@intel.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;
as well as URLs for NNTP newsgroup(s).