• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 1748 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.

Disabling the User led pins on Beaglebone black board

Pradna K
Prodigy 20 points

We are using the GPMC bus on the beaglebone black. To achieve this, we have defined our own dts file for configuring the pins on P8 and P9 headers for GPMC purpose. Though, we have enabled the User led pin group through our dts file, we are observing those pins as userled group in our pin mux.  We were using Kernel 3.14, which was downgraded to Kernel 3.8 to use its capemanager to enable our dts file. Therefore, we are using Kernel 3.8 as of now.How do we disable them as user led group such that, they should belong to the gpmc pin group?

Please provide us the solution to this issue.

  • 0
    TI__Guru**** 393215 points

    This forum supports only the official TI distributed Linux SDK.  Kernel 3.8 is a Beagleboard community project and is not supported by us. Please ask your questions about v3.8 on: http://beagleboard.org/Community/Forums

  • 0 in reply to Biser Gatchev-XID
    Prodigy 20 points

    Hi Biser,

    Thanks for your reply. But, we have another query here. Though, we have configured those user led pins as GPMC pins, they are getting listed as user led groups twice when we 

    cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pingroups

    registered pin groups:
    group: pinmux_userled_pins
    pin 21 (44e10854)
    pin 22 (44e10858)
    pin 23 (44e1085c)
    pin 24 (44e10860)

    group: pinmux_rstctl_pins
    pin 20 (44e10850)

    group: pinmux_i2c0_pins
    pin 98 (44e10988)
    pin 99 (44e1098c)

    group: pinmux_i2c2_pins
    pin 94 (44e10978)
    pin 95 (44e1097c)

    group: pinmux_mmc1_pins
    pin 88 (44e10960)

    group: pinmux_userled_pins
    pin 21 (44e10854)
    pin 22 (44e10858)
    pin 23 (44e1085c)
    pin 24 (44e10860)

    group: pinmux_gpmc_pins
    pin 0 (44e10800)
    pin 1 (44e10804)
    pin 2 (44e10808)
    pin 3 (44e1080c)
    pin 4 (44e10810)
    pin 5 (44e10814)
    pin 6 (44e10818)
    pin 7 (44e1081c)
    pin 8 (44e10820)
    pin 9 (44e10824)
    pin 10 (44e10828)
    pin 11 (44e1082c)
    pin 12 (44e10830)
    pin 13 (44e10834)
    pin 14 (44e10838)
    pin 15 (44e1083c)
    pin 29 (44e10874)
    pin 32 (44e10880)
    pin 35 (44e1088c)
    pin 36 (44e10890)
    pin 37 (44e10894)
    pin 38 (44e10898)
    pin 39 (44e1089c)
    pin 56 (44e108e0)
    pin 58 (44e108e8)
    pin 57 (44e108e4)
    pin 59 (44e108ec)
    pin 54 (44e108d8)
    pin 55 (44e108dc)
    pin 53 (44e108d4)
    pin 51 (44e108cc)
    pin 52 (44e108d0)
    pin 50 (44e108c8)
    pin 48 (44e108c0)
    pin 49 (44e108c4)
    pin 46 (44e108b8)
    pin 47 (44e108bc)
    pin 44 (44e108b0)
    pin 45 (44e108b4)
    pin 42 (44e108a8)
    pin 43 (44e108ac)
    pin 40 (44e108a0)
    pin 41 (44e108a4)
    pin 30 (44e10878)
    pin 32 (44e10880)
    pin 28 (44e10870)
    pin 31 (44e1087c)

    Could you please let us know why these are being listed twice and how do we disable them as user led pins and enable them as gpmc pins?

  • 0 in reply to Pradna K
    TI__Guru**** 393215 points

    You are chasing the same issue on two threads on this forum. I will now close this thread. Please continue on https://e2e.ti.com/support/arm/sitara_arm/f/791/t/433104