Mediatek MT8173 Quad Core big.LITTLE ARM Cortex A72/A53 Processor Code Submitted to Linux Mainline

[Update: MT8173 processor has now been announced, and it’s using Cortex A72 and A53 instead of A57/A53, as initially shown in the Linux kernel source code]

Mediatek is not exactly known to compliant with open source licences, or be involved with the open source community. But the company is certainly going into the right direction with their cooperation with Google leading to source code release for Android One smartphones, and the recently launched Mediatek Labs for community projects, starting with LinkIt One IoT platform. Mediatek is also regularly submitting code to the Linux ARM Kernel mailing list, and yesterday code was submitted for Mediatek MT8173 SoC, a 64-bit ARMv8 processor with two Cortex 53 and two Cortex 57 cores in big.LITTLE configuration. As far as I know, it could be the first Mediatek SoC with “big” Cortex A57 cores.

Code snippet from mt8173.dtsi related to CPU cores:


A short DTS file was also submitted for MT8173 tablet EVB (evaluation board):


The memory section normally defines the location and size of the RAM (0x40000000 correspond to 1GB), but in this device tree file the location and size is shown twice, maybe because its a 64-bit platform addressed with 2x 1GB RAM (TBC) using 32-bit buses. An explanation of this would be welcomed.

That’s about all I know for know, except the new processor shares a lot with MT8135 and other MT65xx series. My search for MTK8173 / MT8173 did not yield interesting results so far.

Share this:

Support CNX Software! Donate via PayPal or cryptocurrencies, become a Patron on Patreon, or buy review samples

8 Replies to “Mediatek MT8173 Quad Core big.LITTLE ARM Cortex A72/A53 Processor Code Submitted to Linux Mainline”

  1. CNX, device tree cells are by definition 32 bits. That means that for 64-bit platforms, 2 consecutive cells are required for address/size value. They are given in big endian format to be human-friendly.

    So, the above defines 1Gb of mem at 0x0000000040000000

Leave a Reply

Your email address will not be published.

Advertisement
Advertisement