linux-kernel - Re: [PATCH 1/3] ARM: imx6q: refactor some ldb related clocks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 20 Aug 2013 12:40:52 -0300
From:	Fabio Estevam <festevam@...il.com>
To:	Liu Ying <Ying.Liu@...escale.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 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
--
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/