Hi, On 06/17/2014 09:49 AM, Arend van Spriel wrote: > On 17-06-14 08:32, Hans de Goede wrote: >> Hi, >> >> On 06/16/2014 10:53 PM, Florian Fainelli wrote: >>> 2014-06-16 10:56 GMT-07:00 Hans de Goede <hdegoede@xxxxxxxxxx>: >>>> From: Arend van Spriel <arend@xxxxxxxxxxxx> >>>> >>>> The Broadcom bcm43xx sdio devices are fullmac devices that may be >>>> integrated in ARM platforms. Currently, the brcmfmac driver for >>>> these devices support use of platform data. This patch specifies >>>> the bindings that allow this platform data to be expressed in the >>>> devicetree. >>>> >>>> Reviewed-by: Hante Meuleman <meuleman@xxxxxxxxxxxx> >>>> Reviewed-by: Franky (Zhenhui) Lin <frankyl@xxxxxxxxxxxx> >>>> Reviewed-by: Daniel (Deognyoun) Kim <dekim@xxxxxxxxxxxx> >>>> Reviewed-by: Pieter-Paul Giesberts <pieterpg@xxxxxxxxxxxx> >>>> Signed-off-by: Arend van Spriel <arend@xxxxxxxxxxxx> >>>> [hdegoede@xxxxxxxxxx: drop clk / reg_on gpio handling, as there is no consensus >>>> on how to handle this yet] >>>> [hdegoede@xxxxxxxxxx: move from bindings/staging to bindings] >>>> Signed-off-by: Hans de Goede <hdegoede@xxxxxxxxxx> >>>> --- >>>> .../bindings/net/wireless/brcm,bcm43xx-fmac.txt | 29 ++++++++++++++++++++++ >>>> 1 file changed, 29 insertions(+) >>>> create mode 100644 Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt >>>> >>>> diff --git a/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt b/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt >>>> new file mode 100644 >>>> index 0000000..6a0aaf2 >>>> --- /dev/null >>>> +++ b/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt >>>> @@ -0,0 +1,29 @@ >>>> +Broadcom BCM43xx Fullmac wireless SDIO devices >>>> + >>>> +This node provides properties for controlling the Broadcom wireless device. The >>>> +node is expected to be specified as a child node to the SDIO controller that >>>> +connects the device to the system. >>>> + >>>> +Required properties: >>>> + >>>> + - compatible : Should be "brcm,bcm43xx-fmac". >>> >>> In general, the use of a wildcard compatible string is discouraged >>> over the use of a more descriptive compatible string. So you should >>> find out what is the first chip that is compatible, and use that >>> compatible string as long as that compatibility remains. >> >> Right, Arend, what should we use then ? > > In earlier discussions, we ended up with this compatible string. The properties are generic enough to be covered by this 'wildcard' string. However, I am not religious about it so if you feel strongly for an explicit string it could be brcm,bcm4329-fmac, but it does not have my preference. It is not something I really feel strong about, but as Florian rightfully points out using wildcard strings is something which is more or less not done in devicetree land, the idea being that just using the lowest model, makes it easier to later add different bindings for later models if that turns out to be necessary. So I've changed the compatibility string to brcm,bcm4329-fmac for v3 of this patch-set. Regards, Hans -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
