linux-kernel - Re: Grafting old platform drivers onto a new DT kernel

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]

Message-ID: <5640C4BF.2010204@free.fr>
Date:	Mon, 9 Nov 2015 17:07:27 +0100
From:	Mason <slash.tmp@...e.fr>
To:	Mans Rullgard <mans@...sr.com>
Cc:	Javier Martinez Canillas <javier@...hile0.org>,
	Andrew Lunn <andrew@...n.ch>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux ARM <linux-arm-kernel@...ts.infradead.org>,
	Marc Zyngier <marc.zyngier@....com>,
	Jason Cooper <jason@...edaemon.net>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ulf Hansson <ulf.hansson@...aro.org>
Subject: Re: Grafting old platform drivers onto a new DT kernel

On 09/11/2015 16:40, Måns Rullgård wrote:

> The simplest solution for you is probably to add a quick and dirty DT
> binding to the old driver.  If it doesn't use any driver-specific
> platform data struct, you only need to set .of_match_table in the
> struct platform_driver.  If there is a platform data struct, you'll also
> need to write some code to populate it from DT properties.  It shouldn't
> take more than a few minutes per driver in most cases.

I'll try that approach, although I fear that "a few minutes per driver"
is an optimistic assessment.

> To get those drivers accepted upstream will obviously take a bit more
> work.

AKA "rewrite from scratch" :-)

Regards.

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