Hi Peter,

> Keith,
>
> Keith Hui wrote:
> > I had to upgrade the kernel from 4.4.14 to 5.4.42 for the i2c-scmi driver
> > to catch on. Then I was getting a shitload of invalid parameter errors
> > which eventually boils down to _SBW being expected to return a package of
> > one integer, instead of just an integer. Oops. I fixed that, but somehow
> > it's still not showing my devices. Gotta try harder.
>
> Just a note that it's interesting, fun and exciting to follow your progress!
>
> Keep up the good work. You'll get there.

Thanks for your encouragement!

***
Hi all,

After another 2 days I now have a working SCMI implementation on P3B-F
and can get readings from lm-sensors using i2c-scmi, with all relevant
vendor code  connected to SCMI. I spent another few hours refactoring
so that it can be more easily extended to other southbridges. At this
point my use case is solved and I can submit and updated patch.

Now that I think more about it...

SCMI is sufficient for getting hwmon working on Linux, but for Windows
I don't know if eg. Speedfan can use it, or if it's even necessary.
The next step in the evolution of ACPI-based hardware monitoring on
ASUS mainboards would be ATK0110. It's an all-ACPI wrapper around
whatever hardware monitor chip is on the actual board. I could figure
out what methods I need to implement, and if I can make SCMI work, I
can make ATK0110 work too, but is it worth the effort?

Pros:
- Forget i2c-scmi and all the i2c crap, just load asus_atk0110 and go
- I can debug my work by overriding DSDT in Linux instead of flashing
- Possibility of wider adoption (use asus-atk0110 for all corebooted
[asus] boards)
Cons:
- My use case has been solved already
- May have to do scaling math that I don't fully understand. As it is,
some values (eg. 12V rail reading) don't make sense
- More hours, more grey hair falling off (:-P
- Who's using this board anyway?

Regards
Keith
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to