From: Kyle Manna <kyle.manna@fuel7.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org,
Samuel Ortiz <sameo@linux.intel.com>,
Jorge Eduardo Candelaria <jedu@slimlogic.co.uk>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH v2 1/6] mfd: TPS65910: Handle non-existent devices
Date: Tue, 25 Oct 2011 10:10:05 -0500 [thread overview]
Message-ID: <4EA6D14D.6060800@fuel7.com> (raw)
In-Reply-To: <20111025071417.GE2919@opensource.wolfsonmicro.com>
On 10/25/2011 02:14 AM, Mark Brown wrote:
> On Mon, Oct 24, 2011 at 12:05:59PM -0500, Kyle Manna wrote:
>> Attempt to read the first register of the device, if there is no
>> device return -ENODEV
> Can you check for a known value in any of the registers?
Unfortunately on this chip there aren't any identification or constant
test registers. The only register close is the JTAGVERNUM_REG and
that's will change across silicon revisions.
- Kyle
next prev parent reply other threads:[~2011-10-25 15:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 17:05 [PATCH v2 0/6] mfd: TPS65910: Bug fixes and enhancements Kyle Manna
2011-10-24 17:05 ` [PATCH v2 1/6] mfd: TPS65910: Handle non-existent devices Kyle Manna
2011-10-25 7:14 ` Mark Brown
2011-10-25 15:10 ` Kyle Manna [this message]
2011-10-25 16:01 ` Mark Brown
2011-10-25 16:20 ` Kyle Manna
2011-10-26 15:00 ` Mark Brown
2011-10-24 17:06 ` [PATCH v2 2/6] mfd: TPS65910: Add I2C slave address macros Kyle Manna
2011-10-24 17:06 ` [PATCH v2 3/6] mfd: TPS65910: Fix typo that clobbers genirq Kyle Manna
2011-10-24 17:06 ` [PATCH v2 4/6] mfd: TPS65910: Move linux/gpio.h include to header Kyle Manna
2011-10-24 17:06 ` [PATCH v2 5/6] mfd: TPS65910: Move regulator defs " Kyle Manna
2011-10-25 7:23 ` Mark Brown
2011-10-24 17:06 ` [PATCH v2 6/6] mfd: TPS65910: Create an array for reg init data Kyle Manna
2011-10-25 7:24 ` Mark Brown
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=4EA6D14D.6060800@fuel7.com \
--to=kyle.manna@fuel7.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jedu@slimlogic.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=sameo@linux.intel.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).