Commit f7f678a0 authored by Stephen Warren's avatar Stephen Warren Committed by Grant Likely

gpio/tegra: Use engineering names in DT compatible property

Engineering names are more stable than marketing names. Hence, use them
for Device Tree compatible properties instead.
Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
Signed-off-by: default avatarGrant Likely <grant.likely@secretlab.ca>
parent a6b09191
NVIDIA Tegra 2 GPIO controller NVIDIA Tegra 2 GPIO controller
Required properties: Required properties:
- compatible : "nvidia,tegra250-gpio" - compatible : "nvidia,tegra20-gpio"
- #gpio-cells : Should be two. The first cell is the pin number and the - #gpio-cells : Should be two. The first cell is the pin number and the
second cell is used to specify optional parameters (currently unused). second cell is used to specify optional parameters (currently unused).
- gpio-controller : Marks the device node as a GPIO controller. - gpio-controller : Marks the device node as a GPIO controller.
...@@ -347,7 +347,7 @@ static int __init tegra_gpio_init(void) ...@@ -347,7 +347,7 @@ static int __init tegra_gpio_init(void)
* driver is converted into a platform_device * driver is converted into a platform_device
*/ */
tegra_gpio_chip.of_node = of_find_compatible_node(NULL, NULL, tegra_gpio_chip.of_node = of_find_compatible_node(NULL, NULL,
"nvidia,tegra250-gpio"); "nvidia,tegra20-gpio");
#endif /* CONFIG_OF_GPIO */ #endif /* CONFIG_OF_GPIO */
gpiochip_add(&tegra_gpio_chip); gpiochip_add(&tegra_gpio_chip);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment