From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
David Airlie <airlied@linux.ie>, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v4 2/3] drm: Add support for the LogiCVC display controller
Date: Fri, 3 Apr 2020 11:13:44 +0200 [thread overview]
Message-ID: <20200403091344.GA720146@aptenodytes> (raw)
In-Reply-To: <20200104192026.GA21210@ravnborg.org>
[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]
Hi Sam,
On Sat 04 Jan 20, 20:20, Sam Ravnborg wrote:
> Good looking driver. Well structured in a number of relevant files.
> A few comments in the following.
> Some parts I fail to follow - due to my lack of DRM knowledge.
> So all in all - only trivial comments.
Thanks for the review and the friendly feedback!
> With these fixed you can add:
> Acked-by: Sam Ravnborg <sam@ravnborg.org>
I'll take most of your suggestions in for the next version and there's just one
point where I disagree:
> > +struct logicvc_drm {
> > + const struct logicvc_drm_caps *caps;
> > + struct logicvc_drm_config config;
> > + struct drm_device *drm;
> Modern drm drivers are expected to embed drm_device.
> See example in drm_drv.c
Well, I see lots of modern drivers that use drm_dev_alloc, including vc4 that
I took as a reference.
My understanding is that embedding the struct is a recommendation but
drm_dev_alloc is still quite valid and that the choice is left open.
Quoting drm_drv.c:
* It is recommended that drivers embed &struct drm_device into their own device
* structure.
*
* Drivers that do not want to allocate their own device struct
* embedding &struct drm_device can call drm_dev_alloc() instead.
In my case, I like the fact that drm_dev_alloc correctly wraps drm_dev_init
and drmm_add_final_kfree (and I'd rather not add & all around unless I'm
obliged to ;)
Cheers,
Paul
--
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Rob Herring <robh+dt@kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v4 2/3] drm: Add support for the LogiCVC display controller
Date: Fri, 3 Apr 2020 11:13:44 +0200 [thread overview]
Message-ID: <20200403091344.GA720146@aptenodytes> (raw)
In-Reply-To: <20200104192026.GA21210@ravnborg.org>
[-- Attachment #1.1: Type: text/plain, Size: 1527 bytes --]
Hi Sam,
On Sat 04 Jan 20, 20:20, Sam Ravnborg wrote:
> Good looking driver. Well structured in a number of relevant files.
> A few comments in the following.
> Some parts I fail to follow - due to my lack of DRM knowledge.
> So all in all - only trivial comments.
Thanks for the review and the friendly feedback!
> With these fixed you can add:
> Acked-by: Sam Ravnborg <sam@ravnborg.org>
I'll take most of your suggestions in for the next version and there's just one
point where I disagree:
> > +struct logicvc_drm {
> > + const struct logicvc_drm_caps *caps;
> > + struct logicvc_drm_config config;
> > + struct drm_device *drm;
> Modern drm drivers are expected to embed drm_device.
> See example in drm_drv.c
Well, I see lots of modern drivers that use drm_dev_alloc, including vc4 that
I took as a reference.
My understanding is that embedding the struct is a recommendation but
drm_dev_alloc is still quite valid and that the choice is left open.
Quoting drm_drv.c:
* It is recommended that drivers embed &struct drm_device into their own device
* structure.
*
* Drivers that do not want to allocate their own device struct
* embedding &struct drm_device can call drm_dev_alloc() instead.
In my case, I like the fact that drm_dev_alloc correctly wraps drm_dev_init
and drmm_add_final_kfree (and I'd rather not add & all around unless I'm
obliged to ;)
Cheers,
Paul
--
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-04-03 9:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 15:06 [PATCH v4 0/3] drm: LogiCVC display controller support Paul Kocialkowski
2019-12-03 15:06 ` Paul Kocialkowski
2019-12-03 15:06 ` [PATCH v4 1/3] dt-bindings: display: Document the Xylon LogiCVC display controller Paul Kocialkowski
2019-12-03 15:06 ` Paul Kocialkowski
2020-01-03 22:44 ` Rob Herring
2020-01-03 22:44 ` Rob Herring
2019-12-03 15:06 ` [PATCH v4 2/3] drm: Add support for the " Paul Kocialkowski
2019-12-03 15:06 ` Paul Kocialkowski
2020-01-04 19:20 ` Sam Ravnborg
2020-01-04 19:20 ` Sam Ravnborg
2020-04-03 9:13 ` Paul Kocialkowski [this message]
2020-04-03 9:13 ` Paul Kocialkowski
2019-12-03 15:06 ` [PATCH v4 3/3] WIP: drm/logicvc: Add plane colorkey support Paul Kocialkowski
2019-12-03 15:06 ` Paul Kocialkowski
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=20200403091344.GA720146@aptenodytes \
--to=paul.kocialkowski@bootlin.com \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thomas.petazzoni@bootlin.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.