From: Daniel Vetter <daniel@ffwll.ch>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Daniel Vetter <daniel@ffwll.ch>, Sam Ravnborg <sam@ravnborg.org>,
David Airlie <airlied@linux.ie>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Sean Paul <sean@poorly.run>,
od@zcrc.me, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Artur Rojek <contact@artur-rojek.eu>
Subject: Re: [PATCH v5 2/2] DRM: Add KMS driver for the Ingenic JZ47xx SoCs
Date: Fri, 21 Jun 2019 11:13:43 +0200 [thread overview]
Message-ID: <20190621091343.GA12905@phenom.ffwll.local> (raw)
In-Reply-To: <1561108050.1777.0@crapouillou.net>
On Fri, Jun 21, 2019 at 11:07:30AM +0200, Paul Cercueil wrote:
>
>
> Le ven. 21 juin 2019 à 11:04, Daniel Vetter <daniel@ffwll.ch> a écrit :
> > On Thu, Jun 20, 2019 at 04:15:59PM +0200, Paul Cercueil wrote:
> > >
> > >
> > > Le mer. 19 juin 2019 à 14:26, Sam Ravnborg <sam@ravnborg.org> a
> > > écrit :
> > > > Hi Paul.
> > > >
> > > > On Mon, Jun 03, 2019 at 05:23:31PM +0200, Paul Cercueil wrote:
> > > > > Add a KMS driver for the Ingenic JZ47xx family of SoCs.
> > > > > This driver is meant to replace the aging jz4740-fb driver.
> > > > >
> > > > > This driver does not make use of the simple pipe helper, for
> > > the
> > > > > reason
> > > > > that it will soon be updated to support more advanced features
> > > like
> > > > > multiple planes, IPU integration for colorspace conversion and
> > > > > up/down
> > > > > scaling, support for DSI displays, and TV-out and HDMI outputs.
> > > > >
> > > > > Signed-off-by: Paul Cercueil <paul@crapouillou.net>
> > > > > Tested-by: Artur Rojek <contact@artur-rojek.eu>
> > > > > ---
> > > > >
> > > > > Notes:
> > > > > v2: - Remove custom handling of panel. The panel is now
> > > > > discovered using
> > > > > the standard API.
> > > > > - Lots of small tweaks suggested by upstream
> > > > >
> > > > > v3: - Use devm_drm_dev_init()
> > > > > - Update compatible strings to -lcd instead of -drm
> > > > > - Add destroy() callbacks to plane and crtc
> > > > > - The ingenic,lcd-mode is now read from the bridge's DT
> > > node
> > > > >
> > > > > v4: Remove ingenic,lcd-mode property completely. The
> > > various
> > > > > modes are now
> > > > > deduced from the connector type, the pixel format or the
> > > bus
> > > > > flags.
> > > > >
> > > > > v5: - Fix framebuffer size incorrectly calculated for 24bpp
> > > > > framebuffers
> > > > > - Use 32bpp framebuffer instead of 16bpp, as it'll work
> > > with
> > > > > both
> > > > > 16-bit and 24-bit panel
> > > > > - Get rid of drm_format_plane_cpp() which has been dropped
> > > > > upstream
> > > > > - Avoid using drm_format_info->depth, which is deprecated.
> > > > In the drm world we include the revision notes in the changelog.
> > > > So I did this when I applied it to drm-misc-next.
> > > >
> > > > Fixed a few trivial checkpatch warnings about indent too.
> > > > There was a few too-long-lines warnings that I ignored. Fixing
> > > them
> > > > would have hurt readability.
> > >
> > > Thanks.
> > >
> > > > I assume you will maintain this driver onwards from now.
> > > > Please request drm-misc commit rights (see
> > > > https://www.freedesktop.org/wiki/AccountRequests/)
> > > > You will need a legacy SSH account.
> > >
> > > I requested an account here:
> > > https://gitlab.freedesktop.org/freedesktop/freedesktop/issues/162
> >
> > This 404s for me. Did you set the issue to private by any chance? Or
> > deleted already again?
> > -Daniel
>
> Sorry, yes, I set it to private. I thought I had to :(
Well I can't ack it if its private, so please change that. Also,
everything is public around here, or almost everything ...
-Daniel
>
> -Paul
>
>
> > >
> > > > And you should familiarize yourself with the maintainer-tools:
> > > > https://drm.pages.freedesktop.org/maintainer-tools/index.html
> > > >
> > > > For my use I use "dim update-branches; dim apply; dim push
> > > > So only a small subset i needed for simple use.
> > > >
> > > > Sam
> > >
> > >
> >
> > --
> > Daniel Vetter
> > Software Engineer, Intel Corporation
> > http://blog.ffwll.ch
>
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2019-06-21 9:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 15:23 [PATCH v5 1/2] dt-bindings: Add doc for the Ingenic JZ47xx LCD controller driver Paul Cercueil
2019-06-03 15:23 ` [PATCH v5 2/2] DRM: Add KMS driver for the Ingenic JZ47xx SoCs Paul Cercueil
2019-06-19 12:26 ` Sam Ravnborg
2019-06-20 14:15 ` Paul Cercueil
2019-06-21 9:04 ` Daniel Vetter
2019-06-21 9:07 ` Paul Cercueil
2019-06-21 9:13 ` Daniel Vetter [this message]
2019-06-21 9:17 ` Paul Cercueil
2019-06-11 21:55 ` [PATCH v5 1/2] dt-bindings: Add doc for the Ingenic JZ47xx LCD controller driver Rob Herring
2019-06-12 8:49 ` Paul Cercueil
2019-06-19 12:18 ` Sam Ravnborg
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=20190621091343.GA12905@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=contact@artur-rojek.eu \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=od@zcrc.me \
--cc=paul@crapouillou.net \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=sean@poorly.run \
/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