[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <a0164db0-e234-44ac-8584-a14f0b625181@siemens.com>
Date: Mon, 16 Jun 2025 10:34:04 +0000
From: "Niedermayr, BENEDIKT" <benedikt.niedermayr@...mens.com>
To: "zev@...ilderbeest.net" <zev@...ilderbeest.net>, "jdelvare@...e.com"
<jdelvare@...e.com>, "linux@...ck-us.net" <linux@...ck-us.net>
CC: "Lopes Ivo, Diogo Miguel" <diogo.ivo@...mens.com>, "Kiszka, Jan"
<jan.kiszka@...mens.com>, "linux-hwmon@...r.kernel.org"
<linux-hwmon@...r.kernel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
Subject: Question about nct6775 regarding MFD
Hi folks,
we are currently refactoring some parts of the
"drivers/platform/x86/siemens/*" which has references to some
Nuvoton Super-I/O chips. One of them is the nct6775.
The driver in question is not implemented as MFD, even though MFD would
have fit perfectly for it (or am I wrong?).
My question now:
Why wasn't the driver implemented as an MFD? Was MFD discussed during
your upstreaming-related conversations?
Kind regards,
Benedikt
Powered by blists - more mailing lists