From: Jiri Pirko <jiri@resnulli.us>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: vadim.fedorenko@linux.dev, corbet@lwn.net,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com,
intel-wired-lan@lists.osuosl.org, kuba@kernel.org,
pabeni@redhat.com, davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH net-next 1/4] dpll: docs: add support for pin signal phase offset/adjust
Date: Mon, 2 Oct 2023 17:00:47 +0200 [thread overview]
Message-ID: <ZRrbH4gdfOg9TmV3@nanopsycho> (raw)
In-Reply-To: <20230927092435.1565336-2-arkadiusz.kubalewski@intel.com>
Wed, Sep 27, 2023 at 11:24:32AM CEST, arkadiusz.kubalewski@intel.com wrote:
>Add dpll documentation on new pin's attributes:
>- phase-offset - measured difference between phase of signals on pin
> and dpll
>- phase-adjust - adjustable value of pin's signal phase
>- phase-adjust-min / phase-adjust-max - values for determining limits
> for phase-adjust
>
>Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
>---
> Documentation/driver-api/dpll.rst | 53 ++++++++++++++++++++++++++++++-
> 1 file changed, 52 insertions(+), 1 deletion(-)
>
>diff --git a/Documentation/driver-api/dpll.rst b/Documentation/driver-api/dpll.rst
>index bb52f1b8c0be..59634a3513bd 100644
>--- a/Documentation/driver-api/dpll.rst
>+++ b/Documentation/driver-api/dpll.rst
>@@ -173,6 +173,47 @@ in order to configure active input of a MUX-type pin, the user needs to
> request desired pin state of the child pin on the parent pin,
> as described in the ``MUX-type pins`` chapter.
>
>+Phase offset measurement and adjustment
>+========================================
>+
>+Device may provide ability to measure a phase difference between signals
>+on a pin and its parent dpll device. If pin-dpll phase offset measurement
>+is supported, it shall be provided with ``DPLL_A_PIN_PHASE_OFFSET``
>+attribute for each parent dpll device.
>+
>+Device may also provide ability to adjust a signal phase on a pin.
>+If pin phase adjustment is supported, minimal and maximal values that pin
>+handle shall be provide to the user on ``DPLL_CMD_PIN_GET`` respond
>+with ``DPLL_A_PIN_PHASE_ADJUST_MIN`` and ``DPLL_A_PIN_PHASE_ADJUST_MAX``
>+attributes. Configured phase adjust value is provided with
>+``DPLL_A_PIN_PHASE_ADJUST`` attribute of a pin, and value change can be
>+requested with the same attribute with ``DPLL_CMD_PIN_SET`` command.
>+
>+ =============================== ======================================
>+ ``DPLL_A_PIN_ID`` configured pin id
>+ ``DPLL_A_PIN_PHASE_ADJUST_MIN`` attr minimum value of phase adjustment
>+ ``DPLL_A_PIN_PHASE_ADJUST_MAX`` attr maximum value of phase adjustment
>+ ``DPLL_A_PIN_PHASE_ADJUST`` attr configured value of phase
>+ adjustment on parent dpll device
>+ ``DPLL_A_PIN_PARENT_DEVICE`` nested attribute for requesting
>+ configuration on given parent dpll
>+ device
>+ ``DPLL_A_PIN_PARENT_ID`` parent dpll device id
>+ ``DPLL_A_PIN_PHASE_OFFSET`` attr measured phase difference
>+ between a pin and parent dpll device
>+ =============================== ======================================
>+
>+All phase related values are provided in pico seconds, which represents
>+time differnece between signals phase. The negative value means that
>+phase of signal on pin is earlier in time than dpll's signal. Positive
>+value means that phase of signal on pin is later in time than signal of
>+a dpll.
>+
>+Phase adjust (also min and max) values are integers, but measured phase
>+offset values are fractional with 3-digit decimal places and shell be
>+divided with ``DPLL_PIN_PHASE_OFFSET_DIVIDER`` to get integer part and
>+modulo divided to get fractional part.
>+
> Configuration commands group
> ============================
>
>@@ -263,6 +304,12 @@ according to attribute purpose.
> frequencies
> ``DPLL_A_PIN_ANY_FREQUENCY_MIN`` attr minimum value of frequency
> ``DPLL_A_PIN_ANY_FREQUENCY_MAX`` attr maximum value of frequency
>+ ``DPLL_A_PIN_PHASE_ADJUST_MIN`` attr minimum value of phase
>+ adjustment
>+ ``DPLL_A_PIN_PHASE_ADJUST_MAX`` attr maximum value of phase
>+ adjustment
>+ ``DPLL_A_PIN_PHASE_ADJUST`` attr configured value of phase
>+ adjustment on parent device
> ``DPLL_A_PIN_PARENT_DEVICE`` nested attr for each parent device
> the pin is connected with
> ``DPLL_A_PIN_PARENT_ID`` attr parent dpll device id
>@@ -270,8 +317,10 @@ according to attribute purpose.
> dpll device
> ``DPLL_A_PIN_STATE`` attr state of pin on the parent
> dpll device
>- ``DPLL_A_PIN_DIRECTION`` attr direction of a pin on the
>+ ``DPLL_A_PIN_DIRECTION`` attr direction of a pin on the
Could be in a separate patch, it's not related to this one.
> parent dpll device
>+ ``DPLL_A_PIN_PHASE_OFFSET`` attr measured phase difference
>+ between a pin and parent dpll
> ``DPLL_A_PIN_PARENT_PIN`` nested attr for each parent pin
> the pin is connected with
> ``DPLL_A_PIN_PARENT_ID`` attr parent pin id
>@@ -284,6 +333,8 @@ according to attribute purpose.
> ``DPLL_CMD_PIN_SET`` command to set pins configuration
> ``DPLL_A_PIN_ID`` attr unique a pin ID
> ``DPLL_A_PIN_FREQUENCY`` attr requested frequency of a pin
>+ ``DPLL_A_PIN_PHASE_ADJUST`` attr requested value of phase
>+ adjustment on parent device
> ``DPLL_A_PIN_PARENT_DEVICE`` nested attr for each parent dpll
> device configuration request
> ``DPLL_A_PIN_PARENT_ID`` attr parent dpll device id
>--
>2.38.1
>
_______________________________________________
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: Jiri Pirko <jiri@resnulli.us>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: netdev@vger.kernel.org, vadim.fedorenko@linux.dev,
corbet@lwn.net, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, linux-doc@vger.kernel.org,
intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH net-next 1/4] dpll: docs: add support for pin signal phase offset/adjust
Date: Mon, 2 Oct 2023 17:00:47 +0200 [thread overview]
Message-ID: <ZRrbH4gdfOg9TmV3@nanopsycho> (raw)
In-Reply-To: <20230927092435.1565336-2-arkadiusz.kubalewski@intel.com>
Wed, Sep 27, 2023 at 11:24:32AM CEST, arkadiusz.kubalewski@intel.com wrote:
>Add dpll documentation on new pin's attributes:
>- phase-offset - measured difference between phase of signals on pin
> and dpll
>- phase-adjust - adjustable value of pin's signal phase
>- phase-adjust-min / phase-adjust-max - values for determining limits
> for phase-adjust
>
>Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
>---
> Documentation/driver-api/dpll.rst | 53 ++++++++++++++++++++++++++++++-
> 1 file changed, 52 insertions(+), 1 deletion(-)
>
>diff --git a/Documentation/driver-api/dpll.rst b/Documentation/driver-api/dpll.rst
>index bb52f1b8c0be..59634a3513bd 100644
>--- a/Documentation/driver-api/dpll.rst
>+++ b/Documentation/driver-api/dpll.rst
>@@ -173,6 +173,47 @@ in order to configure active input of a MUX-type pin, the user needs to
> request desired pin state of the child pin on the parent pin,
> as described in the ``MUX-type pins`` chapter.
>
>+Phase offset measurement and adjustment
>+========================================
>+
>+Device may provide ability to measure a phase difference between signals
>+on a pin and its parent dpll device. If pin-dpll phase offset measurement
>+is supported, it shall be provided with ``DPLL_A_PIN_PHASE_OFFSET``
>+attribute for each parent dpll device.
>+
>+Device may also provide ability to adjust a signal phase on a pin.
>+If pin phase adjustment is supported, minimal and maximal values that pin
>+handle shall be provide to the user on ``DPLL_CMD_PIN_GET`` respond
>+with ``DPLL_A_PIN_PHASE_ADJUST_MIN`` and ``DPLL_A_PIN_PHASE_ADJUST_MAX``
>+attributes. Configured phase adjust value is provided with
>+``DPLL_A_PIN_PHASE_ADJUST`` attribute of a pin, and value change can be
>+requested with the same attribute with ``DPLL_CMD_PIN_SET`` command.
>+
>+ =============================== ======================================
>+ ``DPLL_A_PIN_ID`` configured pin id
>+ ``DPLL_A_PIN_PHASE_ADJUST_MIN`` attr minimum value of phase adjustment
>+ ``DPLL_A_PIN_PHASE_ADJUST_MAX`` attr maximum value of phase adjustment
>+ ``DPLL_A_PIN_PHASE_ADJUST`` attr configured value of phase
>+ adjustment on parent dpll device
>+ ``DPLL_A_PIN_PARENT_DEVICE`` nested attribute for requesting
>+ configuration on given parent dpll
>+ device
>+ ``DPLL_A_PIN_PARENT_ID`` parent dpll device id
>+ ``DPLL_A_PIN_PHASE_OFFSET`` attr measured phase difference
>+ between a pin and parent dpll device
>+ =============================== ======================================
>+
>+All phase related values are provided in pico seconds, which represents
>+time differnece between signals phase. The negative value means that
>+phase of signal on pin is earlier in time than dpll's signal. Positive
>+value means that phase of signal on pin is later in time than signal of
>+a dpll.
>+
>+Phase adjust (also min and max) values are integers, but measured phase
>+offset values are fractional with 3-digit decimal places and shell be
>+divided with ``DPLL_PIN_PHASE_OFFSET_DIVIDER`` to get integer part and
>+modulo divided to get fractional part.
>+
> Configuration commands group
> ============================
>
>@@ -263,6 +304,12 @@ according to attribute purpose.
> frequencies
> ``DPLL_A_PIN_ANY_FREQUENCY_MIN`` attr minimum value of frequency
> ``DPLL_A_PIN_ANY_FREQUENCY_MAX`` attr maximum value of frequency
>+ ``DPLL_A_PIN_PHASE_ADJUST_MIN`` attr minimum value of phase
>+ adjustment
>+ ``DPLL_A_PIN_PHASE_ADJUST_MAX`` attr maximum value of phase
>+ adjustment
>+ ``DPLL_A_PIN_PHASE_ADJUST`` attr configured value of phase
>+ adjustment on parent device
> ``DPLL_A_PIN_PARENT_DEVICE`` nested attr for each parent device
> the pin is connected with
> ``DPLL_A_PIN_PARENT_ID`` attr parent dpll device id
>@@ -270,8 +317,10 @@ according to attribute purpose.
> dpll device
> ``DPLL_A_PIN_STATE`` attr state of pin on the parent
> dpll device
>- ``DPLL_A_PIN_DIRECTION`` attr direction of a pin on the
>+ ``DPLL_A_PIN_DIRECTION`` attr direction of a pin on the
Could be in a separate patch, it's not related to this one.
> parent dpll device
>+ ``DPLL_A_PIN_PHASE_OFFSET`` attr measured phase difference
>+ between a pin and parent dpll
> ``DPLL_A_PIN_PARENT_PIN`` nested attr for each parent pin
> the pin is connected with
> ``DPLL_A_PIN_PARENT_ID`` attr parent pin id
>@@ -284,6 +333,8 @@ according to attribute purpose.
> ``DPLL_CMD_PIN_SET`` command to set pins configuration
> ``DPLL_A_PIN_ID`` attr unique a pin ID
> ``DPLL_A_PIN_FREQUENCY`` attr requested frequency of a pin
>+ ``DPLL_A_PIN_PHASE_ADJUST`` attr requested value of phase
>+ adjustment on parent device
> ``DPLL_A_PIN_PARENT_DEVICE`` nested attr for each parent dpll
> device configuration request
> ``DPLL_A_PIN_PARENT_ID`` attr parent dpll device id
>--
>2.38.1
>
next prev parent reply other threads:[~2023-10-02 15:00 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 9:24 [Intel-wired-lan] [PATCH net-next 0/4] dpll: add phase-offset and phase-adjust Arkadiusz Kubalewski
2023-09-27 9:24 ` Arkadiusz Kubalewski
2023-09-27 9:24 ` [Intel-wired-lan] [PATCH net-next 1/4] dpll: docs: add support for pin signal phase offset/adjust Arkadiusz Kubalewski
2023-09-27 9:24 ` Arkadiusz Kubalewski
2023-10-02 15:00 ` Jiri Pirko [this message]
2023-10-02 15:00 ` Jiri Pirko
2023-10-09 22:53 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-10-09 22:53 ` Kubalewski, Arkadiusz
2023-09-27 9:24 ` [Intel-wired-lan] [PATCH net-next 2/4] dpll: spec: add support for pin-dpll " Arkadiusz Kubalewski
2023-09-27 9:24 ` Arkadiusz Kubalewski
2023-10-02 14:53 ` [Intel-wired-lan] " Jiri Pirko
2023-10-02 14:53 ` Jiri Pirko
2023-10-06 10:29 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-10-06 10:29 ` Kubalewski, Arkadiusz
2023-09-27 9:24 ` [Intel-wired-lan] [PATCH net-next 3/4] dpll: netlink/core: " Arkadiusz Kubalewski
2023-09-27 9:24 ` Arkadiusz Kubalewski
2023-09-27 18:09 ` [Intel-wired-lan] " Vadim Fedorenko
2023-09-27 18:09 ` Vadim Fedorenko
2023-10-02 14:32 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-10-02 14:32 ` Kubalewski, Arkadiusz
2023-10-02 15:04 ` [Intel-wired-lan] " Jiri Pirko
2023-10-02 15:04 ` Jiri Pirko
2023-10-02 15:09 ` [Intel-wired-lan] " Vadim Fedorenko
2023-10-02 15:09 ` Vadim Fedorenko
2023-10-02 23:10 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-10-02 23:10 ` Kubalewski, Arkadiusz
2023-10-03 6:27 ` Jiri Pirko
2023-10-03 6:27 ` Jiri Pirko
2023-10-03 14:29 ` Kubalewski, Arkadiusz
2023-10-03 14:29 ` Kubalewski, Arkadiusz
2023-10-03 17:18 ` Jiri Pirko
2023-10-03 17:18 ` Jiri Pirko
2023-10-04 9:13 ` Kubalewski, Arkadiusz
2023-10-04 9:13 ` Kubalewski, Arkadiusz
2023-10-02 23:03 ` Kubalewski, Arkadiusz
2023-10-02 23:03 ` Kubalewski, Arkadiusz
2023-10-03 6:32 ` [Intel-wired-lan] " Jiri Pirko
2023-10-03 6:32 ` Jiri Pirko
2023-10-03 14:29 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-10-03 14:29 ` Kubalewski, Arkadiusz
2023-10-03 17:19 ` [Intel-wired-lan] " Jiri Pirko
2023-10-03 17:19 ` Jiri Pirko
2023-10-04 9:11 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-10-04 9:11 ` Kubalewski, Arkadiusz
2023-09-27 9:24 ` [Intel-wired-lan] [PATCH net-next 4/4] ice: dpll: implement phase related callbacks Arkadiusz Kubalewski
2023-09-27 9:24 ` Arkadiusz Kubalewski
2023-09-27 13:17 ` [Intel-wired-lan] " kernel test robot
2023-09-27 13:17 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2023-09-05 23:26 [Intel-wired-lan] [PATCH net-next 0/4] dpll: add phase offset and phase adjust Arkadiusz Kubalewski
2023-09-05 23:26 ` [Intel-wired-lan] [PATCH net-next 1/4] dpll: docs: add support for pin signal phase offset/adjust Arkadiusz Kubalewski
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=ZRrbH4gdfOg9TmV3@nanopsycho \
--to=jiri@resnulli.us \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--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.