All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <vigneshr@ti.com>
To: <nm@ti.com>, Matt Ranostay <mranostay@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Vaishnav Achath <vaishnav.a@ti.com>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-j7200: fix main pinmux range
Date: Wed, 21 Sep 2022 15:53:07 +0530	[thread overview]
Message-ID: <166375577215.1126660.12635396035388901294.b4-ty@ti.com> (raw)
In-Reply-To: <20220919205723.8342-1-mranostay@ti.com>

Hi Matt Ranostay,

On Mon, 19 Sep 2022 13:57:23 -0700, Matt Ranostay wrote:
> Range size of 0x2b4 was incorrect since there isn't 173 configurable
> pins for muxing. Additionally there is a non-addessable region in the
> mapping which requires spliting into two ranges.
> 
> main_pmx0 -> 67 pins
> main_pmx1 -> 3 pins
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/1] arm64: dts: ti: k3-j7200: fix main pinmux range
      commit: 0d0a0b4413460383331088b2203ba09a6971bc3a

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh


WARNING: multiple messages have this Message-ID (diff)
From: Vignesh Raghavendra <vigneshr@ti.com>
To: <nm@ti.com>, Matt Ranostay <mranostay@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Vaishnav Achath <vaishnav.a@ti.com>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-j7200: fix main pinmux range
Date: Wed, 21 Sep 2022 15:53:07 +0530	[thread overview]
Message-ID: <166375577215.1126660.12635396035388901294.b4-ty@ti.com> (raw)
In-Reply-To: <20220919205723.8342-1-mranostay@ti.com>

Hi Matt Ranostay,

On Mon, 19 Sep 2022 13:57:23 -0700, Matt Ranostay wrote:
> Range size of 0x2b4 was incorrect since there isn't 173 configurable
> pins for muxing. Additionally there is a non-addessable region in the
> mapping which requires spliting into two ranges.
> 
> main_pmx0 -> 67 pins
> main_pmx1 -> 3 pins
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/1] arm64: dts: ti: k3-j7200: fix main pinmux range
      commit: 0d0a0b4413460383331088b2203ba09a6971bc3a

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh


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

  reply	other threads:[~2022-09-21 10:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 20:57 [PATCH v2] arm64: dts: ti: k3-j7200: fix main pinmux range Matt Ranostay
2022-09-19 20:57 ` Matt Ranostay
2022-09-21 10:23 ` Vignesh Raghavendra [this message]
2022-09-21 10:23   ` Vignesh Raghavendra

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=166375577215.1126660.12635396035388901294.b4-ty@ti.com \
    --to=vigneshr@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mranostay@ti.com \
    --cc=nm@ti.com \
    --cc=vaishnav.a@ti.com \
    /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.