• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 102 subscribers
  • Views 298 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

66ak2h12 device initialization on the arm boot mode.

Gilbert-Kim
Intellectual 350 points

linux kernel initializes k2h's peripherals (srio, hyperlink, pktdma, nwal..) on the arm boot mode.

i faced the problem k2h device initialization is duplicated

while arm kernel is runnung because and examples have init codes and run too.

i think that arm's or dsp's side specific init codes are needed to block to prevent duplication.

but i want to init codes are done only dsp side because there are some parameters whose values are modified.

is this possible to initialize peripherals only dsp side while linux kernel whose specific devices are blocked is running?

  • 0
    TI__Guru** 116100 points
    Hi,
    You can disable the peripherals support in device tree source file (status = "disabled") .
    What are the peripherals want to enable from DSP ?
    SRIO,HYOERLINK,PKTDMA ... ???
  • 0
    TI__Guru* 81335 points

    Hi Gilbert,

    From my understanding, Yes. It is possible.  You can re-configure the kernel by menu config and re-build the kernel after removing the modules wanted init by DSP.  Please refer MCSDK explore wiki for Linux driver.

    Building:

    Or

    You can build the drivers as loadable module (.ko) not to link with kernel.

    Thank you.