All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Datasheet for Fintek F71868a
Date: Sun, 28 Feb 2016 15:38:29 +0000	[thread overview]
Message-ID: <56D31475.3000308@roeck-us.net> (raw)
In-Reply-To: <SNT147-W1A9746D160B8ED3C0290AB3A40@phx.gbl>

On 02/28/2016 03:46 AM, Fulcrum wrote:
>
>
> On 02/25/2016 01:56 PM, Guenter Roeck wrote:
>> On 02/23/2016 01:40 AM, Foxtrot Mike wrote:
>>> Hi everybody
>>>
>>> I have an MSI MB with fintek F71868a chip for hardware monitoring. As
>>> you might know, this chip is currently not suported by Linux. I was
>>> going through the source code of F71805f chip driver and realized that
>>> I might be able to write a driver for the F71868a chip. Atleast, I
>>> should give it a try.
>>>
>> Did you try the f71882fg driver with a recent kernel version ?
>>
>> Guenter
>>
>
> Hi
>
> I did try the F71882fg driver. I was going through the source code of this driver and realized that F71686a is mentioned in multiple arrays and structures in the source code yet still you have to force the driver for f71686a chip using another chip's ID. You have to forcefully load this driver for F71868a chip using:
>
> #modprobe f71882fg force_id=0x1007
> or
> #modprobe f71882fg force_id=0x1106
>
> 0x1007 is the chip ID of F71869a, and,
> 0x1106 is the chip ID of F71868
>
> Referring to 'linux-4.4.2/drivers/hwmon/f71882fg.c', I found that:
>
> 1- Towards the top of the driver, the chipset ID of F71686 is mentioned. The ID of F71868a is not given.
>
So what is the chip ID of your chip ? There is no "F71868" chip as far as I know.
Sure, one could nitpick that the constant is not named SIO_F81866A_ID but
SIO_F81866_ID, but usually we are not that picky. The chip ID for F71868A
is supposed to be 0x1106.

Guenter

> 2- You'll find entries against F71868a in multiple arrays (f71882fg_names[], f71882fg_has_in[] f71882fg) in the driver code. There is no entry against F71868 in any array.
>
> 3- Not all the registers of F71882fg and f71868a are the same. For example, register 69h is reserved for F71868a but in case of F71882fg, it refers to 'F71882FG_REG_TEMP_CONFIG'
>
> I have no knowledge of driver development but the inability to autoload this driver for F71868a chip (although the source code 'seems' to support this chip) is a little baffling. May be there's a bug?
>
> Regards,
> Fulcrum
>


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2016-02-28 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23  9:40 [lm-sensors] Datasheet for Fintek F71868a Foxtrot Mike
2016-02-25  5:56 ` Guenter Roeck
2016-02-28 15:38 ` Guenter Roeck [this message]
2016-02-28 17:54 ` Guenter Roeck
2016-02-28 18:36 ` Fulcrum
2016-02-28 18:48 ` Guenter Roeck
2016-02-28 22:14 ` Fulcrum

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=56D31475.3000308@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=lm-sensors@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.