From: "Jernej Škrabec" <jernej.skrabec@siol.net>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
David Airlie <airlied@linux.ie>, Chen-Yu Tsai <wens@csie.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
plaes@plaes.org, icenowy@aosc.io,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Subject: Re: [PATCH v2 11/18] drm/sun4i: Add A83T support
Date: Tue, 28 Nov 2017 23:33:44 +0100 [thread overview]
Message-ID: <1722782.9j9JEoLEfc@jernej-laptop> (raw)
In-Reply-To: <20171128220014.w35rcliusubfdvoe@flea.home>
Hi!
Dne torek, 28. november 2017 ob 23:00:14 CET je Maxime Ripard napisal(a):
> On Tue, Nov 28, 2017 at 04:48:55PM +0100, Jernej Škrabec wrote:
> > > On Mon, Nov 27, 2017 at 05:01:49PM +0100, Jernej Škrabec wrote:
> > > > Dne ponedeljek, 27. november 2017 ob 16:41:35 CET je Maxime Ripard
> >
> > napisal(a):
> > > > > Add support for the A83T display pipeline.
> > > > >
> > > > > Reviewed-by: Chen-Yu Tsai <wens@csie.org>
> > > > > Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> > > > > ---
> > > > >
> > > > > Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 3
> > > > > +++
> > > > > drivers/gpu/drm/sun4i/sun4i_drv.c | 2
> > > > > ++
> > > > > drivers/gpu/drm/sun4i/sun4i_tcon.c | 5
> > > > > +++++
> > > > > drivers/gpu/drm/sun4i/sun8i_mixer.c | 4
> > > > > ++++
> > > > > 4 files changed, 14 insertions(+)
> > > > >
> > > > > diff --git
> > > > > a/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt
> > > > > b/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt
> > > > > index
> > > > > d4259a4f5171..d6b52e5c48c0 100644
> > > > > --- a/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt
> > > > > +++ b/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt
> > > > >
> > > > > @@ -93,6 +93,7 @@ Required properties:
> > > > > * allwinner,sun6i-a31s-tcon
> > > > > * allwinner,sun7i-a20-tcon
> > > > > * allwinner,sun8i-a33-tcon
> > > > >
> > > > > + * allwinner,sun8i-a83t-tcon-lcd
> > > > >
> > > > > * allwinner,sun8i-v3s-tcon
> > > > >
> > > > > - reg: base address and size of memory-mapped region
> > > > > - interrupts: interrupt associated to this IP
> > > > >
> > > > > @@ -224,6 +225,7 @@ supported.
> > > > >
> > > > > Required properties:
> > > > > - compatible: value must be one of:
> > > > > + * allwinner,sun8i-a83t-de2-mixer
> > > >
> > > > What will be the name of the second mixer, once support for HDMI is
> > > > added?
> > > > Should we start directly with 0 and 1 postfix ?
> > >
> > > What are the differences exactly without the two mixers?
> >
> > Mixer properties:
> > - mixer index (0 or 1), important for determining CCSC base (see my
> > patches)
> Is that the only thing we need to determine?
For now, mixer index is important only for determining CCSC base in conjuction
with VEP capability. Obviously, I can't exclude that there is some other case
where that mixer index is needed.
Can't we just add reg property for that?
>
> > - number of VI planes (usually 1)
>
> Usually or always?
V3s mixer has 2 VI channels and others have 1.
(Channel is better term, since is used throughout BSP code)
>
> > - number of UI planes (usually 1 or 3)
>
> Same question.
For now, most SoCs (I didn't check all) have 3 UI channels on first mixer and 1
UI channel on second mixer. Except V3s, which have only one mixer with 1 UI
channel.
>
> > - writeback support (yes/no)
> > - scale line buffer length (2048 or 4096)
> > - smart backligth support (yes/no)
> >
> > channel properties (for both, VI and UI):
> > - scaler support (yes/no, usually yes)
Again, V3s is exception here. Scaler is not supported on UI channel, but other
SoCs have scalers on all channels.
Disclaimer: I didn't check DE2 capabilities of all SoCs, only few populars.
Best regards,
Jernej
> > - overlay count (seems to be always 4)
> > - VEP support (yes/no)
> >
> > Those are properties found in BSP de_feat.c, so I guess that's enough to
> > make any kind of decision in the code.
> >
> > Usually, but we can't count on that, first mixer has 1 VI and 3 UI planes
> > and second mixer has 1 VI and 1 UI plane.
>
> Right. So that would be easy to support using a property as well. The
> only difference would be the CSC base.
>
> Maxime
>
> --
> Maxime Ripard, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
next prev parent reply other threads:[~2017-11-28 22:33 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 15:41 [PATCH v2 00/18] drm/sun4i: Add A83t LVDS support Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 01/18] dt-bindings: panel: lvds: Document power-supply property Maxime Ripard
2017-11-28 17:48 ` Rob Herring
2017-11-30 15:30 ` Maxime Ripard
2017-11-30 19:57 ` Rob Herring
2017-11-27 15:41 ` [PATCH v2 02/18] drm/panel: lvds: Add support for the " Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 03/18] dt-bindings: display: sun4i-drm: Add LVDS properties Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 04/18] drm/sun4i: Fix error path handling Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 05/18] drm/sun4i: Force the mixer rate at 150MHz Maxime Ripard
2017-11-27 16:07 ` Jernej Škrabec
2017-11-28 8:58 ` Maxime Ripard
2017-11-28 21:56 ` Jernej Škrabec
2017-11-29 15:55 ` Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 06/18] drm/sun4i: Rename layers to UI planes Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 07/18] drm/sun4i: sun8i: Rework the UI channels code Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 08/18] drm/sun4i: Reorder and document DE2 mixer registers Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 09/18] drm/sun4i: Create minimal multipliers and dividers Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 10/18] drm/sun4i: Add LVDS support Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 11/18] drm/sun4i: Add A83T support Maxime Ripard
2017-11-27 16:01 ` Jernej Škrabec
2017-11-28 9:02 ` Maxime Ripard
2017-11-28 11:50 ` Icenowy Zheng
2017-11-28 15:46 ` Maxime Ripard
2017-11-28 15:48 ` Jernej Škrabec
2017-11-28 22:00 ` Maxime Ripard
2017-11-28 22:33 ` Jernej Škrabec [this message]
2017-11-30 15:33 ` Maxime Ripard
2017-12-02 21:58 ` Jernej Škrabec
2017-11-27 16:19 ` Chen-Yu Tsai
2017-11-28 8:59 ` Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 12/18] " Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 13/18] ARM: dts: sun8i: a83t: Add display pipeline Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 14/18] ARM: dts: sun8i: a83t: Enable the PWM Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 15/18] ARM: dts: sun8i: a83t: Add LVDS pins group Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 16/18] ARM: dts: sun8i: a83t: Add the PWM pin group Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 17/18] ARM: dts: sun8i: a711: Reinstate the PMIC compatible Maxime Ripard
2017-11-27 15:41 ` [PATCH v2 18/18] ARM: dts: sun8i: a711: Enable the LCD Maxime Ripard
2017-11-27 16:20 ` [PATCH v2 00/18] drm/sun4i: Add A83t LVDS support Jernej Škrabec
2017-11-28 15:46 ` Maxime Ripard
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=1722782.9j9JEoLEfc@jernej-laptop \
--to=jernej.skrabec@siol.net \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=icenowy@aosc.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=plaes@plaes.org \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=wens@csie.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).