From: Andrew Lunn <andrew@lunn.ch>
To: Eduardo Valentin <eduardo.valentin@ti.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
linux ARM <linux-arm-kernel@lists.infradead.org>,
iwamatsu@nigauri.org, linux-pm@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
jgunthorpe@obsidianresearch.com,
Sebastian Hesselbarth <sebastian.hesselbarth@googlemail.com>,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: [PATCH 1/2] thermal: Add support for thermal sensor for Orion SoC
Date: Mon, 7 Jan 2013 11:16:55 +0100 [thread overview]
Message-ID: <20130107101655.GS3392@lunn.ch> (raw)
In-Reply-To: <50EA9E10.7080605@ti.com>
> OK. Please put me on Cc so I will keep the review.
>
> >We differentiate between the different SoCs by DT. Each has its own
> >.dtsi file and we will put the node into only those which have the
> >hardware.
>
> Ok. That I understand, but my question was more into the difference
> between 88F6282 and 88F6283. Do you need to differentiate those two?
Hi Eduardo
No, there is no need to differentiate between these. As far as the
temperature sensor goes, they are identical. I've been testing on a
88F6282 and Nobuhiro Iwamatsu on a 88F6283.
Andrew
next prev parent reply other threads:[~2013-01-07 10:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 11:03 [PATCH 0/2] Thermal sensor for Orion/Kirkwood Andrew Lunn
2012-12-14 11:03 ` [PATCH 1/2] thermal: Add support for thermal sensor for Orion SoC Andrew Lunn
2012-12-14 11:30 ` R, Durgadoss
2012-12-14 11:50 ` Andrew Lunn
2012-12-14 22:03 ` Nobuhiro Iwamatsu
2012-12-14 18:13 ` Jason Gunthorpe
2012-12-14 21:54 ` Nobuhiro Iwamatsu
2012-12-14 22:11 ` Andrew Lunn
2013-01-04 7:33 ` Zhang Rui
2013-01-04 8:15 ` Andrew Lunn
2013-01-04 9:40 ` Eduardo Valentin
2013-01-04 9:47 ` Eduardo Valentin
2013-01-04 15:35 ` Andrew Lunn
2013-01-07 10:06 ` Eduardo Valentin
2013-01-07 10:16 ` Andrew Lunn [this message]
2012-12-14 11:03 ` [PATCH 2/2] ARM: Kirkwood: Add support thermal sensor for 88F6282 and 88F6283 Andrew Lunn
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=20130107101655.GS3392@lunn.ch \
--to=andrew@lunn.ch \
--cc=eduardo.valentin@ti.com \
--cc=iwamatsu@nigauri.org \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=sebastian.hesselbarth@googlemail.com \
--cc=thomas.petazzoni@free-electrons.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).