Netdev List
 help / color / mirror / Atom feed
From: Benjamin Larsson <benjamin.larsson@genexis.eu>
To: Andrew Lunn <andrew@lunn.ch>
Cc: John Crispin <john@phrozen.org>, Ziyou Xu <xuziyougm@gmail.com>,
	netdev@vger.kernel.org,
	Matheus Sampaio Queiroga <srherobrine20@gmail.com>,
	Lorenzo Bianconi <lorenzo@kernel.org>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	Russell King <linux@armlinux.org.uk>,
	Gaoyang Wei <yhyxwgy@gmail.com>
Subject: Re: [RFC] net: towards a generic PON framework
Date: Thu, 1 Oct 2026 14:25:50 +0200	[thread overview]
Message-ID: <904b556b-a73a-49e1-bb5e-36fa28b1a3be@genexis.eu> (raw)
In-Reply-To: <e3dfe67b-6d29-4bfb-9642-8c9e86a9a7b1@lunn.ch>

Hi.

On 9/28/26 16:10, Andrew Lunn wrote:
>> In the case of ANI-G 263 I looked at hwmon a while ago and IIRC there was no
>> nice way to consume hwmon information from inside the kernel
> Not my subsystem, but that surprises me. How is temperature management
> performed, where you need to reduce clocks speeds if the system is
> getting too warm. Fan control is a similar problem. Both need access
> to temperature sensor values.
>
> 	Andrew

I only looked at this api briefly. From the api function names and 
documentation it looked like the main direction was towards user space. 
I still postulate that for in-kernel omci ME handling some kernel work 
would be needed to get access to some data, data that might be more easy 
to get access to from user space.

But as I have written 0 omci stacks this is just my general feeling. And 
there is lots of insanity in the standards covering omci, you dont need 
to implement everything just because its in the standard.

Anyway, I'll focus all my efforts into reviewing/testing the RFC coming 
from John and Christian.

MvH

Benjamin Larsson


  reply	other threads:[~2026-10-01 12:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-26 17:46 [RFC] net: towards a generic PON framework Gaoyang Wei
2026-09-26 19:28 ` Matheus Sampaio Queiroga
2026-09-26 20:21   ` Gaoyang Wei
2026-09-26 21:55     ` Matheus Sampaio Queiroga
2026-09-26 22:15       ` Gaoyang Wei
2026-09-27  0:05         ` Matheus Sampaio Queiroga
2026-09-27  4:38           ` Gaoyang Wei
2026-09-27 17:47             ` Matheus Sampaio Queiroga
2026-09-27 18:27               ` Gaoyang Wei
2026-09-27 16:57 ` Andrew Lunn
2026-09-27 17:22   ` Gaoyang Wei
2026-09-27 19:24     ` Ziyou Xu
2026-09-27 19:47     ` Andrew Lunn
2026-09-27 20:29       ` Ziyou Xu
2026-09-27 22:30         ` Andrew Lunn
2026-09-27 22:49         ` Andrew Lunn
2026-09-27 23:11           ` Gaoyang Wei
2026-09-28  1:25             ` Andrew Lunn
2026-09-28  8:37               ` John Crispin
2026-09-28 10:54                 ` Benjamin Larsson
2026-09-28 14:10                   ` Andrew Lunn
2026-10-01 12:25                     ` Benjamin Larsson [this message]
2026-09-28 11:23                 ` Gaoyang Wei
2026-09-28 14:05                 ` Andrew Lunn
2026-09-27 20:47 ` Benjamin Larsson
2026-09-27 20:58   ` Gaoyang Wei

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=904b556b-a73a-49e1-bb5e-36fa28b1a3be@genexis.eu \
    --to=benjamin.larsson@genexis.eu \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=john@phrozen.org \
    --cc=linux@armlinux.org.uk \
    --cc=lorenzo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=srherobrine20@gmail.com \
    --cc=xuziyougm@gmail.com \
    --cc=yhyxwgy@gmail.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