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?

Regards,
Parth

On Sat, Sep 24, 2011 at 7:12 AM, Pavan Savoy <[email protected]> wrote:

> On Sat, Sep 24, 2011 at 5:43 AM, parth shah <[email protected]>
> 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 <[email protected]>
> wrote:
> >>
> >> On Mon, Sep 19, 2011 at 7:50 PM, parth shah <[email protected]>
> >> 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: [email protected]
> >> > website: http://groups.google.com/group/android-kernel
> >>
> >>
> >>
> >> --
> >> --Pavan Savoy
> >>
> >> --
> >> unsubscribe: [email protected]
> >> website: http://groups.google.com/group/android-kernel
> >
> > --
> > unsubscribe: [email protected]
> > website: http://groups.google.com/group/android-kernel
>
>
>
> --
> --Pavan Savoy
>
> --
> unsubscribe: [email protected]
> website: http://groups.google.com/group/android-kernel
>

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-kernel

Reply via email to