Thread (39 messages) read the whole thread 39 messages, 5 authors, 2017-12-02

[PATCH v2 11/18] drm/sun4i: Add A83T support

From: Maxime Ripard <hidden>
Date: 2017-11-30 15:33:15
Also in: dri-devel, linux-clk, lkml

On Tue, Nov 28, 2017 at 11:33:44PM +0100, Jernej ?krabec wrote:
Hi!

Dne torek, 28. november 2017 ob 23:00:14 CET je Maxime Ripard napisal(a):
quoted
On Tue, Nov 28, 2017 at 04:48:55PM +0100, Jernej ?krabec wrote:
quoted
quoted
On Mon, Nov 27, 2017 at 05:01:49PM +0100, Jernej ?krabec wrote:
quoted
Dne ponedeljek, 27. november 2017 ob 16:41:35 CET je Maxime Ripard
napisal(a):
quoted
quoted
quoted
Add support for the A83T display pipeline.

Reviewed-by: Chen-Yu Tsai <redacted>
Signed-off-by: Maxime Ripard <redacted>
---

 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.
That's unfortunate...
Can't we just add reg property for that?
No, reg is here specifically for the bus address, not for an index,
and in general, indices are poorly perceived and have been subject to
a lot of debate in the past. Hence why I'd really like to avoid any
solution looking like this. But I guess we don't really have the
choice either.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20171130/d6798306/attachment.sig>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help