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:	Fri, 07 Jun 2013 13:22:58 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Benoit Cousson <b-cousson@...com>
CC:	J Keerthy <j-keerthy@...com>, devicetree-discuss@...ts.ozlabs.org,
	linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
	ldewangan@...dia.com, grant.likely@...retlab.ca,
	swarren@...dia.com, sameo@...ux.intel.com, gg@...mlogic.co.uk,
	lee.jones@...aro.org
Subject: Re: [PATCH] ARM: dts: add dtsi for palmas

On 06/07/2013 06:27 AM, Benoit Cousson wrote:
> Hi Keerthy,
> 
> On 06/07/2013 01:28 PM, J Keerthy wrote:
>> Adds palmas mfd and palmas regulator nodes. This is
>> based on the patch series:
>>
>> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg89957.html
>>
>> The device tree nodes are based on:
>> https://lkml.org/lkml/2013/6/6/25
...
>> diff --git a/arch/arm/boot/dts/palmas.dtsi b/arch/arm/boot/dts/palmas.dtsi
...
>> +&palmas {
>> +	compatible = "ti,palmas";
>> +	interrupt-controller;
>> +	#interrupt-cells = <2>;
> 
> The I2C address should be there as well. We used to put it in the board
> file, but this is really an I2C device specific information and not
> board specific in that case.

I thought the I2C address was variable depending on OTP settings, and
hence the I2C address is board-specific; depending on which variant of
the PMIC was stuffed onto the board?

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