All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Paul Walmsley <pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Wei Ni <wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
	LM Sensors <lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org>
Subject: Re: Unhandled LM90 irq 308 on Dalmore?
Date: Mon, 06 Jan 2014 12:13:12 -0700	[thread overview]
Message-ID: <52CB0048.5040304@wwwdotorg.org> (raw)
In-Reply-To: <52B52B64.5020304-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

On 12/20/2013 10:47 PM, Paul Walmsley wrote:
> 
> On 12/20/2013 08:26 AM, Stephen Warren wrote:
...
>> Note that upstream Linux *only* supports Dalmore A04, and no other
>> version. If you have a different board revision, it's not expected to
>> work with upstream. IIRC, Eric Brower volunteered to track down the
>> correct board revision for people working on upstream.
> 
> Indeed, that's probably the problem, then
> 
> It would be good if this was documented somewhere in the upstream kernel
> tree.

I'll send a patch to document that in the DTS file.

> And even better if the kernel was able to read the Dalmore EEPROM
> and print out a warning upon kernel boot...

That would be painful, since it'd be board-specific code that isn't
really coupled with a specific piece of HW for which there's a driver.
I'd rather avoid that kind of thing.

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Paul Walmsley <pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Wei Ni <wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
	LM Sensors <lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org>
Subject: Re: [lm-sensors] Unhandled LM90 irq 308 on Dalmore?
Date: Mon, 06 Jan 2014 19:13:12 +0000	[thread overview]
Message-ID: <52CB0048.5040304@wwwdotorg.org> (raw)
In-Reply-To: <52B52B64.5020304-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

On 12/20/2013 10:47 PM, Paul Walmsley wrote:
> 
> On 12/20/2013 08:26 AM, Stephen Warren wrote:
...
>> Note that upstream Linux *only* supports Dalmore A04, and no other
>> version. If you have a different board revision, it's not expected to
>> work with upstream. IIRC, Eric Brower volunteered to track down the
>> correct board revision for people working on upstream.
> 
> Indeed, that's probably the problem, then
> 
> It would be good if this was documented somewhere in the upstream kernel
> tree.

I'll send a patch to document that in the DTS file.

> And even better if the kernel was able to read the Dalmore EEPROM
> and print out a warning upon kernel boot...

That would be painful, since it'd be board-specific code that isn't
really coupled with a specific piece of HW for which there's a driver.
I'd rather avoid that kind of thing.

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

  parent reply	other threads:[~2014-01-06 19:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19 10:08 Unhandled LM90 irq 308 on Dalmore? Paul Walmsley
     [not found] ` <52B2C5AD.5080405-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-12-19 10:45   ` Jean Delvare
2013-12-19 10:45     ` [lm-sensors] " Jean Delvare
     [not found]     ` <20131219114500.1b1ea0b7-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2013-12-19 22:36       ` Paul Walmsley
2013-12-19 22:36         ` [lm-sensors] " Paul Walmsley
2013-12-20  3:16         ` Wei Ni
2013-12-20  3:16           ` [lm-sensors] " Wei Ni
     [not found]           ` <52B3B679.20206-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-12-20 16:26             ` Stephen Warren
2013-12-20 16:26               ` [lm-sensors] " Stephen Warren
     [not found]               ` <52B46FD2.1030409-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-12-21  5:47                 ` Paul Walmsley
2013-12-21  5:47                   ` [lm-sensors] " Paul Walmsley
     [not found]                   ` <52B52B64.5020304-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-01-06 19:13                     ` Stephen Warren [this message]
2014-01-06 19:13                       ` Stephen Warren
     [not found]                       ` <52CB0048.5040304-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-01-06 19:40                         ` Guenter Roeck
2014-01-06 19:40                           ` [lm-sensors] " Guenter Roeck
     [not found]                           ` <20140106194052.GA27078-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2014-01-06 19:42                             ` Stephen Warren
2014-01-06 19:42                               ` [lm-sensors] " Stephen Warren

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=52CB0048.5040304@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
    --cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
    --cc=pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=wni-DDmLM1+adcrQT0dZR+AlfA@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.