All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Kubalewski, Arkadiusz" <arkadiusz.kubalewski@intel.com>
Cc: Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	Bart Van Assche <bvanassche@acm.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Jiri Pirko <jiri@nvidia.com>,
	Jonathan Lemon <jonathan.lemon@gmail.com>,
	Jiri Pirko <jiri@resnulli.us>, Paolo Abeni <pabeni@redhat.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"Olech, Milena" <milena.olech@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next v4 2/9] dpll: spec: Add Netlink spec in YAML
Date: Tue, 22 Aug 2023 09:54:56 -0700	[thread overview]
Message-ID: <20230822095456.0a08b008@kernel.org> (raw)
In-Reply-To: <DM6PR11MB4657E60D5A092E9FC05BC9EF9B1EA@DM6PR11MB4657.namprd11.prod.outlook.com>

On Mon, 21 Aug 2023 10:15:41 +0000 Kubalewski, Arkadiusz wrote:
> I prepared some POC's and it seems most convenient way to do the
> split was to add new argument as proposed on the previous mail.
> After all the spec generated diff for uAPI header like this:
> 
> --- a/include/uapi/linux/dpll.h
> +++ b/include/uapi/linux/dpll.h
> @@ -148,7 +148,17 @@ enum dpll_a {
>         DPLL_A_LOCK_STATUS,
>         DPLL_A_TEMP,
>         DPLL_A_TYPE,
> -       DPLL_A_PIN_ID,
> +
> +       __DPLL_A_MAX,
> +       DPLL_A_MAX = (__DPLL_A_MAX - 1)
> +};
> +
> +enum dpll_a_pin {
> +       DPLL_A_PIN_ID = 1,
> +       DPLL_A_PIN_PARENT_ID,
> +       DPLL_A_PIN_MODULE_NAME,
> +       DPLL_A_PIN_PAD,
> +       DPLL_A_PIN_CLOCK_ID,
>         DPLL_A_PIN_BOARD_LABEL,
>         DPLL_A_PIN_PANEL_LABEL,
>         DPLL_A_PIN_PACKAGE_LABEL,
> @@ -164,8 +174,8 @@ enum dpll_a {
>         DPLL_A_PIN_PARENT_DEVICE,
>         DPLL_A_PIN_PARENT_PIN,
> 
> -       __DPLL_A_MAX,
> -       DPLL_A_MAX = (__DPLL_A_MAX - 1)
> +       __DPLL_A_PIN_MAX,
> +       DPLL_A_PIN_MAX = (__DPLL_A_PIN_MAX - 1)
>  };
> 
> So we have additional attribute for targeting either a pin or device
> DPLL_A_PIN_PARENT_ID (u32) - which would be enclosed in the nests as
> previously:
> - DPLL_A_PIN_PARENT_DEVICE (if parent is a device)
> - DPLL_A_PIN_PARENT_PIN (if parent is a pin)
> 
> 
> I will adapt the docs and send this to Vadim's repo for review today,
> if that is ok for us.

LGTM!
_______________________________________________
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>,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	Jonathan Lemon <jonathan.lemon@gmail.com>,
	Paolo Abeni <pabeni@redhat.com>,
	"Olech, Milena" <milena.olech@intel.com>,
	"Michalik, Michal" <michal.michalik@intel.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>, poros <poros@redhat.com>,
	mschmidt <mschmidt@redhat.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	Bart Van Assche <bvanassche@acm.org>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>, Jiri Pirko <jiri@nvidia.com>
Subject: Re: [PATCH net-next v4 2/9] dpll: spec: Add Netlink spec in YAML
Date: Tue, 22 Aug 2023 09:54:56 -0700	[thread overview]
Message-ID: <20230822095456.0a08b008@kernel.org> (raw)
In-Reply-To: <DM6PR11MB4657E60D5A092E9FC05BC9EF9B1EA@DM6PR11MB4657.namprd11.prod.outlook.com>

On Mon, 21 Aug 2023 10:15:41 +0000 Kubalewski, Arkadiusz wrote:
> I prepared some POC's and it seems most convenient way to do the
> split was to add new argument as proposed on the previous mail.
> After all the spec generated diff for uAPI header like this:
> 
> --- a/include/uapi/linux/dpll.h
> +++ b/include/uapi/linux/dpll.h
> @@ -148,7 +148,17 @@ enum dpll_a {
>         DPLL_A_LOCK_STATUS,
>         DPLL_A_TEMP,
>         DPLL_A_TYPE,
> -       DPLL_A_PIN_ID,
> +
> +       __DPLL_A_MAX,
> +       DPLL_A_MAX = (__DPLL_A_MAX - 1)
> +};
> +
> +enum dpll_a_pin {
> +       DPLL_A_PIN_ID = 1,
> +       DPLL_A_PIN_PARENT_ID,
> +       DPLL_A_PIN_MODULE_NAME,
> +       DPLL_A_PIN_PAD,
> +       DPLL_A_PIN_CLOCK_ID,
>         DPLL_A_PIN_BOARD_LABEL,
>         DPLL_A_PIN_PANEL_LABEL,
>         DPLL_A_PIN_PACKAGE_LABEL,
> @@ -164,8 +174,8 @@ enum dpll_a {
>         DPLL_A_PIN_PARENT_DEVICE,
>         DPLL_A_PIN_PARENT_PIN,
> 
> -       __DPLL_A_MAX,
> -       DPLL_A_MAX = (__DPLL_A_MAX - 1)
> +       __DPLL_A_PIN_MAX,
> +       DPLL_A_PIN_MAX = (__DPLL_A_PIN_MAX - 1)
>  };
> 
> So we have additional attribute for targeting either a pin or device
> DPLL_A_PIN_PARENT_ID (u32) - which would be enclosed in the nests as
> previously:
> - DPLL_A_PIN_PARENT_DEVICE (if parent is a device)
> - DPLL_A_PIN_PARENT_PIN (if parent is a pin)
> 
> 
> I will adapt the docs and send this to Vadim's repo for review today,
> if that is ok for us.

LGTM!

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>,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	Jonathan Lemon <jonathan.lemon@gmail.com>,
	Paolo Abeni <pabeni@redhat.com>,
	"Olech, Milena" <milena.olech@intel.com>,
	"Michalik, Michal" <michal.michalik@intel.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>, poros <poros@redhat.com>,
	mschmidt <mschmidt@redhat.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	Bart Van Assche <bvanassche@acm.org>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>, Jiri Pirko <jiri@nvidia.com>
Subject: Re: [PATCH net-next v4 2/9] dpll: spec: Add Netlink spec in YAML
Date: Tue, 22 Aug 2023 09:54:56 -0700	[thread overview]
Message-ID: <20230822095456.0a08b008@kernel.org> (raw)
In-Reply-To: <DM6PR11MB4657E60D5A092E9FC05BC9EF9B1EA@DM6PR11MB4657.namprd11.prod.outlook.com>

On Mon, 21 Aug 2023 10:15:41 +0000 Kubalewski, Arkadiusz wrote:
> I prepared some POC's and it seems most convenient way to do the
> split was to add new argument as proposed on the previous mail.
> After all the spec generated diff for uAPI header like this:
> 
> --- a/include/uapi/linux/dpll.h
> +++ b/include/uapi/linux/dpll.h
> @@ -148,7 +148,17 @@ enum dpll_a {
>         DPLL_A_LOCK_STATUS,
>         DPLL_A_TEMP,
>         DPLL_A_TYPE,
> -       DPLL_A_PIN_ID,
> +
> +       __DPLL_A_MAX,
> +       DPLL_A_MAX = (__DPLL_A_MAX - 1)
> +};
> +
> +enum dpll_a_pin {
> +       DPLL_A_PIN_ID = 1,
> +       DPLL_A_PIN_PARENT_ID,
> +       DPLL_A_PIN_MODULE_NAME,
> +       DPLL_A_PIN_PAD,
> +       DPLL_A_PIN_CLOCK_ID,
>         DPLL_A_PIN_BOARD_LABEL,
>         DPLL_A_PIN_PANEL_LABEL,
>         DPLL_A_PIN_PACKAGE_LABEL,
> @@ -164,8 +174,8 @@ enum dpll_a {
>         DPLL_A_PIN_PARENT_DEVICE,
>         DPLL_A_PIN_PARENT_PIN,
> 
> -       __DPLL_A_MAX,
> -       DPLL_A_MAX = (__DPLL_A_MAX - 1)
> +       __DPLL_A_PIN_MAX,
> +       DPLL_A_PIN_MAX = (__DPLL_A_PIN_MAX - 1)
>  };
> 
> So we have additional attribute for targeting either a pin or device
> DPLL_A_PIN_PARENT_ID (u32) - which would be enclosed in the nests as
> previously:
> - DPLL_A_PIN_PARENT_DEVICE (if parent is a device)
> - DPLL_A_PIN_PARENT_PIN (if parent is a pin)
> 
> 
> I will adapt the docs and send this to Vadim's repo for review today,
> if that is ok for us.

LGTM!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-08-22 16:55 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 20:03 [Intel-wired-lan] [PATCH net-next v4 0/9] Create common DPLL configuration API Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 1/9] dpll: documentation on DPLL subsystem interface Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-15  2:52   ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15  2:52     ` Jakub Kicinski
2023-08-15  2:52     ` Jakub Kicinski
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 2/9] dpll: spec: Add Netlink spec in YAML Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-15  2:43   ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15  2:43     ` Jakub Kicinski
2023-08-15  2:43     ` Jakub Kicinski
2023-08-17 18:40     ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-08-17 18:40       ` Kubalewski, Arkadiusz
2023-08-17 18:40       ` Kubalewski, Arkadiusz
2023-08-17 23:36       ` [Intel-wired-lan] " Jakub Kicinski
2023-08-17 23:36         ` Jakub Kicinski
2023-08-17 23:36         ` Jakub Kicinski
2023-08-18  7:23         ` [Intel-wired-lan] " Jiri Pirko
2023-08-18  7:23           ` Jiri Pirko
2023-08-18  7:23           ` Jiri Pirko
2023-08-21 10:15           ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-08-21 10:15             ` Kubalewski, Arkadiusz
2023-08-21 10:15             ` Kubalewski, Arkadiusz
2023-08-22 16:54             ` Jakub Kicinski [this message]
2023-08-22 16:54               ` Jakub Kicinski
2023-08-22 16:54               ` Jakub Kicinski
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 3/9] dpll: core: Add DPLL framework base functions Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-15  3:17   ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15  3:17     ` Jakub Kicinski
2023-08-15  3:17     ` Jakub Kicinski
2023-08-15  6:00     ` [Intel-wired-lan] " Jiri Pirko
2023-08-15  6:00       ` Jiri Pirko
2023-08-15  6:00       ` Jiri Pirko
2023-08-15 18:20     ` [Intel-wired-lan] " Vadim Fedorenko
2023-08-15 18:20       ` Vadim Fedorenko
2023-08-15 18:20       ` Vadim Fedorenko
2023-08-15 18:28       ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15 18:28         ` Jakub Kicinski
2023-08-15 18:28         ` Jakub Kicinski
2023-08-15 18:38         ` [Intel-wired-lan] " Vadim Fedorenko
2023-08-15 18:38           ` Vadim Fedorenko
2023-08-15 18:38           ` Vadim Fedorenko
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 4/9] dpll: netlink: " Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-15  3:23   ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15  3:23     ` Jakub Kicinski
2023-08-15  3:23     ` Jakub Kicinski
2023-08-15  3:24   ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15  3:24     ` Jakub Kicinski
2023-08-15  3:24     ` Jakub Kicinski
2023-08-15 15:18     ` [Intel-wired-lan] " Vadim Fedorenko
2023-08-15 15:18       ` Vadim Fedorenko
2023-08-15 15:18       ` Vadim Fedorenko
2023-08-15 16:55       ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15 16:55         ` Jakub Kicinski
2023-08-15 16:55         ` Jakub Kicinski
2023-08-15 18:25         ` [Intel-wired-lan] " Vadim Fedorenko
2023-08-15 18:25           ` Vadim Fedorenko
2023-08-15 18:25           ` Vadim Fedorenko
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 5/9] netdev: expose DPLL pin handle for netdevice Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 6/9] ice: add admin commands to access cgu configuration Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 7/9] ice: implement dpll interface to control cgu Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-12  6:19   ` [Intel-wired-lan] " Jiri Pirko
2023-08-12  6:19     ` Jiri Pirko
2023-08-12  6:19     ` Jiri Pirko
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 8/9] ptp_ocp: implement DPLL ops Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 9/9] mlx5: Implement SyncE support using DPLL infrastructure Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-11 20:03   ` Vadim Fedorenko
2023-08-12  6:22 ` [Intel-wired-lan] [PATCH net-next v4 0/9] Create common DPLL configuration API Jiri Pirko
2023-08-12  6:22   ` Jiri Pirko
2023-08-12  6:22   ` Jiri Pirko
2023-08-12 11:20   ` [Intel-wired-lan] " Vadim Fedorenko
2023-08-12 11:20     ` Vadim Fedorenko
2023-08-12 11:20     ` Vadim Fedorenko
2023-08-15  2:45 ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15  2:45   ` Jakub Kicinski
2023-08-15  2:45   ` Jakub Kicinski
2023-08-15 11:36   ` [Intel-wired-lan] " Vadim Fedorenko
2023-08-15 11:36     ` Vadim Fedorenko
2023-08-15 11:36     ` Vadim Fedorenko
2023-08-15 11:52     ` [Intel-wired-lan] " Jiri Pirko
2023-08-15 11:52       ` Jiri Pirko
2023-08-15 11:52       ` Jiri Pirko
2023-08-15 14:32       ` [Intel-wired-lan] " Vadim Fedorenko
2023-08-15 14:32         ` Vadim Fedorenko
2023-08-15 14:32         ` Vadim Fedorenko
2023-08-15 17:02       ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15 17:02         ` Jakub Kicinski
2023-08-15 17:02         ` Jakub Kicinski
2023-08-18 10:15         ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-08-18 10:15           ` Kubalewski, Arkadiusz
2023-08-18 10:15           ` Kubalewski, Arkadiusz
2023-08-18 21:03           ` [Intel-wired-lan] " Jakub Kicinski
2023-08-18 21:03             ` Jakub Kicinski
2023-08-18 21:03             ` Jakub Kicinski

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=20230822095456.0a08b008@kernel.org \
    --to=kuba@kernel.org \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=bvanassche@acm.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jiri@nvidia.com \
    --cc=jiri@resnulli.us \
    --cc=jonathan.lemon@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=milena.olech@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.