GPIO status

Kernel development related

GPIO status

Postby Thijs » Sun Jan 09, 2011 8:19 pm

Hi all,

I just compiled the following SamDroid modules against Dopi's latest experimental branch:

Code: Select all
btgpio.ko
dhd.ko
dpram.ko
multipdp.ko
rfs.ko
s3c_cmm.ko
s3c_g2d_driver.ko
s3c_g3d.ko
s3c_jpeg.ko
s3c_mfc.ko
s3c_pp.ko
s3c_rotator.ko
xsr_debug.ko
xsr.ko
xsr_stl.ko


As you see, this resulted in a quite impressive list of additional JetDroid modules. Unfortunately the following modules require GPIO definitions (missing in JetKernel):

Code: Select all
/home/tbressers/JetDroid/modules/dpram/dpram.c:959: error: 'GPIO_CP_BOOT_SEL' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:1055: error: 'GPIO_PHONE_RST_N' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:1061: error: 'GPIO_CP_BOOT_SEL' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:1296: error: 'GPIO_PHONE_RST_N' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:2280: error: 'GPIO_SIM_DETECT_N' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:2491: error: 'GPIO_SIM_DETECT_N' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:2491: error: 'GPIO_SIM_DETECT_N_AF' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:2495: error: 'GPIO_FLM_RXD' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:2495: error: 'GPIO_FLM_RXD_AF' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:2498: error: 'GPIO_FLM_TXD' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:2498: error: 'GPIO_FLM_TXD_AF' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:2508: error: 'GPIO_CP_BOOT_SEL' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:2522: error: 'GPIO_PHONE_RST_N' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:2529: error: 'GPIO_PDA_ACTIVE' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:2617: error: 'GPIO_PDA_ACTIVE' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:2623: error: 'GPIO_PDA_ACTIVE' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/dpram/dpram.c:2657: error: 'GPIO_SIM_DETECT_N' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/camera/samsung/s5k4ca.c:203: error: 'GPIO_I2C1_SCL' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/camera/samsung/s5k4ca.c:203: error: 'GPIO_I2C1_SDA' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/camera/samsung/s5k4ca.c:208: error: 'GPIO_CAM_STANDBY' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/camera/samsung/s5k4ca.c:222: error: 'GPIO_CAM_STANDBY' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/camera/samsung/s5k4ca.c:251: error: 'GPIO_I2C1_SCL' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/camera/samsung/s5k4ca.c:251: error: 'GPIO_I2C1_SCL_AF' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/camera/samsung/s5k4ca.c:251: error: 'GPIO_I2C1_SDA' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/camera/samsung/s5k4ca.c:251: error: 'GPIO_I2C1_SDA_AF' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/camera/samsung/s5k4ca.c:258: error: 'GPIO_I2C1_SCL' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/camera/samsung/s5k4ca.c:258: error: 'GPIO_I2C1_SDA' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/camera/samsung/s5k4ca.c:260: error: 'GPIO_CAM_STANDBY' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/vibetonz/vibetonz.c:61: error: 'GPIO_VIB_EN' undeclared (first use in this function)
/home/tbressers/JetDroid/modules/vibetonz/vibetonz.c:164: error: 'GPIO_VIB_EN' undeclared (first use in this function)


Maybe we can use this thread to give updates on GPIO?

Best regards - Thijs
Thijs
Dev Team
Dev Team
 
Posts: 114
Joined: Fri Sep 10, 2010 6:28 pm

Advertisement

       

Re: GPIO status

Postby Dopi » Mon Jan 10, 2011 12:53 pm

Hi Thijs,

thanks for having a try on the modules. It was on my list for quite a time, but I did not manage to try to compile it myself, yet. However, I already created a working copy the Samdroid modules in the JetDroid repo ( https://github.com/JetDroid/JetKernel_modules).

Besides the necessary GPIO fixes in the main kernel we need to make some changes to these modules, too. Here is what I have in mind.

  • copy our Wifi driver module from the main kernel (drivers/staging/wlan-bcm ) there
  • the I5700 camera module is most probably useless. it needs to be verified if we can use parts of the I9000 camera modules.

Your list of compile results is very usefull as it highlights wich GPIOs we still need to map. The GPIO mapping table is already available to our dev-team. If anyone needs it, please PM me. There are however some signals that I don't yet know how to map to the Jet. Some more research is need for those.

Cheers,
Dopi
Ad banners support the JetDroid forum. Please consider clicking them once in a while.
User avatar
Dopi
Dev Team
Dev Team
 
Posts: 926
Joined: Sun Aug 22, 2010 9:47 pm

Re: GPIO status

Postby Thijs » Mon Jan 10, 2011 2:11 pm

Dopi wrote:The GPIO mapping table is already available to our dev-team. If anyone needs it, please PM me. There are however some signals that I don't yet know how to map to the Jet. Some more research is need for those.

Cheers,
Dopi

Hi Dopi,

Good to hear that. Are you still working on the dpram related GPIO signals? I saw you updated a few GPIO signals recently...

Best regards - Thijs
Thijs
Dev Team
Dev Team
 
Posts: 114
Joined: Fri Sep 10, 2010 6:28 pm

Re: GPIO status

Postby Dopi » Mon Jan 10, 2011 3:33 pm

Thijs wrote:Good to hear that. Are you still working on the dpram related GPIO signals? I saw you updated a few GPIO signals recently...

I try to update the GPIOs every now and then. I am not completely sure which ones are related to dpram only. The signals for inter-processor communications are quite a few - most signals from your compile errors fall in this area. Thus the best thing might be fixing them all ;)

Cheers,
Dopi
Ad banners support the JetDroid forum. Please consider clicking them once in a while.
User avatar
Dopi
Dev Team
Dev Team
 
Posts: 926
Joined: Sun Aug 22, 2010 9:47 pm

Re: GPIO status

Postby Thijs » Mon Jan 10, 2011 8:59 pm

Dopi wrote:I try to update the GPIOs every now and then. I am not completely sure which ones are related to dpram only. The signals for inter-processor communications are quite a few - most signals from your compile errors fall in this area. Thus the best thing might be fixing them all ;)

Cheers,
Dopi

Hi Dopi,

In jet_gpio.h, GPIO_USBSW_SDA_3V0 is mapped on S3C64XX_GPK(7) while the GPIO excel sheet says PHONE_RST_N must be mapped on that pin. Because USB seems to be working fine, I'm wondering where to map PHONE_RST_N on... But I may very well be misunderstanding something.

Can you help me out? Or even better implement the dpram GPIO settings? It obvious isn't my speciality :)

Best regards - Thijs
Thijs
Dev Team
Dev Team
 
Posts: 114
Joined: Fri Sep 10, 2010 6:28 pm

Re: GPIO status

Postby Dopi » Mon Jan 10, 2011 10:37 pm

Thijs wrote:In jet_gpio.h, GPIO_USBSW_SDA_3V0 is mapped on S3C64XX_GPK(7) while the GPIO excel sheet says PHONE_RST_N must be mapped on that pin. Because USB seems to be working fine, I'm wondering where to map PHONE_RST_N on... But I may very well be misunderstanding something.

Can you help me out? Or even better implement the dpram GPIO settings? It obvious isn't my speciality :)

Mmmh. Maybe there is something wrong with the excel table. I will check this again.

Cheers,
Dopi
Ad banners support the JetDroid forum. Please consider clicking them once in a while.
User avatar
Dopi
Dev Team
Dev Team
 
Posts: 926
Joined: Sun Aug 22, 2010 9:47 pm

Re: GPIO status

Postby Dopi » Tue Jan 11, 2011 11:04 am

Dopi wrote:
Thijs wrote:In jet_gpio.h, GPIO_USBSW_SDA_3V0 is mapped on S3C64XX_GPK(7) while the GPIO excel sheet says PHONE_RST_N must be mapped on that pin. Because USB seems to be working fine, I'm wondering where to map PHONE_RST_N on... But I may very well be misunderstanding something.

Can you help me out? Or even better implement the dpram GPIO settings? It obvious isn't my speciality :)

Mmmh. Maybe there is something wrong with the excel table. I will check this again.

Cheers,
Dopi

Oh, boy! Sometimes this phone really holds some challenges for us ;) I checked the connections you mentioned and found out that GPIO_USBSW_SDA_3V0 and GPIO_USBSW_SCL_3V0 are mapped correctly. I need to check why this is not in the excel table.

The interesting part was that there is no PHONE_RST_N (or similar) signal output on the AP (S3C6410). In the Jet design the reset of the MSM CP (communication processor) is controlled via the PMU. It has two reset outputs, one for the AP and one for the CP.

It looks like we need some more changes for dpram to work, than just fixing the GPIO table. I will check the MAX8906 driver to see if I can find any way to control the reset outputs.

Cheers,
Dopi
Ad banners support the JetDroid forum. Please consider clicking them once in a while.
User avatar
Dopi
Dev Team
Dev Team
 
Posts: 926
Joined: Sun Aug 22, 2010 9:47 pm

Re: GPIO status

Postby Thijs » Tue Jan 11, 2011 12:48 pm

Dopi wrote:I will check the MAX8906 driver to see if I can find any way to control the reset outputs.

Cheers,
Dopi

Yes, it's quite a struggle and makes you wonder why (or what for), every now and then.

Thanks for your help!

best regards - Thijs
Thijs
Dev Team
Dev Team
 
Posts: 114
Joined: Fri Sep 10, 2010 6:28 pm

Re: GPIO status

Postby Dopi » Tue Jan 11, 2011 4:14 pm

Thijs wrote:Yes, it's quite a struggle and makes you wonder why (or what for), every now and then.

I also checked our GPIO map for completeness. Currently we have 143 pins correctly mapped and 17 pins to fix. For 5 pins I need to check the mapping (schematic vs source code). This sounds like a doable task for the coming days / weeks ... ;)

Cheers,
Dopi
Ad banners support the JetDroid forum. Please consider clicking them once in a while.
User avatar
Dopi
Dev Team
Dev Team
 
Posts: 926
Joined: Sun Aug 22, 2010 9:47 pm

Re: GPIO status

Postby Thijs » Tue Jan 11, 2011 7:05 pm

Dopi wrote:
Thijs wrote:Yes, it's quite a struggle and makes you wonder why (or what for), every now and then.

I also checked our GPIO map for completeness. Currently we have 143 pins correctly mapped and 17 pins to fix. For 5 pins I need to check the mapping (schematic vs source code). This sounds like a doable task for the coming days / weeks ... ;)

Cheers,
Dopi


That ain't to bad... let's go for 'days' :D

best regards - Thijs
Thijs
Dev Team
Dev Team
 
Posts: 114
Joined: Fri Sep 10, 2010 6:28 pm

Next

Return to JetKernel

Who is online

Users browsing this forum: No registered users and 1 guest

  • Advertisement
cron