From: Conor Dooley <conor@kernel.org>
To: Bruno Thomsen <bruno.thomsen@gmail.com>
Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
Lars Alex Pedersen <lapeddk@gmail.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Tony Lindgren <tony@atomide.com>,
Roger Quadros <rogerq@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Andreas Kemnade <andreas@kemnade.info>,
Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: [PATCH 1/2] ARM: dts: ti/omap: am335x: add kamstrup emperor platform
Date: Wed, 18 Mar 2026 17:41:19 +0000 [thread overview]
Message-ID: <20260318-broadband-defiling-11dffbb8f230@spud> (raw)
In-Reply-To: <20260318085420.7680-1-bruno.thomsen@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
On Wed, Mar 18, 2026 at 09:54:19AM +0100, Bruno Thomsen wrote:
> Device tree can be used on the following 3 products:
> - Kamstrup READy Concentrator 1M (RC1M)
> - Kamstrup READy Concentrator 2M (RC2M)
> - Kamstrup READy Concentrator 2C (RC2C)
>
> Concentrators are used as 868MHz gateway for heat, cooling and water
> meters using wM-Bus, Kamstrup LinkIQ or OMS LPWAN communication protocols.
>
> RC1M only support one way communication (Rx only) where RC2M and RC2C
> support full two way communication (Rx/Tx) with meters.
>
> Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
> Co-developed-by: Lars Alex Pedersen <lapeddk@gmail.com>
> Signed-off-by: Lars Alex Pedersen <lapeddk@gmail.com>
Patch order is wrong here btw, binding before user please.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-03-18 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 8:54 [PATCH 1/2] ARM: dts: ti/omap: am335x: add kamstrup emperor platform Bruno Thomsen
2026-03-18 8:54 ` [PATCH 2/2] dt-bindings: omap: add kamstrup am335x " Bruno Thomsen
2026-03-18 17:40 ` Conor Dooley
2026-03-18 17:41 ` Conor Dooley [this message]
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=20260318-broadband-defiling-11dffbb8f230@spud \
--to=conor@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=bruno.thomsen@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lapeddk@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=tony@atomide.com \
/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