From: Petko Manolov <petko.manolov@konsulko.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
dinguyen@kernel.org, arnemaximilian.richter@draeger.com,
martynas.grybauskas@draeger.com
Subject: Re: [PATCH v6 2/3] dt-bindings: arm: altera: add Draeger M48 Module
Date: Sun, 20 Sep 2026 10:23:43 +0300 [thread overview]
Message-ID: <20260920072343.GB7878@cabron.k.g> (raw)
In-Reply-To: <20260918-robust-spotted-orangutan-4b669c@quoll>
On 26-09-18 13:55:58, Krzysztof Kozlowski wrote:
> On Thu, Sep 17, 2026 at 07:31:55PM +0300, Petko Manolov wrote:
> > Add DT compatible string for Draeger's M48 CPU Module that is also based on
> > Altera SoCFPGA.
>
> CPU modules almost never can be alone, thus this is incomplete. You need the
> final board compatible. SoM could be a fallback. See NXP bindings how it is
> doing for example.
Module is perhaps not the best of choice for this board, but to avoid duplicity
please read my next reply.
Petko
next prev parent reply other threads:[~2026-09-20 7:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 16:31 [PATCH v6 0/3] arm: dts: altera: add Draeger M48 CPU Module Petko Manolov
2026-09-17 16:31 ` [PATCH v6 1/3] dt-bindings: vendor-prefixes: add Draeger AG Petko Manolov
2026-09-18 11:54 ` Krzysztof Kozlowski
2026-09-17 16:31 ` [PATCH v6 2/3] dt-bindings: arm: altera: add Draeger M48 Module Petko Manolov
2026-09-18 11:55 ` Krzysztof Kozlowski
2026-09-20 7:23 ` Petko Manolov [this message]
2026-09-21 7:42 ` Petko Manolov
2026-09-21 14:11 ` Krzysztof Kozlowski
2026-09-24 6:48 ` Petko Manolov
2026-09-17 16:31 ` [PATCH v6 3/3] arm: dts: altera: add Draeger M48 CPU Module Petko Manolov
2026-09-17 16:43 ` sashiko-bot
2026-09-18 11:57 ` Krzysztof Kozlowski
2026-09-20 7:59 ` Petko Manolov
2026-09-20 9:52 ` Krzysztof Kozlowski
2026-09-21 9:06 ` Petko Manolov
2026-09-21 14:16 ` Krzysztof Kozlowski
2026-09-24 6:48 ` Petko Manolov
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=20260920072343.GB7878@cabron.k.g \
--to=petko.manolov@konsulko.com \
--cc=arnemaximilian.richter@draeger.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martynas.grybauskas@draeger.com \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.