linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Robert Rosengren <robert.rosengren@axis.com>,
	Jean Delvare <jdelvare@suse.de>,
	"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>
Cc: Johan Adolfsson <johana@axis.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [lm-sensors] [PATCH] hwmon: (ads7828) Make sample interval configurable
Date: Tue, 27 Jan 2015 06:26:29 -0800	[thread overview]
Message-ID: <54C7A015.4010001@roeck-us.net> (raw)
In-Reply-To: <54C74567.9020201@axis.com>

On 01/26/2015 11:59 PM, Robert Rosengren wrote:
> On 01/16/2015 07:30 PM, Guenter Roeck wrote:
>> I sent a couple of patches a minute ago which should take care of the issue.
>> Would be great if you can test it.
> I applied the v2 versions of the patches for a quick test, but it was not successful. Haven't done any further investigation on what the problem might be, but when trying to read the sysfs driver I get "read error: No such device or address".
>
> The sysfs path have moved with the REGMAP settings, from /sys/bus/i2c/devices/<x>/in0_input to /sys/bus/i2c/devices/<x>/hwmon/hwmon0/in0_input.
>
> Any ideas? Haven't had REGMAP configured in my kernel earlier, might it be some specific configuration I miss?
>

Robert,

Another thought: What is your kernel version, and what is your i2c controller ?

SMBus support was added to regmap only recently, so if your controller only
supports SMBus (not raw i2c transactions), and you have an older kernel,
this might not work. The driver should fail to instantiate in that case,
though, if I recall correctly.

Thanks,
Guenter


  parent reply	other threads:[~2015-01-27 14:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 12:05 [PATCH] hwmon: (ads7828) Make sample interval configurable Robert Rosengren
2015-01-16 14:52 ` Guenter Roeck
2015-01-16 18:30   ` [lm-sensors] " Guenter Roeck
2015-01-19 11:14     ` SV: " Robert Rosengren
2015-01-27  7:59     ` Robert Rosengren
2015-01-27 10:37       ` Jean Delvare
2015-01-27 14:23         ` Guenter Roeck
2015-01-27 14:07       ` Guenter Roeck
2015-01-27 19:54         ` Robert Rosengren
2015-01-27 20:05           ` Guenter Roeck
2015-01-27 22:34             ` Jean Delvare
2015-01-28  4:06               ` Guenter Roeck
     [not found]                 ` <54C87F3C.2020105@axis.com>
2015-01-28  6:28                   ` Robert Rosengren
2015-01-28 14:50                   ` Guenter Roeck
2015-01-29  7:00                     ` Robert Rosengren
2015-01-29  7:05                       ` Guenter Roeck
2015-01-29 12:07                         ` Robert Rosengren
2015-01-29 14:10                           ` Guenter Roeck
2015-01-29 19:30                           ` Guenter Roeck
2015-01-31 20:11                             ` Guenter Roeck
2015-02-02  8:12                               ` Robert Rosengren
2015-02-02 16:21                                 ` Guenter Roeck
2015-01-27 14:26       ` Guenter Roeck [this message]
2015-01-27 16:37       ` Guenter Roeck
2015-01-16 20:30 ` Guenter Roeck

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=54C7A015.4010001@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jdelvare@suse.de \
    --cc=johana@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=robert.rosengren@axis.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).