[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <11675313-d92f-e562-0fd5-21339b5aa599@suse.de>
Date: Sun, 21 May 2017 16:19:39 +0200
From: Andreas Färber <afaerber@...e.de>
To: Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
Arend Van Spriel <arend.vanspriel@...adcom.com>
Cc: robh+dt@...nel.org, kvalo@...eaurora.org, mark.rutland@....com,
devicetree@...r.kernel.org, linux-wireless@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH 1/1] dt-binding: net: wireless: fix node name in the
BCM43xx example
Hi,
Am 16.05.2017 um 21:56 schrieb Martin Blumenstingl:
> On Tue, May 16, 2017 at 12:05 AM, Arend Van Spriel
> <arend.vanspriel@...adcom.com> wrote:
>> On 15-5-2017 22:13, Martin Blumenstingl wrote:
>>> The example in the BCM43xx documentation uses "brcmf" as node name.
>>> However, wireless devices should be named "wifi" instead. Fix this to
>>
>> Since when is that a rule. I never got the memo and the DTC did not ever
>> complain to me about the naming.
How do you expect it to? Maintain a blacklist of every device model
someone might use, including all typo variations?
> That being said I do not really care
>> and I suppose it is for the sake of consistency only.
> I'm not sure if it's actually a rule or (as you already noted) just
> for consistency. back when I added devicetree support to ath9k Rob
> pointed out that the node should be named "wifi" (instead of "ath9k"),
> see [0]
The general rule is that the node name should be the type of the device,
not duplicate its compatible string.
For consistency Rob was asking we use "wifi" as node name.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Powered by blists - more mailing lists