[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180921164541.GX22824@google.com>
Date: Fri, 21 Sep 2018 09:45:41 -0700
From: Matthias Kaehlcke <mka@...omium.org>
To: Sinan Kaya <okaya@...eaurora.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Marcin Wojtas <mw@...ihalf.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Marcel Holtmann <marcel@...tmann.org>,
Johan Hedberg <johan.hedberg@...il.com>,
linux-kernel@...r.kernel.org, linux-bluetooth@...r.kernel.org,
Balakrishna Godavarthi <bgodavar@...eaurora.org>,
Loic Poulain <loic.poulain@...aro.org>,
Brian Norris <briannorris@...omium.org>
Subject: Re: [PATCH 0/2] Add API to retrieve the Bluetooth Device Address
(BD_ADDR)
On Fri, Sep 21, 2018 at 01:25:45AM -0400, Sinan Kaya wrote:
> On 9/20/2018 7:19 PM, Matthias Kaehlcke wrote:
> > If the existing users populate a custom property with the BD address
> > in the bootloader you could roll out a bootloader change. You'd have
> > to make sure that bootloader and kernel match. The bootloader could
> > still populate the custom property to be compatible with 'old'
> > kernels.
>
> If there is no standard about the name of the property, this probably
> doesn't belong to property.c but should rather be hosted in bluetooth
> directory for consumption among the bluetooth drivers.
Well, there is a generic binding
(https://elixir.bootlin.com/linux/v4.18/source/Documentation/devicetree/bindings/net/bluetooth.txt),
the fact that there are drivers that aren't adhering to it doesn't
change that.
Powered by blists - more mailing lists