From: moinejf@free.fr (Jean-Francois Moine)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 0/2] drivers/base: simplify simple DT-based components
Date: Sun, 9 Feb 2014 10:22:19 +0100 [thread overview]
Message-ID: <20140209102219.3ab40b5e@armhf> (raw)
In-Reply-To: <20140207202351.GH26684@n2100.arm.linux.org.uk>
On Fri, 7 Feb 2014 20:23:51 +0000
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> Here's my changes to the TDA998x driver to add support for the component
> helper. The TDA998x driver retains support for the old way so that
> drivers can be transitioned. For any one DRM "card" the transition to
I rewrote the tda998x as a simple encoder+connector (i.e. not a
slave_encoder) with your component helper, and the code is much clearer
and simpler: the DRM driver has nothing to do except to know that the
tda998x is a component and to set the possible_crtcs.
AFAIK, only the tilcdc drm driver is using the tda998x as a
slave_encoder. It does a (encoder+connector) conversion to
(slave_encoder). Then, in your changes in the TDA998x, you do a
(slave_encoder) translation to (encoder+connector).
This seems rather complicated!
I think it would be easier to use your component helper and rewrite
(remove?) tilcdc_slave.c.
> And yes, I'm thinking that maybe moving compare_of() into the component
> support so that drivers can share this generic function may be a good
> idea.
This function exists already in drivers/of/platform.c as
of_dev_node_match(). It just needs to be exported.
--
Ken ar c'henta? | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
WARNING: multiple messages have this Message-ID (diff)
From: Jean-Francois Moine <moinejf@free.fr>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Rob Clark <robdclark@gmail.com>
Cc: devel@driverdev.osuosl.org, Daniel Vetter <daniel@ffwll.ch>,
Takashi Iwai <tiwai@suse.de>,
dri-devel@lists.freedesktop.org,
Sascha Hauer <kernel@pengutronix.de>,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH RFC 0/2] drivers/base: simplify simple DT-based components
Date: Sun, 9 Feb 2014 10:22:19 +0100 [thread overview]
Message-ID: <20140209102219.3ab40b5e@armhf> (raw)
In-Reply-To: <20140207202351.GH26684@n2100.arm.linux.org.uk>
On Fri, 7 Feb 2014 20:23:51 +0000
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> Here's my changes to the TDA998x driver to add support for the component
> helper. The TDA998x driver retains support for the old way so that
> drivers can be transitioned. For any one DRM "card" the transition to
I rewrote the tda998x as a simple encoder+connector (i.e. not a
slave_encoder) with your component helper, and the code is much clearer
and simpler: the DRM driver has nothing to do except to know that the
tda998x is a component and to set the possible_crtcs.
AFAIK, only the tilcdc drm driver is using the tda998x as a
slave_encoder. It does a (encoder+connector) conversion to
(slave_encoder). Then, in your changes in the TDA998x, you do a
(slave_encoder) translation to (encoder+connector).
This seems rather complicated!
I think it would be easier to use your component helper and rewrite
(remove?) tilcdc_slave.c.
> And yes, I'm thinking that maybe moving compare_of() into the component
> support so that drivers can share this generic function may be a good
> idea.
This function exists already in drivers/of/platform.c as
of_dev_node_match(). It just needs to be exported.
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jean-Francois Moine <moinejf@free.fr>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Rob Clark <robdclark@gmail.com>
Cc: devel@driverdev.osuosl.org, dri-devel@lists.freedesktop.org,
Takashi Iwai <tiwai@suse.de>,
Sascha Hauer <kernel@pengutronix.de>,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH RFC 0/2] drivers/base: simplify simple DT-based components
Date: Sun, 9 Feb 2014 10:22:19 +0100 [thread overview]
Message-ID: <20140209102219.3ab40b5e@armhf> (raw)
In-Reply-To: <20140207202351.GH26684@n2100.arm.linux.org.uk>
On Fri, 7 Feb 2014 20:23:51 +0000
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> Here's my changes to the TDA998x driver to add support for the component
> helper. The TDA998x driver retains support for the old way so that
> drivers can be transitioned. For any one DRM "card" the transition to
I rewrote the tda998x as a simple encoder+connector (i.e. not a
slave_encoder) with your component helper, and the code is much clearer
and simpler: the DRM driver has nothing to do except to know that the
tda998x is a component and to set the possible_crtcs.
AFAIK, only the tilcdc drm driver is using the tda998x as a
slave_encoder. It does a (encoder+connector) conversion to
(slave_encoder). Then, in your changes in the TDA998x, you do a
(slave_encoder) translation to (encoder+connector).
This seems rather complicated!
I think it would be easier to use your component helper and rewrite
(remove?) tilcdc_slave.c.
> And yes, I'm thinking that maybe moving compare_of() into the component
> support so that drivers can share this generic function may be a good
> idea.
This function exists already in drivers/of/platform.c as
of_dev_node_match(). It just needs to be exported.
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2014-02-09 9:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 17:11 [PATCH RFC 0/2] drivers/base: simplify simple DT-based components Jean-Francois Moine
2014-02-07 17:11 ` Jean-Francois Moine
2014-02-07 17:11 ` Jean-Francois Moine
2014-02-07 15:55 ` [PATCH RFC 1/2] drivers/base: permit base components to omit the bind/unbind ops Jean-Francois Moine
2014-02-07 15:55 ` Jean-Francois Moine
2014-02-07 15:55 ` Jean-Francois Moine
2014-02-07 17:34 ` Russell King - ARM Linux
2014-02-07 17:34 ` Russell King - ARM Linux
2014-02-07 17:34 ` Russell King - ARM Linux
2014-02-07 16:53 ` [PATCH RFC 2/2] drivers/base: declare phandle DT nodes as components Jean-Francois Moine
2014-02-07 16:53 ` Jean-Francois Moine
2014-02-07 17:43 ` Russell King - ARM Linux
2014-02-07 17:43 ` Russell King - ARM Linux
2014-02-07 17:43 ` Russell King - ARM Linux
2014-02-07 17:33 ` [PATCH RFC 0/2] drivers/base: simplify simple DT-based components Russell King - ARM Linux
2014-02-07 17:33 ` Russell King - ARM Linux
2014-02-07 17:33 ` Russell King - ARM Linux
2014-02-07 18:42 ` Jean-Francois Moine
2014-02-07 18:42 ` Jean-Francois Moine
2014-02-07 18:59 ` Russell King - ARM Linux
2014-02-07 18:59 ` Russell King - ARM Linux
2014-02-07 18:59 ` Russell King - ARM Linux
2014-02-08 0:23 ` Russell King - ARM Linux
2014-02-08 0:23 ` Russell King - ARM Linux
2014-02-08 0:23 ` Russell King - ARM Linux
2014-02-07 20:23 ` Russell King - ARM Linux
2014-02-07 20:23 ` Russell King - ARM Linux
2014-02-07 20:23 ` Russell King - ARM Linux
2014-02-09 9:22 ` Jean-Francois Moine [this message]
2014-02-09 9:22 ` Jean-Francois Moine
2014-02-09 9:22 ` Jean-Francois Moine
2014-02-09 10:04 ` Russell King - ARM Linux
2014-02-09 10:04 ` Russell King - ARM Linux
2014-02-09 10:04 ` 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=20140209102219.3ab40b5e@armhf \
--to=moinejf@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.