News: 0001467234

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

ASUS Linux Driver Adding Ability To Toggle CPU Cores, APU Memory Settings & dGPU TGP

([Hardware] 5 Hours Ago ASUS WMI Driver)


The ASUS WMI platform driver for Linux that is predominantly used by ASUS laptops for enabling more functionality under Linux has a new patch series available that is enabling yet more features for the latest ASUS hardware on Linux.

Luke Jones continues near single handedly improving the ASUS WMI x86 platform driver for in turn improving the ASUS laptop experience under Linux. Posted today were a set of nine patches making more improvements to the ASUS WMI driver code as well as tacking on some more features.

With the new ASUS WMI driver patches, there is a new "panel_fhd" option exposed under sysfs for some ASUS laptops that allow setting between Ultra HD (UHD) and Full HD (FHD) modes for the laptop panel.

There is also another feature wired up for dynamically toggling the E/P cores enabled for Intel-powered ASUS laptops. New "cores_enabled" and "cores_max" sysfs attributes are exposed for run-time toggling of efficiency/performance cores for Intel-powered ASUS laptops.

Also new is a "apu_mem" setting for controlling the APU's memory setting on various ASUS devices such as the ROG Ally gaming handheld. This allows adjusting the amount of device memory available to the APU.

Lastly is a "dgpu_tgp" setting that is exposed for a few ASUS ROG laptops. This allows adjusting the total graphics power (TGP) of the discrete GPU on systems that allow for dynamically adjusting the GPU power limit.

More details on these feature patches for the ASUS WMI Linux driver can be found via [1]this patch series . Hopefully these new ASUS laptop/device features will be ready for the Linux v6.11 kernel later this summer.



[1] https://lore.kernel.org/lkml/20240528013626.14066-1-luke@ljones.dev/



M@GOid

Weasel

A comment on schedules:
Ok, how long will it take?
For each manager involved in initial meetings add one month.
For each manager who says "data flow analysis" add another month.
For each unique end-user type add one month.
For each unknown software package to be employed add two months.
For each unknown hardware device add two months.
For each 100 miles between developer and installation add one month.
For each type of communication channel add one month.
If an IBM mainframe shop is involved and you are working on a non-IBM
system add 6 months.
If an IBM mainframe shop is involved and you are working on an IBM
system add 9 months.
Round up to the nearest half-year.
--Brad Sherman
By the way, ALL software projects are done by iterative prototyping.
Some companies call their prototypes "releases", that's all.