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: Thu, 24 Sep 2026 09:48:00 +0300 [thread overview]
Message-ID: <20260924064800.GC6325@bender.k.g> (raw)
In-Reply-To: <d6b1b369-a14b-4605-88cd-7ce348720111@kernel.org>
On 26-09-21 16:11:06, Krzysztof Kozlowski wrote:
> On 21/09/2026 09:42, Petko Manolov wrote:
> >
> > Can you please point me to such example?
>
> Any recent NXP-based SoM from their bindings.
I'm afraid i do not fully understand the above. However, it might be related to
the following.
There's another patch that is pending for submission and i just realized there
might be an issue with it. As you already know the M48 has two independent
cpus: socfpga and imx6. In my Draeger M48 socfpga patch i add "draeger,m48" to
Documentation/devicetree/bindings/arm/altera.yaml
Unfortunately "draeger,m48" is also the string that i was going to add to
Documentation/devicetree/bindings/arm/fsl.yaml. So the question is: is it
permitted to have the same string in two different architecture bindings?
If it is not then, what would be the best naming convention here? Something
like "draeger,m48-altera" and "draeger,m48-imx6" or some other combination?
Petko
next prev parent reply other threads:[~2026-09-24 6:48 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
2026-09-21 7:42 ` Petko Manolov
2026-09-21 14:11 ` Krzysztof Kozlowski
2026-09-24 6:48 ` Petko Manolov [this message]
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=20260924064800.GC6325@bender.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.