> Date: Thu, 11 Dec 2014 05:08:11 -0500 > From: Matt Dainty <[email protected]> > > * sven falempin <[email protected]> [2014-12-10 12:32:15]: > > On Wed, Dec 10, 2014 at 9:31 AM, Stuart Henderson <[email protected]> wrote: > > > On 2014/12/10 09:15, sven falempin wrote: > > >> http://lxr.free-electrons.com/source/drivers/hwmon/nct6775.c > > >> > > >> https://github.com/groeck/nct6775 > > >> > > >> So i guess the first step is to detect the chip > > > > > > You'll also need somewhere (files) to put the detection. Maybe look at > > > the commit from when tcpcib was added as an example. > > > > > > It might be somewhat similar to the Winbond superio chips (Nuvoton is > > > a spin off company). > > > > > >> On Wed, Dec 10, 2014 at 8:32 AM, sven falempin <[email protected]> > > >> wrote: > > >> > I guess the chip used is obviously this one : > > >> > > > >> > Nuvoton NCT6106D > > >> > > > >> > spec : > > >> > https://download.nuvoton.com/NuvotonMOSS/DownloadService/Member/DocumentsInfo.aspx?tp_GUID=DA00-NCT6106D > > > > > > The watchdog part of this appears to use the same registers as NCT5104D > > > in the pcengines APU. > > > > Well the sequence to configure is the same in the doc > > > > << > > 7.1.1 Enter the Extended Function Mode > > To place the chip into the Extended Function Mode, two successive > > writes of 0x87 must be applied to Extended > > Function Enable Registers (EFERs, i.e. 2Eh or 4Eh). > > >> > > > > I am not sure i understand, is this a pci device or a isa device ? > > Have a look at the wbsio(4) driver. There's already a constant defined for > the NCT6776 so you probably just need to add the missing ID(s) and go from > there.
Yes indeed. That's the correct thing to do. According to the datasheet the Chip ID is 0x10, but we have found that recent Nuvoton datasheets often lie about this, so you might want to enable the printf in wbsio_probe() to see what the real chip ID is. Looks like the chip has a hardware monitoring function as well. Might be possible to add support for this to lm(4). I believe somebody wrote a diff to add watchdog support for this family of chips at some point. A bit of a problem is that on some of these chips the watchdog timer signal is multiplexed on one of the GPIO pins and that pin is often configurable. Which pin to use (or whether the watchdog works at all) depends on the motherboard layout. And the pin that works on your motherboard might be the self destruct button on some other motherboard. That's why we didn't pursue this any further at the time. Things might be a bit saner for your chip though. Cheers, Mark
