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:	Thu, 10 Oct 2013 14:33:19 +0200
From:	Stephen GALLIMORE <stephen.gallimore@...com>
To:	Maxime COQUELIN <maxime.coquelin@...com>,
	Wolfram Sang <wsa@...-dreams.de>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>
Cc:	Stuart MENEFY <stuart.menefy@...com>,
	Lee Jones <lee.jones@...aro.org>,
	Gabriel FERNANDEZ <gabriel.fernandez@...com>,
	Srinivas KANDAGATLA <srinivas.kandagatla@...com>
Subject: RE: [PATCH v4 3/4] ARM: STi: Supply I2C configuration to STiH415 SoC


> -----Original Message-----
> From: Maxime COQUELIN [mailto:maxime.coquelin@...com]
> Sent: 08 October 2013 17:43
>.....
> +
> +		i2c@...40000 {
> +			compatible	= "st,comms-ssc-i2c";
> +			reg		= <0xfed40000 0x110>;
> +			interrupts	=  <GIC_SPI 187 IRQ_TYPE_EDGE_RISING>;

This should specify level (high) triggered, not edge triggered, for our
SoC integrations.

Note that level triggered is the default GIC setup and was therefore
what was being used when you specified "0" for the flags previously.

> +			clocks		= <&CLKS_ICN_REG_0>;
> +			clock-names	= "ssc";
> +			clock-frequency = <400000>;
> +			pinctrl-names	= "default";
> +			pinctrl-0	= <&pinctrl_i2c0_default>;
> +
> +			status		= "disabled";
> +		};

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ