From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "Gustavo F. Padovan" <gustavo@padovan.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Bluez mailing list <linux-bluetooth@vger.kernel.org>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>
Subject: Re: [PATCH v1] Bluetooth: hci_bcm: Support platform enumeration
Date: Tue, 28 Mar 2017 11:19:53 +0300 [thread overview]
Message-ID: <1490689193.708.24.camel@linux.intel.com> (raw)
In-Reply-To: <F9B2AE00-087D-4F2F-9F74-30CF991AF641@holtmann.org>
On Mon, 2017-03-27 at 20:00 +0200, Marcel Holtmann wrote:
> Hi Andy,
>
> > > > 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.
> > >
> > > explain to me what this the case. Didn’t we enabled also DT for
> > > Edison? And I assumed in general we planned to move away from
> > > platform
> > > drivers in favour of DT.
> >
> > Nope. It's SFI based device which basically means platform data
> > only.
>
> hold on, but SFI can be enumerated like ACPI. What am I missing here?
You missed a whole point. :-)
SFI so useless that you may just forget about it.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-03-28 8:19 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
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 [this message]
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=1490689193.708.24.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