Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3765450imu; Mon, 28 Jan 2019 10:22:34 -0800 (PST) X-Google-Smtp-Source: ALg8bN7DH22uw1ttRkshtFv6CrxXkKuYlTHO6EMTuHYhKN3YFXNpAlsyVQLMyV7jD6JyVDlgkXll X-Received: by 2002:a63:960a:: with SMTP id c10mr20602410pge.106.1548699754225; Mon, 28 Jan 2019 10:22:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548699754; cv=none; d=google.com; s=arc-20160816; b=YhMHkbbIgJwRil7tIsXNFi7EK74OsyYGXNL5eSvzHB6tMcrSZMyQ/pk9sFLX8MvUPT cIU+Yr4BlsKMN6TsEGoxZfM9Onfg+TcTd2mywopGBVrLOtmiI1EKFJhYJ85euHP7/PMi vBPOaOwHpcLsJs2f3s3SJoVbqM5SNgaCti+UE2VGbC9GQs7VN98lrQbuLUU1pvMa7p+3 yep0St24YX3xIlapnd8DT/rRQX8Ra6L4vDjs+YUcu2k6hhlVydvblS5JMmFLGcyxxzyc BVAJl5RJOKVAQs5t1Wkb4L83nNPW20qNocfOKFiT0IYpwaUiZMX5NupB5H8f4wasOvrp UE6Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=HOa1GzVM/rBsuwAjwoGi6bmuQVSILLGp/ZxnGks2mfg=; b=i7q2ZfbIqqsfv0011hoStDvQ4r4n1KJZ2LHzgyvh+KySSQStWwI+6uISXC7J/Ci8D9 Ji9gMLsATUXiJQTIjWU2OoRY7YVjAR8zU0JXtfT6q1uuVX5RmCmoFks/U2nuKfXcIC1k P5AJv3Z36VGuwFHx2UtRLAHKjRZRygjqzCFvB9tnyzPN9p3jhRylIZ0FhDWbN9z18Jki c4bxBaI0+n7vh3UMKE7iJSVX6t3Pkab8z1NmTK2gK0PGcdEARVlyL22f2Pq+WpfpFNrh FEhDILuq3jS258q8j2sSyvODv6+MQ3hJ5bjLtr4NdQFT6a1gbL5FW6x6drrzEvaJ9xbS 3u6g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=ctiozCTD; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u25si31932764pgm.532.2019.01.28.10.22.18; Mon, 28 Jan 2019 10:22:34 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=ctiozCTD; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727128AbfA1SWA (ORCPT + 99 others); Mon, 28 Jan 2019 13:22:00 -0500 Received: from mail.kernel.org ([198.145.29.99]:59154 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726266AbfA1SV7 (ORCPT ); Mon, 28 Jan 2019 13:21:59 -0500 Received: from mail-qt1-f169.google.com (mail-qt1-f169.google.com [209.85.160.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 2A27C21741; Mon, 28 Jan 2019 18:21:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1548699718; bh=minqxleUCdZFINR50Zp2RJs/hYe3aH2rXsBNL59YXVI=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=ctiozCTDzdmDXWIAkACbpuv0pXLvi371XS/AujWzc8vLZlVrZZm2XQ0+EfEJBZ9rA H1Sm5Zmh7hL1oOYfs0iKhRLZc4UHUHtz0TmRMtk6G7CGD6BIjz6BmgBUWcBctgCBIO 4rrx3lehM7kDQhAvGFegrKSaJbBtIXf/2Ss+LPvg= Received: by mail-qt1-f169.google.com with SMTP id t13so19360407qtn.3; Mon, 28 Jan 2019 10:21:58 -0800 (PST) X-Gm-Message-State: AJcUukeS4ZgpMV5XQzQrj5EdlYa+lN8XpQJNZ5MEoq789RcbuHJzY7tA jWDYgaBgHKH+vqdDX8oFkiNAiqPc9cQ+D4XtNg== X-Received: by 2002:ac8:2d2b:: with SMTP id n40mr21710017qta.38.1548699717383; Mon, 28 Jan 2019 10:21:57 -0800 (PST) MIME-Version: 1.0 References: <20190124145309.21698-1-ben.whitten@lairdtech.com> <20190124145309.21698-4-ben.whitten@lairdtech.com> In-Reply-To: <20190124145309.21698-4-ben.whitten@lairdtech.com> From: Rob Herring Date: Mon, 28 Jan 2019 12:21:46 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v3 lora-next 3/4] dt-bindings: lora: sx125x: add clock bindings To: Ben Whitten Cc: =?UTF-8?Q?Andreas_F=C3=A4rber?= , David Miller , Mark Rutland , netdev , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , linux-lpwan@lists.infradead.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 24, 2019 at 8:54 AM Ben Whitten wrote: > > From: Ben Whitten > > The SX125x consumes a clock (FXOSC) ranging from 32 to 36 MHz as its main > XTAL. It may also consume a clock for the TX synthesizer or DAC input clock > (FCLK_IN). > If the radio is coupled with an SX130x the radio is therefor operating in > master mode and it may also provide a gated version of FXOSC clock for the > concentrator. In this case the concentrator is expecting a 32 MHz input > clock. > > In the example we connect fxosc to the "txco" clock source, represented by a > fixed clock. The radio also provides a clock output "fclk_out" for > consumption by the SX130x concentrator. > > Signed-off-by: Ben Whitten > --- > v2 -> v3: > * Name clock inputs and outputs > * Add FCLK_IN > v1 -> v2: > * Fixed incorrect usage of clock cells > * Fixed wording in commit and descriptions > * Dropped enforced clock names > --- > .../bindings/net/lora/semtech,sx125x.yaml | 33 +++++++++++++++++++ > 1 file changed, 33 insertions(+) > > diff --git a/Documentation/devicetree/bindings/net/lora/semtech,sx125x.yaml b/Documentation/devicetree/bindings/net/lora/semtech,sx125x.yaml > index fe2d2a23c28b..be45bcfd97be 100644 > --- a/Documentation/devicetree/bindings/net/lora/semtech,sx125x.yaml > +++ b/Documentation/devicetree/bindings/net/lora/semtech,sx125x.yaml > @@ -27,12 +27,41 @@ properties: > description: The chip select on the SPI bus or radio number in concentrator > , with radio A = 0 and radio B = 1. > > + clocks: > + maxItems: 2 > + description: Input clock (FXOSC) provider with output ranging from 32 MHz > + to 36 MHz. TX synthesizer or DAC input clock (FCLK_IN) provider with > + output ranging from 32 MHz to 36 MHz. > + > + clock-names: > + items: > + - const: fxosc > + - const: fclk_in The example has a single clock. Is that valid? If so, then you need to add minItems and maxItems. > + description: Input clock (FXOSC), TX synthesizer or DAC input clock > + (FCLK_IN) > + > + clock-output-names: > + items: > + - const: fclk_out > + description: Output clock (FCLK_OUT) name, clock is gated version of the > + input (FXOSC). Used in master mode operation. > + > + '#clock-cells': > + const: 0 > + > required: > - compatible > - reg > > examples: > - | > + tcxo: dummy32m { > + compatible = "fixed-clock"; > + clock-frequency = <32000000>; > + clock-output-names = "tcxo"; > + #clock-cells = <0>; > + }; > + > spi { > #address-cells = <1>; > #size-cells = <0>; > @@ -40,5 +69,9 @@ examples: > radio0: radio@0 { > compatible = "semtech,sx1257"; > reg = <0>; > + clocks = <&tcxo>; > + clock-names = "fxosc"; > + clock-output-names = "fclk_out"; > + #clock-cells = <0>; > }; > }; > -- > 2.17.1 >