[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140724142918.GG28485@lunn.ch>
Date: Thu, 24 Jul 2014 16:29:18 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Jason Cooper <jason@...edaemon.net>
Cc: Benoit Masson <benoitm@...enite.com>, Andrew Lunn <andrew@...n.ch>,
Arnd Bergmann <arnd@...db.de>,
Gregory CLEMENT <gregory.clement@...e-electrons.com>,
Benoit Masson <yahoo@...enite.com>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Russell King <linux@....linux.org.uk>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Sebastian Hesselbarth <sebastian.hesselbarth@...glemail.com>
Subject: Re: [PATCH 2/2] ARM: mvebu: Added dts defintion for Lenovo Iomega
ix4-300d NAS
> The only outstanding point (Arnd?), is that I think it's ok to have the
> i2c...a0 compatible string in the dts files, but Andrew seems to think
> otherwise. Is that still true Andrew?
Hi Jason
I can live with i2c...a0 compatible string, but it has minor problems:
1) The binding Documentation says not to do it. So we are ignoring our
own documentation.
2) It seems likely that at some point the OEM will swap to B1 revision
SoCs. The i2c device then does not require this quirk, but we have
hard coded in the DT file that it is required. B1 revision would
work, but not optimally.
So i would prefer not to explicitly enable the quirk, but determine at
run time if the quirk is needed for the SoC revision it is running on.
Andrew
--
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