[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YFJWWrX+UgXyD9NS@kroah.com>
Date: Wed, 17 Mar 2021 20:19:54 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: min.li.xe@...esas.com
Cc: derek.kiernan@...inx.com, dragan.cvetic@...inx.com, arnd@...db.de,
linux-kernel@...r.kernel.org, linux-api@...r.kernel.org
Subject: Re: [PATCH net-next v1] misc: Add Renesas Synchronization Management
Unit (SMU) support
On Wed, Mar 17, 2021 at 02:59:56PM -0400, min.li.xe@...esas.com wrote:
> From: Min Li <min.li.xe@...esas.com>
>
> This driver is developed for the IDT ClockMatrix(TM) and 82P33xxx families
> of timing and synchronization devices.It will be used by Renesas PTP Clock
> Manager for Linux (pcm4l) software to provide support to GNSS assisted
> partial timing support (APTS) and other networking timing functions.
>
> Current version provides kernel API's to support the following functions
> -set combomode to enable SYNCE clock support
> -read dpll's state to determine if the dpll is locked to the GNSS channel
> -read dpll's ffo (fractional frequency offset)
>
> Signed-off-by: Min Li <min.li.xe@...esas.com>
Why the "net-next" in the subject line?
This is not for the network tree (given that you didn't even cc:
netdev...) or am I confused?
thanks,
gre gk-h
Powered by blists - more mailing lists