Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752116AbbKIQMV (ORCPT ); Mon, 9 Nov 2015 11:12:21 -0500 Received: from unicorn.mansr.com ([81.2.72.234]:34379 "EHLO unicorn.mansr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751749AbbKIQMU convert rfc822-to-8bit (ORCPT ); Mon, 9 Nov 2015 11:12:20 -0500 From: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= To: Mason Cc: Javier Martinez Canillas , Andrew Lunn , LKML , Linux ARM , Marc Zyngier , Jason Cooper , Thomas Gleixner , Ulf Hansson Subject: Re: Grafting old platform drivers onto a new DT kernel References: <563B3749.50701@free.fr> <20151105151559.GA16666@lunn.ch> <5640B877.4020108@free.fr> <5640C4BF.2010204@free.fr> Date: Mon, 09 Nov 2015 16:12:16 +0000 In-Reply-To: <5640C4BF.2010204@free.fr> (Mason's message of "Mon, 9 Nov 2015 17:07:27 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 977 Lines: 25 Mason writes: > 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. If the driver only needs an MMIO region and an IRQ, it is literally five lines of code. -- M?ns Rullg?rd mans@mansr.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/