On Sat, May 13, 2023 at 11:53 AM Henning Schild <henning.schild@xxxxxxxxxxx> wrote: > > Am Thu, 11 May 2023 14:52:17 +0200 > schrieb Bartosz Golaszewski <brgl@xxxxxxxx>: > > > On Fri, Apr 28, 2023 at 11:33 AM Henning Schild > > <henning.schild@xxxxxxxxxxx> wrote: > > > > > > Am Fri, 28 Apr 2023 10:26:18 +0200 > > > schrieb "Wu, Xing Tong (DI FA CTR IPC CN PRC4)" > > > <XingTong.Wu@xxxxxxxxxxx>: > > > > > > > Hi all > > > > > > > > The chip id of NCT6116D is 0XD281, you can refer to > > > > NCT6116D_Datasheet_V1_0.pdf, Page 291 > > > > > > Thanks Xing Tong. I think we have come to agree that for now > > > NCT6116D 0xD281 will not be supported in the kernel. Maybe until > > > someone has access to that very chip and a use-case. > > > > > > But you managed to somehow get these datasheets, which are still not > > > publicly available. Maybe you can use your contacts at Nuvoton to > > > kindly ask them to publish those specs on their website for future > > > reference. Some specs are there, but not all. That would help > > > people to add more chips and avoid mistakes like they happened to > > > me. > > > > > > Henning > > > > > > > Henning, do you plan to respin this with the ID corrected? > > Bart, no this one fixes the name of the chip i have at hand, and fixes > the size of its last bank. So it is valid on its own and should IMHO be > merged as is. > > Since i do not have a NCT6116D (0xD281) i could basically just guess > (not too hard) but not test. And i do not really feel like contributing > untested code for which there is no known user/tester. > > Henning > > > Bart > Fair enough, applied. Bart