mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH v4 2/3] dt-bindings: arm: altera: add Draeger M48 Module
Date: Mon, 14 Sep 2026 19:53:18 +0300	[thread overview]
Message-ID: <20260914165318.GA10966@cabron.k.g> (raw)
In-Reply-To: <565e4f26-69c3-4129-b4f1-29d67c381591@kernel.org>

On 26-09-13 16:20:54, Krzysztof Kozlowski wrote:
> On 13/09/2026 15:32, Petko Manolov wrote:
> > On 26-09-13 11:18:16, Krzysztof Kozlowski wrote:
> >> On Fri, Sep 11, 2026 at 06:07:53PM +0300, Petko Manolov wrote:
> >>> Add DT compatible string for Draeger's M48 CPU Module, an i.MX6
> >>> based board.
> >>
> >> Sashiko comment is valid.
> > 
> > Sashiko doesn't know that this is indeed an i.MX6q board with the Altera FPGA as
> > a separate module, that is secondary to the NXP SoC.
> > 
> > What do you want me to put in the commit message so that everyone is happy?
> 
> Your commit msgs for bindings and DTS should explain the hardware and with the
> current explanation this is just so incomplete that basically wrong. i.mx6 is

Incomplete - yes, but who cares.  The only consumer is Draeger and they know
better than anyone else what the board looks like and what it is for.

Wrong - how?

> completely different vendor. Altera FPGA does not make it Altera SoCFPGA,
> these are two different things. If Linux runs on iMX6, then what are you
> describing here? DTS which never is going to be loaded because there is no
> SocFPGA?

I'm no Draeger employee, but i've been told that both the i.MX6 and the FPGA are
running Linux (both chips are on the same physical board) and are monitoring
each other's health.  Apart from doing whatever whatever their primary task is.
Whichever fails, the other guy takes over on the fly. This is a medical device
so full redundancy is a must.

So, again and in order to save everyone's time, please elaborate (preferably
with an existing example) whatever it is that you expect to see in the cover
letter and the commit messages.


		Petko

  reply	other threads:[~2026-09-14 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 15:07 [PATCH v4 0/3] arm: dts: altera: add Draeger M48 CPU Module Petko Manolov
2026-09-11 15:07 ` [PATCH v4 1/3] dt-bindings: vendor-prefixes: add Draeger AG Petko Manolov
2026-09-11 15:07 ` [PATCH v4 2/3] dt-bindings: arm: altera: add Draeger M48 Module Petko Manolov
2026-09-13  9:18   ` Krzysztof Kozlowski
2026-09-13 13:32     ` Petko Manolov
2026-09-13 14:20       ` Krzysztof Kozlowski
2026-09-14 16:53         ` Petko Manolov [this message]
2026-09-11 15:07 ` [PATCH v4 3/3] arm: dts: altera: add Draeger M48 CPU Module 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=20260914165318.GA10966@cabron.k.g \
    --to=petko.manolov@konsulko.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®