[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5214401D.8010402@freescale.com>
Date: Wed, 21 Aug 2013 12:20:45 +0800
From: Liu Ying <Ying.Liu@...escale.com>
To: Fabio Estevam <festevam@...il.com>
CC: Sascha Hauer <kernel@...gutronix.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
DRI mailing list <dri-devel@...ts.freedesktop.org>,
Shawn Guo <shawn.guo@...aro.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 1/3] ARM: imx6q: refactor some ldb related clocks
On 08/20/2013 11:40 PM, Fabio Estevam wrote:
> On Tue, Aug 20, 2013 at 5:38 AM, Liu Ying <Ying.Liu@...escale.com> wrote:
>
>> diff --git a/Documentation/devicetree/bindings/clock/imx6q-clock.txt b/Documentation/devicetree/bindings/clock/imx6q-clock.txt
>> index 5a90a72..90e923e 100644
>> --- a/Documentation/devicetree/bindings/clock/imx6q-clock.txt
>> +++ b/Documentation/devicetree/bindings/clock/imx6q-clock.txt
>> @@ -89,8 +89,6 @@ clocks and IDs.
>> gpu3d_shader 74
>> ipu1_podf 75
>> ipu2_podf 76
>> - ldb_di0_podf 77
>> - ldb_di1_podf 78
>> ipu1_di0_pre 79
>> ipu1_di1_pre 80
>> ipu2_di0_pre 81
>
> This causes a 'hole' in the clock numbering scheme: 74, 75, 76, 79, 80, etc
>
I find there is a 'hole' in Documentation/devicetree/bindings/clock/imx5-clock.txt as well.
The 'hole' was taken by tve_di(26) clock before.
Is this more acceptable?
ldb_di0_podf_unused 77
ldb_di1_podf_unused 78
Liu Ying
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists