From: "Andreas Färber" <afaerber@suse.de>
To: Ben Whitten <ben.whitten@gmail.com>
Cc: linux-lpwan@lists.infradead.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH lora-next 2/4] dt-bindings: lora: sx125x: add basic documentation
Date: Sat, 12 Jan 2019 04:48:44 +0100 [thread overview]
Message-ID: <20191f9a-46b9-2ad1-d56b-7af302589f93@suse.de> (raw)
In-Reply-To: <20190108084132.10214-2-ben.whitten@gmail.com>
Am 08.01.19 um 09:41 schrieb Ben Whitten:
> The sx125x family are IQ radio transceivers from Semtech configured over
> SPI, they are typically connected to an sx130x series concentrator however
> may be connected to a host directly.
"SX125x" and "SX130x"
>
> Required properties include the radio number of the host or concentrator
> bus.
>
> Signed-off-by: Ben Whitten <ben.whitten@gmail.com>
> ---
> .../bindings/lora/semtech,sx125x.yaml | 45 +++++++++++++++++++
> 1 file changed, 45 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/lora/semtech,sx125x.yaml
>
> diff --git a/Documentation/devicetree/bindings/lora/semtech,sx125x.yaml b/Documentation/devicetree/bindings/lora/semtech,sx125x.yaml
> new file mode 100644
> index 000000000000..5eadec860b70
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/lora/semtech,sx125x.yaml
> @@ -0,0 +1,45 @@
> +# SPDX-License-Identifier: GPL-2.0
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/lora/semtech,sx125x.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Semtech IQ modulator/de-modulator transeiver
> +
> +maintainers:
> + - Andreas Färber <afaerber@suse.de>
> + - Ben Whitten <ben.whitten@gmail.com>
> +
> +description: |
> + The sx125x family are highly integrated RF front-end to digital I and Q
> + modulator/demodulator Multi-PHY mode transceiver capable of supporting
> + multiple constant and non-constant envelope modulation schemes.
"SX125x"
"are ... transceivers"
> +
> +properties:
> + compatible:
> + items:
> + - enum:
> + - semtech,sx1255
> + - semtech,sx1257
> + - semtech,sx1258
Do we need all three? Probably yes for the concentrator to make decisions?
> +
> + reg:
> + maxItems: 1
> + description: The chip select on the SPI bus or radio number in concentrator.
", with radio A = 0 and radio B = 1."
> +
> + spi-max-frequency:
> + maximum: 10000000
> + default: 8000000
> + description: The frequency of the SPI communication to the radio,
> + in Hz. Maximum SPI frequency is 10MHz.
If on the concentrator's SPI bus then this is unused. You don't mark it
required below, so maybe add a textual note?
> +
> +required:
> + - compatible
> + - reg
> +
> +examples:
> + - |
> + radio0: lora@0 {
> + compatible = "semtech,sx1257";
> + reg = <0>;
> + };
If you compare my sx127x implementation, should we prepare a
"radio-frequency" (or "radio-center-frequency") property for the
antenna, to preconfigure the driver during probe? Contents would then be
<868000000>, for example.
Thanks,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2019-01-12 3:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 8:41 [PATCH lora-next 1/4] dt-bindings: lora: sx130x: add basic documentation Ben Whitten
2019-01-08 8:41 ` [PATCH lora-next 2/4] dt-bindings: lora: sx125x: " Ben Whitten
2019-01-12 3:48 ` Andreas Färber [this message]
2019-01-16 17:22 ` Ben Whitten
2019-01-08 8:41 ` [PATCH lora-next 3/4] dt-bindings: lora: sx125x: add clock bindings Ben Whitten
2019-01-12 4:14 ` Andreas Färber
2019-01-08 8:41 ` [PATCH lora-next 4/4] dt-bindings: lora: sx130x: " Ben Whitten
2019-01-12 4:44 ` Andreas Färber
2019-01-12 3:37 ` [PATCH lora-next 1/4] dt-bindings: lora: sx130x: add basic documentation Andreas Färber
2019-01-16 16:41 ` Ben Whitten
2019-01-21 19:14 ` Rob Herring
2019-01-21 19:27 ` Rob Herring
2019-01-21 20:11 ` Rob Herring
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=20191f9a-46b9-2ad1-d56b-7af302589f93@suse.de \
--to=afaerber@suse.de \
--cc=ben.whitten@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lpwan@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).