[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <425858dc-59fe-2311-61ae-3b6dc77a2576@nxp.com>
Date: Fri, 7 Oct 2022 17:09:18 +0530
From: Manjunatha Venkatesh <manjunatha.venkatesh@....com>
To: Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Will Deacon <will@...nel.org>, Jens Axboe <axboe@...nel.dk>,
robh+dt@...nel.org
Cc: mb@...htnvm.io, ckeepax@...nsource.cirrus.com, arnd@...db.d,
mst@...hat.com, javier@...igon.com, mikelley@...rosoft.com,
jasowang@...hat.com, sunilmut@...rosoft.com,
bjorn.andersson@...aro.org, krzysztof.kozlowski+dt@...aro.org,
devicetree@...r.kernel.org, ashish.deshpande@....com,
rvmanjumce@...il.com
Subject: Re: [EXT] Re: [PATCH v5 1/2] dt-bindings: uwb: Device tree
information for Nxp SR1XX SOCs
On 9/14/2022 8:06 PM, Arnd Bergmann wrote:
> Caution: EXT Email
>
> On Wed, Sep 14, 2022, at 4:29 PM, Manjunatha Venkatesh wrote:
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - nxp,sr1xx
>> +
> You should not have wildcard names in the compatible string.
> Make this a specific model number without 'xx', and
> have the devices list their own name along with the oldest
> one they are compatible with.
>
> Arnd
This driver is common for both sr100 and sr150,so we have used sr1xx
naming convention or can we use name with highest version(sr150)?
Powered by blists - more mailing lists