linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Rolf Eike Beer <eb@emlix.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] ACPI / platform: add IDs for Broadcom Bluetooth and GPS chips
Date: Fri, 16 May 2014 14:51:56 +0300	[thread overview]
Message-ID: <20140516115155.GA10355@xps8300> (raw)
In-Reply-To: <1965215.zv0fvIVbHP@devpool02>

Hi,

On Thu, May 15, 2014 at 09:50:45AM +0200, Rolf Eike Beer wrote:
> Heikki Krogerus wrote:
> > > the AzureWave AW-AH691A module looks similar to me, it is identified as
> > > AAM4752. However if I add it to that list I don't get anything, even with
> > > the brcmfmac driver loaded. Is there any magic missing?
> > 
> > Which machine are you using? Could you attach the output of acpidump?
> 
> this is an Aava Inari 8 tablet (pre-release hardware). To avoid spamming the 
> list with the same DSDT twice, please have a look at my reply in the thread 
> "Re: [Patch V2 0/9] I2C ACPI operation region handler support".

Okay. So the AAM4752 is a GPS module attached to the UART. You need
to add the HID to the list in drivers/acpi/acpi_platform.c and also to
the driver, which is net/rfkill/rfkill-gpio.c in this case.

But that will only give you a rfkill switch that allows you to
control the enable signal of the chip via rfkill framework. The actual
communication with the chip happens from userspace via /dev/ttySx
(/dev/ttyS2 on your board), just like with any other peripheral
attached to UARTs. So no drivers needed for that.


Br,

-- 
heikki

  reply	other threads:[~2014-05-16 11:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 11:59 [PATCH] ACPI / platform: add IDs for Broadcom Bluetooth and GPS chips Heikki Krogerus
2014-05-13 13:14 ` Rolf Eike Beer
2014-05-14 11:56   ` Heikki Krogerus
2014-05-15  7:50     ` Rolf Eike Beer
2014-05-16 11:51       ` Heikki Krogerus [this message]
2014-05-19 22:58 ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140516115155.GA10355@xps8300 \
    --to=heikki.krogerus@linux.intel.com \
    --cc=eb@emlix.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).