From: Thierry Reding <thierry.reding@gmail.com>
To: Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: linux-tegra@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
Russell King <rmk+kernel@arm.linux.org.uk>
Subject: Re: [PATCH v2 5/7] drm/tegra: Convert to master/component framework
Date: Mon, 19 May 2014 17:25:40 +0200 [thread overview]
Message-ID: <20140519152539.GA30978@ulmo> (raw)
In-Reply-To: <CAH9NwWfF_rMWqPRzr7sPFkwwME1ZXG8=Np3NHDEib1MDm1tgWA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1341 bytes --]
On Mon, May 19, 2014 at 10:56:08AM +0200, Christian Gmeiner wrote:
> 2014-05-13 17:30 GMT+02:00 Thierry Reding <thierry.reding@gmail.com>:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > Instead of the current implementation, reuse the recently introduced
> > master/component framework, which is equivalent in most regards. One
> > issue is that there is no device to bind the DRM driver to. In order
> > to still allow the driver to be probed, expose an interface from the
> > host1x device and provide an interface driver to bind to that.
> >
> > The interface driver then registers (or removes) the master that will be
> > used to instantiate and bind the DRM driver. Since the drm_host1x bus
> > implementation is now gone the dummy device instantiated by it can no
> > longer be used as the parent for the DRM device. However since the
> > parent device doesn't need to be modified, the host1x parent device that
> > exposes the interface can be used instead.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
>
> Is there a git tree somewhere to have a look at? I am interested in the usage
> of the master/component framework.
I've pushed my latest working branches to gitorious[0]. staging/work is
the branch that has everything.
Thierry
[0]: https://gitorious.org/thierryreding/linux
[-- 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
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Russell King <rmk+kernel@arm.linux.org.uk>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 5/7] drm/tegra: Convert to master/component framework
Date: Mon, 19 May 2014 17:25:40 +0200 [thread overview]
Message-ID: <20140519152539.GA30978@ulmo> (raw)
In-Reply-To: <CAH9NwWfF_rMWqPRzr7sPFkwwME1ZXG8=Np3NHDEib1MDm1tgWA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]
On Mon, May 19, 2014 at 10:56:08AM +0200, Christian Gmeiner wrote:
> 2014-05-13 17:30 GMT+02:00 Thierry Reding <thierry.reding@gmail.com>:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > Instead of the current implementation, reuse the recently introduced
> > master/component framework, which is equivalent in most regards. One
> > issue is that there is no device to bind the DRM driver to. In order
> > to still allow the driver to be probed, expose an interface from the
> > host1x device and provide an interface driver to bind to that.
> >
> > The interface driver then registers (or removes) the master that will be
> > used to instantiate and bind the DRM driver. Since the drm_host1x bus
> > implementation is now gone the dummy device instantiated by it can no
> > longer be used as the parent for the DRM device. However since the
> > parent device doesn't need to be modified, the host1x parent device that
> > exposes the interface can be used instead.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
>
> Is there a git tree somewhere to have a look at? I am interested in the usage
> of the master/component framework.
I've pushed my latest working branches to gitorious[0]. staging/work is
the branch that has everything.
Thierry
[0]: https://gitorious.org/thierryreding/linux
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-19 15:25 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 15:30 [PATCH v2 0/7] drm/tegra: Convert to master/component framework Thierry Reding
2014-05-13 15:30 ` Thierry Reding
2014-05-13 15:30 ` [PATCH v2 1/7] drm: Introduce drm_set_unique() Thierry Reding
2014-05-13 15:30 ` Thierry Reding
2014-05-13 15:46 ` David Herrmann
2014-05-13 15:46 ` David Herrmann
2014-05-13 15:30 ` [PATCH v2 2/7] drivers/base: Allow driver-data to be attached to a master Thierry Reding
2014-05-13 15:30 ` Thierry Reding
2014-05-13 15:30 ` [PATCH v2 3/7] drivers/base: Allow multiple masters per device Thierry Reding
2014-05-13 15:30 ` Thierry Reding
2014-05-13 15:30 ` [PATCH v2 4/7] drivers/base: Add interface framework Thierry Reding
2014-05-13 15:30 ` Thierry Reding
2014-05-13 17:57 ` Daniel Vetter
2014-05-13 17:57 ` Daniel Vetter
[not found] ` <20140513175713.GS3908-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2014-05-13 21:31 ` Thierry Reding
2014-05-13 21:31 ` Thierry Reding
2014-05-14 14:34 ` Daniel Vetter
2014-05-14 14:34 ` Daniel Vetter
2014-05-14 15:13 ` Thierry Reding
2014-05-14 15:13 ` Thierry Reding
2014-05-14 0:32 ` Greg Kroah-Hartman
2014-05-14 14:37 ` Daniel Vetter
2014-05-14 14:37 ` Daniel Vetter
2014-05-14 17:22 ` Greg Kroah-Hartman
[not found] ` <20140514003215.GA21520-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2014-05-15 8:53 ` Thierry Reding
2014-05-15 8:53 ` Thierry Reding
2014-05-20 9:27 ` Andrzej Hajda
2014-05-13 15:30 ` [PATCH v2 5/7] drm/tegra: Convert to master/component framework Thierry Reding
2014-05-13 15:30 ` Thierry Reding
[not found] ` <1399995050-28435-6-git-send-email-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-05-19 8:56 ` Christian Gmeiner
2014-05-19 8:56 ` Christian Gmeiner
2014-05-19 15:25 ` Thierry Reding [this message]
2014-05-19 15:25 ` Thierry Reding
2014-05-13 15:30 ` [PATCH v2 6/7] drm: Add device registration documentation Thierry Reding
2014-05-13 15:30 ` Thierry Reding
2014-05-13 17:59 ` Daniel Vetter
2014-05-13 17:59 ` Daniel Vetter
2014-05-13 15:30 ` [PATCH v2 7/7] drm: Document how to register devices without struct drm_bus Thierry Reding
2014-05-13 15:30 ` Thierry Reding
2014-05-13 15:55 ` David Herrmann
2014-05-13 15:55 ` David Herrmann
2014-05-22 9:56 ` [PATCH v2 0/7] drm/tegra: Convert to master/component framework Thierry Reding
2014-05-22 9:56 ` Thierry Reding
2014-05-23 11:03 ` Greg Kroah-Hartman
2014-05-23 11:03 ` Greg Kroah-Hartman
2014-05-25 11:45 ` Thierry Reding
2014-05-25 11:45 ` Thierry Reding
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=20140519152539.GA30978@ulmo \
--to=thierry.reding@gmail.com \
--cc=christian.gmeiner@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 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.