From: Christoph Niedermaier <cniedermaier@dh-electronics.com>
To: Marek Vasut <marex@nabladev.com>,
Francesco Dolcini <francesco@dolcini.it>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
kernel <kernel@dh-electronics.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/2] ARM: dts: imx6ull-dhcor-maveo-box: Remove unused SPI device
Date: Thu, 22 Oct 2026 09:12:12 +0000 [thread overview]
Message-ID: <71d725ee47804205826bdda322fdfdb6@dh-electronics.com> (raw)
In-Reply-To: <d4b9c444-a848-4b4f-9273-1c832db45fc8@nabladev.com>
From: Marek Vasut <marex@nabladev.com>
Sent: Wednesday, October 21, 2026 8:56 PM
> On 10/21/26 8:37 PM, Francesco Dolcini wrote:
>> On Wed, Oct 21, 2026 at 07:19:30PM +0200, Marek Vasut wrote:
>>> On 10/21/26 3:44 PM, Christoph Niedermaier wrote:
>>>> On the maveo box, the SPI pins are connected to connector X10,
>>>> but no device is connected. The device "dhcom-board" was used
>>>> only to test the hardware, but was not removed afterward. So
>>>> remove this device to accurately represent the current hardware
>>>> configuration here.
>>>>
>>>> Fixes: 145e2732a5e9 ("ARM: dts: imx6ull-dhcor: Add Marantec maveo box")
>>>> Signed-off-by: Christoph Niedermaier <cniedermaier@dh-electronics.com>
>>>> ---
>>>> Cc: Rob Herring <robh@kernel.org>
>>>> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
>>>> Cc: Conor Dooley <conor+dt@kernel.org>
>>>> Cc: Frank Li <Frank.Li@nxp.com>
>>>> Cc: Sascha Hauer <s.hauer@pengutronix.de>
>>>> Cc: Pengutronix Kernel Team <kernel@pengutronix.de>
>>>> Cc: Fabio Estevam <festevam@gmail.com>
>>>> Cc: Marek Vasut <marex@nabladev.com>
>>>> Cc: devicetree@vger.kernel.org
>>>> Cc: imx@lists.linux.dev
>>>> Cc: kernel@dh-electronics.com
>>>> Cc: linux-kernel@vger.kernel.org
>>>> ---
>>>> arch/arm/boot/dts/nxp/imx/imx6ull-dhcor-maveo-box.dts | 8 --------
>>>> 1 file changed, 8 deletions(-)
>>>>
>>>> diff --git a/arch/arm/boot/dts/nxp/imx/imx6ull-dhcor-maveo-box.dts b/arch/arm/boot/dts/nxp/imx/imx6ull-dhcor-maveo-box.dts
>>>> index 047f7b2d8526..eb0b91040110 100644
>>>> --- a/arch/arm/boot/dts/nxp/imx/imx6ull-dhcor-maveo-box.dts
>>>> +++ b/arch/arm/boot/dts/nxp/imx/imx6ull-dhcor-maveo-box.dts
>>>> @@ -60,14 +60,6 @@ &ecspi4 {
>>>> pinctrl-0 = <&pinctrl_ecspi4>;
>>>> pinctrl-names = "default";
>>>> status = "okay";
>>>
>>> Drop "status = "okay"" too , since this controller will be unused ?
>>
>> you can instantiate a new device on the SPI bus from userspace. up to
>> you, but if I was a user I would appreciate to have it enabled.
> Good point -- Christoph, is this the (use)case here , can the user do that?
I don't think that's the case, since there isn't currently an SPI device
connected to this interface. Nevertheless, I'd be interested to know how
to instantiate a new device from user space.
Regards
Christoph
next prev parent reply other threads:[~2026-10-22 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 13:44 Christoph Niedermaier
2026-10-21 13:44 ` [PATCH 2/2] ARM: dts: imx6ull-dhcor-maveo-box: Correct PCB number Christoph Niedermaier
2026-10-21 17:20 ` Marek Vasut
2026-10-22 8:59 ` Christoph Niedermaier
2026-10-21 17:19 ` [PATCH 1/2] ARM: dts: imx6ull-dhcor-maveo-box: Remove unused SPI device Marek Vasut
2026-10-21 18:37 ` Francesco Dolcini
2026-10-21 18:55 ` Marek Vasut
2026-10-22 9:12 ` Christoph Niedermaier [this message]
2026-10-22 9:25 ` Francesco Dolcini
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=71d725ee47804205826bdda322fdfdb6@dh-electronics.com \
--to=cniedermaier@dh-electronics.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=francesco@dolcini.it \
--cc=imx@lists.linux.dev \
--cc=kernel@dh-electronics.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@nabladev.com \
--cc=robh@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
all inboxes | Powered by JetHome®