[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 05 May 2017 20:34:16 +0800
From: Icenowy Zheng <icenowy@...c.io>
To: linux-arm-kernel@...ts.infradead.org,
Maxime Ripard <maxime.ripard@...e-electrons.com>
CC: devicetree <devicetree@...r.kernel.org>,
linux-kernel-owner@...r.kernel.org,
linux-sunxi <linux-sunxi@...glegroups.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
dri-devel <dri-devel@...ts.freedesktop.org>,
Chen-Yu Tsai <wens@...e.org>, Rob Herring <robh+dt@...nel.org>,
linux-clk <linux-clk@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [linux-sunxi] [PATCH v6 11/13] ARM: dts: sun8i: add DE2 nodes for V3s SoC
于 2017年5月5日 GMT+08:00 下午8:30:35, Maxime Ripard <maxime.ripard@...e-electrons.com> 写到:
>On Fri, May 05, 2017 at 04:53:43PM +0800, icenowy@...c.io wrote:
>> > > + de2_clocks: clock@...0000 {
>> > > + compatible =
>"allwinner,sun50i-h5-de2-clk";
>> >
>> > I am a bit skeptical about this. Since the V3S only has one mixer,
>do
>> > the clocks
>> > for the second one even exist?
>>
>> It's described in the de_clock.c in the BSP source code, and in
>hardware
>> these bits can be really set (although without clock output).
>>
>> So I use this compatible which has still the extra clocks.
>
>If it's not usable, then it shouldn't be in the code, it's basically
>dead code.
Thus should we have one more DE2 CCU compatible without mixer1
clocks for V3s?
Powered by blists - more mailing lists