• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 804 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

DRA76P: SPRAC44A document as DRA7xx reference

DRA76P: am57xx_generate_pin_config_data output to mux_data.h

AClemotte
Expert 1060 points
Part Number: DRA76P


Hi,


I'm working on the definition of a new dts file for a desing based on the DRA76P. After follow the SPRAC44A guide (e2e.ti.com/.../3019923, I was able to generate the two files (iodelay and iopad) that should be added to the mux_data.h file, but I dont know how I must do know. The guide does not mention anything from this point. My question is really open, but right know, I dont what should I do. Any suggestion?

Regards

  • 0
    TI__Mastermind 42515 points

    Hi,

    please check "Appendix C" in SPRAC44A for instruction how to use a perl script which from genericPadConf.txt and genericIOdelay.txt generates output which can be added to mux_data.h.

    Regards,

    Yordan

  • 0 in reply to Yordan Kamenov
    Expert 1060 points

    Thanks Yordan, but I already generated the output files, iodelay and padconfig. My question is related to the method of adding content to the mux_data.h file.


    My suppositions:

    - I found mux_data.h has three struct types: pad_conf_entry, iodelay_cfg_entry and omap_hsmmc_pinctrl_state. I must create these three structure.
    - Two of these new structures, pad_conf_entry and iodelay_cfg_entry must be created with the output of both files: iodelay and padconfig (created by the script)


    My questions:

    - Are my suppositions right?
    - What about the content of the omap_hsmmc_pinctrl_state structure?
    - Why the name of the structures are related to the processor and not to the board? I mean, my structure has also the DRA76x, but I'll call it something related to my board.


    Regards,

  • 0 in reply to AClemotte
    TI__Genius 9905 points

    Yes, you are right. Create these structures from the output of the tool.

    All the names are SoC specific, not boars specific

    omap_hsmmc_pinctrl_state is not needed

  • 0 in reply to Nikhil Devshatwar
    Expert 1060 points

    And after this, what should I do to point to this new structures?

    Regards,

  • 0 in reply to AClemotte
    TI__Genius 9905 points

    In the TI u-boot, board/ti/dra7xx/mux_data.h There is an array for dra76x to describe the pinmux and iodelay values.

    You just have to replce your values there. The array is already getting referenced from board/ti/dra7xx/evm.c to configure the pinmux and iodelay while initializing the board.

    Regards,

    Nikhil D

  • 0 in reply to Nikhil Devshatwar
    Expert 1060 points

    OK, so I'll replace the contend of:

    - const struct pad_conf_entry dra76x_core_padconf_array[]

    - const struct iodelay_cfg_entry dra76x_es1_0_iodelay_cfg_array[]