[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181218145853.GA15352@bogus>
Date: Tue, 18 Dec 2018 08:58:53 -0600
From: Rob Herring <robh@...nel.org>
To: Chen-Yu Tsai <wens@...e.org>
Cc: Marcel Holtmann <marcel@...tmann.org>,
Johan Hedberg <johan.hedberg@...il.com>,
Mark Rutland <mark.rutland@....com>,
Maxime Ripard <maxime.ripard@...tlin.com>,
Chen-Yu Tsai <wens@...e.org>,
Loic Poulain <loic.poulain@...il.com>,
linux-bluetooth@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Ondrej Jirman <megous@...ous.com>
Subject: Re: [PATCH v3 01/15] dt-bindings: net: broadcom-bluetooth: Fix
external clock names
On Mon, 17 Dec 2018 12:04:35 +0800, Chen-Yu Tsai wrote:
> The Broadcom Bluetooth controllers can take up to two external clocks:
> an external frequency reference, substituting the main crystal, and a
> LPO clock at 32.768 kHz substituting the internal LPO clock.
>
> In particular, the external LPO clock must be used when the controller
> does not have NVRAM connected, and the main reference frequency is not
> the default 20 MHz. This is described in detail in the datasheet.
>
> The original "extclk" clock name is ambiguous as to which of these it
> refers to, and some designs might even require both.
>
> This patch deprecates the existing name, and adds "txco" and "lpo".
>
> Tested-by: Ondrej Jirman <megous@...ous.com>
> Signed-off-by: Chen-Yu Tsai <wens@...e.org>
> ---
> .../devicetree/bindings/net/broadcom-bluetooth.txt | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
Reviewed-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists