linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jagan Teki <jagan@amarulasolutions.com>
To: Chen-Yu Tsai <wens@csie.org>, Icenowy Zheng <icenowy@aosc.io>
Cc: Rob Herring <robh+dt@kernel.org>,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	devicetree <devicetree@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	linux-sunxi <linux-sunxi@googlegroups.com>
Subject: Re: [PATCH 3/7] bus: add bus driver for accessing Allwinner A64 DE2
Date: Thu, 19 Apr 2018 12:05:36 +0530	[thread overview]
Message-ID: <CAMty3ZBAbMzRaSwWat+irbxALcOCuEHzsL6yOQJ4AkC9N8Ugxg@mail.gmail.com> (raw)
In-Reply-To: <CAMty3ZAfBZSc9f5mRxSaYzW6W1JkVkJ7+swMAm3Gg_EFWUkULw@mail.gmail.com>

On Sat, Apr 14, 2018 at 4:16 PM, Jagan Teki <jagan@amarulasolutions.com> wrote:
> On Sat, Apr 14, 2018 at 4:00 PM, Chen-Yu Tsai <wens@csie.org> wrote:
>> On Sat, Apr 14, 2018 at 6:25 PM, Jagan Teki <jagan@amarulasolutions.com> wrote:
>>> On Fri, Mar 16, 2018 at 11:23 PM, Icenowy Zheng <icenowy@aosc.io> wrote:
>>>> The "Display Engine 2.0" (usually called DE2) on the Allwinner A64 SoC
>>>> is different from the ones on other Allwinner SoCs. It requires a SRAM
>>>> region to be claimed, otherwise all DE2 subblocks won't be accessible.
>>>>
>>>> Add a bus driver for the Allwinner A64 DE2 part which claims the SRAM
>>>> region when probing.
>>>
>>> Along with this bus driver, we also need
>>> drivers/gpu/drm/sun4i/sun4i_drv.c which can usually drive the
>>> pipelines like mixer0 and 1 are the cases for A64?
>>
>> I imagine that's the next part to be sent out, after the hardware
>> representation in the device tree has been decided on.
>
> Yeah, this hardware representation along with separate bus driver
> going like in another direction especially if we add pipelines support
> to it, may be we can add sram stuff to platdata of existinf
> sun4i_drv.c

Look like SRAM init during sun4i_drv is unable to claim or map the
memory? do we have any suggestion on adding 'allwinner,pipelines' ? is
it ok to add one more de which is compatible with sun4i_drv.c like
this.

de: display-engine {
                compatible = "allwinner,sun8i-a64-display-engine",
"allwinner,sun8i-h3-display-engine";
                allwinner,pipelines = <&mixer0>;
};

Jagan.

-- 
Jagan Teki
Senior Linux Kernel Engineer | Amarula Solutions
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

  reply	other threads:[~2018-04-19  6:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 17:53 [PATCH 0/7] Allwinner A64 DE2 CCU support with dedicated DE2 bus driver Icenowy Zheng
2018-03-16 17:53 ` [PATCH 1/7] dt-bindings: add compatible string for the A64 DE2 CCU Icenowy Zheng
2018-03-19 22:00   ` Stephen Boyd
2018-03-26 22:22   ` Rob Herring
2018-03-16 17:53 ` [PATCH 2/7] dt-bindings: add binding for the Allwinner A64 DE2 bus Icenowy Zheng
2018-03-20 18:46   ` Maxime Ripard
2018-03-21  2:18     ` Icenowy Zheng
2018-03-21 17:13       ` [linux-sunxi] " Jernej Škrabec
2018-03-22  6:08         ` Icenowy Zheng
2018-03-26 22:22           ` Rob Herring
2018-03-26 23:31             ` Icenowy Zheng
2018-03-27  8:11               ` Maxime Ripard
2018-03-16 17:53 ` [PATCH 3/7] bus: add bus driver for accessing Allwinner A64 DE2 Icenowy Zheng
2018-04-14 10:25   ` Jagan Teki
2018-04-14 10:30     ` Chen-Yu Tsai
2018-04-14 10:46       ` Jagan Teki
2018-04-19  6:35         ` Jagan Teki [this message]
2018-03-16 17:53 ` [PATCH 4/7] clk: sunxi-ng: add A64 compatible string Icenowy Zheng
2018-03-16 17:53 ` [PATCH 5/7] arm64: allwinner: a64: add DE2 CCU related device tree nodes Icenowy Zheng
2018-03-20 18:47   ` Maxime Ripard
2018-03-16 17:53 ` [PATCH 6/7] arm64: allwinner: a64: add simplefb for A64 SoC Icenowy Zheng
2018-03-16 17:53 ` [PATCH 7/7] arm64: allwinner: a64: add HDMI regulator to all DTs' simplefb_hdmi Icenowy Zheng

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=CAMty3ZBAbMzRaSwWat+irbxALcOCuEHzsL6yOQJ4AkC9N8Ugxg@mail.gmail.com \
    --to=jagan@amarulasolutions.com \
    --cc=devicetree@vger.kernel.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=linux-sunxi@googlegroups.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=robh+dt@kernel.org \
    --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).