From: khali@linux-fr.org (Jean Delvare)
To: linux-arm-kernel@lists.infradead.org
Subject: [lm-sensors] [PATCH 1/2] ARM: dt: t30 cardhu: add dt entry for lm90
Date: Tue, 9 Jul 2013 09:55:25 +0200 [thread overview]
Message-ID: <20130709095525.5158a0a5@endymion.delvare> (raw)
In-Reply-To: <51DBC058.2040904@nvidia.com>
On Tue, 9 Jul 2013 15:48:40 +0800, Wei Ni wrote:
> On 07/09/2013 02:21 PM, Thierry Reding wrote:
> > It should work out of the box. As a matter of fact the same chip is used
> > on Tamonten and the DTS files use "onnn,nct1008". That used to work. If
> > it no longer does then that's a regression.
>
> I synced the linux-next from:
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> and use the tag v3.10-rc7, but in the lm90.c it doesn't have DT support,
> such as "onnn,nct1008".
> I googled it and found there has patch:
> [PATCH] hwmon: (lm90) Add device tree support , which is in:
> http://lists.lm-sensors.org/pipermail/lm-sensors/2013-February/038099.html
> , but it didn't be merged into the linux-next.
It was not, because of the next reply in the same thread:
http://lists.lm-sensors.org/pipermail/lm-sensors/2013-February/038100.html
> which git repository and branch should I use ?
It is supposed to just work. What doesn't work for you exactly?
--
Jean Delvare
next prev parent reply other threads:[~2013-07-09 7:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 9:09 [PATCH 0/2] Enable lm90 in Tegra30 and Tegra114 Wei Ni
2013-07-04 9:09 ` [PATCH 1/2] ARM: dt: t30 cardhu: add dt entry for lm90 Wei Ni
2013-07-05 17:38 ` Stephen Warren
2013-07-08 7:35 ` Wei Ni
2013-07-08 7:50 ` [lm-sensors] " Jean Delvare
2013-07-08 9:36 ` Wei Ni
2013-07-08 13:14 ` Guenter Roeck
2013-07-09 6:21 ` Thierry Reding
2013-07-09 7:48 ` Wei Ni
2013-07-09 7:55 ` Jean Delvare [this message]
2013-07-09 8:58 ` Wei Ni
2013-07-08 13:12 ` Guenter Roeck
2013-07-04 9:09 ` [PATCH 2/2] ARM: dt: t114 dalmore: " Wei Ni
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=20130709095525.5158a0a5@endymion.delvare \
--to=khali@linux-fr.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox