devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Philippe Schenker <dev@pschenker.ch>
Cc: devicetree@vger.kernel.org,
	Philippe Schenker <philippe.schenker@toradex.com>,
	Fabio Estevam <festevam@gmail.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	NXP Linux Team <linux-imx@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] arm: dts: colibri-imx6ull: keep peripherals disabled
Date: Sat, 29 Oct 2022 09:03:18 +0800	[thread overview]
Message-ID: <20221029010318.GE125525@dragon> (raw)
In-Reply-To: <20221005133929.1243443-1-dev@pschenker.ch>

On Wed, Oct 05, 2022 at 03:39:26PM +0200, Philippe Schenker wrote:
> From: Philippe Schenker <philippe.schenker@toradex.com>
> 
> Toradex does provide device-tree overlays to enable certain evaluation
> hardware. Keep the buses disabled by default to be enabled again with
> overlays.
> 
> For customers including this device-tree this has also the advantage
> that the hardware we want by default running does not automatically
> enable signals on their end.
> 
> Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>

We idiomatically prefix i.MX arm DTS like 'ARM: dts: ...'  Please be
noted for the future patches.

Fixed prefix and applied the series.

Shawn

      parent reply	other threads:[~2022-10-29  1:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 13:39 [PATCH 1/4] arm: dts: colibri-imx6ull: keep peripherals disabled Philippe Schenker
2022-10-05 13:39 ` [PATCH 2/4] arm: dts: colibri-imx6ull: enable default peripherals Philippe Schenker
2022-10-05 13:39 ` [PATCH 3/4] arm: dts: colibri-imx6ull: add -hog to gpio hogs Philippe Schenker
2022-10-05 13:39 ` [PATCH 4/4] arm: dts: colibri-imx7: fix confusing naming Philippe Schenker
2022-10-29  1:03 ` Shawn Guo [this message]

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=20221029010318.GE125525@dragon \
    --to=shawnguo@kernel.org \
    --cc=dev@pschenker.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --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=philippe.schenker@toradex.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).