Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3768582imu; Mon, 28 Jan 2019 10:26:03 -0800 (PST) X-Google-Smtp-Source: ALg8bN6SRwR89c3tjFt1DhOSoeeuxFHsuRBYR9Qvh/6SyFZVqQOTOBtUVZvp/rllnsza4X2C7Q1/ X-Received: by 2002:a63:7512:: with SMTP id q18mr19161458pgc.231.1548699963669; Mon, 28 Jan 2019 10:26:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548699963; cv=none; d=google.com; s=arc-20160816; b=dITZRDxH2FTESDsTEJF0ulXE2f9Q26tAmXr2jQz27E/3dw/qadKjs/tGBxWC/E5HVx PS19A2vbK4CDD9Tp9Cgak681b8eUkDyhBFrpbV3lsu+XK5NuraiXkyWXd0LH9+OSxzeN P4quIUNRfJJ6dRO9QhKJ25BxANZlnMdiW4SEFRjrMMgpxcqRuLjuJBDK79gBKZEEMPvu 1S0cCN/JOqNjWLTSU24mloiwbO7gl+MIlop01DWKhchZMrWDG/o4R8g8E4nUkJkwwS/w iza2yz9m2mDEjq3dSKlRBBUrxbdA0wXNBZk2aRDh1Rxsl4dNwMo4bbjmtMugH8Oly7a3 jWow== 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=eQxSHNJ4olnvcWtDtpGZkuZZUNYu3Izl5dOnfNzAwyw=; b=p/50EzN1n1Ulp5mLgo9J6Gl25Q8IvJfQMyi5t1TcbNzOr5p/m/jPBO86qN0MUS9mwh NYxGjRo02RipIwJ82ClcEraCxBKEDkdXTK4kf0KSJ2NgaLWvCRUERc5aPGCvqwWOBcqp Ba3YC0GEE6f+rJezPMOHbeKKdJ+L8xnG+gagKqjdHxmHHLxlDtAlzUz1uSjqiH8m2nW3 LC+652nU83XwsHIx46gmLmQrnVV8RQzXtQewiVLsDGhFR/IU4m0JE/A4iNjAw4JxOg/3 sE/Zqr+l/27PkSxYwOZMRcGuEi7fYNFlNhZujaNyNgkuxTVZpmTc/sfwKEClREiEdu7J 4DPQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=TQz4bvm0; 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 d82si9393804pfj.124.2019.01.28.10.25.47; Mon, 28 Jan 2019 10:26:03 -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=TQz4bvm0; 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 S1727552AbfA1SX6 (ORCPT + 99 others); Mon, 28 Jan 2019 13:23:58 -0500 Received: from mail.kernel.org ([198.145.29.99]:32772 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726906AbfA1SX5 (ORCPT ); Mon, 28 Jan 2019 13:23:57 -0500 Received: from mail-qt1-f171.google.com (mail-qt1-f171.google.com [209.85.160.171]) (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 CDF5321741; Mon, 28 Jan 2019 18:23:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1548699837; bh=wwF4P/+YTPiLR9mrP7tHgk5BSl12r3VGfZLXwRzAEG0=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=TQz4bvm0NbGm8relDCwvrm4CgO/KoYlPhpba5I9DduvPvsbl6SWQ6xQ/0G+94oP0G K484Szvm1uNDL8Q4glf1KdEPh6t3DbIfh98OXrP6TMHWQ2fgR/78mIh6RQGveNuxpt bXKh7S8glyHppkxeN8LUkL9901U1zmzNADFrD7IA= Received: by mail-qt1-f171.google.com with SMTP id e5so19293230qtr.12; Mon, 28 Jan 2019 10:23:56 -0800 (PST) X-Gm-Message-State: AJcUukcLhChiuoMMl15XKM2MxFScbQMS6i9uT2BPws+BSGi975EdDXDl Ql2PRF0LNlGvPNOKqKJeJ6yAgDFWG9ynydo1HA== X-Received: by 2002:aed:3ecf:: with SMTP id o15mr22699276qtf.26.1548699836063; Mon, 28 Jan 2019 10:23:56 -0800 (PST) MIME-Version: 1.0 References: <20190124145309.21698-1-ben.whitten@lairdtech.com> <20190124145309.21698-5-ben.whitten@lairdtech.com> In-Reply-To: <20190124145309.21698-5-ben.whitten@lairdtech.com> From: Rob Herring Date: Mon, 28 Jan 2019 12:23:45 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v3 lora-next 4/4] dt-bindings: lora: sx130x: 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 SX130x family consumes two clocks, a 32 MHz clock provided by a > connected IQ transceiver, and a 133 MHz high speed clock. > It also provides a 32 MHz clock out to the radio in the TX path. > > In the example we connect the concentrator to a fixed clock providing > the 133 MHz high speed clock, and we connect to a connected transceiver > 32 MHz clock. > > A radio in the TX path is also connected to the 32 MHz clock out from the > concentrator. > > The connected radios are both fed from a fixed 32 MHz clock, with only > one being the clock source back to the SX130x concentrator. > > Signed-off-by: Ben Whitten > --- > v2 -> v3: > * Name input clocks specifically > * Add output clock for radio in TX path > v1 -> v2: > * Fixed incorrect usage of clock cells > * Fixed wording in commit and descriptions > --- > .../bindings/net/lora/semtech,sx130x.yaml | 52 ++++++++++++++++++- > 1 file changed, 51 insertions(+), 1 deletion(-) Other than the issue on patch 3 that affects the example here, Reviewed-by: Rob Herring