RE: mux init with multiple signal paths.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Silesh C V wrote:
> Hi,
>
> What is the best way to mux signals which are available on
> multiple pins ?
> For example on omap4, gpio 103 can be muxed on
>
> 1.gpmc_ncs6.
> 2.sdmmc_dat1.
>

Specify the signal as pad.signal:
gpmc_ncs6.sdmmc_dat1

(where, pad is the signal name on mode0, and
signal is the signal name for the mode you are interested in).

> omap_mux_init_gpio and omap_mux_init_signal on these pins will now
> return with -EINVAL without modifying the mux register and the pin
> will be left in the state in which the x-loader/u-boot left it at. So
> is it true that the mux framework does not support muxing pins which
> have multiple paths and they have to muxed by accessing the registers
> directly ? Or am I missing something ?
>

The technique above works at least with omap_mux_init_signal.

I'm not so sure about omap_mux_init_gpio.

- Anand
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux