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 18:48:13 +0000	[thread overview]
Message-ID: <56D340ED.3090409@roeck-us.net> (raw)
In-Reply-To: <SNT147-W1A9746D160B8ED3C0290AB3A40@phx.gbl>

On 02/28/2016 10:36 AM, Fulcrum wrote:
>
> On 02/29/2016 01:54 AM, Guenter Roeck wrote:
>
>> The kernel log should tell you when you load the driver without force_id.
>
> I tried loading the driver without force_id, and it did work. I learnt
> about force_id for this chip in some forum post, and never thought of loading the driver without force_id. Here are the kernel logs (dmesg):
>
> [25369.887005] f71882fg: Found f71868a chip at 0x290, revision 48
> [25369.887150] f71882fg f71882fg.656: Fan: 1 is in duty-cycle mode
> [25369.887177] f71882fg f71882fg.656: Fan: 2 is in duty-cycle mode
> [25369.887202] f71882fg f71882fg.656: Fan: 3 is in duty-cycle mode
>
> There was no chip id in dmesg logs though.
>
It tells you the chip name, so it isn't considered to be necessary.

>> If sensors-detect provides the chip name, its ID is recognized.
> Here is the f71868a related output from sensors-detect:
>
> Driver `to-be-written':
> * ISA bus, address 0x295
> Chip `Fintek F71868A Super IO Sensors' (confidence: 9)
>
> Note: there is no driver for Fintek F71868A Super IO Sensors yet.
> Check http://www.lm-sensors.org/wiki/Devices for updates.
>
> No chip id here either.
>
>> Are you sure the driver doesn't load without force_id ?
>> If so, do you see a message in the kernel log ? What does it say ?
>> There should be something like
>>      f71882fg: Unsupported Fintek device: <hex ID>
>> in the log.
>>
>
> Does work without force_id.
>
>> No, this is not an auto-loading driver. The kernel does not support auto-loading
>> Super-IO chip drivers. In case you wonder: It shouldn't, because Super-IO chip
>> detection is not well defined. Running sensors-detect is critical enough; even
>> that asks you and says "This is _usually_ safe" (emphasis added). We don't really
>> want to do this automatically with every boot.
>
> I didn't know about auto-loading problem with Super-IO chip drivers.
> This fact and the faulty output from sensors-detect were the reasons
> behind this long convesation. LOL
>

Glad I could help. On mystery solved, thousands to go ;-)

> Thanks a lot for helping me and this information.
>
My pleasure.

Thanks,
Guenter



_______________________________________________
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 18:48 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
2016-02-28 17:54 ` Guenter Roeck
2016-02-28 18:36 ` Fulcrum
2016-02-28 18:48 ` Guenter Roeck [this message]
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=56D340ED.3090409@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.