TQM5200 2.6-denx SM501 voyager enabling problem.

TQM5200 2.6-denx SM501 voyager enabling problem.

[Pedro Luis D. L.]

Hello,
I'm working right now with a TQM5200 microcontroller on a STX5200 board.
I'm having problems to enable SM501 video output using 2.6-denx kernel. The=
 system is working properly using 2.4 kernel and I can have graphical outpu=
t, so I can be sure that there's no hardware problem.
With 2.6 I have used the tqm5200_defconfig configuration file and then I ha=
ve enabled the following features in the kernel:
 - Device Drivers -> Multifunction Device Drivers -> Support forSilicon Mot=
ion SM501.
 - Device Drivers -> Graphic Support ->  Support for frame buffer devices.
 - Device Drivers -> Graphic Support ->  Support for frame buffer devices -=
> Silicon Motion SM501 framebuffer support.
 - Device Drivers -> Character devices -> Virtual Terminal.
 - Device Drivers -> Character devices -> Support for console on virtual te=
rminal.
But I still can't make the SM501 driver initialized at booting time and the=
re's no framebuffer video device available. /dev/fb and /dev/fb0 nodes are =
already created.
I'm using 1.3.1 u-boot from denx repository compiled with  CONFIG_STK52XX=
=3Dy and CONFIG_MINIFAP=3Dy options, and video=3Dvoyager:fp options is pass=
ed to the kernel at booting.

I'm sure there's something I'm missing to enable in the kernel. Maybe someo=
ne can sent me a hint. I would appreciate any!

Pedro L.



_________________________________________________________________
MSN Noticias
http://noticias.msn.es/comunidad.aspx=

Re: TQM5200 2.6-denx SM501 voyager enabling problem.

[Martin Krause]

Hi Pedro,

Pedro Luis D. L. <carcadiz <at> hotmail.com> writes:
> Hello,
> I'm working right now with a TQM5200 microcontroller on a STX5200 board.
> I'm having problems to enable SM501 video output using 2.6-denx kernel. The 

Have you tried to contact TQ-Components (the manufacturer of the TQM5200 
board)? Under the email address support@tqc.de you should get help for
hardware and software questions to all of their products.

Regards,
Martin

RE: TQM5200 2.6-denx SM501 voyager enabling problem.

[Pedro Luis D. L.]

Martin Krause  wrote:


> Hi Pedro,
>=20
> Pedro Luis D. L.  hotmail.com> writes:
>> Hello,
>> I'm working right now with a TQM5200 microcontroller on a STX5200 board.
>> I'm having problems to enable SM501 video output using 2.6-denx kernel. =
The=20
>=20
> Have you tried to contact TQ-Components (the manufacturer of the TQM5200=
=20
> board)? Under the email address support@tqc.de you should get help for
> hardware and software questions to all of their products.
>=20
> Regards,
> Martin

Hi Martin,

Well, that sounds like a very reasonable suggestion. I think I should give =
it a try. Maybe my bad experience with other providers pushed me to ask in =
this list before. But you're right!

Regards,
Pedro.
=20
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

_________________________________________________________________
Tecnolog=EDa, moda, motor, viajes,=85suscr=EDbete a nuestros boletines para=
 estar siempre a la =FAltima
Guapos y guapas, clips musicales y estrenos de cine. =

RE: TQM5200 2.6-denx SM501 voyager enabling problem.

[Pedro Luis D. L.]

I wrote: (:-p)
>=20
>=20
> Martin Krause  wrote:
>=20
>=20
>> Hi Pedro,
>>=20
>> Pedro Luis D. L.  hotmail.com> writes:
>>> Hello,
>>> I'm working right now with a TQM5200 microcontroller on a STX5200 board=
.
>>> I'm having problems to enable SM501 video output using 2.6-denx kernel.=
 The=20
>>=20
>> Have you tried to contact TQ-Components (the manufacturer of the TQM5200=
=20
>> board)? Under the email address support@tqc.de you should get help for
>> hardware and software questions to all of their products.
>>=20
>> Regards,
>> Martin
>=20
> Hi Martin,
>=20
> Well, that sounds like a very reasonable suggestion. I think I should giv=
e it a try. Maybe my bad experience with other providers pushed me to ask i=
n this list before. But you're right!
>=20
> Regards,
> Pedro.
> =20
>=20

I tried to contact TQ but they seem not to be able to solve my problem. The=
y suggested that the problem could be in the different endianness used by M=
PC5200 and SMI501. That problem seems to be corrected in the driver. Anyway=
, this endianness problem may come to light if I had any video output. It i=
s possible to change the endianness of SM501 chip from the u-boot writing a=
 register. I did it and it made no difference at all. The real problem is s=
till that none device is initialized or detected even when the Framebuffer =
driver for SM501 and MFD Driver for SM501 are compiled with the kernel. I c=
hecked that platform driver for both are registered (using some printk outp=
ut) but their probe functions are never invoked.

I thought that my problem could be that I don't have initialized the device=
 within the platform file tqm5200.c. I added the following code (marked wit=
h +) to this file under arch/powerpc/platforms/52xx/tqm5200.c

+static struct resource sm501_resources[] =3D {
+	[0]	=3D {
+		.start	=3D 0xE3E00000,
+		.end	=3D 0xE3DFFFFF,
+		.flags	=3D IORESOURCE_MEM,
+	},
+};
+
+static struct platform_device sm501_device =3D {
+	.name		=3D "sm501",
+	.id		=3D 0,
+	.num_resources	=3D ARRAY_SIZE(sm501_resources),
+	.resource	=3D sm501_resources,
+};

static void __init tqm5200_setup_arch(void)
{
	if (ppc_md.progress)
		ppc_md.progress("tqm5200_setup_arch()", 0);

	/* Some mpc5200 & mpc5200b related configuration */
	mpc5200_setup_xlb_arbiter();

	/* Map wdt for mpc52xx_restart() */
	mpc52xx_map_wdt();

#ifdef CONFIG_PCI
	np =3D of_find_node_by_type(NULL, "pci");
	if (np) {
		mpc52xx_add_bridge(np);
		of_node_put(np);
	}
#endif
+
+	platform_device_register(&sm501_device);
+
}

I got this idea from the configuration files from other platforms, but I st=
ill need to find out how exactly "resources" must be defined. Anybody knows=
 wheather am I pointing in the right direction and this makes any sense?

As far as I understand now (and I may be terribly wrong), once that SM501 M=
FD and Framebuffer drivers are registered,  I need to tell the kernel where=
 to find the device in the local bus. Is it right?

Thanks in advance,

Pedro.

_________________________________________________________________
Tecnolog=EDa, moda, motor, viajes,=85suscr=EDbete a nuestros boletines para=
 estar siempre a la =FAltima
Guapos y guapas, clips musicales y estrenos de cine. =

Re: TQM5200 2.6-denx SM501 voyager enabling problem.

[Anatolij Gustschin]

Hello,

Pedro Luis D. L. wrote:

<snip>

> I tried to contact TQ but they seem not to be able to solve my
> problem. They suggested that the problem could be in the different
> endianness used by MPC5200 and SMI501. That problem seems to be
> corrected in the driver. Anyway, this endianness problem may come
> to light if I had any video output. It is possible to change the
> endianness of SM501 chip from the u-boot writing a register.
> I did it and it made no difference at all. The real problem is
> still that none device is initialized or detected even when the
> Framebuffer driver for SM501 and MFD Driver for SM501 are compiled
> with the kernel. I checked that platform driver for both are
> registered (using some printk output) but their probe functions
> are never invoked.
> 
> I thought that my problem could be that I don't have initialized
> the device within the platform file tqm5200.c. I added the following
> code (marked with +) to this file under arch/powerpc/platforms/52xx/tqm5200.c
> 
> +static struct resource sm501_resources[] = {
> +	[0]	= {
> +		.start	= 0xE3E00000,
> +		.end	= 0xE3DFFFFF,

This is wrong as '.end' resource should be greater than '.start'.
The value for '.end' seems to origin from the typo in TQ docs for
TQM5200. The proper value results from adding 2MB register space
of the SM501 to the IO base 0xe3e00000 and is 0xe3ffffff.
Furthermore you didn't define any framebuffer memory resource
which is strictly needed here for the framebuffer driver.

> +		.flags	= IORESOURCE_MEM,
> +	},
> +};
> +
> +static struct platform_device sm501_device = {
> +	.name		= "sm501",
> +	.id		= 0,
> +	.num_resources	= ARRAY_SIZE(sm501_resources),
> +	.resource	= sm501_resources,
> +};
> 
> static void __init tqm5200_setup_arch(void)
> {
> 	if (ppc_md.progress)
> 		ppc_md.progress("tqm5200_setup_arch()", 0);
> 
> 	/* Some mpc5200 & mpc5200b related configuration */
> 	mpc5200_setup_xlb_arbiter();
> 
> 	/* Map wdt for mpc52xx_restart() */
> 	mpc52xx_map_wdt();
> 
> #ifdef CONFIG_PCI
> 	np = of_find_node_by_type(NULL, "pci");
> 	if (np) {
> 		mpc52xx_add_bridge(np);
> 		of_node_put(np);
> 	}
> #endif
> +
> +	platform_device_register(&sm501_device);
> +
> }
> 
> I got this idea from the configuration files from other platforms,
> but I still need to find out how exactly "resources" must be defined.
> Anybody knows wheather am I pointing in the right direction and this
> makes any sense?

yes, the direction is right or this is at least a possible solution
among others provided that you do it correctly.
Calling "platform_device_register(...)" from "tqm5200_setup_arch()"
won't work, so move this call and the resource definitions to
sm501 platform driver. A really right direction would be adding
sm501 resource description to the device tree and adding appropriate
code to the sm501 platform driver, but it is more effort.

> As far as I understand now (and I may be terribly wrong), once
> that SM501 MFD and Framebuffer drivers are registered,  I need
> to tell the kernel where to find the device in the local bus.
> Is it right?

yes, try the patch below, and also ensure that
CONFIG_VT,
CONFIG_VT_CONSOLE,
CONFIG_FRAMEBUFFER_CONSOLE
are enabled in the kernel configuration.

diff --git a/drivers/mfd/sm501.c b/drivers/mfd/sm501.c
index afd8296..599ffe6 100644
--- a/drivers/mfd/sm501.c
+++ b/drivers/mfd/sm501.c
@@ -901,6 +901,9 @@ static int sm501_init_dev(struct sm501_devdata *sm)
 
 	INIT_LIST_HEAD(&sm->devices);
 
+	/* switch to BE */
+	writel(0xffffffff, sm->regs + SM501_ENDIAN_CONTROL);
+
 	devid = readl(sm->regs + SM501_DEVICEID);
 
 	if ((devid & SM501_DEVICEID_IDMASK) != SM501_DEVICEID_SM501) {
@@ -1263,8 +1266,31 @@ static struct platform_driver sm501_plat_drv = {
 	.resume		= sm501_plat_resume,
 };
 
+/* define some sm501 resources on tqm5200 */
+#define SM501_FB_BASE	0xe0000000
+#define SM501_IO_BASE	0xe3e00000
+#define SM501_FB_END	((SM501_FB_BASE) + 0x7fffff)
+#define SM501_IO_END	((SM501_IO_BASE) + 0x1fffff)
+
+static struct resource sm501_device0_resources[] = {
+	[0] = {.start = SM501_FB_BASE, .end = SM501_FB_END, .flags = IORESOURCE_MEM,},
+	[1] = {.start = SM501_IO_BASE, .end = SM501_IO_END, .flags = IORESOURCE_MEM,},
+};
+
+static struct platform_device sm501_device0 = {
+	.name = "sm501",
+	.id = 0,
+	.num_resources = ARRAY_SIZE(sm501_device0_resources),
+	.resource = sm501_device0_resources,
+};
+
+static struct platform_device *mfd_devices[] __initdata = {
+	&sm501_device0,
+};
+
 static int __init sm501_base_init(void)
 {
+	platform_add_devices(mfd_devices, ARRAY_SIZE(mfd_devices));
 	platform_driver_register(&sm501_plat_drv);
 	return pci_register_driver(&sm501_pci_drv);
 }

Best regards,
Anatolij

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office@denx.de

RE: TQM5200 2.6-denx SM501 voyager enabling problem.

[Pedro Luis D. L.]

Anatolij wrote:

> Hello,

Hello Anatoli,

> Pedro Luis D. L. wrote:
>=20
>=20
>=20
>> I tried to contact TQ but they seem not to be able to solve my
>> problem. They suggested that the problem could be in the different
>> endianness used by MPC5200 and SMI501. That problem seems to be
>> corrected in the driver. Anyway, this endianness problem may come
>> to light if I had any video output. It is possible to change the
>> endianness of SM501 chip from the u-boot writing a register.
>> I did it and it made no difference at all. The real problem is
>> still that none device is initialized or detected even when the
>> Framebuffer driver for SM501 and MFD Driver for SM501 are compiled
>> with the kernel. I checked that platform driver for both are
>> registered (using some printk output) but their probe functions
>> are never invoked.
>>=20
>> I thought that my problem could be that I don't have initialized
>> the device within the platform file tqm5200.c. I added the following
>> code (marked with +) to this file under arch/powerpc/platforms/52xx/tqm5=
200.c
>>=20
>> +static struct resource sm501_resources[] =3D {
>> +	[0]	=3D {
>> +		.start	=3D 0xE3E00000,
>> +		.end	=3D 0xE3DFFFFF,
>=20
> This is wrong as '.end' resource should be greater than '.start'.
> The value for '.end' seems to origin from the typo in TQ docs for
> TQM5200. The proper value results from adding 2MB register space
> of the SM501 to the IO base 0xe3e00000 and is 0xe3ffffff.
> Furthermore you didn't define any framebuffer memory resource
> which is strictly needed here for the framebuffer driver.

Yes, I supposed I had to add another resource, but I was not sure how to po=
int them. I didn't realize the documentation error, ups, but it is true, e3=
d is smaller than e3E... My mistake, sorry :-(


>> +		.flags	=3D IORESOURCE_MEM,
>> +	},
>> +};
>> +
>> +static struct platform_device sm501_device =3D {
>> +	.name		=3D "sm501",
>> +	.id		=3D 0,
>> +	.num_resources	=3D ARRAY_SIZE(sm501_resources),
>> +	.resource	=3D sm501_resources,
>> +};
>>=20
>> static void __init tqm5200_setup_arch(void)
>> {
>> 	if (ppc_md.progress)
>> 		ppc_md.progress("tqm5200_setup_arch()", 0);
>>=20
>> 	/* Some mpc5200 & mpc5200b related configuration */
>> 	mpc5200_setup_xlb_arbiter();
>>=20
>> 	/* Map wdt for mpc52xx_restart() */
>> 	mpc52xx_map_wdt();
>>=20
>> #ifdef CONFIG_PCI
>> 	np =3D of_find_node_by_type(NULL, "pci");
>> 	if (np) {
>> 		mpc52xx_add_bridge(np);
>> 		of_node_put(np);
>> 	}
>> #endif
>> +
>> +	platform_device_register(&sm501_device);
>> +
>> }
>>=20
>> I got this idea from the configuration files from other platforms,
>> but I still need to find out how exactly "resources" must be defined.
>> Anybody knows wheather am I pointing in the right direction and this
>> makes any sense?
>=20
> yes, the direction is right or this is at least a possible solution
> among others provided that you do it correctly.
> Calling "platform_device_register(...)" from "tqm5200_setup_arch()"
> won't work, so move this call and the resource definitions to
> sm501 platform driver. A really right direction would be adding
> sm501 resource description to the device tree and adding appropriate
> code to the sm501 platform driver, but it is more effort.

I thought about this possible solution (adding resource description to devi=
ce tree), but as far as I understood, the device tree was intended to descr=
ibe the microcontroller peripherals and tqm5200, based on the mpc5200 is so=
ld out also without sm501, so that's why I discarded this option.

>> As far as I understand now (and I may be terribly wrong), once
>> that SM501 MFD and Framebuffer drivers are registered,  I need
>> to tell the kernel where to find the device in the local bus.
>> Is it right?
>=20
> yes, try the patch below, and also ensure that
> CONFIG_VT,
> CONFIG_VT_CONSOLE,
> CONFIG_FRAMEBUFFER_CONSOLE
> are enabled in the kernel configuration.
>=20
> diff --git a/drivers/mfd/sm501.c b/drivers/mfd/sm501.c
> index afd8296..599ffe6 100644
> --- a/drivers/mfd/sm501.c
> +++ b/drivers/mfd/sm501.c
> @@ -901,6 +901,9 @@ static int sm501_init_dev(struct sm501_devdata *sm)
> =20
>  	INIT_LIST_HEAD(&sm->devices);
> =20
> +	/* switch to BE */
> +	writel(0xffffffff, sm->regs + SM501_ENDIAN_CONTROL);
> +
>  	devid =3D readl(sm->regs + SM501_DEVICEID);
> =20
>  	if ((devid & SM501_DEVICEID_IDMASK) !=3D SM501_DEVICEID_SM501) {
> @@ -1263,8 +1266,31 @@ static struct platform_driver sm501_plat_drv =3D {
>  	.resume		=3D sm501_plat_resume,
>  };
> =20
> +/* define some sm501 resources on tqm5200 */
> +#define SM501_FB_BASE	0xe0000000
> +#define SM501_IO_BASE	0xe3e00000
> +#define SM501_FB_END	((SM501_FB_BASE) + 0x7fffff)
> +#define SM501_IO_END	((SM501_IO_BASE) + 0x1fffff)
> +
> +static struct resource sm501_device0_resources[] =3D {
> +	[0] =3D {.start =3D SM501_FB_BASE, .end =3D SM501_FB_END, .flags =3D IO=
RESOURCE_MEM,},
> +	[1] =3D {.start =3D SM501_IO_BASE, .end =3D SM501_IO_END, .flags =3D IO=
RESOURCE_MEM,},
> +};
> +
> +static struct platform_device sm501_device0 =3D {
> +	.name =3D "sm501",
> +	.id =3D 0,
> +	.num_resources =3D ARRAY_SIZE(sm501_device0_resources),
> +	.resource =3D sm501_device0_resources,
> +};
> +
> +static struct platform_device *mfd_devices[] __initdata =3D {
> +	&sm501_device0,
> +};
> +
>  static int __init sm501_base_init(void)
>  {
> +	platform_add_devices(mfd_devices, ARRAY_SIZE(mfd_devices));
>  	platform_driver_register(&sm501_plat_drv);
>  	return pci_register_driver(&sm501_pci_drv);
>  }
>=20
> Best regards,
> Anatolij

It worked!! Thank you very much. The device is added and I can get some out=
put throught the LCD attached. Although the output is not correct yet (look=
s like static noise :-) ), but I think it could be because of an incorrect =
clocks and registers initialization. I should check it up right now.

I think this patch might be include within the kernel. Maybe like a configu=
ration option just in case that SM501 is attached to the tqm. I don't know =
how to do it but I'll give it a try and submit a patch to denx once I have =
a proper output when I figure out how.

Thank you very much,

Pedro L.

> --=20
> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office@denx.de

_________________________________________________________________
La vida de los famosos al desnudo en MSN Entretenimiento
http://entretenimiento.es.msn.com/=

Re: TQM5200 2.6-denx SM501 voyager enabling problem.

[Wolfgang Denk]

In message <BLU106-W13F58AFC51977B5ACB4318CA130@phx.gbl> you wrote:
> 
> I thought about this possible solution (adding resource description to device tree), but as far as I understood, the device tree was intended to describe the microcontroller peripherals and tqm5200, based on the mpc5200 is sold out also without sm501, s
> o that's why I discarded this option.

The device tree describes the hardware, and the TQM5200 (with  SM501)
and  the  TQM5200S  (without  the SM501) are two different boards and
need different device trees.


And, Pedro - could you please restrict your line length to some 70+
characters or so? Thanks.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"The greatest warriors are the ones who fight for peace."
- Holly Near

RE: TQM5200 2.6-denx SM501 voyager enabling problem.

[Pedro Luis D. L.]

Wolfgang wrote:

>>=20
>> I thought about this possible solution (adding resource description to=20
>> device tree), but as far as I understood, the device tree was intended t=
o=20
>> describe the microcontroller peripherals and tqm5200, based on the mpc52=
00=20
>> is sold out also without sm501, so that's why I discarded this option.
>
>=20
> The device tree describes the hardware, and the TQM5200 (with  SM501)
> and  the  TQM5200S  (without  the SM501) are two different boards and
> need different device trees.
>=20

So I got it wrong... Good to know. Once I had something working I can give =
it=20
a try and make a different device tree for TQM5200 and TQM5200S and try
to initialize the SM501 using of_platform api.

>=20
> And, Pedro - could you please restrict your line length to some 70+
> characters or so? Thanks.

Ups, sorry. I'll do it since now.

> Best regards,
>=20
> Wolfgang Denk
>

Best regards,

Pedro L. Dominguez.
=20
> --=20
> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
> "The greatest warriors are the ones who fight for peace."
> - Holly Near

_________________________________________________________________
Tecnolog=EDa, moda, motor, viajes,=85suscr=EDbete a nuestros boletines para=
 estar siempre a la =FAltima
Guapos y guapas, clips musicales y estrenos de cine. =