Quantcast
Channel: Forums - Recent Threads
Viewing all articles
Browse latest Browse all 262198

Linux/DRA77P: Enabling MMC3 Interface

$
0
0

Part Number:DRA77P

Tool/software: Linux

Hi,

We have followed few steps mentioned in e2e for enabling mmc3 interface in the dra76-evm.dts device tree file as the following,

&dra7_pmx_core {	
	mmc3_pins_default: mmc3_pins_default {
		pinctrl-single,pins = <
			0x37C (PIN_INPUT_PULLUP | MUX_MODE0)	/* mmc3_clk.clk */
			0x380 (PIN_INPUT_PULLUP | MUX_MODE0)	/* mmc3_cmd.cmd */
			0x384 (PIN_INPUT_PULLUP | MUX_MODE0)	/* mmc3_dat0.dat0 */
			0x388 (PIN_INPUT_PULLUP | MUX_MODE0)	/* mmc3_dat1.dat1 */
			0x38C (PIN_INPUT_PULLUP | MUX_MODE0)	/* mmc3_dat2.dat2 */
			0x390 (PIN_INPUT_PULLUP | MUX_MODE0)	/* mmc3_dat3.dat3 */
		>;
	};
	mmc3_pins_hs: mmc3_pins_hs {
		pinctrl-single,pins = <
			0x37C (PIN_INPUT_PULLUP | MUX_VIRTUAL_MODE11 | MUX_MODE0)	/* mmc3_clk.clk */
			0x380 (PIN_INPUT_PULLUP | MUX_VIRTUAL_MODE11 | MUX_MODE0)	/* mmc3_cmd.cmd */
			0x384 (PIN_INPUT_PULLUP | MUX_VIRTUAL_MODE11 | MUX_MODE0)	/* mmc3_dat0.dat0 */
			0x388 (PIN_INPUT_PULLUP | MUX_VIRTUAL_MODE11 | MUX_MODE0)	/* mmc3_dat1.dat1 */
			0x38C (PIN_INPUT_PULLUP | MUX_VIRTUAL_MODE11 | MUX_MODE0)	/* mmc3_dat2.dat2 */
			0x390 (PIN_INPUT_PULLUP | MUX_VIRTUAL_MODE11 | MUX_MODE0)	/* mmc3_dat3.dat3 */
		>;
	};
}; 
 
&mmc3{	
	status = "okay";
	vmmc-supply = <&vio_1v8>;
	bus-width = <4>;
	ti,non-removable;
	max-frequency = <192000000>;
	pinctrl-names = "default", "hs";
	pinctrl-0 = <&mmc3_pins_default>;
	pinctrl-1 = <&mmc3_pins_hs>;
	clock-names = "fck", "clk32k";
	clocks = <&mmc3_gfclk_div>, <&mmc3_clk32k>;	
};

Also we have enabled it in the u-boot device tree also and was able to list the mmc3 device in u-boot.

In the kernel on inserting the command cat /sys/kernel/debug/mmc2/ios (mmc3 is listed as mmc2), the following is observed,

root@dra7xx-evm:~# cat /sys/kernel/debug/mmc2/ios
clock:  0 Hz
vdd:  0 (invalid)
bus mode: 2 (push-pull)
chip select: 0 (don't care)
power mode: 0 (off)
bus width: 0 (1 bits)
timing spec: 0 (legacy)
signal voltage: 0 (1.80 V)
driver type: 0 (driver type B)

We are using ti-processor-sdk-linux-automotive-dra7xx-evm-5_00_00_01.

What changes might be required for correcting this ?

Do we have any procedure in enabling the mmc3 in the sdk dra7xx-evm-5_00_00_01 ?

Regards,

Padmesh


Viewing all articles
Browse latest Browse all 262198

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>