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:	Wed, 25 May 2016 11:11:05 -0500
From:	Nishanth Menon <nm@...com>
To:	Ravikumar Kattekola <rk@...com>, <paul@...an.com>,
	<tony@...mide.com>, <linux@...linux.org.uk>, <robh+dt@...nel.org>,
	<pawel.moll@....com>, <mark.rutland@....com>,
	<ijc+devicetree@...lion.org.uk>, <galak@...eaurora.org>,
	<linux-omap@...r.kernel.org>, <devicetree@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] dts: dra7: Add device tree node for i2c6

On 05/25/2016 07:53 AM, Ravikumar Kattekola wrote:
> DRA72x devices have an extra i2c controller instance - i2c6
> Adding device description for the same.
> 
> Reference : DRA72x_SR1.0 TRM [ SPRUHP2Q ]
> 
> Signed-off-by: Ravikumar Kattekola <rk@...com>
> ---
>  arch/arm/boot/dts/dra7.dtsi | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
> index 3a8f397..84729a1 100644
> --- a/arch/arm/boot/dts/dra7.dtsi
> +++ b/arch/arm/boot/dts/dra7.dtsi
> @@ -27,6 +27,7 @@
>  		i2c2 = &i2c3;
>  		i2c3 = &i2c4;
>  		i2c4 = &i2c5;
> +		i2c5 = &i2c6;
>  		serial0 = &uart1;
>  		serial1 = &uart2;
>  		serial2 = &uart3;
> @@ -929,6 +930,16 @@
>  			status = "disabled";
>  		};
>  
> +		i2c6: i2c@...58000 {
> +			compatible = "ti,omap4-i2c";
> +			reg = <0x48458000 0x100>;
> +			interrupts = <GIC_SPI 402 IRQ_TYPE_LEVEL_HIGH>;
> +			#address-cells = <1>;
> +			#size-cells = <0>;
> +			ti,hwmods = "i2c6";
> +			status = "disabled";
> +		};
> +
>  		mmc1: mmc@...9c000 {
>  			compatible = "ti,omap4-hsmmc";
>  			reg = <0x4809c000 0x400>;
> 
NAK again for the same reasoning.

-- 
Regards,
Nishanth Menon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ