netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Prathosh.Satish@microchip.com>
To: <ivecera@redhat.com>, <netdev@vger.kernel.org>
Cc: <arkadiusz.kubalewski@intel.com>, <jiri@resnulli.us>,
	<davem@davemloft.net>, <kuba@kernel.org>, <pabeni@redhat.com>,
	<linux-kernel@vger.kernel.org>, <mschmidt@redhat.com>,
	<poros@redhat.com>
Subject: Re: [PATCH net-next 0/5] dpll: zl3073x: Add misc features
Date: Mon, 14 Jul 2025 14:11:42 +0000	[thread overview]
Message-ID: <bc221fdb-d674-4111-8bb7-e2eadda60b35@microchip.com> (raw)
In-Reply-To: <20250710153848.928531-1-ivecera@redhat.com>

On 10/07/2025 16:38, Ivan Vecera wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Add several new features missing in initial submission:
>
> * Embedded sync for both pin types
> * Phase offset reporting for connected input pin
> * Selectable phase offset monitoring (aka all inputs phase monitor)
> * Phase adjustments for both pin types
> * Fractional frequency offset reporting for input pins
>
> Everything was tested on Microchip EVB-LAN9668 EDS2 development board.
>
> Ivan Vecera (5):
>    dpll: zl3073x: Add support to get/set esync on pins
>    dpll: zl3073x: Add support to get phase offset on connected input pin
>    dpll: zl3073x: Implement phase offset monitor feature
>    dpll: zl3073x: Add support to adjust phase
>    dpll: zl3073x: Add support to get fractional frequency offset
>
>   drivers/dpll/zl3073x/core.c | 171 ++++++++
>   drivers/dpll/zl3073x/core.h |  16 +
>   drivers/dpll/zl3073x/dpll.c | 805 +++++++++++++++++++++++++++++++++++-
>   drivers/dpll/zl3073x/dpll.h |   4 +
>   drivers/dpll/zl3073x/regs.h |  55 +++
>   5 files changed, 1049 insertions(+), 2 deletions(-)
>
> --
> 2.49.0
>
Tested-by: Prathosh Satish <prathosh.satish@microchip.com>


      parent reply	other threads:[~2025-07-14 14:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10 15:38 [PATCH net-next 0/5] dpll: zl3073x: Add misc features Ivan Vecera
2025-07-10 15:38 ` [PATCH net-next 1/5] dpll: zl3073x: Add support to get/set esync on pins Ivan Vecera
2025-07-14 14:13   ` Prathosh.Satish
2025-07-15 12:52   ` Paolo Abeni
2025-07-15 14:10     ` Ivan Vecera
2025-07-10 15:38 ` [PATCH net-next 2/5] dpll: zl3073x: Add support to get phase offset on connected input pin Ivan Vecera
2025-07-14 14:14   ` Prathosh.Satish
2025-07-10 15:38 ` [PATCH net-next 3/5] dpll: zl3073x: Implement phase offset monitor feature Ivan Vecera
2025-07-14 14:15   ` Prathosh.Satish
2025-07-15 13:02   ` Paolo Abeni
2025-07-15 14:18     ` Ivan Vecera
2025-07-10 15:38 ` [PATCH net-next 4/5] dpll: zl3073x: Add support to adjust phase Ivan Vecera
2025-07-14 14:15   ` Prathosh.Satish
2025-07-15 13:12   ` Paolo Abeni
2025-07-15 14:24     ` Ivan Vecera
2025-07-10 15:38 ` [PATCH net-next 5/5] dpll: zl3073x: Add support to get fractional frequency offset Ivan Vecera
2025-07-14 10:55 ` [PATCH net-next 0/5] dpll: zl3073x: Add misc features Jiri Pirko
2025-07-14 14:11 ` Prathosh.Satish [this message]

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=bc221fdb-d674-4111-8bb7-e2eadda60b35@microchip.com \
    --to=prathosh.satish@microchip.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=davem@davemloft.net \
    --cc=ivecera@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mschmidt@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=poros@redhat.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).