From: daniel@ffwll.ch (Daniel Vetter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] drm: Cleanup probe function for component based masters.
Date: Tue, 20 Oct 2015 12:02:33 +0200 [thread overview]
Message-ID: <20151020100233.GW13786@phenom.ffwll.local> (raw)
In-Reply-To: <1445332995-11212-1-git-send-email-Liviu.Dudau@arm.com>
On Tue, Oct 20, 2015 at 10:23:11AM +0100, Liviu Dudau wrote:
> Changelog:
> v4: Fixed a bug where the wrong pointer was sent to component_match_add() and
> component_master_add_with_match() in the armada_drv.c file that was flagged
> by kbuild test robot. Dropped the RFC tag and added Acked-bys received from
> Russell King.
> v3: Removed the call to dma_set_coherent_mask() from the generic
> drm_of_component_probe(). Also changes to shorten lines over 80 chars long.
> v2: Rebased the patchset on top of drm-next rather than Linus' latest -rc
>
> A few drivers in drivers/gpu/drm are component-enabled and use quite similar
> code sequences to probe for their encoder slaves at the remote end of the ports.
> Move the code into a "generic" function and remove it from the drivers.
>
> The end results is that drivers get a reference count fix (imx), more thorough
> error checking (imx again) plus a decrease in the overall count of LoC.
>
> I'm looking for comments and testing of the patchset (only compile tested from my
> end as I don't have access to all the devices touched by the changes). My main
> interest is in finding out if -EINVAL is the correct code to return if
> dev->of_node == NULL (handy now, as it is different from the other possible error
> codes and used in armada to trigger old platform_data support. Also looking for
> thoughts on the correctness of the patch and if it possible to co-opt more drivers
> into using the function.
Merged all four to drm-misc, thanks.
-Daniel
>
> Best regards,
> Liviu
>
> Liviu Dudau (4):
> drm: Introduce generic probe function for component based masters.
> drm/imx: Convert the probe function to the generic drm_of_component_probe()
> drm/rockchip: Convert the probe function to the generic drm_of_component_probe()
> drm/armada: Convert the probe function to the generic drm_of_component_probe()
>
> drivers/gpu/drm/armada/armada_drv.c | 68 +++++++---------------
> drivers/gpu/drm/drm_of.c | 88 +++++++++++++++++++++++++++++
> drivers/gpu/drm/imx/imx-drm-core.c | 55 ++----------------
> drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 81 ++------------------------
> include/drm/drm_of.h | 13 +++++
> 5 files changed, 130 insertions(+), 175 deletions(-)
>
> --
> 2.6.0
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2015-10-20 10:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 9:23 [PATCH v4 0/4] drm: Cleanup probe function for component based masters Liviu Dudau
2015-10-20 9:23 ` [PATCH v4 1/4] drm: Introduce generic " Liviu Dudau
2015-10-20 10:00 ` Emil Velikov
2015-10-20 10:09 ` Russell King - ARM Linux
2015-10-20 10:18 ` Liviu Dudau
2015-10-20 9:23 ` [PATCH v4 2/4] drm/imx: Convert the probe function to the generic drm_of_component_probe() Liviu Dudau
2015-10-20 9:23 ` [PATCH v4 3/4] drm/rockchip: " Liviu Dudau
2015-10-20 9:23 ` [PATCH v4 4/4] drm/armada: " Liviu Dudau
2015-10-20 10:02 ` Daniel Vetter [this message]
2015-10-20 10:18 ` [PATCH v4 0/4] drm: Cleanup probe function for component based masters Liviu Dudau
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=20151020100233.GW13786@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--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 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).