On Thu, Sep 29, 2011 at 8:27 PM, parth shah <parthmshah2...@gmail.com> wrote: > Hello Pavan, > > We don't have the file board-sholes.c > > We have mx51_bbg.c which is completely different from board-sholes.c.
Ok, If this is the file where in you intend to add platform devices, Then yes this seems alright. > I provided you git for imx515 kernel. According to that which file do i have > to modified? > > Regards, > Parth > > > On Wed, Sep 28, 2011 at 8:20 PM, Pavan Savoy <pavan.sa...@gmail.com> wrote: >> >> On Wed, Sep 28, 2011 at 10:00 PM, parth shah <parthmshah2...@gmail.com> >> wrote: >> > Hello Pavan, >> > >> > I pointed the BSP of imx515 in my last mail. >> >> Hey, I just assumed it would a cute little kernel git repo which I can >> add remote and provide a quick wl127x-rfkill for it. >> But 'alas, it is a just 610MB something binary which has some weird >> kernel.git folder which just has patches :( >> >> > Can you provide me right wl127x_rfkill Platform >> > data structure for imx515? >> >> Anyway, I would still like to help in anyway possible. >> If you can point me out any problems compiling a wl127x-rfkill for >> your kernel version. >> >> > We also have another project in which we are planning to use WL1271. Let >> > me >> > know if there is more information required from my side. >> >> Also, the platform data is pretty much platform specific. >> There are a few examples here where the platform data is populated and >> the platform device being added, >> >> >> http://git.omapzoom.org/?p=kernel/omap.git;a=blob;f=arch/arm/mach-omap2/board-sholes.c;h=4f19dc1fbfad698307edf529ef0e68ac8d2d4aa2;hb=refs/heads/android-omap-2.6.32 >> >> static struct wl127x_rfkill_platform_data sholes_wl1271_pdata = { >> 1218 .bt_nshutdown_gpio = SHOLES_WL1271_NSHUTDOWN_GPIO, >> 1219 .fm_enable_gpio = -1, >> 1220 .bt_hw_init = sholes_wl1271_init, >> 1221 .bt_hw_release = sholes_wl1271_release, >> 1222 .bt_hw_enable = sholes_wl1271_enable, >> 1223 .bt_hw_disable = sholes_wl1271_disable, >> 1224 }; >> The SHOLES_WL1271_NSHUTDOWN_GPIO should be BT_EN gpio on your platform. >> >> & the platform device is added here, >> static void __init sholes_bt_init(void) >> 1244 { >> 1245 /* Mux setup for Bluetooth chip-enable */ >> 1246 omap_cfg_reg(T3_34XX_GPIO179); >> 1247 >> 1248 /* Mux setup for BT wake GPIO and hostwake GPIO */ >> 1249 omap_cfg_reg(AF21_34XX_GPIO8_OUT); >> 1250 omap_cfg_reg(W7_34XX_GPIO178_DOWN); >> 1251 >> 1252 platform_device_register(&sholes_wl1271_device); >> 1253 platform_device_register(&sholes_wl1271_test_device); >> 1254 } >> >> >> > Regards, >> > Parth >> > >> > >> > On Tue, Sep 27, 2011 at 5:59 AM, Pavan Savoy <pavan.sa...@gmail.com> >> > wrote: >> >> >> >> On Tue, Sep 27, 2011 at 2:45 AM, parth shah <parthmshah2...@gmail.com> >> >> wrote: >> >> > Hi Pavan, >> >> > >> >> > Thanks for this information. >> >> > >> >> > I did not have wl127x-rfkill.c in mx515 BSP so i included it from >> >> > http://gitorious.org . >> >> > >> >> > Now i need to change so many files in my BSP to accommodate >> >> > wl127x-rfkill.c. >> >> > I modified rfkill.h which was there in BSP. >> >> > >> >> > After then i'm getting errors in arch/arm/mach-mx5/mx53_smd_rfkill.c. >> >> > >> >> > Is there any guide that i can follow or is there anything wrong am i >> >> > doing >> >> > here? >> >> >> >> Nope, No guide as such. >> >> The only thing needed in the BSP is the right wl127x_rfkill Platform >> >> data structure, which has 1 important gpio called the nshutdown gpio. >> >> >> >> In case you need more details, point me out to the BSP code of >> >> yours... I can have a look... >> >> >> >> >> >> > Regards, >> >> > Parth >> >> > >> >> > On Sat, Sep 24, 2011 at 7:12 AM, Pavan Savoy <pavan.sa...@gmail.com> >> >> > wrote: >> >> >> >> >> >> On Sat, Sep 24, 2011 at 5:43 AM, parth shah >> >> >> <parthmshah2...@gmail.com> >> >> >> wrote: >> >> >> > Hello Pavan, >> >> >> > >> >> >> > I'm having problem reading Data back using read_hci_event(). i'm >> >> >> > using >> >> >> > WL1271 from TI. >> >> >> > >> >> >> > I got the response from TI saying "BT_EN should be drive high when >> >> >> > setting >> >> >> > up UART while kernel is loading? " >> >> >> > Also we are using 2.6.35 kernel version. >> >> >> >> >> >> You can make use of the wl127x-rfkill reference driver that comes >> >> >> along with android kernel (not vanilla). >> >> >> Check out drivers/misc/wl127x-rfkill.c - This is a little driver >> >> >> that >> >> >> exposes the GPIO via an rfkill interface. >> >> >> >> >> >> So, to drive high the BT_EN gpio (say GPIO number 100) - You need to >> >> >> have platform data into the wl127x-rfkill to have nshut_down as 100. >> >> >> Upon probe, you can toggle the gpio from user-space via echo 1 > >> >> >> /sys/class/rfkill/rfkill0/state. >> >> >> >> >> >> >> >> >> > How can i do that? >> >> >> > Regards, >> >> >> > Parth >> >> >> > >> >> >> > On Mon, Sep 19, 2011 at 7:24 PM, Pavan Savoy >> >> >> > <pavan.sa...@gmail.com> >> >> >> > wrote: >> >> >> >> >> >> >> >> On Mon, Sep 19, 2011 at 7:50 PM, parth shah >> >> >> >> <parthmshah2...@gmail.com> >> >> >> >> wrote: >> >> >> >> > Hello Friends, >> >> >> >> > >> >> >> >> > I have 3 UART on my board. i'm usinf UART2 for Bluetooth. >> >> >> >> > >> >> >> >> > How can i mapped that UART to Bluez stack so that i can run >> >> >> >> > hciattach >> >> >> >> > commad? >> >> >> >> >> >> >> >> hciattach takes command line arguments for the UART in use, like >> >> >> >> hciattach /dev/ttyS1 => if UART2. >> >> >> >> >> >> >> >> > Also which driver does BT UART use in general? >> >> >> >> >> >> >> >> Also depends on the manufacturer argument for the hciattach, If >> >> >> >> no >> >> >> >> specific arg and "any" is used, hci_h4.c working along with >> >> >> >> hci_ldisc >> >> >> >> is used (drivers/bluetooth/ directory). >> >> >> >> >> >> >> >> > >> >> >> >> > Regards, >> >> >> >> > Parth >> >> >> >> > >> >> >> >> > -- >> >> >> >> > unsubscribe: android-kernel+unsubscr...@googlegroups.com >> >> >> >> > website: http://groups.google.com/group/android-kernel >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> --Pavan Savoy >> >> >> >> >> >> >> >> -- >> >> >> >> unsubscribe: android-kernel+unsubscr...@googlegroups.com >> >> >> >> website: http://groups.google.com/group/android-kernel >> >> >> > >> >> >> > -- >> >> >> > unsubscribe: android-kernel+unsubscr...@googlegroups.com >> >> >> > website: http://groups.google.com/group/android-kernel >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> --Pavan Savoy >> >> >> >> >> >> -- >> >> >> unsubscribe: android-kernel+unsubscr...@googlegroups.com >> >> >> website: http://groups.google.com/group/android-kernel >> >> > >> >> > -- >> >> > unsubscribe: android-kernel+unsubscr...@googlegroups.com >> >> > website: http://groups.google.com/group/android-kernel >> >> >> >> >> >> >> >> -- >> >> --Pavan Savoy >> >> >> >> -- >> >> unsubscribe: android-kernel+unsubscr...@googlegroups.com >> >> website: http://groups.google.com/group/android-kernel >> > >> > -- >> > unsubscribe: android-kernel+unsubscr...@googlegroups.com >> > website: http://groups.google.com/group/android-kernel >> >> >> >> -- >> --Pavan Savoy >> >> -- >> unsubscribe: android-kernel+unsubscr...@googlegroups.com >> website: http://groups.google.com/group/android-kernel > > -- > unsubscribe: android-kernel+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-kernel -- --Pavan Savoy -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
