All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Anders <anders-3bOZC6EutKuELgA04lAiVw@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Need help: Watchdog-driver over smbus (i2c)
Date: Mon, 30 Nov 2009 22:30:07 +0100	[thread overview]
Message-ID: <4B14395F.4070608@anduras.de> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1599 bytes --]

Hello!

I'm trying to code a watchdog driver for the Winbond w83793g chip. I
already coded a watchdog for another Winbond chip before, but for
this I need to access it over the system managment bus (or more
specific the i2c, client address 2E).

I already coded the detection and initialization routines, but now I
need some help, because I do not know how to use the i2c framework
together with the watchdog framework.
All other drivers I found are using the sysfs framework. This functions
use the to_i2c_client() function to get a pointer to the i2c client.

I tried to store the i2c client pointer to a global variable, to use
it later in the watchdog functions.
But when I try to use the "i2c_smbus_read_byte_data()" or
"i2c_smbus_write_byte_data()" functions, I will get a kernel OOPS
(without any hw-sensors driver loaded!).

What is the best method to get the watchdog framework (i.e. the open,
close, write, read and ioctl functions) to work with the i2c framework?


Moreover the w83793g hardware sensors driver may already
accessing the same chip. What is the normal way to deal with this?


Regards
 Sven Anders

-- 
 Sven Anders <anders-3bOZC6EutKuELgA04lAiVw@public.gmane.org>                 () Ascii Ribbon Campaign
                                                 /\ Support plain text e-mail
 ANDURAS service solutions AG
 Innstrasse 71 - 94036 Passau - Germany
 Web: www.anduras.de - Tel: +49 (0)851-4 90 50-0 - Fax: +49 (0)851-4 90 50-55

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin

[-- Attachment #1.2: anders.vcf --]
[-- Type: text/x-vcard, Size: 367 bytes --]

begin:vcard
fn:Sven Anders
n:Anders;Sven
org:ANDURAS AG;Research and Development
adr;quoted-printable:;;Innstra=C3=9Fe 71;Passau;Bavaria;94036;Germany
email;internet:anders-3bOZC6EutKuELgA04lAiVw@public.gmane.org
title:Dipl. Inf.
tel;work:++49 (0)851 / 490 50 -0
tel;fax:++49 (0)851 / 590 50 - 55
x-mozilla-html:FALSE
url:http://www.anduras.de
version:2.1
end:vcard


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 4888 bytes --]

             reply	other threads:[~2009-11-30 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 21:30 Sven Anders [this message]
     [not found] ` <4B14395F.4070608-3bOZC6EutKuELgA04lAiVw@public.gmane.org>
2009-12-01  9:31   ` Need help: Watchdog-driver over smbus (i2c) Jean Delvare
     [not found]     ` <20091201103120.6ba0f7e0-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-12-03 20:56       ` Sven Anders
     [not found]         ` <4B18261B.8070507-3bOZC6EutKuELgA04lAiVw@public.gmane.org>
2009-12-03 22:17           ` Jean Delvare

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=4B14395F.4070608@anduras.de \
    --to=anders-3bozc6eutkuelga04laivw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.