Skip to content

Omap mux changes for v2.6.33 merge window (Series short description)

Tony Lindgren linux-arm-kernel linux-omap 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 8 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 8 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/8] Omap mux changes for v2.6.33 merge window (Series short description)
Quoted 9 lines · Mike Rapoport

Tony,

Quoted 6 lines · Tony Lindgren
Quoted 4 lines · Tony Lindgren

Hi all,

Here are some omap mux updates for review. These
are intended for the v2.6.33 merge window.

Quoted 8 lines
Quoted 4 lines

Forgot to edit the subject :)

Also, these patches are available in the mux branch of the linux-omap tree for easy testing.

After all the discussions we had, what would be preferable way to define the board mux configuration? The omap_board_mux array or a calls for omap_mux_init_signal?

You should be able to just boot with CONFIG_DEBUG_FS, check how the pins are set, and adjust as needed via sysfs. Then when happy with the settings, just do:

# cat /sys/kernel/debug/omap_mux/board                    
OMAP3_MUX(CAM_D0, OMAP_PIN_INPUT | OMAP_PIN_OFF_WAKEUPENABLE | OMAP_MUX_MODE4),
OMAP3_MUX(CAM_D10, OMAP_PIN_OUTPUT | OMAP_MUX_MODE7), 
OMAP3_MUX(CAM_D11, OMAP_PIN_INPUT | OMAP_PIN_OFF_WAKEUPENABLE | OMAP_MUX_MODE4),
OMAP3_MUX(CAM_D1, OMAP_PIN_INPUT_PULLUP | OMAP_PIN_OFF_WAKEUPENABLE | OMAP_MUX_MODE4),
OMAP3_MUX(CAM_D2, OMAP_PIN_INPUT | OMAP_PIN_OFF_WAKEUPENABLE | OMAP_MUX_MODE4), 
OMAP3_MUX(CAM_D3, OMAP_PIN_OUTPUT | OMAP_MUX_MODE4),
OMAP3_MUX(CAM_D4, OMAP_PIN_OUTPUT | OMAP_MUX_MODE7),
OMAP3_MUX(CAM_D5, OMAP_PIN_OUTPUT | OMAP_MUX_MODE4),
OMAP3_MUX(CAM_D6, OMAP_PIN_INPUT | OMAP_MUX_MODE0),
OMAP3_MUX(CAM_D7, OMAP_PIN_INPUT | OMAP_MUX_MODE0),
OMAP3_MUX(CAM_D8, OMAP_PIN_INPUT | OMAP_MUX_MODE0),
OMAP3_MUX(CAM_D9, OMAP_PIN_INPUT | OMAP_MUX_MODE0),
...

And then use the output for the struct omap_board_mux board_mux[] in your board-*.c files.

For the common device init functions and omap_hwmod, we probably want to use the signal names. That allows more generic initialization of the internal devices, but some pins for sure still need to be muxed in a board specific way.

Regards,

Tony