Displaying 3 results from an estimated 3 matches for "0x0a49".
Did you mean:
0x0a4
2017 Nov 06
0
[PATCH v2] pmu/fuc: don't use movw directly anymore
...00f804,
0xb607e407,
+ 0x01d00604,
+ 0xf804bd00,
+/* 0x0a0d: i2c_drive_sda */
+ 0x0036b000,
+ 0xf1110bf4,
+ 0xb607e007,
0x02d00604,
0xf804bd00,
-/* 0x0a31: i2c_sense_scl */
- 0x0132f400,
- 0x07c437f1,
- 0xcf0634b6,
- 0x31fd0033,
- 0x060bf404,
-/* 0x0a47: i2c_sense_scl_done */
- 0xf80131f4,
-/* 0x0a49: i2c_sense_sda */
- 0x0132f400,
- 0x07c437f1,
- 0xcf0634b6,
- 0x32fd0033,
- 0x060bf404,
-/* 0x0a5f: i2c_sense_sda_done */
- 0xf80131f4,
-/* 0x0a61: i2c_raise_scl */
- 0xf140f900,
- 0xf0089847,
- 0x21f50137,
-/* 0x0a6e: i2c_raise_scl_wait */
- 0xe7f109ed,
- 0x21f403e8,
- 0x3121f57e,
- 0x0901f40a,
-...
2017 May 07
6
[RFC v2 0/6] PMU engine counters
reworked this series quite a lot.
Now we want the Host to configure the counters through the PMU.
The series isn't complete though because it needs:
1. reordering
2. better commit messages
but I felt like sending those out before doing a final version.
I also found some weird register overwriting issue on the PMU I have to track
down, because it interfers with the counter read out. I am
2017 Jun 05
7
[PATCH v3 0/7] PMU engine counters
I think I am done reworking the series and getting to a point where I think
it is basically finished. The configuration of the slots could be improved
later on when working on dynamic reclocking, but for now it's good enough to
report the current GPU utilization to userspace.
Patches 1-4 imeplement PMU commands to setup and readout the counters.
Patches 5-6 lets Nouveau make use of 1-4.
Patch