-
Notifications
You must be signed in to change notification settings - Fork 0
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
How to find the corresponding values for "kUSBSleepPortCurrentLimit" and "kUSBWakePortCurrentLimit" in SSDT-EC-USBX #41
Comments
Good morning and thank you so much for creating this issue. Actually, as far as I'm aware, the values proposed in my
Hope I clarified your doubts |
Could you give me the link to the post discussing the two discarded values? I'm surprised that Regarding the two other values, are those only meaningful if I connect an iPad to the laptop (or is it irrelevant if I only use an iPhone or Android phone)? |
I'm still looking for it. I think I have saved it somewhere. Will let you know
As far as I'm aware it's meaningful if you connect an iPad. Still looking for documentation :/ UPDATEI found this: acidanthera/bugtracker#1001 (comment) Apparently you can test other devices also which have greater power consumption |
I tried loading two versions to see the differences. In IOReg, both cases only show It also seems like on MacbookPro, only the two properties are present. The MacbookPro14,3 in this example proves that (the same as the post you referred to). Regarding the value, I started with 3000 and it's been working stable for days. Today, I switched to 2100 and it also seems to work fine. Actually, I don't see any different in
It seems like with different devices, macOS will adjust Edit: add image |
Hi, it seems interesting to me that your SSDT-EC-USBX discards 2 desktop properties in the USBX. However, comparing your two values of "kUSBSleepPortCurrentLimit" and "kUSBWakePortCurrentLimit" to the original code by
acidanthera
, they are different.Your version:
acidanthera
's version:I wonder how to get the appropriate values for those two keys. There's not much info on this topic. The only one I found seems to suggest I need an ioreg or an ACPI dump from the real mac model with the same SMBIOS version.
The text was updated successfully, but these errors were encountered: