Hi,
On Tue, Oct 30, 2012 at 7:44 PM, Thomas Petazzoni
<thomas.petazzoni@xxxxxxxxxxxxxxxxxx> wrote:
> Dear Nobuhiro Iwamatsu,
>
> On Tue, 30 Oct 2012 19:39:41 +0900, Nobuhiro Iwamatsu wrote:
>> The Armada-XP SoC has the same I2C controller as mv64xxxi-i2c.
>> This validates to use mv64xxx in this SoC.
>>
>> Signed-off-by: Nobuhiro Iwamatsu <iwamatsu@xxxxxxxxxxx>
>> ---
>> drivers/i2c/busses/Kconfig | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
>> index 65dd599..ff53cf4 100644
>> --- a/drivers/i2c/busses/Kconfig
>> +++ b/drivers/i2c/busses/Kconfig
>> @@ -474,7 +474,7 @@ config I2C_MPC
>>
>> config I2C_MV64XXX
>> tristate "Marvell mv64xxx I2C Controller"
>> - depends on (MV64X60 || PLAT_ORION)
>> + depends on (MV64X60 || PLAT_ORION || MACH_ARMADA_370_XP)
>> help
>> If you say yes to this option, support will be included for the
>> built-in I2C interface on the Marvell 64xxx line of host bridges.
>
> This is not needed: ARCH_MVEBU already selects PLAT_ORION.
>
Oh, I see. Thanks!
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
