mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michal Suchánek" <msuchanek@suse.de>
To: Maxime Ripard <maxime@cerno.tech>
Cc: linux-arm-kernel@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
	Ondrej Jirman <megous@megous.com>,
	Corentin Labbe <clabbe@baylibre.com>,
	Stefan Mavrodiev <stefan@olimex.com>,
	Icenowy Zheng <icenowy@aosc.io>,
	Georgii Staroselskii <georgii.staroselskii@emlid.com>,
	Bastian Germann <bage@linutronix.de>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: arm: sunxi: Fix Orange Pi Zero bindings
Date: Mon, 12 Oct 2020 20:04:02 +0200	[thread overview]
Message-ID: <20201012180402.GT29778@kitsune.suse.cz> (raw)
In-Reply-To: <20201012144753.mdxdacp7ctxxhhl2@gilmour.lan>

On Mon, Oct 12, 2020 at 04:47:53PM +0200, Maxime Ripard wrote:
> On Thu, Oct 08, 2020 at 08:40:06PM +0200, Michal Suchanek wrote:
> > There are two models of Orange Pi zero which are confusingly marketed
> > under the same name. Old model comes without a flash memory and current
> > model does have a flash memory. Add bindings for each model.
> > 
> > Signed-off-by: Michal Suchanek <msuchanek@suse.de>
> 
> Unfortunately, changing a compatible or a DT filename is not an option

So how do you handle the situation when you find out that there are two
different devices marketed under the same name?

Surely the device tree is labaled by the device name but now you need
two device trees that describe the two devices.

Thanks

Michal

  reply	other threads:[~2020-10-12 18:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08 18:40 [PATCH 1/2] ARM: dts: sun8i: h2+: Fix Orange Pi Zero device description Michal Suchanek
2020-10-08 18:40 ` [PATCH 2/2] dt-bindings: arm: sunxi: Fix Orange Pi Zero bindings Michal Suchanek
2020-10-12 14:47   ` Maxime Ripard
2020-10-12 18:04     ` Michal Suchánek [this message]
2020-10-12 20:03       ` Ondřej Jirman

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=20201012180402.GT29778@kitsune.suse.cz \
    --to=msuchanek@suse.de \
    --cc=bage@linutronix.de \
    --cc=clabbe@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=georgii.staroselskii@emlid.com \
    --cc=icenowy@aosc.io \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime@cerno.tech \
    --cc=megous@megous.com \
    --cc=robh+dt@kernel.org \
    --cc=stefan@olimex.com \
    --cc=wens@csie.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®