The point behind GPIO pins is that they're generic. There's a multiplexer in the NIC which lets you map various GPIO pins to any internal function. So, you need to find which GPIO pins the bluetooth device is connected to. Once you know that, you can set the GPIO input/output multiplexer bits to give those GPIO pins the right BT behaviour. Adrian On 2 April 2013 08:20, sandeep suresh <sandeep.suresh@xxxxxxxxxxx> wrote: > Hello Mr.Adrian, > The card manufacturer like Compex systems for AR9287 has these pins > available on PCIe interface. But my query is AR9287 specific. AR9287 is a 76 > pin IC. GPIO4 is Pin22, GPIO5 is Pin23, GPIO6 is Pin 24 and so on. The > question is if I need to access COEX signals (WL_ACTIVE, BT_ACTIVE, > BT_PRIORITY, BT_FREQUENCY), on which of these 76 pins can I access them? > Please help. > > Regards > Sandeep. > > From: Adrian Chadd <adrian@xxxxxxxxxxx> > To: sandeep suresh <sandeep.suresh@xxxxxxxxxxx> > Cc: ath9k-devel <ath9k-devel@xxxxxxxxxxxxxxx>; > "linux-wireless@xxxxxxxxxxxxxxx" <linux-wireless@xxxxxxxxxxxxxxx> > Sent: Tuesday, 2 April 2013 8:23 PM > Subject: Re: AR9287; mapping between GPIOs and COEX pins > > It depends on what the card manufacturer has done. > > > > > Adrian > > On 2 April 2013 04:57, sandeep suresh <sandeep.suresh@xxxxxxxxxxx> wrote: >> Hello All, >> In AR9287, there are ten GPIOs and GPIO[0:3] are mapped to JTAG. >> Remaining GPIOs [4:9] are free. Can you please help me with the mapping of >> GPIO pins to COEX pins? That means which GPIO is connected to: >> a) WLAN_ACTIVE >> b)BT_PRIORITY >> c)BT_ACTIVE >> d)BT_FREQUENCY >> >> Thanks & regards >> Sandeep. > > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
