From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Marcel Holtmann <marcel@holtmann.org>,
Gustavo Padovan <gustavo@padovan.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth@vger.kernel.org
Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Subject: Re: [PATCH v1] Bluetooth: hci_bcm: Support platform enumeration
Date: Sun, 26 Mar 2017 15:28:16 +0300 [thread overview]
Message-ID: <1490531296.708.3.camel@linux.intel.com> (raw)
In-Reply-To: <20170310122820.7584-1-andriy.shevchenko@linux.intel.com>
On Fri, 2017-03-10 at 14:28 +0200, Andy Shevchenko wrote:
> Until now the driver supports only ACPI enumeration. Nevertheless
> Intel Edison SoM has Broadcom Wi-Fi + BT chip and neither ACPI nor DT
> enumeration mechanism.
>
> Enable pure platform driver in order to support Intel Edison SoM.
>
Any comment on this?
> Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/bluetooth/hci_bcm.c | 50 ++++++++++++++++++++++++++++++----
> -----------
> 1 file changed, 33 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/bluetooth/hci_bcm.c b/drivers/bluetooth/hci_bcm.c
> index 5262a2077d7a..a26a4ca6968b 100644
> --- a/drivers/bluetooth/hci_bcm.c
> +++ b/drivers/bluetooth/hci_bcm.c
> @@ -697,28 +697,14 @@ static int bcm_resource(struct acpi_resource
> *ares, void *data)
> /* Always tell the ACPI core to skip this resource */
> return 1;
> }
> +#endif /* CONFIG_ACPI */
>
> -static int bcm_acpi_probe(struct bcm_device *dev)
> +static int bcm_platform_probe(struct bcm_device *dev)
> {
> struct platform_device *pdev = dev->pdev;
> - LIST_HEAD(resources);
> - const struct dmi_system_id *dmi_id;
> - const struct acpi_gpio_mapping *gpio_mapping =
> acpi_bcm_int_last_gpios;
> - const struct acpi_device_id *id;
> - int ret;
>
> dev->name = dev_name(&pdev->dev);
>
> - /* Retrieve GPIO data */
> - id = acpi_match_device(pdev->dev.driver->acpi_match_table,
> &pdev->dev);
> - if (id)
> - gpio_mapping = (const struct acpi_gpio_mapping *) id-
> >driver_data;
> -
> - ret = acpi_dev_add_driver_gpios(ACPI_COMPANION(&pdev->dev),
> - gpio_mapping);
> - if (ret)
> - return ret;
> -
> dev->clk = devm_clk_get(&pdev->dev, NULL);
>
> dev->device_wakeup = devm_gpiod_get_optional(&pdev->dev,
> @@ -755,6 +741,33 @@ static int bcm_acpi_probe(struct bcm_device *dev)
> return -EINVAL;
> }
>
> + return 0;
> +}
> +
> +#ifdef CONFIG_ACPI
> +static int bcm_acpi_probe(struct bcm_device *dev)
> +{
> + struct platform_device *pdev = dev->pdev;
> + LIST_HEAD(resources);
> + const struct dmi_system_id *dmi_id;
> + const struct acpi_gpio_mapping *gpio_mapping =
> acpi_bcm_int_last_gpios;
> + const struct acpi_device_id *id;
> + int ret;
> +
> + /* Retrieve GPIO data */
> + id = acpi_match_device(pdev->dev.driver->acpi_match_table,
> &pdev->dev);
> + if (id)
> + gpio_mapping = (const struct acpi_gpio_mapping *) id-
> >driver_data;
> +
> + ret = acpi_dev_add_driver_gpios(ACPI_COMPANION(&pdev->dev),
> + gpio_mapping);
> + if (ret)
> + return ret;
> +
> + ret = bcm_platform_probe(dev);
> + if (ret)
> + return ret;
> +
> /* Retrieve UART ACPI info */
> ret = acpi_dev_get_resources(ACPI_COMPANION(&dev->pdev->dev),
> &resources, bcm_resource, dev);
> @@ -789,7 +802,10 @@ static int bcm_probe(struct platform_device
> *pdev)
>
> dev->pdev = pdev;
>
> - ret = bcm_acpi_probe(dev);
> + if (has_acpi_companion(&pdev->dev))
> + ret = bcm_acpi_probe(dev);
> + else
> + ret = bcm_platform_probe(dev);
> if (ret)
> return ret;
>
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-03-26 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 12:28 [PATCH v1] Bluetooth: hci_bcm: Support platform enumeration Andy Shevchenko
2017-03-26 12:28 ` Andy Shevchenko [this message]
2017-03-27 14:01 ` Marcel Holtmann
2017-03-27 17:18 ` Andy Shevchenko
2017-03-27 18:00 ` Marcel Holtmann
2017-03-28 8:19 ` Andy Shevchenko
2017-03-28 11:11 ` Marcel Holtmann
2017-03-28 11:11 ` Marcel Holtmann
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=1490531296.708.3.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gustavo@padovan.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
/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