From: Thierry Reding <thierry.reding@avionic-design.de>
To: Rob Clark <robdclark@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
dri-devel@lists.freedesktop.org
Subject: Re: thoughts on requiring multi-arch support for arm drm drivers?
Date: Mon, 21 Jan 2013 08:17:35 +0100 [thread overview]
Message-ID: <20130121071735.GC15508@avionic-0098.adnet.avionic-design.de> (raw)
In-Reply-To: <CAF6AEGsSEtpJNKgHpZsUM9aadxYfHV7BhjfS86q0SH5ZXYaZ3w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1839 bytes --]
On Sun, Jan 20, 2013 at 09:08:34AM -0600, Rob Clark wrote:
> One thing I've run into in the past when trying to make changes in drm
> core, and Daniel Vetter has mentioned the same, is that it is a bit of
> a pain to compile test things for the arm drivers that do not support
> CONFIG_ARCH_MULTIPLATFORM. I went through a while back and fixed up
> the low hanging fruit (basically the drivers that just needed a
> Kconfig change). But, IIRC some of the backlight related code in
> shmob had some non-trivial plat dependencies. And I think when tegra
> came in, it introduced some non-trivial plat dependencies.
I've talked to Stephen about this a few days ago and his (tentative)
plan is to support ARCH_MULTIPLATFORM in 3.9. I'm not sure if that's
soon enough for you. I think the one remaining platform dependency is
the tegra_periph_reset_{assert,deassert}() which should be gone with the
common clock framework changes which should go into 3.9. Stephen has
other work-in-progress patches for the rest, so I think chances are
actually pretty good to get this ready for 3.9.
> What do others think about requiring multiarch or no arch dependencies
> for new drivers, and cleaning up existing drivers. Even if it is at
> reduced functionality (like maybe #ifdef CONFIG_ARCH_SHMOBILE for some
> of the backlight code in shmob) or doesn't even work but is just for
> the purpose of being able to compile test the rest of the code?
I imagine that on Tegra we could add dummy implementations for the reset
functions, which should allow it to build it for non-Tegra. However, I
don't think it's really worth the churn to do this now just to remove
them again in 3.9. The general direction would seem to be to require new
platforms to be multi-platform from the start, so any new drivers should
not cause the same pain anyway.
Thierry
[-- Attachment #1.2: Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-01-21 7:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 15:08 thoughts on requiring multi-arch support for arm drm drivers? Rob Clark
2013-01-20 15:42 ` Daniel Vetter
2013-01-20 15:42 ` Daniel Vetter
2013-01-21 7:28 ` Thierry Reding
2013-01-21 7:17 ` Thierry Reding [this message]
2013-01-21 13:57 ` Rob Clark
2013-01-21 15:47 ` Laurent Pinchart
2013-01-21 15:54 ` Rob Clark
2013-01-23 1:29 ` Laurent Pinchart
2013-01-23 1:42 ` Rob Clark
2013-01-23 7:39 ` Sascha Hauer
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=20130121071735.GC15508@avionic-0098.adnet.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=robdclark@gmail.com \
/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.