linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Harvey <tharvey@gateworks.com>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Device Tree Mailing List <devicetree@vger.kernel.org>,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] imx8mm-venice-gw7901: move UART gpio config into hog group
Date: Mon, 11 Apr 2022 12:25:53 -0700	[thread overview]
Message-ID: <CAJ+vNU151J42NSeqGrk7mG+k6Nk+=vPrSBGREFd725E2YaZ=JQ@mail.gmail.com> (raw)
In-Reply-To: <20220411012714.GC129381@dragon>

On Sun, Apr 10, 2022 at 6:27 PM Shawn Guo <shawnguo@kernel.org> wrote:
>
> On Tue, Apr 05, 2022 at 01:04:07PM -0700, Tim Harvey wrote:
> > Move UART related GPIO into hog group so that they still are pinmuxed
> > even if the uart driver is not probed.
>
> What are these GPIOs used for?  So they will be used anyway even when
> UART support is disabled?
>
> Shawn

Shawn,

Agreed - please drop this and 'imx8mm-venice-gw7902: move UART gpio
config into hog group' [1]

Best Regards,

Tim
[1] https://patchwork.kernel.org/project/linux-arm-kernel/patch/20220405200435.18797-1-tharvey@gateworks.com/

      reply	other threads:[~2022-04-11 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 20:04 [PATCH] imx8mm-venice-gw7901: move UART gpio config into hog group Tim Harvey
2022-04-11  1:27 ` Shawn Guo
2022-04-11 19:25   ` Tim Harvey [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='CAJ+vNU151J42NSeqGrk7mG+k6Nk+=vPrSBGREFd725E2YaZ=JQ@mail.gmail.com' \
    --to=tharvey@gateworks.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --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 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).