linux-kernel - Re: [PATCH v5 1/6] mtd: nand: vf610_nfc: Freescale NFC for VF610, MPC5125 and others

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] [day] [month] [year] [list]

Message-ID: <BLU436-SMTP1380BAD5F776944D62A9148B8B80@phx.gbl>
Date:	Mon, 15 Jun 2015 10:29:17 -0400
From:	Bill Pringlemeir <bpringle@...patico.ca>
To:	Sebastian Andrzej Siewior <sebastian@...akpoint.cc>
CC:	Stefan Agner <stefan@...er.ch>, dwmw2@...radead.org,
	computersforpeace@...il.com, robh+dt@...nel.org,
	pawel.moll@....com, mark.rutland@....com,
	ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
	shawn.guo@...aro.org, kernel@...gutronix.de,
	boris.brezillon@...e-electrons.com, marb@...at.de,
	aaron@...tycactus.com, bpringlemeir@...il.com,
	linux-mtd@...ts.infradead.org, devicetree@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Bill Pringlemeir <bpringlemeir@...ps.com>
Subject: Re: [PATCH v5 1/6] mtd: nand: vf610_nfc: Freescale NFC for VF610, MPC5125 and others

On  9 Jun 2015, sebastian@...akpoint.cc wrote:

> On 2015-06-06 11:53:31 [+0200], Stefan Agner wrote:

>> +static const struct of_device_id vf610_nfc_dt_ids[] = {
>> +	{ .compatible = "fsl,vf610-nfc" },
>> +	{ .compatible = "fsl,mpc5125-nfc" },

> I advise against a "fsl,mpc5125-nfc" binding. First of all it is the
> same as the previous one. Second of all it was not tested at all on
> the SoC it suggests to work. Plus the chip select function has a
> comment hat it won't work on MPC5125. So it really makes no sense to
> add it here.

Someone has used a version of the driver on the PowerPC.  I don't have
access to his email address now.  Anyways, the chipselect code is
different on the PowerPC versions of the controller afair.  So if some
external code sets up the chipselect for a single chip, then things are
fine.

Both the PowerPC and ARM support DT/OF, but you can never actually run
either version as the code must be compiled for either assembler.  So I
am not quite sure that this was the correct way to go anyways...  So I
agree with your conclusion we can remove that binding.

Regards,
Bill.
--
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/