linux-kernel - Re: [PATCH v2 1/6] mfd: TPS65910: Handle non-existent devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 25 Oct 2011 17:01:17 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Kyle Manna <kyle.manna@...l7.com>
Cc:	linux-kernel@...r.kernel.org, Samuel Ortiz <sameo@...ux.intel.com>,
	Jorge Eduardo Candelaria <jedu@...mlogic.co.uk>,
	Liam Girdwood <lrg@...com>
Subject: Re: [PATCH v2 1/6] mfd: TPS65910: Handle non-existent devices

On Tue, Oct 25, 2011 at 10:10:05AM -0500, Kyle Manna wrote:
> On 10/25/2011 02:14 AM, Mark Brown wrote:

> >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.

It seems like a more useful implementation would be to have the driver
read and display this revision number during boot, this will give you
the register readability check and also let us know the device revision
which might be useful for diagnostics.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/