On Tue, Jan 07, 2014 at 05:35:03PM +0100, Gregory CLEMENT wrote:
> +static struct property i2c_offload_broken = {
> + .name = "offload-broken",
> +};
> +
> +static void __init i2c_quirk(void)
> +{
> + struct device_node *np;
> + u32 dev, rev;
> +
> + /*
> + * Only revisons more recent than A0 support the offload
> + * mechanism. We can exit only if we are sure that we can
> + * get the SoC revision and it is more recent than A0.
> + */
> + if (mvebu_get_soc_id(&rev, &dev) == 0 && dev > MV78XX0_A0_REV)
> + return;
> +
> + for_each_compatible_node(np, NULL, "marvell,mv78230-i2c")
> + of_add_property(np, &i2c_offload_broken);
I like this approach.
However, when I first read this I thought it should be a -a0 specific
compatible string, not a 'offload-broken' property - any idea what the
DT consensus is here? I've seen both approach in use ..
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
