-
Notifications
You must be signed in to change notification settings - Fork 0
/
MachinexChangeLog
10046 lines (6308 loc) · 309 KB
/
MachinexChangeLog
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
2017-10-31 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: even longer
2017-10-31 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: bracket
2017-10-31 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/intelli_hotplug.c, drivers/cpufreq/mx_hotplug.c,
include/linux/workqueue.h, kernel/workqueue.c: revert workqueue
changes - some fixes to mx plug
2017-10-31 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: remove that
2017-10-31 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: fix my ordering on unlikely error
case in startup
2017-10-31 robcore <robpatershuk@gmail.com>
* kernel/workqueue.c: fix a derp
2017-10-31 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c, include/linux/workqueue.h,
kernel/workqueue.c: modified modify_delayed_work so that it checks
for NULL values...catering to my own shitty race conditions
2017-10-31 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: bracket
2017-10-31 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: some more security for our little
quandry
2017-10-31 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: fix a potential early NULL pointer
reference with a bandaid for now
2017-10-31 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: more tinkering
2017-10-31 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a-bluelight.c,
drivers/leds/leds-an30259a.c: leds - trying out a setting for
BLUE_BRIGHTNESS_OFFSET i found
2017-10-31 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: going nuts with it
2017-10-31 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: k gonna try this
2017-10-31 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: that should do it
2017-10-31 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: delay the shutdown led sequence
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq_interactive.c: try out using C for the
initial freq calculation, because we are actually just trying to
find the closest freq represented by loadadjfreq / tl
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq_interactive.c: bump up DEFAULT_TARGET_LOAD
by 1
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: more tunable updates
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c, openrecoveryscript: shifting gears
doesnt make as much sense in this mixed metaphor as clutch
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c, openrecoveryscript: just gonna keep
lowering these thresholds until i see the results i want
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c, openrecoveryscript: down allll the
thresholds
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c, openrecoveryscript: be more picky
when offlining cores than onlining
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: add some insurance to allow us to
online all the fucking cores we want when its time to shut down.
also, remove some leftover unused bloat
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: add load averaging to the core
up/down decision making
2017-10-30 robcore <robpatershuk@gmail.com>
* kernel/sched/loadavg.c: load avg/runqueue stats: actually format
the code in the spirit of the original description
2017-10-30 robcore <robpatershuk@gmail.com>
* kernel/sched/loadavg.c: hold up just do it at the individual core
level
2017-10-30 robcore <robpatershuk@gmail.com>
* kernel/sched/loadavg.c: the individual cores too
2017-10-30 robcore <robpatershuk@gmail.com>
* kernel/sched/loadavg.c: fuck it divide it by ten right at the
source
2017-10-30 robcore <robpatershuk@gmail.com>
* kernel/sched/loadavg.c: do this even better
2017-10-30 robcore <robpatershuk@gmail.com>
* kernel/sched/loadavg.c: give us a user facing interface for total
cpu load
2017-10-30 robcore <robpatershuk@gmail.com>
* include/linux/sched.h, kernel/sched/loadavg.c: created a total
loadavg function
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c: dont need that
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: allow boost to mod the delayed work,
and bypass the sampling rate. also, move it before any of the
request calculation because it is outside of the basic functioning.
finally, ensure that we syncronize the scheduler when finished doing
whatever
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: hit the brakes no longer needs to be
passed values
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: mx hotplug - fix some logic
regarding first and second gear. our downshift one value could have
easily been blocking the hit the brakes function. also remove checks
for number of cpus online, because that is for the external
functions to sort out. and a few other little fixups
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: up the sampling rate and boost
length
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: more lowering
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c, drivers/cpufreq/mx_hotplug_wip.c:
fix my driver, the averaging was not wise, and stick to releasing
the brakes on driver stop.
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: compiler optimize
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: dont let checkpoint go below zero
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: more of the endless tweaking
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: mx hotplug experiment - take a
dynamic average of nr running, and throw it in its own high pri
kthread
2017-10-30 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: lowered again
2017-10-30 robcore <robpatershuk@gmail.com>
* build_kernel.sh, drivers/cpufreq/mx_hotplug.c: brought down my mx
thresholds again
2017-10-29 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: and more
2017-10-29 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: even lower
2017-10-29 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: lowered the thresholds again
2017-10-29 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c, drivers/cpufreq/userspace_hotplug.c:
DUH didnt even have uplug enabled from the function. jesus what a
bad day
2017-10-29 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: adjust the lower rate too, and
remove some bloat
2017-10-29 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c, openrecoveryscript: more mx
adjustments
2017-10-29 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c, drivers/cpufreq/userspace_hotplug.c:
jeeze my head is obviously sore
2017-10-29 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/userspace_hotplug.c: uspace hotplug can be in the
kernel sysfs
2017-10-29 robcore <robpatershuk@gmail.com>
* arch/arm/configs/canadefconfig, drivers/cpufreq/Kconfig,
drivers/cpufreq/Makefile, drivers/cpufreq/userspace_hotplug.c: some
protection for userspace hotplug not to get confused if things like
core control or hardplug are being used (the latter is somewhat
pointless if userspace hotplug is in use)
2017-10-29 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/userspace_hotplug.c, openrecoveryscript: i think i
have a sensical skelaton for the userspace cpu hotplug driver
2017-10-29 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c, drivers/cpufreq/userspace_hotplug.c:
more mx adjustments
2017-10-29 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: more slight adjustments
2017-10-29 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c, drivers/cpufreq/userspace_hotplug.c:
adjusted thresholds in mx plug, changed a variable name, and did a
little work in userspace
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: mx hotplug - some slight adjustments
to the thresholds, and more fun naming
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: mx hotplug - some slight adjustments
to the thresholds, and more fun naming
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c: no more scaling governor changes from
the traditional sysfs interface. read only.
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c, drivers/cpufreq/userspace_hotplug.c:
gonna introduce a nifty little userspace hotplug driver, might as
well do something useful with my cpumask test code
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c, include/linux/cpufreq.h: duh. check if
the cpu is online before grabbing the policy. also, check if the
policy exists and if not, return ENOMEM. This is fine and intended
behaviour. the goal is to change the policy immediately if online,
and provide a cached governor to wake up to when the core is
offline, so failing for this step is of little to no consequence
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c,
drivers/cpufreq/cpufreq_machinex_gov_attr.c,
include/linux/cpufreq.h: duh rob, if the cpu is online you have to
set the new policy
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: change some of my terminology
strictly for fun
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: lower my thresholds a bit
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c,
drivers/cpufreq/cpufreq_machinex_gov_attr.c,
include/linux/cpufreq.h: hehe forgot userspace. but to ones defence
it is a forgetable gov
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c,
drivers/cpufreq/cpufreq_conservative.c,
drivers/cpufreq/cpufreq_intelliactive.c,
drivers/cpufreq/cpufreq_interactive.c,
drivers/cpufreq/cpufreq_machinex_gov_attr.c,
drivers/cpufreq/cpufreq_machinex_gov_attr.h,
drivers/cpufreq/cpufreq_ondemand.c,
drivers/cpufreq/cpufreq_performance.c,
drivers/cpufreq/cpufreq_powersave.c,
drivers/cpufreq/cpufreq_userspace.c, include/linux/cpufreq.h,
kernel/sched/cpufreq_schedutil.c: MUAHAHAHAHA hacked the governor
for permanence using my same ol governor array scheme!!!!!!!
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c: same dumbness
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c: maybe if i wasnt an idiot
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c, include/linux/cpufreq.h: could it be
this easy?
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c, include/linux/cpufreq.h: hmm
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c, include/linux/cpufreq.h: cpufreq - back
to basics, i need to find out which step fails
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c: hehehe i think i modified this
properly. now if the governor has changed when the cpu is offline,
we take a copy of it, and do a dummy "store" during policy init
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c, include/linux/cpufreq.h: revert that
junk
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c, include/linux/cpufreq.h: ohhh i get it
gonna do a thing
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: given that we only try the mutex
lock in mx hotplug input boost, go ahead and eliminate the count,
there are numerous factors that still make boost less consistent, so
the count isnt needed on top of them
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c, include/linux/cpufreq.h: early
prototype of persistent governor changes despite unplugged cores
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: get rid of the defs for the failed
workqueue setup
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: a few more slight adjustments - made
boost checking a little more streamlined, and slightly raised the
single core down limit
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: theeere we go
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: mother FUCK"
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: lets stay on the conservative side
for touch boosting
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: mother FUCKER
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: aaand fix my boost logic
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: raging semi-colon
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: made it a bit smarter once more
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: fixup boosting logic to allow for
trylock on touch side
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: FUCK double equal
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: ohhhh im an idiot
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: oops no semi colon there. syntax
mang
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c, drivers/input/omniboost.c,
include/linux/cpu.h: I THINK Ive implemented something a little
safer for touchboost. also, adjust levels just a bit
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: adjust our thresholds a bit...IT
WORKS!
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: dont need that return
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: oops i change dthat back to a
straight up lock
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c, drivers/input/omniboost.c: get rid
of timer lock and try it just with mutex, make startstop smarter,
get rid of kthread parking, and lock hotplug suspend. also, remove
the nos boost from omniboost for now because i dont think that works
with our syncronization structure (yet)
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: glad i spotted that, needed some
brackets
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: protect reset wip with mutex too
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: reset_wip() on startup, not shutdown
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: make the start up/teardown safer
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: syntax fix
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c, drivers/input/omniboost.c,
include/linux/cpu.h: a little more work on the hotplug front -
trying out parking again, as well as setting the target based on the
avg nr running, not making cpus online the deciding factor
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: THATS what i meant to do in mx
hotplug
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c: rever the cpufreq changes - they break
stuff
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c: dont think we need the sem in the sysfs
funcs
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c: oops didnt hit save
2017-10-28 robcore <robpatershuk@gmail.com>
* arch/arm/configs/canadefconfig, drivers/cpufreq/cpufreq.c: testing
holding the rwsem for some of our crucial hardlimit values in
cpufreq
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: mx_hotplug - add a mutex for
syncronization, get rid of global target_cpus var - send the
adjusted cpu core target directly to the up/down functions, wake up
the process on start and resume even before queuing so the task
doesnt look hung to the freezer, and a couple of other little
cleanups
2017-10-28 robcore <robpatershuk@gmail.com>
* kernel/sched/loadavg.c: use a common variable to enable/disable
showing these values, having it on by default combined with using a
polling application increases overhead significantly
2017-10-28 robcore <robpatershuk@gmail.com>
* Documentation/ABI/testing/sysfs-devices-power,
drivers/base/cpu.c, drivers/base/power/domain_governor.c,
drivers/base/power/qos.c, drivers/base/power/runtime.c,
drivers/base/power/sysfs.c, drivers/cpuidle/governors/menu.c,
include/linux/pm_qos.h: fuck it we dont have latency issues and that
causes warnings in mmc sleep resulting in perma wakelocks
2017-10-28 robcore <robpatershuk@gmail.com>
* drivers/base/cpu.c: oops didnt have pm qos there
2017-10-28 robcore <robpatershuk@gmail.com>
* Documentation/ABI/testing/sysfs-devices-power,
drivers/base/cpu.c, drivers/base/power/domain_governor.c,
drivers/base/power/qos.c, drivers/base/power/runtime.c,
drivers/base/power/sysfs.c, drivers/cpuidle/governors/menu.c,
include/linux/pm_qos.h: PM / QoS: Fix device resume latency PM QoS
2017-10-27 robcore <robpatershuk@gmail.com>
* arch/arm/configs/canadefconfig: well... it doesnt implode anymore!
that said, it also doesnt actually do any plugging
2017-10-27 robcore <robpatershuk@gmail.com>
* arch/arm/configs/canadefconfig, drivers/cpufreq/mx_hotplug.c: this
will probably fail, but id like to see it do so
2017-10-27 robcore <robpatershuk@gmail.com>
* arch/arm/configs/canadefconfig, drivers/cpufreq/mx_hotplug.c:
screw the hotplug driver for now
2017-10-27 robcore <robpatershuk@gmail.com>
* arch/arm/configs/canadefconfig,
arch/arm/mach-msm/acpuclock-krait.c, drivers/cpufreq/mx_hotplug.c: a
couple fixups in mx hotplug, and some renaming because im liking the
mechanical theme
2017-10-27 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/acpuclock-krait.c,
arch/arm/mach-msm/board-jf_eur.c, drivers/cpufreq/mx_hotplug.c: some
more insurance that thermal wont be brought up before the cpufreq
driver is registered
2017-10-27 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: mx hotplug is looking neater
2017-10-27 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/acpuclock-krait.c: instead of randomly cycling
all of the cpu freqs after resuming from suspend, just use the
cpufreq resume function extension. (this way we know we have the
policies for the cpus, and it avoids a waste of energy if we dont)
2017-10-27 robcore <robpatershuk@gmail.com>
* arch/arm/kernel/Makefile, arch/arm/mm/Kconfig: truly shutting off
deprecated swp emulation
2017-10-27 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: brakes
2017-10-27 robcore <robpatershuk@gmail.com>
* arch/arm/configs/canadefconfig: shit i read up on this again today
disable swap emulation
2017-10-27 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c: can be static
2017-10-27 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c, include/linux/cpufreq.h: oh yeah and
made hardlimit ready percpu
2017-10-27 robcore <robpatershuk@gmail.com>
* arch/arm/configs/canadefconfig,
arch/arm/mach-msm/acpuclock-krait.c,
arch/arm/mach-msm/board-jf_eur.c,
drivers/cpufreq/alucard_hotplug.c,
drivers/cpufreq/bricked_hotplug.c, drivers/cpufreq/cpufreq.c,
drivers/cpufreq/intelli_hotplug.c, drivers/cpufreq/lazyplug.c,
drivers/cpufreq/msm_sleeper.c, drivers/cpufreq/mx_hotplug.c,
drivers/thermal/msm_thermal.c, include/linux/cpufreq.h,
kernel/cpu_hardplug.c: did some overhauling with mx hotplug
(studied), and got rid of the "hotplug ready" parameter that should
have been percpu and is frankly no different from checking if
(cpu_online(cpu) && policy !=NULL), which we already do fucking
EVERY where so this bool is just a redundant, non-working idiot move
on my end. turns out debug prints are our friend
2017-10-27 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/acpuclock-krait.c: print out a curiousity of
mine
2017-10-27 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: gonna have to set up a workqueue
2017-10-27 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: FUCK
2017-10-27 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: right we got rid of the dumb goto
2017-10-27 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: try ensuring we let task running
happen
2017-10-27 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c: oops forgot to bind my mask to 0
2017-10-27 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/Makefile, drivers/cpufreq/mx_hotplug.c,
drivers/cpufreq/mx_hotplug_wip.c: mother FUCKER
2017-10-27 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/mx_hotplug.c, drivers/cpufreq/mx_hotplug_wip.c:
trying something nuts
2017-10-27 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/intelli_hotplug.c: intelliplug 15.8 - break early
if we are already at our target
2017-10-27 robcore <robpatershuk@gmail.com>
* arch/arm/configs/canadefconfig, drivers/cpufreq/Kconfig,
drivers/cpufreq/Makefile, drivers/cpufreq/cpufreq_interactive.c,
drivers/cpufreq/mx_hotplug.c, drivers/cpufreq/{ix_hotplug.c =>
mx_hotplug_wip.c}: starting on mx_hotplug - userspace facing api is
just a dummy until i get my wip ready to go - also a small
interactive fix i think
2017-10-26 robcore <robpatershuk@gmail.com>
* kernel/sched/loadavg.c: built myself a little load/nr_running avg
reference to monitor info
2017-10-26 robcore <robpatershuk@gmail.com>
* include/linux/sysfs.h: added some helpers for storing and showing
funcs
2017-10-26 robcore <robpatershuk@gmail.com>
* include/linux/sched.h, kernel/sched/core.c,
kernel/sched/loadavg.c, kernel/sched/sched_avg.c: some hacking/some
fixing of signed to unsigned for cpu vars, and prep for a little
debug interface im building myself
2017-10-26 robcore <robpatershuk@gmail.com>
* kernel/sched/loadavg.c: loadavg - we were using a long for "cpu"
and an int for ave_nr_running, very backwards. fixed
2017-10-26 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/ix_hotplug.c: actually thats probably a bad idea
2017-10-26 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/msm_rq_stats.c, drivers/cpufreq/ix_hotplug.c:
trying some ix adjustments before dropping it entirely
2017-10-26 robcore <robpatershuk@gmail.com>
* arch/arm/configs/canadefconfig, drivers/cpufreq/Kconfig,
drivers/cpufreq/Makefile, drivers/cpufreq/ix_hotplug.c: trying out
instigatorxs hotplug driver
2017-10-25 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/ix_hotplug.c: doing some work with instigators hp
2017-10-25 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c: thinking out loud
2017-10-25 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c: cpufreq - remove unused policy
arguement from cpufreq_parse_governor
2017-10-25 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/acpuclock-krait.c: get rid of unnecessary vars
in acpuclock
2017-10-25 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/acpuclock-krait.c: waste of time
2017-10-25 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/acpuclock-krait.c: trying a thing again
2017-10-25 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/acpuclock-krait.c: trying out the ol "set policy
cur" routine in the cpufreq driver again
2017-10-25 robcore <robpatershuk@gmail.com>
* drivers/cpufreq/cpufreq.c, include/linux/cpufreq.h: hardlimit -
update the reapplication process to reflect changes in the cpufreq
core regarding per-policy vs. per-cpu structures. pass policy to
hardlimit functions, and use a switch to indicate whether it should
do a final update. also, get rid of update scaling limits now that
reapply hardlimits is a part of the core. the whole process can
simply be one function. ...also fixup our check for cur limits in
the "check_cpu_hardlimit" routine, this way we retry 2 more times
before giving up
2017-10-25 robcore <robpatershuk@gmail.com>
* mm/shmem.c: mm: shmem: check for mapping owner before
dereferencing
2017-10-24 robcore <robpatershuk@gmail.com>
* drivers/leds/ledtrig-backlight.c: more fb notif/bl updating. can
you see im on a long term mission?
2017-10-24 robcore <robpatershuk@gmail.com>
* build_kernel.sh: make the ordering of my open recovery script
smarter. also, create and push it for adb wireless condition,
despite the pending manual reboot
2017-10-24 robcore <robpatershuk@gmail.com>
* drivers/video/backlight/backlight.c: throw in some backlight
debugging for my frame of reference
2017-10-24 robcore <robpatershuk@gmail.com>
* .gitignore, openrecoveryscript-last.txt: removed last ors and
added it to gitignore
2017-10-24 robcore <robpatershuk@gmail.com>
* openrecoveryscript-last.txt: nothing important
2017-10-24 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/platsmp.c, openrecoveryscript-last.txt: oh
interesting, smp must setup nr_cpu_ids to be safe for cpu ops
2017-10-24 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/platsmp.c: wait now i will try something
2017-10-24 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/platsmp.c, openrecoveryscript-last.txt: i wanna
see something
2017-10-24 robcore <robpatershuk@gmail.com>
* drivers/misc/cpumask_calculator.c, openrecoveryscript-last.txt:
get rid of redundant kobject
2017-10-24 robcore <robpatershuk@gmail.com>
* arch/arm/configs/canadefconfig,
drivers/input/touchscreen/virtual_wakeup_key.c,
drivers/misc/Kconfig, drivers/misc/Makefile,
drivers/misc/cpumask_calculator.c: wrote a quick little cpumask
calculator (super inappropriate, should definitely be a userspace
program, but this will work perfectly for synapse), and simplified
the virtual wakeup key driver
2017-10-24 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: missing comma
2017-10-24 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c, openrecoveryscript-last.txt: more
led fun
2017-10-24 robcore <robpatershuk@gmail.com>
* kernel/cpu_hardplug.c: fuck it this bad boy is 4.0
2017-10-24 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/platsmp.c, kernel/cpu_hardplug.c,
openrecoveryscript-last.txt: there fixed it, no need for the added
prints, we have sysfs in hardplug to verify if anything goes wrong
2017-10-24 robcore <robpatershuk@gmail.com>
* kernel/cpu_hardplug.c: lets see if i made this appropriately
self-correcting
2017-10-24 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/platsmp.c, kernel/cpu_hardplug.c,
openrecoveryscript-last.txt: hopefully fixed us all up...
(headscratcher this is)
2017-10-24 robcore <robpatershuk@gmail.com>
* build_kernel.sh: updated my script to flash and reboot if twrp
detected
2017-10-24 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/platsmp.c, kernel/cpu_hardplug.c: i think my
alterations to platsmp were a bad idea, so went back to usual there
and threw nonboot initialization into hardplug
2017-10-24 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/platsmp.c: just a derp
2017-10-24 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/platsmp.c, kernel/cpu_hardplug.c: nevermind i
think smp init happens before even the core initcall
2017-10-24 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/platsmp.c, kernel/cpu_hardplug.c: that woulda
fucked us, i think we actually get our possible mask from the kernel
smp init sequence, not platform
2017-10-24 robcore <robpatershuk@gmail.com>
* kernel/cpu_hardplug.c: aaaaand put the comma in the right place
rob. jeeze i need a break i cant even write a simple print statement
2017-10-24 robcore <robpatershuk@gmail.com>
* kernel/cpu_hardplug.c: shit i knew my naming would get frustrating
2017-10-24 robcore <robpatershuk@gmail.com>
* kernel/cpu_hardplug.c: syntax is key
2017-10-24 robcore <robpatershuk@gmail.com>
* kernel/cpu_hardplug.c: hardplug 3.6 - utilize some of our new mask
techniques
2017-10-24 robcore <robpatershuk@gmail.com>
* arch/arm/mach-msm/platsmp.c, arch/arm/mach-msm/pmu.c,
include/linux/cpumask.h, kernel/cpu.c, kernel/cpu_hardplug.c: this
is an idea, create a "nonboot" cpu mask to have a constant cpumask
that can easily just be copied and used for other functions
2017-10-24 robcore <robpatershuk@gmail.com>
* build_kernel.sh: nevermind it works!
2017-10-24 robcore <robpatershuk@gmail.com>
* build_kernel.sh: just for my testing
2017-10-24 robcore <robpatershuk@gmail.com>
* build_kernel.sh, openrecoveryscript: more fixups
2017-10-24 robcore <robpatershuk@gmail.com>
* build_kernel.sh, openrecoveryscript: aaaand im proud of twrp for
finding the script even though i had my full build machine path in
front of the zip name
2017-10-24 robcore <robpatershuk@gmail.com>
* build_kernel.sh, openrecoveryscript: oops my rm -f did NOT belong
in the openrecoveryscript, not scripting format rob duh
2017-10-24 robcore <robpatershuk@gmail.com>
* build_kernel.sh: do the heavy lifting on our end, not through adb
2017-10-24 robcore <robpatershuk@gmail.com>
* build_kernel.sh: trying out some open recovery fun
2017-10-23 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: and more and more and more
2017-10-23 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: little more conservative
2017-10-23 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: extend second half again
2017-10-23 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: moar;
2017-10-23 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: and a bit more
2017-10-23 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: and more
2017-10-23 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: going nuts with the led stuff for
fun
2017-10-23 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: trying another thing leds
2017-10-23 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: leds
2017-10-23 robcore <robpatershuk@gmail.com>
* drivers/leds/leds-an30259a.c: extend leds some more