From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: Grafting old platform drivers onto a new DT kernel
Date: Mon, 9 Nov 2015 17:07:27 +0100 [thread overview]
Message-ID: <5640C4BF.2010204@free.fr> (raw)
In-Reply-To: <yw1xtwov5gh1.fsf@unicorn.mansr.com>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Mason <slash.tmp@free.fr>
To: Mans Rullgard <mans@mansr.com>
Cc: Javier Martinez Canillas <javier@dowhile0.org>,
Andrew Lunn <andrew@lunn.ch>, LKML <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Jason Cooper <jason@lakedaemon.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: Grafting old platform drivers onto a new DT kernel
Date: Mon, 9 Nov 2015 17:07:27 +0100 [thread overview]
Message-ID: <5640C4BF.2010204@free.fr> (raw)
In-Reply-To: <yw1xtwov5gh1.fsf@unicorn.mansr.com>
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.
next prev parent reply other threads:[~2015-11-09 16:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 11:02 Grafting old platform drivers onto a new DT kernel Mason
2015-11-05 11:02 ` Mason
2015-11-05 15:15 ` Andrew Lunn
2015-11-05 15:15 ` Andrew Lunn
2015-11-05 15:42 ` Javier Martinez Canillas
2015-11-05 15:42 ` Javier Martinez Canillas
2015-11-09 15:15 ` Mason
2015-11-09 15:15 ` Mason
2015-11-09 15:36 ` Marc Zyngier
2015-11-09 15:36 ` Marc Zyngier
2016-02-03 15:33 ` Sebastian Frias
2015-11-09 15:40 ` Måns Rullgård
2015-11-09 15:40 ` Måns Rullgård
2015-11-09 16:07 ` Mason [this message]
2015-11-09 16:07 ` Mason
2015-11-09 16:12 ` Måns Rullgård
2015-11-09 16:12 ` Måns Rullgård
2015-11-09 17:03 ` Mason
2015-11-09 17:03 ` Mason
2015-11-09 17:13 ` Måns Rullgård
2015-11-09 17:13 ` Måns Rullgård
2015-11-10 12:44 ` Mason
2015-11-10 12:44 ` Mason
2015-11-10 12:56 ` Arnd Bergmann
2015-11-10 12:56 ` Arnd Bergmann
2015-11-09 16:26 ` Russell King - ARM Linux
2015-11-09 16:26 ` Russell King - ARM Linux
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=5640C4BF.2010204@free.fr \
--to=slash.tmp@free.fr \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.