On Thu, Mar 31, 2016 at 11:01:58AM -0700, Tim Harvey wrote: > On Wed, Mar 30, 2016 at 6:57 PM, Shawn Guo <shawnguo@xxxxxxxxxx> wrote: > > On Wed, Mar 30, 2016 at 02:09:16PM -0700, Guenter Roeck wrote: > >> The question was if the property name should be ext-reset-output or > >> fsl,ext-reset-output. In my opinion, it should be fsl,ext-reset-output > >> because it is not a generic property. Tim disagrees. > >> > > Guenter, > > My issue regarding the vendor prefix was not a hard dissagreement but > was more about me understanding the rational behind using vendor > prefixes. In this case the imx2_wdt driver 'is' a vendor specific > driver as its compatible strings are prefixed with 'fsl,' so isn't > 'any' property added to devicetree/bindings/watchdog/fsl-imx-wdt.txt > inherently a vendor specific properly already? I assume that is why > the 'big-endian' property isn't 'fsl,big-endian'. We should read it as that 'big-endian' is a generic property defined by generic bindings - bindings/regmap/regmap.txt, and we just reference the bindings in fsl-imx-wdt.txt. Taking mmc bindings as example, bindings/mmc/mmc.txt defines generic bindings, while bindings/mmc/fsl-imx-esdhc.txt defines i.MX vendor specific properties, which should ideally have vendor prefix. Shawn -- 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
