devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: devicetree <devicetree@vger.kernel.org>,
	Chen-Yu Tsai <wens@csie.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/1] ARM: dts: sunxi: Fix simplefb not working in 4.7-rc1
Date: Mon, 20 Jun 2016 22:56:59 +0200	[thread overview]
Message-ID: <d239fb49-61a1-a574-8fa8-205b6a51a595@redhat.com> (raw)
In-Reply-To: <20160620074610.GH26668@lukather>

Hi,

On 20-06-16 09:46, Maxime Ripard wrote:
> On Mon, Jun 13, 2016 at 10:30:57AM +0200, Hans de Goede wrote:
>> Hi,
>>
>> On 13-06-16 10:01, Maxime Ripard wrote:
>>> On Thu, Jun 09, 2016 at 12:47:36PM +0200, Hans de Goede wrote:
>>>> Hi,
>>>>
>>>> On 09-06-16 09:46, Maxime Ripard wrote:
>>>>> Hi Hans,
>>>>>
>>>>> On Sat, Jun 04, 2016 at 08:05:23PM +0200, Hans de Goede wrote:
>>>>>> Hi Maxime,
>>>>>>
>>>>>> While testing 4.7-rc1 / linux-sunxi/sunxi-next on a A10s I noticed that
>>>>>> hdmi out is no longer working (screen goes black when the kernel turns
>>>>>> of unused clocks).
>>>>>>
>>>>>> This is caused by the dtsi for sun4i / sun5i / sun7i based boards now
>>>>>> listing pll3, without pll3 being added to the clocks list for the
>>>>>> simplefb nodes.
>>>>>
>>>>> Why not do just that then? It's more appropriate for a fix imho.
>>>>
>>>> You mean just for sun5i-a10s, or for all of sun4i / sun5i-a10s and
>>>> sun7i ?
>>>>
>>>> For sun4i and sun7i things are already fixed in next:
>>>>
>>>> https://git.kernel.org/cgit/linux/kernel/git/mripard/linux.git/commit/?id=5a7f2310cc847a73852e70bc720a61ca9bf986a6
>>>> https://git.kernel.org/cgit/linux/kernel/git/mripard/linux.git/commit/?id=c79255ca4d7b67cce4eac4dd532e097ce49f3679
>>>>
>>>> It seems best to use those fixes, rather then come up with a separate
>>>> fix for 4.7.
>>>>
>>>> My patch for fixing sun5i-a10s is inline with the 2 above patches,
>>>> which seems best, rather then doing something special for just sun5i-a10s.
>>>
>>> Well, you are doing something special for just the A10s: the patches
>>> quoted above just add a bunch of clocks and add the handles to the
>>> list of clocks managed by simplefb.
>>>
>>> For the A10s, you also declare the whole display engine block without
>>> anyone having tested that it was actually working.
>>
>> A10s is the same SoC as A13 / R8, just in a different package / with
>> different pins routed to the outside and it features a parallel LCD
>> interface just like the A13 / R8. We've had this confirmed by
>> Allwinner multiple times now, A13 / A10s / R8 literary are the same
>> chip, there simply is no way the displayblock on the A10s somehow
>> is magically different.
>>
>> Given all this, clearly having this identical displayblock in the
>> shared sun5i.dtsi is the right thing to do.
>
> Maybe, but this is not a patch for an 4.7-rc* release, but for the
> next merge window.

Ok, I'll send out a patch with the simple fix for 4.7 for sun4i / sun5i-a10s / sun7i
then.

Regards,

Hans

      reply	other threads:[~2016-06-20 20:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-04 18:05 [PATCH 0/1] ARM: dts: sunxi: Fix simplefb not working in 4.7-rc1 Hans de Goede
     [not found] ` <1465063524-4925-1-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-06-04 18:05   ` [PATCH] ARM: dts: sun5i: Move display blocks to sun5i.dtsi Hans de Goede
     [not found]     ` <1465063524-4925-2-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-06-08 15:28       ` Peter Korsgaard
2016-06-09  7:46   ` [PATCH 0/1] ARM: dts: sunxi: Fix simplefb not working in 4.7-rc1 Maxime Ripard
2016-06-09 10:47     ` Hans de Goede
     [not found]       ` <21258fc0-0250-951b-2ee7-d022fb3c09ac-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-06-13  8:01         ` Maxime Ripard
2016-06-13  8:30           ` Hans de Goede
     [not found]             ` <1a9a0d76-5bbf-4b79-abee-1c9dd0436567-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-06-20  7:46               ` Maxime Ripard
2016-06-20 20:56                 ` Hans de Goede [this message]

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=d239fb49-61a1-a574-8fa8-205b6a51a595@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).