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
