From: Jyri Sarha <jsarha@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: dri-devel@lists.freedesktop.org, airlied@linux.ie,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
bcousson@baylibre.com, tony@atomide.com, tomi.valkeinen@ti.com,
detheridge@ti.com, moinejf@free.fr,
laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH RFC 3/6] drm/tilcdc: Add support for external compontised DRM encoder
Date: Fri, 6 Mar 2015 10:33:27 +0200 [thread overview]
Message-ID: <54F96657.10200@ti.com> (raw)
In-Reply-To: <20150302160135.GA29584@n2100.arm.linux.org.uk>
On 03/02/15 18:01, Russell King - ARM Linux wrote:
> On Thu, Feb 26, 2015 at 04:55:32PM +0200, Jyri Sarha wrote:
>> + ret = component_bind_all(dev->dev, dev);
>> + if (ret < 0) {
>> + dev_err(dev->dev, "Binding subcomponents failed: %d\n", ret);
>
> Do you need to print this? The component helper is already fairly
> verbose about what succeeds and fails.
>
Will remove.
>> +static const struct component_master_ops tilcdc_comp_ops = {
>> + .add_components = tilcdc_add_external_components,
>
> I'd much rather you used the new matching support rather than using the
> old .add_components. The new matching support is more efficient as you
> only have to scan DT once, rather than each time we try to probe. That
> will mean...
>
That is otherwise fine, but with the match code it not possible to
implement a master that may not have any components.
Would it be Ok to add a check that master->ops->add_components is
defined, before calling it in find_componets()
(drivers/base/component.c:120) and return 0 if it is not?
Best regards,
Jyri
>> @@ -613,12 +643,12 @@ static int tilcdc_pdev_probe(struct platform_device *pdev)
>> return -ENXIO;
>> }
>
> You need to build a struct component_match array here using
> component_match_add()...
>
>>
>> - return drm_platform_init(&tilcdc_driver, pdev);
>> + return component_master_add(&pdev->dev, &tilcdc_comp_ops);
>
> and then finally register the ops with component_master_add_with_match().
>
> Thanks.
>
next prev parent reply other threads:[~2015-03-06 8:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 14:55 [PATCH RFC 0/6] Use DRM component API in tilcdc to connect to tda998x Jyri Sarha
2015-02-26 14:55 ` [PATCH RFC 1/6] drm/tilcdc: Fix module unloading Jyri Sarha
2015-03-02 13:10 ` Tomi Valkeinen
2015-02-26 14:55 ` [PATCH RFC 2/6] drm/tilcdc: Remove tilcdc slave support for tda998x driver Jyri Sarha
2015-02-26 14:55 ` [PATCH RFC 3/6] drm/tilcdc: Add support for external compontised DRM encoder Jyri Sarha
2015-03-02 12:44 ` Tomi Valkeinen
2015-03-02 16:01 ` Russell King - ARM Linux
2015-03-06 8:33 ` Jyri Sarha [this message]
2015-03-06 9:58 ` Russell King - ARM Linux
2015-03-06 10:21 ` Jyri Sarha
2015-03-06 10:35 ` Russell King - ARM Linux
2015-02-26 14:55 ` [PATCH RFC 4/6] drm/tilcdc: Add DRM_TILCDC_INIT for "ti,tilcdc,slave" binding support Jyri Sarha
[not found] ` <6cf3243f87975ef349dead7af136870fa406ad6b.1424961754.git.jsarha-l0cyMroinI0@public.gmane.org>
2015-03-02 13:04 ` Tomi Valkeinen
[not found] ` <cover.1424961754.git.jsarha-l0cyMroinI0@public.gmane.org>
2015-02-26 14:55 ` [PATCH RFC 5/6] drm/tilcdc: Force building of DRM_TILCDC_INIT Jyri Sarha
2015-03-02 12:59 ` Tomi Valkeinen
2015-02-26 14:55 ` [PATCH RFC 6/6] ARM: dts: am335x-boneblack: Use new binding for HDMI Jyri Sarha
2015-03-02 12:28 ` Tomi Valkeinen
2015-03-02 16:06 ` Russell King - ARM Linux
2015-03-02 17:08 ` Tomi Valkeinen
2015-03-02 17:42 ` Russell King - ARM Linux
2015-03-03 8:35 ` Tomi Valkeinen
2015-03-02 11:34 ` [PATCH RFC 0/6] Use DRM component API in tilcdc to connect to tda998x 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=54F96657.10200@ti.com \
--to=jsarha@ti.com \
--cc=airlied@linux.ie \
--cc=bcousson@baylibre.com \
--cc=detheridge@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=moinejf@free.fr \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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.