From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
Marco Felsch <m.felsch@pengutronix.de>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, shawnguo@kernel.org, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com, marex@denx.de,
frieder.schrempf@kontron.de
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] dt-bindings: arm: fsl: fix DEBIX binding
Date: Wed, 5 Jul 2023 11:37:15 +0200 [thread overview]
Message-ID: <2d9b2341-84ca-d152-8a42-90b815c66125@linaro.org> (raw)
In-Reply-To: <61e9e380-dcb0-4dd4-562d-bffea2da5097@pengutronix.de>
On 05/07/2023 11:28, Ahmad Fatoum wrote:
>>> + items:
>>> + - enum:
>>> + - polyhex,imx8mp-debix-model-a # Polyhex Debix Model A Board
>>> + - const: polyhex,imx8mp-debix # Polyhex Debix boards
>>
>> Same comments as for patch #2. I think this should be rather deprecated
>> - not a good pattern.
>
> The middle compatible was my suggestion, because there's also the Debix Model
> B Standard and Model B SE, which is the same board, but different SoC variant:
>
> Model A: Commercial Temperature Grade
> Model B Standard: Industrial Temperature Grade
> Model B SE: Industrial Temperature Grate, but i.MX8MP Lite
> (No Neural/Video/Image accelerators).
>
> As everything outside the SoC is the same, I wanted a generic board
> compatible that bootloaders can match against. The SoMs should probably
> not reuse it, but I think it should be kept (perhaps renamed?) for the
> SBCs that don't utilize the Debix SoM.
The order of compatibles in patch two does not really look correct,
although it is accepted in some cases (e.g. Renesas). But anyway "Debix"
sounds like a vendor - they even have website - so compatible for all
boards seems too generic. This should be compatible for one specific
board. I understand that one board can have different SoMs (it is
common, just look at Toradex or Variscite), but it does not mean that
board should be unspecific.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-07-05 9:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 18:41 [PATCH 1/3] dt-bindings: arm: fsl: fix DEBIX binding Marco Felsch
2023-07-04 18:41 ` [PATCH 2/3] dt-bindings: arm: Add Polyhex DEBIX SOM A based boards Marco Felsch
2023-07-05 6:35 ` Krzysztof Kozlowski
2023-07-04 18:41 ` [PATCH 3/3] arm64: dts: freescale: Add DEBIX SOM A and SOM A I/O Board support Marco Felsch
2023-07-04 20:24 ` Fabio Estevam
2023-07-14 14:38 ` Marco Felsch
2023-07-05 6:37 ` Krzysztof Kozlowski
2023-07-14 14:40 ` Marco Felsch
2023-07-05 6:35 ` [PATCH 1/3] dt-bindings: arm: fsl: fix DEBIX binding Krzysztof Kozlowski
2023-07-05 8:28 ` Marco Felsch
2023-07-05 9:15 ` Krzysztof Kozlowski
2023-07-05 9:28 ` Ahmad Fatoum
2023-07-05 9:37 ` Krzysztof Kozlowski [this message]
2023-07-14 15:16 ` Marco Felsch
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=2d9b2341-84ca-d152-8a42-90b815c66125@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=a.fatoum@pengutronix.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=marex@denx.de \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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