Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CONFIG_ASUS_ARMOURY needs to be enabled for all desktops. #380

Open
flukejones opened this issue Jan 19, 2025 · 7 comments
Open

CONFIG_ASUS_ARMOURY needs to be enabled for all desktops. #380

flukejones opened this issue Jan 19, 2025 · 7 comments

Comments

@flukejones
Copy link

I just got notice from a cachy user on asus that they don't have full functionality available. It looks like CONFIG_ASUS_ARMOURY is enabled only for deckify?

A side note: My latest patches from https://github.com/flukejones/linux/tree/wip/ally-6.12 are now safe for clang compilation (if that was ever an issue - tested with serpentOS).

@1Naim
Copy link
Member

1Naim commented Jan 19, 2025

Hi Luke, what device is your user using? We currently only pull your ASUS patches for the handheld kernel.

@flukejones
Copy link
Author

Laptop. This driver is required for all asus rog and tuf laptops from 2021+.

It is in the process of being upstreamed and has had reviews - just a little more work to do.

@ptr1337
Copy link
Member

ptr1337 commented Jan 19, 2025

Laptop. This driver is required for all asus rog and tuf laptops from 2021+.

It is in the process of being upstreamed and has had reviews - just a little more work to do.

Currently we have only pulled it into the handheld kernel, since there were a lot of changes in the past months.
We will look how it goes with 6.13 and might then push it into the default kernels too.

@flukejones
Copy link
Author

There will be more changes coming but the majority of things is very stable now. The one change that needs to be done is adding safe limits for the ppt for each device as a table in kernel.

I'll keep you appraised of things. It should be easier to include my full series as a single patch file

@1Naim
Copy link
Member

1Naim commented Feb 4, 2025

Hi Luke, I'm thinking about including your asus-armoury driver for 6.14 cycle. I'm thinking about including only the armoury stuff for all kernels and only the ally stuff for the handheld kernel? What do you think?

If I'm seeing this correctly, in your wip/ally-master branch, starting from commit 7efaa140aca7ebefa86774fbe29d6936e9336c56 to HEAD is for asus-armoury and below that is for Ally. Is that correct?

@flukejones
Copy link
Author

@1Naim You will want all patches for both branches. The asus-armoury driver contains a lot of stuff, in particular the actual min/max limits for the PPT settings you can access through ls /sys/devices/virtual/firmware-attributes/asus-armoury/attributes/ppt_*/

Do keep in mind there will be some more changes. Maybe. But right now it's in a very stable state with a lot of kinks ironed out. And the asus_armoury driver has been through a few reviews.

I'll be sending various parts for review soon.

Oh and also: master is not suitable for use on 6.13 yet. And the ally-6.13 branch isn't updated, I will backport the master work soon.

@1Naim
Copy link
Member

1Naim commented Feb 4, 2025

You will want all patches for both branches. The asus-armoury driver contains a lot of stuff, in particular the actual min/max limits for the PPT settings you can access through ls /sys/devices/virtual/firmware-attributes/asus-armoury/attributes/ppt_*/

Oh I misphrased it :p I meant armoury for desktop kernels and armoury + ally on handheld kernels. It looks like I got my answer anyway and including the whole patchset seems to be the right way to go.

Do keep in mind there will be some more changes. Maybe. But right now it's in a very stable state with a lot of kinks ironed out. And the asus_armoury driver has been through a few reviews

All good, I see that you're still working on it and I'll probably include it in either 6.14rc2 or 6.14rc3. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants