All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo2@yeah.net>
To: Esben Haabendal <esben@geanix.com>
Cc: Russell King <linux@armlinux.org.uk>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Dong Aisheng <aisheng.dong@nxp.com>, Jacky Bai <ping.bai@nxp.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
	linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 1/3] ARM: imx: Allow user to disable pinctrl
Date: Mon, 3 Jun 2024 10:50:19 +0800	[thread overview]
Message-ID: <Zl0va6yv2VY4ky0l@dragon> (raw)
In-Reply-To: <20240506-imx-pinctrl-optional-v2-1-bdff75085156@geanix.com>

On Mon, May 06, 2024 at 12:23:53PM +0200, Esben Haabendal wrote:
> Making pinctrl drivers and subsequently the pinctrl framework
> user-controllable, allows building a kernel without this.
> While in many (most) cases, this could make the system unbootable, it
> does allow building smaller kernels for those situations where picntrl
> is not needed.
> 
> One such situation is when building a kernel for NXP LS1021A systems,
> which does not have run-time controllable pinctrl, so pinctrl framework
> and drivers are 100% dead-weight.
> 
> 
> Signed-off-by: Esben Haabendal <esben@geanix.com>

Acked-by: Shawn Guo <shawnguo@kernel.org>


WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo2@yeah.net>
To: Esben Haabendal <esben@geanix.com>
Cc: Russell King <linux@armlinux.org.uk>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Dong Aisheng <aisheng.dong@nxp.com>, Jacky Bai <ping.bai@nxp.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
	linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 1/3] ARM: imx: Allow user to disable pinctrl
Date: Mon, 3 Jun 2024 10:50:19 +0800	[thread overview]
Message-ID: <Zl0va6yv2VY4ky0l@dragon> (raw)
In-Reply-To: <20240506-imx-pinctrl-optional-v2-1-bdff75085156@geanix.com>

On Mon, May 06, 2024 at 12:23:53PM +0200, Esben Haabendal wrote:
> Making pinctrl drivers and subsequently the pinctrl framework
> user-controllable, allows building a kernel without this.
> While in many (most) cases, this could make the system unbootable, it
> does allow building smaller kernels for those situations where picntrl
> is not needed.
> 
> One such situation is when building a kernel for NXP LS1021A systems,
> which does not have run-time controllable pinctrl, so pinctrl framework
> and drivers are 100% dead-weight.
> 
> 
> Signed-off-by: Esben Haabendal <esben@geanix.com>

Acked-by: Shawn Guo <shawnguo@kernel.org>


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-06-03  2:51 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 10:23 [PATCH v2 0/3] ARM: imx: only enable pinctrl as needed Esben Haabendal
2024-05-06 10:23 ` Esben Haabendal
2024-05-06 10:23 ` [PATCH v2 1/3] ARM: imx: Allow user to disable pinctrl Esben Haabendal
2024-05-06 10:23   ` Esben Haabendal
2024-06-03  2:50   ` Shawn Guo [this message]
2024-06-03  2:50     ` Shawn Guo
2024-09-13  7:21     ` Esben Haabendal
2024-09-24  7:45   ` Linus Walleij
2024-09-26  7:28     ` Esben Haabendal
2024-09-26  8:40     ` Shawn Guo
2024-11-26 16:17   ` Guenter Roeck
2024-11-26 21:24     ` Linus Walleij
2024-11-26 23:53       ` Guenter Roeck
2024-11-27  0:12         ` Fabio Estevam
2024-11-27  6:59           ` Arnd Bergmann
2024-11-27  9:13           ` Rasmus Villemoes
2024-11-27  9:18             ` Arnd Bergmann
2024-11-27 10:13               ` Rasmus Villemoes
2024-11-27 11:29                 ` Arnd Bergmann
2024-11-27 14:36                   ` Fabio Estevam
2024-11-28  7:32                     ` Esben Haabendal
2024-05-06 10:23 ` [PATCH v2 2/3] pinctrl: freescale: Use CONFIG_SOC_IMXRT to guard i.MX RT1xxx drivers Esben Haabendal
2024-05-06 10:23   ` Esben Haabendal
2024-05-06 11:29   ` Arnd Bergmann
2024-05-06 11:29     ` Arnd Bergmann
2024-05-07  7:37     ` Esben Haabendal
2024-05-07  7:37       ` Esben Haabendal
2024-05-07  7:43       ` Arnd Bergmann
2024-05-07  7:43         ` Arnd Bergmann
2024-05-06 10:23 ` [PATCH v2 3/3] pinctrl: freescale: enable use with COMPILE_TEST Esben Haabendal
2024-05-06 10:23   ` Esben Haabendal
2024-05-27 11:05 ` [PATCH v2 0/3] ARM: imx: only enable pinctrl as needed Linus Walleij
2024-05-27 11:05   ` Linus Walleij
2024-10-01 11:55   ` Linus Walleij

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=Zl0va6yv2VY4ky0l@dragon \
    --to=shawnguo2@yeah.net \
    --cc=aisheng.dong@nxp.com \
    --cc=arnd@arndb.de \
    --cc=esben@geanix.com \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=ping.bai@nxp.com \
    --cc=rasmus.villemoes@prevas.dk \
    --cc=s.hauer@pengutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.