All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Kubalewski, Arkadiusz" <arkadiusz.kubalewski@intel.com>
Cc: "geert+renesas@glider.be" <geert+renesas@glider.be>,
	"mst@redhat.com" <mst@redhat.com>,
	"razor@blackwall.org" <razor@blackwall.org>,
	"phil@nwl.cc" <phil@nwl.cc>,
	"javierm@redhat.com" <javierm@redhat.com>,
	"edumazet@google.com" <edumazet@google.com>,
	"benjamin.tissoires@redhat.com" <benjamin.tissoires@redhat.com>,
	"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"lucien.xin@gmail.com" <lucien.xin@gmail.com>,
	"leon@kernel.org" <leon@kernel.org>,
	"corbet@lwn.net" <corbet@lwn.net>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"masahiroy@kernel.org" <masahiroy@kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	"vadfed@meta.com" <vadfed@meta.com>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"airlied@redhat.com" <airlied@redhat.com>,
	"vadfed@fb.com" <vadfed@fb.com>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"ricardo.canuelo@collabora.com" <ricardo.canuelo@collabora.com>,
	Jiri Pirko <jiri@resnulli.us>, "arnd@arndb.de" <arnd@arndb.de>,
	"idosch@nvidia.com" <idosch@nvidia.com>,
	"richardcochran@gmail.com" <richardcochran@gmail.com>,
	"claudiajkang@gmail.com" <claudiajkang@gmail.com>,
	"kuniyu@amazon.com" <kuniyu@amazon.com>,
	"jacek.lawrynowicz@linux.intel.com"
	<jacek.lawrynowicz@linux.intel.com>,
	"liuhangbin@gmail.com" <liuhangbin@gmail.com>,
	"nicolas.dichtel@6wind.com" <nicolas.dichtel@6wind.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"axboe@kernel.dk" <axboe@kernel.dk>,
	"sj@kernel.org" <sj@kernel.org>,
	"vadim.fedorenko@linux.dev" <vadim.fedorenko@linux.dev>,
	"linux@zary.sk" <linux@zary.sk>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"ogabbay@kernel.org" <ogabbay@kernel.org>,
	"nipun.gupta@amd.com" <nipun.gupta@amd.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"andy.ren@getcruise.com" <andy.ren@getcruise.com>,
	"tzimmermann@suse.de" <tzimmermann@suse.de>,
	"jonathan.lemon@gmail.com" <jonathan.lemon@gmail.com>,
	"M, Saeed" <saeedm@nvidia.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"Olech, Milena" <milena.olech@intel.com>,
	"hkallweit1@gmail.com" <hkallweit1@gmail.com>
Subject: Re: [Intel-wired-lan] [RFC PATCH v9 00/10] Create common DPLL configuration API
Date: Wed, 12 Jul 2023 09:54:22 -0700	[thread overview]
Message-ID: <20230712095422.00acaeaa@kernel.org> (raw)
In-Reply-To: <DM6PR11MB465701C009D1DC2972F900F29B36A@DM6PR11MB4657.namprd11.prod.outlook.com>

On Wed, 12 Jul 2023 09:19:53 +0000 Kubalewski, Arkadiusz wrote:
> >> Don't think it is way to go, and I don't think there is anything good
> >> with preventing device drivers from labeling their pins the way they
> >> want.  
> >
> >We had a long argument about how label should have a clearly defined
> >meaning. We're not going to rehash it on every revision. What did I miss :|  
> 
> Well, as I understand we are discussing if dpll subsystem shall prevent
> labeling the SyncE type pins. I have labeled them in ice explicitly with
> the name of a pci device they belong to.
> 
> You haven't miss much, mostly the problem is described in this thread.

Please read this thread:

https://lore.kernel.org/all/20230503191643.12a6e559@kernel.org/
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: "Kubalewski, Arkadiusz" <arkadiusz.kubalewski@intel.com>
Cc: Jiri Pirko <jiri@resnulli.us>,
	"vadfed@meta.com" <vadfed@meta.com>,
	"jonathan.lemon@gmail.com" <jonathan.lemon@gmail.com>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"corbet@lwn.net" <corbet@lwn.net>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"vadfed@fb.com" <vadfed@fb.com>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
	"M, Saeed" <saeedm@nvidia.com>,
	"leon@kernel.org" <leon@kernel.org>,
	"richardcochran@gmail.com" <richardcochran@gmail.com>,
	"sj@kernel.org" <sj@kernel.org>,
	"javierm@redhat.com" <javierm@redhat.com>,
	"ricardo.canuelo@collabora.com" <ricardo.canuelo@collabora.com>,
	"mst@redhat.com" <mst@redhat.com>,
	"tzimmermann@suse.de" <tzimmermann@suse.de>,
	"Michalik, Michal" <michal.michalik@intel.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"jacek.lawrynowicz@linux.intel.com" 
	<jacek.lawrynowicz@linux.intel.com>,
	"airlied@redhat.com" <airlied@redhat.com>,
	"ogabbay@kernel.org" <ogabbay@kernel.org>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"nipun.gupta@amd.com" <nipun.gupta@amd.com>,
	"axboe@kernel.dk" <axboe@kernel.dk>,
	"linux@zary.sk" <linux@zary.sk>,
	"masahiroy@kernel.org" <masahiroy@kernel.org>,
	"benjamin.tissoires@redhat.com" <benjamin.tissoires@redhat.com>,
	"geert+renesas@glider.be" <geert+renesas@glider.be>,
	"Olech, Milena" <milena.olech@intel.com>,
	"kuniyu@amazon.com" <kuniyu@amazon.com>,
	"liuhangbin@gmail.com" <liuhangbin@gmail.com>,
	"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
	"andy.ren@getcruise.com" <andy.ren@getcruise.com>,
	"razor@blackwall.org" <razor@blackwall.org>,
	"idosch@nvidia.com" <idosch@nvidia.com>,
	"lucien.xin@gmail.com" <lucien.xin@gmail.com>,
	"nicolas.dichtel@6wind.com" <nicolas.dichtel@6wind.com>,
	"phil@nwl.cc" <phil@nwl.cc>,
	"claudiajkang@gmail.com" <claudiajkang@gmail.com>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>, poros <poros@redhat.com>,
	mschmidt <mschmidt@redhat.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"vadim.fedorenko@linux.dev" <vadim.fedorenko@linux.dev>
Subject: Re: [RFC PATCH v9 00/10] Create common DPLL configuration API
Date: Wed, 12 Jul 2023 09:54:22 -0700	[thread overview]
Message-ID: <20230712095422.00acaeaa@kernel.org> (raw)
In-Reply-To: <DM6PR11MB465701C009D1DC2972F900F29B36A@DM6PR11MB4657.namprd11.prod.outlook.com>

On Wed, 12 Jul 2023 09:19:53 +0000 Kubalewski, Arkadiusz wrote:
> >> Don't think it is way to go, and I don't think there is anything good
> >> with preventing device drivers from labeling their pins the way they
> >> want.  
> >
> >We had a long argument about how label should have a clearly defined
> >meaning. We're not going to rehash it on every revision. What did I miss :|  
> 
> Well, as I understand we are discussing if dpll subsystem shall prevent
> labeling the SyncE type pins. I have labeled them in ice explicitly with
> the name of a pci device they belong to.
> 
> You haven't miss much, mostly the problem is described in this thread.

Please read this thread:

https://lore.kernel.org/all/20230503191643.12a6e559@kernel.org/

  reply	other threads:[~2023-07-12 16:54 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23 12:38 [Intel-wired-lan] [RFC PATCH v9 00/10] Create common DPLL configuration API Arkadiusz Kubalewski
2023-06-23 12:38 ` Arkadiusz Kubalewski
2023-06-23 12:38 ` [Intel-wired-lan] [RFC PATCH v9 01/10] dpll: documentation on DPLL subsystem interface Arkadiusz Kubalewski
2023-06-23 12:38   ` Arkadiusz Kubalewski
2023-06-28 21:11   ` [Intel-wired-lan] " Jakub Kicinski
2023-06-28 21:11     ` Jakub Kicinski
2023-07-10  9:45     ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-07-10  9:45       ` Kubalewski, Arkadiusz
2023-06-23 12:38 ` [Intel-wired-lan] [RFC PATCH v9 02/10] dpll: spec: Add Netlink spec in YAML Arkadiusz Kubalewski
2023-06-23 12:38   ` Arkadiusz Kubalewski
2023-06-23 12:38 ` [Intel-wired-lan] [RFC PATCH v9 03/10] dpll: core: Add DPLL framework base functions Arkadiusz Kubalewski
2023-06-23 12:38   ` Arkadiusz Kubalewski
2023-06-29  8:13   ` [Intel-wired-lan] " Jiri Pirko
2023-06-29  8:13     ` Jiri Pirko
2023-07-10  9:50     ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-07-10  9:50       ` Kubalewski, Arkadiusz
2023-06-23 12:38 ` [Intel-wired-lan] [RFC PATCH v9 04/10] dpll: netlink: " Arkadiusz Kubalewski
2023-06-23 12:38   ` Arkadiusz Kubalewski
2023-06-23 12:38 ` [Intel-wired-lan] [RFC PATCH v9 05/10] dpll: api header: " Arkadiusz Kubalewski
2023-06-23 12:38   ` Arkadiusz Kubalewski
2023-06-23 12:38 ` [Intel-wired-lan] [RFC PATCH v9 06/10] netdev: expose DPLL pin handle for netdevice Arkadiusz Kubalewski
2023-06-23 12:38   ` Arkadiusz Kubalewski
2023-06-23 12:38 ` [Intel-wired-lan] [RFC PATCH v9 07/10] ice: add admin commands to access cgu configuration Arkadiusz Kubalewski
2023-06-23 12:38   ` Arkadiusz Kubalewski
2023-07-27 21:16   ` [Intel-wired-lan] " Linus Walleij
2023-07-27 21:16     ` Linus Walleij
2023-07-28  9:55     ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-07-28  9:55       ` Kubalewski, Arkadiusz
2023-06-23 12:38 ` [Intel-wired-lan] [RFC PATCH v9 08/10] ice: implement dpll interface to control cgu Arkadiusz Kubalewski
2023-06-23 12:38   ` Arkadiusz Kubalewski
2023-06-23 12:38 ` [Intel-wired-lan] [RFC PATCH v9 09/10] ptp_ocp: implement DPLL ops Arkadiusz Kubalewski
2023-06-23 12:38   ` Arkadiusz Kubalewski
2023-06-23 12:38 ` [Intel-wired-lan] [RFC PATCH v9 10/10] mlx5: Implement SyncE support using DPLL infrastructure Arkadiusz Kubalewski
2023-06-23 12:38   ` Arkadiusz Kubalewski
2023-06-23 15:19 ` [Intel-wired-lan] [RFC PATCH v9 00/10] Create common DPLL configuration API Jiri Pirko
2023-06-23 15:19   ` Jiri Pirko
2023-06-23 15:53   ` [Intel-wired-lan] " Jakub Kicinski
2023-06-23 15:53     ` Jakub Kicinski
2023-06-24  9:23     ` [Intel-wired-lan] " Jiri Pirko
2023-06-24  9:23       ` Jiri Pirko
2023-06-24 21:43       ` [Intel-wired-lan] " Jakub Kicinski
2023-06-24 21:43         ` Jakub Kicinski
2023-06-27 10:18 ` [Intel-wired-lan] " Jiri Pirko
2023-06-27 10:18   ` Jiri Pirko
2023-06-28  9:15   ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-06-28  9:15     ` Kubalewski, Arkadiusz
2023-06-28  9:27     ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-06-28  9:27       ` Kubalewski, Arkadiusz
2023-06-28 11:11       ` [Intel-wired-lan] " Vadim Fedorenko
2023-06-28 11:11         ` Vadim Fedorenko
2023-06-28 13:09         ` [Intel-wired-lan] " Jiri Pirko
2023-06-28 13:09           ` Jiri Pirko
2023-06-28 13:22           ` [Intel-wired-lan] " Vadim Fedorenko
2023-06-28 13:22             ` Vadim Fedorenko
2023-06-28 14:02             ` [Intel-wired-lan] " Jiri Pirko
2023-06-28 14:02               ` Jiri Pirko
2023-06-28 11:15     ` [Intel-wired-lan] " Jiri Pirko
2023-06-28 11:15       ` Jiri Pirko
2023-07-10 10:07       ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-07-10 10:07         ` Kubalewski, Arkadiusz
2023-07-10 12:09         ` [Intel-wired-lan] " Jiri Pirko
2023-07-10 12:09           ` Jiri Pirko
2023-07-11 10:34           ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-07-11 10:34             ` Kubalewski, Arkadiusz
2023-07-11 11:52             ` [Intel-wired-lan] " Jiri Pirko
2023-07-11 11:52               ` Jiri Pirko
2023-07-11 17:17               ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-07-11 17:17                 ` Kubalewski, Arkadiusz
2023-07-11 20:14                 ` [Intel-wired-lan] " Jakub Kicinski
2023-07-11 20:14                   ` Jakub Kicinski
2023-07-12  9:19                   ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-07-12  9:19                     ` Kubalewski, Arkadiusz
2023-07-12 16:54                     ` Jakub Kicinski [this message]
2023-07-12 16:54                       ` Jakub Kicinski
  -- strict thread matches above, loose matches on Subject: below --
2023-07-13  5:33 [Intel-wired-lan] " Vitaly Grinberg

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=20230712095422.00acaeaa@kernel.org \
    --to=kuba@kernel.org \
    --cc=airlied@redhat.com \
    --cc=andy.ren@getcruise.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=arnd@arndb.de \
    --cc=axboe@kernel.dk \
    --cc=benjamin.tissoires@redhat.com \
    --cc=claudiajkang@gmail.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=hkallweit1@gmail.com \
    --cc=idosch@nvidia.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jacek.lawrynowicz@linux.intel.com \
    --cc=javierm@redhat.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=jiri@resnulli.us \
    --cc=jonathan.lemon@gmail.com \
    --cc=kuniyu@amazon.com \
    --cc=leon@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux@zary.sk \
    --cc=liuhangbin@gmail.com \
    --cc=lucien.xin@gmail.com \
    --cc=masahiroy@kernel.org \
    --cc=milena.olech@intel.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=nipun.gupta@amd.com \
    --cc=ogabbay@kernel.org \
    --cc=pabeni@redhat.com \
    --cc=phil@nwl.cc \
    --cc=razor@blackwall.org \
    --cc=ricardo.canuelo@collabora.com \
    --cc=richardcochran@gmail.com \
    --cc=saeedm@nvidia.com \
    --cc=sj@kernel.org \
    --cc=tzimmermann@suse.de \
    --cc=vadfed@fb.com \
    --cc=vadfed@meta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.