mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: icenowy@aosc.io
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: devicetree@vger.kernel.org, Chen-Yu Tsai <wens@csie.org>,
	linux-sunxi@googlegroups.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: sun8i: a33: add dts for Q8 tablets with different resolution
Date: Mon, 21 Aug 2017 16:44:30 +0800	[thread overview]
Message-ID: <4a0a72b4679db296a8e48512c41a2ce5@aosc.io> (raw)
In-Reply-To: <20170821084053.s4qmhlvgsmckmqgh@flea.lan>

在 2017-08-21 16:40,Maxime Ripard 写道:
> On Thu, Aug 17, 2017 at 03:49:26PM +0800, Icenowy Zheng wrote:
>> Q8 tablets with Allwinner A33 SoC now come with two kind of LCD, 
>> either
>> 800x480 or 1024x600.
>> 
>> In order for sun4i-drm to be able to choose correct LCD configuration,
>> two different device trees should be present, one for a resolution.
>> 
>> Add stub device trees for two resolutions.
>> 
>> As the sun4i-drm driver still has some problems to support the LCDs, 
>> the
>> real LCD device nodes are not added to the device tree files.
>> 
>> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
> 
> This should be an overlay, ideally applied by the bootloader.

I think this is not suitable for overlay.

The two kind of Q8 tablets are not compatible at all, and they
should both have a suitable device tree. The old DT without
resolution is only kept for backward compatibility.

> 
> Maxime
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2017-08-21  8:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17  7:49 Icenowy Zheng
2017-08-21  8:40 ` Maxime Ripard
2017-08-21  8:44   ` icenowy [this message]
2017-08-22 20:33     ` 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=4a0a72b4679db296a8e48512c41a2ce5@aosc.io \
    --to=icenowy@aosc.io \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=maxime.ripard@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

all inboxes | Powered by JetHome®