From: Arnd Bergmann <arnd@arndb.de>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2 1/3] video: clps711x: Add new Cirrus Logic CLPS711X framebuffer driver
Date: Fri, 23 May 2014 14:14:00 +0000 [thread overview]
Message-ID: <4580210.sUvVkKflZg@wuerfel> (raw)
In-Reply-To: <1397285583-15187-1-git-send-email-shc_work@mail.ru>
On Friday 23 May 2014 17:10:35 Tomi Valkeinen wrote:
> On 23/05/14 16:13, Alexander Shiyan wrote:
>
> >> Would it be possible to add the new driver along the old driver, and use
> >> the new driver only for the boards you have, and for boards for which
> >> it's clear the the old driver is not working? This could be merged for 3.16.
> >
> > At this time yes, we can. But since I plan to add multiplatform support
> > for this SOC, this seems not possible.
> > I can try to make multiplatform support optional, then it could be done...
>
> Hmm, why is that not possible with multiplatform support? What do you
> mean with multiplatform support here?
We are migrating all ARM platforms to allow building them into a single
kernel. However, that means that device drivers cannot access platform
specific header files any more and have to get hardware information from
DT or through platform data. The existing driver however uses mach/hardware.h.
Arnd
next prev parent reply other threads:[~2014-05-23 14:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 6:53 [PATCH v2 1/3] video: clps711x: Add new Cirrus Logic CLPS711X framebuffer driver Alexander Shiyan
2014-04-24 5:03 ` Alexander Shiyan
2014-04-24 7:57 ` Tomi Valkeinen
2014-04-24 8:39 ` Tomi Valkeinen
2014-04-30 11:14 ` Tomi Valkeinen
2014-05-05 5:06 ` Olof Johansson
2014-05-07 9:40 ` Tomi Valkeinen
2014-05-08 10:14 ` Tomi Valkeinen
2014-05-16 22:56 ` Olof Johansson
2014-05-23 12:31 ` Tomi Valkeinen
2014-05-23 12:43 ` Tomi Valkeinen
2014-05-23 13:48 ` Arnd Bergmann
2014-05-23 14:10 ` Tomi Valkeinen
2014-05-23 14:14 ` Arnd Bergmann [this message]
2014-05-23 14:26 ` Tomi Valkeinen
2014-05-23 14:32 ` Tomi Valkeinen
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=4580210.sUvVkKflZg@wuerfel \
--to=arnd@arndb.de \
--cc=linux-fbdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox