Hi, I used this: /* * XXX: Use a flat representation of the AM33XX interconnect. * The real AM33XX interconnect network is quite complex.Since * that will not bring real advantage to represent that in DT * for the moment, just use a fake OCP bus entry to represent * the whole bus hierarchy. */ ocp { compatible = "simple-bus"; #address-cells = <1>; #size-cells = <1>; ranges; ti,hwmods = "l3_main"; . . . dali_gpio { compatible = "arm,dali_gpio"; dali_TX = <9>; dali_RX = <10>; }; } Thanks Nayan Gadre. On Thu, Jul 21, 2016 at 11:19 AM, Raul Piper <raulpblooper@gmail.com> wrote:
kindly cc the previous people in "To" .Sorry I missed in while replying you.
On Thu, Jul 21, 2016 at 11:17 AM, Raul Piper <raulpblooper@gmail.com> wrote:
HI,
On Thu, Jul 21, 2016 at 9:43 AM, Gadre Nayan <gadrenayan@gmail.com> wrote:
Hi,
OF stands for open firmware, OF uses a format to represent platform information, which is called a device tree.
An example of how the driver extracts information from device tree:
#if defined(CONFIG_OF) static const struct of_device_id dali_of_ids[] = { { .compatible = "arm,dali_gpio", }, {}, };
MODULE_DEVICE_TABLE(of, dali_of_ids); #endif
static struct platform_driver dali_driver = { .driver = { .name = "dali_gpio", .of_match_table = of_match_ptr(dali_of_ids), }, .probe = Dali_probe, .remove = Dali_remove, };
The driver is going to fetch information from the device tree later on (in probe) using the compatible property mentioned. So if the tree has the same compatible string then subsequent information can be obtained from that device tree node.
Thanks
Can you please post the coresponding dt binding code?
On Thu, Jul 21, 2016 at 9:42 AM, Gadre Nayan <gadrenayan@gmail.com> wrote:
Hi,
OF stands for open firmware, OF uses a format to represent platform information, which is called a device tree.
An example of how the driver extracts information from device tree:
#if defined(CONFIG_OF) static const struct of_device_id dali_of_ids[] = { { .compatible = "arm,dali_gpio", }, {}, };
MODULE_DEVICE_TABLE(of, dali_of_ids); #endif
static struct platform_driver dali_driver = { .driver = { .name = "dali_gpio", .of_match_table = of_match_ptr(dali_of_ids), }, .probe = Dali_probe, .remove = Dali_remove, };
The driver is going to fetch information from the device tree later on (in probe) using the compatible property mentioned. So if the tree has the same compatible string then subsequent information can be obtained from that device tree node.
Thanks Nayan Gadre
On Wed, Jul 20, 2016 at 8:30 PM, Anish Kumar <anish198519851985@gmail.com> wrote:
On Jul 20, 2016, at 4:15 AM, Raul Piper <raulpblooper@gmail.com> wrote:
Hi, I wanted to know the part number
What is part number?
for the leds-gpio.c in the driver/leds folder and the device tree bindings for this driver .Can some one point out to me where in Linux kernel it is?
Also why below line has been used.Is it mandatory? ... .of_match_table = of_gpio_leds_match,
This is needed when you are using device tree for getting the board settings but you can also do the same without this as well. Read up on device tree in kernel Documentation folder.
},
thanks in advance , Rp
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
participants (1)
-
Gadre Nayan