[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <532F63E7.8000708@gmail.com>
Date: Sun, 23 Mar 2014 23:44:55 +0100
From: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
To: Russell King - ARM Linux <linux@....linux.org.uk>
CC: Jean-Francois Moine <moinejf@...e.fr>, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] drm/i2c: tda998x: Change the compatible strings
On 03/23/2014 09:03 PM, Russell King - ARM Linux wrote:
> On Sun, Mar 23, 2014 at 07:12:05PM +0100, Sebastian Hesselbarth wrote:
>> On 03/23/2014 11:19 AM, Jean-Francois Moine wrote:
>>> On Fri, 21 Mar 2014 14:37:52 +0100
>>> Sebastian Hesselbarth <sebastian.hesselbarth@...il.com> wrote:
>>>>> Required properties;
>>>>> - - compatible: must be "nxp,tda998x"
>>>>> + - compatible: may be "nxp,tda9989", "nxp,tda19988" or "nxp,tda19989"
>>>>
>>>> There is a "DT is ABI" policy and although there is no mainline Linux
>>>> user of current compatible, the correct way would be to deprecate
>>>> "nxp,tda998x" and introduce new compatibles.
>>>
>>> Pratically, what is this way?
>>
>> Currently, there is no effective way to deprecate a binding or
>> compatible. You just add the one(s) that are more sensible and
>> you mark the old one as DEPRECATED by simply writing it in the
>> binding doc.
>>
>> The driver should support the old binding at least for a while.
>
> It doesn't need to - it's only been in development trees so far, and
> never been in a mainline full release. Until it does, the binding
> does not become stable.
Ok, I see. Thanks for the clarification. A note about it would
have been nice though. Anyway, sorry for the noise.
Sebastian
--
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