lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <172452923383.505729.8023635627832942886.b4-ty@ti.com>
Date: Sat, 24 Aug 2024 14:54:02 -0500
From: Nishanth Menon <nm@...com>
To: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley <conor+dt@...nel.org>, Judith Mendez <jm@...com>
CC: Nishanth Menon <nm@...com>, Vignesh Raghavendra <vigneshr@...com>,
        Tero
 Kristo <kristo@...nel.org>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, Jan Kiszka
	<jan.kiszka@...mens.com>,
        Bhavya Kapoor <b-kapoor@...com>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-am654-idk: Add Support for MCAN

Hi Judith Mendez,

On Wed, 21 Aug 2024 15:54:14 -0500, Judith Mendez wrote:
> There are two MCAN instances present on the am65x SoC [0].
> Since there are two CAN transceivers on the IDK application
> board for AM654 EVM [1], enable m_can0 and m_can1, add the
> two corresponding CAN transceiver nodes, and set a maximum
> data rate of 5 Mbps.
> 
> [0] https://www.ti.com/lit/ds/symlink/am6548.pdf
> [1] https://www.ti.com/lit/zip/sprr382
> 
> [...]

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

[1/1] arm64: dts: ti: k3-am654-idk: Add Support for MCAN
      commit: f0f961ab9c9652c2f07bd7120a5b2b462ad6fd92

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
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ