From: Thierry Reding <thierry.reding@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Russell King <rmk+kernel@arm.linux.org.uk>,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [RFC 0/5] drm/tegra: Convert to master/component framework
Date: Thu, 1 May 2014 00:01:55 +0200 [thread overview]
Message-ID: <20140430220154.GA23950@ulmo> (raw)
In-Reply-To: <1398179373-29966-1-git-send-email-thierry.reding@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3422 bytes --]
On Tue, Apr 22, 2014 at 05:09:28PM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Hi,
>
> This series converts the Tegra DRM driver to the master/component
> framework. The length of the series and the list of people in Cc is
> mostly due to the fact that Tegra has some special requirements as
> opposed to other drivers and therefore requires some changes outside
> of DRM.
>
> Patches 1 and 2 make some changes to the master/component framework
> which are necessary to convert Tegra DRM to use it. Note that since I'm
> looking for early review I haven't converted any of the existing users
> since I'm not sure if these are acceptable changes.
>
> Patch 3 adds a new interface framework that supplements the master/
> component framework and can be used in situations where there is no
> struct device * that a driver can bind to.
>
> A new function is introduced in patch 4 which can be used to get rid of
> the DRM bus infrastructure in individual drivers. It should be able to
> replace the requirement of having a drm_bus for all USB and platform
> DRM drivers. For backwards-compatibility with legacy PCI drivers some-
> thing different will probably be needed.
>
> Finally, patch 5 converts the Tegra DRM driver over to using the master/
> component framework using the above four patches.
>
> Each patch has a somewhat more elaborate description of why it is needed
> or what problem it solves. The patchset applies on top of linux-next
> with Daniel's DRM cleanup series applied.
>
> I welcome any questions or comments you might have.
>
> Thierry
>
> Thierry Reding (5):
> drivers/base: Allow multiple masters per device
> drivers/base: Allow driver-data to be attached to a master
> drivers/base: Add interface framework
> drm: Introduce drm_set_unique()
> drm/tegra: Convert to master/component framework
Ping. Anyone?
Thierry
> drivers/base/Makefile | 2 +-
> drivers/base/component.c | 31 ++-
> drivers/base/interface.c | 186 ++++++++++++++
> drivers/gpu/drm/drm_ioctl.c | 37 ++-
> drivers/gpu/drm/drm_stub.c | 1 +
> drivers/gpu/drm/tegra/Makefile | 1 -
> drivers/gpu/drm/tegra/bus.c | 64 -----
> drivers/gpu/drm/tegra/dc.c | 58 ++---
> drivers/gpu/drm/tegra/drm.c | 171 +++++++++----
> drivers/gpu/drm/tegra/drm.h | 27 +-
> drivers/gpu/drm/tegra/dsi.c | 144 +++++------
> drivers/gpu/drm/tegra/gr2d.c | 78 +++---
> drivers/gpu/drm/tegra/gr3d.c | 77 +++---
> drivers/gpu/drm/tegra/hdmi.c | 69 ++---
> drivers/gpu/drm/tegra/sor.c | 71 ++----
> drivers/gpu/host1x/Makefile | 1 -
> drivers/gpu/host1x/bus.c | 553 -----------------------------------------
> drivers/gpu/host1x/bus.h | 29 ---
> drivers/gpu/host1x/dev.c | 21 +-
> drivers/gpu/host1x/dev.h | 7 +-
> include/drm/drmP.h | 3 +
> include/linux/component.h | 20 +-
> include/linux/host1x.h | 64 +----
> include/linux/interface.h | 40 +++
> 24 files changed, 625 insertions(+), 1130 deletions(-)
> create mode 100644 drivers/base/interface.c
> delete mode 100644 drivers/gpu/drm/tegra/bus.c
> delete mode 100644 drivers/gpu/host1x/bus.c
> delete mode 100644 drivers/gpu/host1x/bus.h
> create mode 100644 include/linux/interface.h
>
> --
> 1.9.2
>
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-04-30 22:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 15:09 [RFC 0/5] drm/tegra: Convert to master/component framework Thierry Reding
2014-04-22 15:09 ` [RFC 1/5] drivers/base: Allow multiple masters per device Thierry Reding
2014-04-22 15:09 ` [RFC 2/5] drivers/base: Allow driver-data to be attached to a master Thierry Reding
2014-04-22 15:09 ` [RFC 3/5] drivers/base: Add interface framework Thierry Reding
2014-04-22 15:09 ` [RFC 4/5] drm: Introduce drm_set_unique() Thierry Reding
2014-04-22 15:48 ` Daniel Vetter
2014-04-23 7:17 ` Thierry Reding
2014-04-23 8:40 ` Daniel Vetter
2014-04-23 10:48 ` David Herrmann
2014-04-23 13:37 ` Thierry Reding
2014-04-22 15:09 ` [RFC 5/5] drm/tegra: Convert to master/component framework Thierry Reding
2014-04-30 22:01 ` Thierry Reding [this message]
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=20140430220154.GA23950@ulmo \
--to=thierry.reding@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).