Searched hist:"16 c4c524" (Results 1 – 5 of 5) sorted by relevance
/openbmc/linux/Documentation/devicetree/bindings/i2c/ |
H A D | i2c-pxa-pci-ce4100.txt | 16c4c524 Tue Nov 13 11:16:43 CST 2012 Wolfram Sang <wolfram@the-dreams.de> bindings: i2c: use consistent naming for i2c binding descriptions
Filenames of devictree binding documentation seems to be arbitrary and for me it is unneeded hazzle to find the corresponding documentation for a specific driver.
Naming the description the same as the driver is a lot easier and makes sense to me since the driver defines the binding it understands.
Also, remove a reference in one source to the binding documentation, since path information easily gets stale.
Signed-off-by: Wolfram Sang <wolfram@the-dreams.de> Cc: Rob Herring <robherring2@gmail.com> Cc: Grant Likely <grant.likely@secretlab.ca> Signed-off-by: Grant Likely <grant.likely@secretlab.ca> 16c4c524 Tue Nov 13 11:16:43 CST 2012 Wolfram Sang <wolfram@the-dreams.de> bindings: i2c: use consistent naming for i2c binding descriptions Filenames of devictree binding documentation seems to be arbitrary and for me it is unneeded hazzle to find the corresponding documentation for a specific driver. Naming the description the same as the driver is a lot easier and makes sense to me since the driver defines the binding it understands. Also, remove a reference in one source to the binding documentation, since path information easily gets stale. Signed-off-by: Wolfram Sang <wolfram@the-dreams.de> Cc: Rob Herring <robherring2@gmail.com> Cc: Grant Likely <grant.likely@secretlab.ca> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
|
H A D | i2c-davinci.txt | 16c4c524 Tue Nov 13 11:16:43 CST 2012 Wolfram Sang <wolfram@the-dreams.de> bindings: i2c: use consistent naming for i2c binding descriptions
Filenames of devictree binding documentation seems to be arbitrary and for me it is unneeded hazzle to find the corresponding documentation for a specific driver.
Naming the description the same as the driver is a lot easier and makes sense to me since the driver defines the binding it understands.
Also, remove a reference in one source to the binding documentation, since path information easily gets stale.
Signed-off-by: Wolfram Sang <wolfram@the-dreams.de> Cc: Rob Herring <robherring2@gmail.com> Cc: Grant Likely <grant.likely@secretlab.ca> Signed-off-by: Grant Likely <grant.likely@secretlab.ca> 16c4c524 Tue Nov 13 11:16:43 CST 2012 Wolfram Sang <wolfram@the-dreams.de> bindings: i2c: use consistent naming for i2c binding descriptions Filenames of devictree binding documentation seems to be arbitrary and for me it is unneeded hazzle to find the corresponding documentation for a specific driver. Naming the description the same as the driver is a lot easier and makes sense to me since the driver defines the binding it understands. Also, remove a reference in one source to the binding documentation, since path information easily gets stale. Signed-off-by: Wolfram Sang <wolfram@the-dreams.de> Cc: Rob Herring <robherring2@gmail.com> Cc: Grant Likely <grant.likely@secretlab.ca> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
|
H A D | i2c-octeon.txt | 16c4c524 Tue Nov 13 11:16:43 CST 2012 Wolfram Sang <wolfram@the-dreams.de> bindings: i2c: use consistent naming for i2c binding descriptions
Filenames of devictree binding documentation seems to be arbitrary and for me it is unneeded hazzle to find the corresponding documentation for a specific driver.
Naming the description the same as the driver is a lot easier and makes sense to me since the driver defines the binding it understands.
Also, remove a reference in one source to the binding documentation, since path information easily gets stale.
Signed-off-by: Wolfram Sang <wolfram@the-dreams.de> Cc: Rob Herring <robherring2@gmail.com> Cc: Grant Likely <grant.likely@secretlab.ca> Signed-off-by: Grant Likely <grant.likely@secretlab.ca> 16c4c524 Tue Nov 13 11:16:43 CST 2012 Wolfram Sang <wolfram@the-dreams.de> bindings: i2c: use consistent naming for i2c binding descriptions Filenames of devictree binding documentation seems to be arbitrary and for me it is unneeded hazzle to find the corresponding documentation for a specific driver. Naming the description the same as the driver is a lot easier and makes sense to me since the driver defines the binding it understands. Also, remove a reference in one source to the binding documentation, since path information easily gets stale. Signed-off-by: Wolfram Sang <wolfram@the-dreams.de> Cc: Rob Herring <robherring2@gmail.com> Cc: Grant Likely <grant.likely@secretlab.ca> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
|
H A D | i2c-pnx.txt | 16c4c524 Tue Nov 13 11:16:43 CST 2012 Wolfram Sang <wolfram@the-dreams.de> bindings: i2c: use consistent naming for i2c binding descriptions
Filenames of devictree binding documentation seems to be arbitrary and for me it is unneeded hazzle to find the corresponding documentation for a specific driver.
Naming the description the same as the driver is a lot easier and makes sense to me since the driver defines the binding it understands.
Also, remove a reference in one source to the binding documentation, since path information easily gets stale.
Signed-off-by: Wolfram Sang <wolfram@the-dreams.de> Cc: Rob Herring <robherring2@gmail.com> Cc: Grant Likely <grant.likely@secretlab.ca> Signed-off-by: Grant Likely <grant.likely@secretlab.ca> 16c4c524 Tue Nov 13 11:16:43 CST 2012 Wolfram Sang <wolfram@the-dreams.de> bindings: i2c: use consistent naming for i2c binding descriptions Filenames of devictree binding documentation seems to be arbitrary and for me it is unneeded hazzle to find the corresponding documentation for a specific driver. Naming the description the same as the driver is a lot easier and makes sense to me since the driver defines the binding it understands. Also, remove a reference in one source to the binding documentation, since path information easily gets stale. Signed-off-by: Wolfram Sang <wolfram@the-dreams.de> Cc: Rob Herring <robherring2@gmail.com> Cc: Grant Likely <grant.likely@secretlab.ca> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
|
/openbmc/linux/drivers/i2c/busses/ |
H A D | i2c-ocores.c | 16c4c524 Tue Nov 13 11:16:43 CST 2012 Wolfram Sang <wolfram@the-dreams.de> bindings: i2c: use consistent naming for i2c binding descriptions
Filenames of devictree binding documentation seems to be arbitrary and for me it is unneeded hazzle to find the corresponding documentation for a specific driver.
Naming the description the same as the driver is a lot easier and makes sense to me since the driver defines the binding it understands.
Also, remove a reference in one source to the binding documentation, since path information easily gets stale.
Signed-off-by: Wolfram Sang <wolfram@the-dreams.de> Cc: Rob Herring <robherring2@gmail.com> Cc: Grant Likely <grant.likely@secretlab.ca> Signed-off-by: Grant Likely <grant.likely@secretlab.ca> 16c4c524 Tue Nov 13 11:16:43 CST 2012 Wolfram Sang <wolfram@the-dreams.de> bindings: i2c: use consistent naming for i2c binding descriptions Filenames of devictree binding documentation seems to be arbitrary and for me it is unneeded hazzle to find the corresponding documentation for a specific driver. Naming the description the same as the driver is a lot easier and makes sense to me since the driver defines the binding it understands. Also, remove a reference in one source to the binding documentation, since path information easily gets stale. Signed-off-by: Wolfram Sang <wolfram@the-dreams.de> Cc: Rob Herring <robherring2@gmail.com> Cc: Grant Likely <grant.likely@secretlab.ca> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
|