Hello Mark,
On 21/08/15 20:25, ext Mark Rutland wrote:
>> Now as "i2c-davinci" driver has special handling for Keystone it's time to
>> switch
>> > the device tree to use new "compatible" property.
>> >
>> > Signed-off-by: Alexander Sverdlin <alexander.sverd...@nokia.com>
>> > ---
>> > arch/arm/boot/dts/keystone.dtsi | 6 +++---
>> > 1 files changed, 3 insertions(+), 3 deletions(-)
>> >
>> > diff --git a/arch/arm/boot/dts/keystone.dtsi
>> > b/arch/arm/boot/dts/keystone.dtsi
>> > index 72816d6..a846597 100644
>> > --- a/arch/arm/boot/dts/keystone.dtsi
>> > +++ b/arch/arm/boot/dts/keystone.dtsi
>> > @@ -106,7 +106,7 @@
>> > };
>> >
>> > i2c0: i2c@2530000 {
>> > - compatible = "ti,davinci-i2c";
>> > + compatible = "ti,keystone-i2c";
>>From what I understand of the previous patch, this is effectively an
> optimisation, and things worked to some extent with the "ti,davinci-i2c"
> string.
Indeed this is an optimization.
> So could you leave that as a fallback, i.e. have:
>
> compatible = "ti,keystone-i2c", "ti,davinci-i2c";
And I have no problem leaving fallback compatible.
> That way an old kernel still functions with this DT, which among other things
> makes debugging and bisecting far easier.
I've just thought, that we do not care about backwards-compatibility for the DT
in
the kernel tree, because one always have the correct one linked to the kernel.
And this evaluation module never has it flashed to some persistent storage
outside
of kernel image, so version mismatch is impossible.
> Or are things actually broken with the "ti,davinci-i2c" string?
No, not in this case.
--
Best regards,
Alexander Sverdlin.
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
