[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y7UYpQq/DBCNcKiL@kroah.com>
Date: Wed, 4 Jan 2023 07:11:49 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Tony Nguyen <anthony.l.nguyen@...el.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
pabeni@...hat.com, edumazet@...gle.com,
Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>,
johan@...nel.org, jirislaby@...nel.org,
Alexander Lobakin <alexandr.lobakin@...el.com>,
Karol Kolacinski <karol.kolacinski@...el.com>,
Michal Michalik <michal.michalik@...el.com>
Subject: Re: [RFC PATCH net-next 1/1] ice: use GNSS subsystem instead of TTY
On Thu, Dec 15, 2022 at 03:10:47PM -0800, Tony Nguyen wrote:
> From: Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>
>
> Previously support for GNSS was implemented as a TTY driver, it allowed
> to access GNSS receiver on /dev/ttyGNSS_<bus><func>.
>
> Use generic GNSS subsystem API instead of implementing own TTY driver.
> The receiver is accessible on /dev/gnss<id>. In case of multiple
> receivers in the OS, correct device can be found by enumerating either:
> - /sys/class/net/<eth port>/device/gnss/
> - /sys/class/gnss/gnss<id>/device/
>
> User expecting onboard GNSS receiver support is required to enable
> CONFIG_GNSS=y/m in kernel config.
>
> Reviewed-by: Alexander Lobakin <alexandr.lobakin@...el.com>
> Signed-off-by: Karol Kolacinski <karol.kolacinski@...el.com>
> Signed-off-by: Michal Michalik <michal.michalik@...el.com>
> Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>
> ---
> Based on feedback from:
> https://lore.kernel.org/netdev/20220829220049.333434-4-anthony.l.nguyen@intel.com/
Why is this "RFC"? What is left to be done to it to warrant that
marking?
thanks,
greg k-h
Powered by blists - more mailing lists