From: "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com>
To: ext Kevin Hilman <khilman@deeprootsystems.com>
Cc: Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] OMAP3 PM export chip IDCODE, Production ID and Die ID
Date: Wed, 14 Oct 2009 12:44:07 +0300 [thread overview]
Message-ID: <20091014094407.GA7471@codecarver.research.nokia.com> (raw)
In-Reply-To: <636c5030910131251p14057abdobab3ba5bfb0d67f2@mail.gmail.com>
On Tue, Oct 13, 2009 at 09:51:30PM +0200, ext Kevin Hilman wrote:
> On Tue, Oct 13, 2009 at 12:48 PM, Tony Lindgren <tony@atomide.com> wrote:
> > * Kevin Hilman <khilman@deeprootsystems.com> [091013 12:09]:
> >> "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com> writes:
> >>
> >> > From: De-Schrijver Peter (Nokia-D/Helsinki) <Peter.De-Schrijver@nokia.com>
> >> >
> >> > This patch exports the OMAP3 IDCODE, Production ID and Die ID to userspace via
> >> > sysfs. This can be used to track down silicon specific issues. The info is
> >> > exported via sysfs because it should be possible to include this in corematic
> >> > dumps.
> >> >
> >> > Signed-off-by: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com>
> >>
> >> Please export these via debugfs.
> >
> > I don't think we want to export unique chip identifiers by default.
> >
>
> Right, which is why I suggested using debugfs, which is something that
> probably wouldn't be enabled/exported on default production kernels.
>
Which is why I do not want it in debugfs as we log this info in
crash reports on devices which might not have debugfs enabled.
Cheers,
Peter.
--
goa is a state of mind
next prev parent reply other threads:[~2009-10-14 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 14:51 [PATCH] OMAP3 PM export chip IDCODE, Production ID and Die ID Peter 'p2' De Schrijver
2009-10-12 15:04 ` Felipe Contreras
2009-10-13 18:45 ` Kevin Hilman
2009-10-13 19:48 ` Tony Lindgren
2009-10-13 19:51 ` Kevin Hilman
2009-10-14 9:44 ` Peter 'p2' De Schrijver [this message]
2010-01-18 11:46 ` Eduardo Valentin
2010-01-18 16:05 ` Kevin Hilman
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=20091014094407.GA7471@codecarver.research.nokia.com \
--to=peter.de-schrijver@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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