{"push_id":2667014098,"size":487,"distinct_size":487,"ref":"refs/heads/linux-next-ouya","head":"5af7f0a8ff493c0a11fa51236449e4b775873c0f","before":"79084ac111be49dbfece83cf2317de92a6b40bd9","commits":[{"sha":"41477acf092251eb0cfe83068f48dbcb2521478a","author":{"name":"Arnaldo Carvalho de Melo","email":"293abb6b76d7791c0732cc517d38c4b5c734b87f@redhat.com"},"message":"perf hists: Save the callchain_size in struct hist_entry\n\nSo that we can figure out the real size of the struct and also be able\nto tell if callchains may be present in this histogram entry.\n\nSince we can't always guarantee that from hist_entry->hists we can use\nhists_to_evsel, to then look at evsel->attr.sample_type for\nPERF_SAMPLE_CALLCHAIN, like with the 'perf c2c' tool, that uses plain\n'struct hists' instances, we need another way of deciding if a specific\nhist_entry instance has callchains associated with it, i.e. if its\nhist_entry->callchain[0] has space allocated for.\n\nCc: Adrian Hunter <adrian.hunter@intel.com>\nCc: David Ahern <dsahern@gmail.com>\nCc: Jin Yao <yao.jin@linux.intel.com>\nCc: Jiri Olsa <jolsa@kernel.org>\nCc: Namhyung Kim <namhyung@kernel.org>\nCc: Wang Nan <wangnan0@huawei.com>\nLink: https://lkml.kernel.org/n/tip-ptvndealxs1k7myluvu9flnq@git.kernel.org\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/41477acf092251eb0cfe83068f48dbcb2521478a"},{"sha":"e5654455795f2f89328f7b301dacb6926e57e2b8","author":{"name":"Arnaldo Carvalho de Melo","email":"293abb6b76d7791c0732cc517d38c4b5c734b87f@redhat.com"},"message":"perf hists: Make hist_entry__has_callchains() work with 'perf c2c'\n\nSince 'perf c2c' uses 'struct hists' not allocated together with a\n'struct perf_evsel' instance, we can't go from a 'struct hist_entry'\npointer to a 'struct perf_evsel' via he->hists, so, instead, check if\nspace was set aside for hist_entry->callchain[0] at hist_entry__new()\ntime.\n\nReported-by: Jin Yao <yao.jin@linux.intel.com>\nReported-by: Jiri Olsa <jolsa@kernel.org>\nCc: Adrian Hunter <adrian.hunter@intel.com>\nCc: David Ahern <dsahern@gmail.com>\nCc: Namhyung Kim <namhyung@kernel.org>\nCc: Wang Nan <wangnan0@huawei.com>\nFixes: fabd37b837f6 (\"perf hists: Check if a hist_entry has callchains before using them\")\nLink: https://lkml.kernel.org/n/tip-e8ife8djvvvwmeze3s4yodii@git.kernel.org\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/e5654455795f2f89328f7b301dacb6926e57e2b8"},{"sha":"29f9fcdd3f8edccad5809cf939ce921752460fe7","author":{"name":"Arnaldo Carvalho de Melo","email":"293abb6b76d7791c0732cc517d38c4b5c734b87f@redhat.com"},"message":"perf hists browser gtk: Use hist_entry__has_callchains()\n\nSince we can't go from struct hists to struct evsel for all cases (c2c\nis an exception) and we have access to the hist_entry, use\nhist_entry__has_callchains() in the GTK+ hists browser to figure out\nif callchains are available.\n\nCc: Adrian Hunter <adrian.hunter@intel.com>\nCc: David Ahern <dsahern@gmail.com>\nCc: Jin Yao <yao.jin@linux.intel.com>\nCc: Jiri Olsa <jolsa@kernel.org>\nCc: Namhyung Kim <namhyung@kernel.org>\nCc: Wang Nan <wangnan0@huawei.com>\nLink: https://lkml.kernel.org/n/tip-8owkgrruzzi5emvblwh4e6le@git.kernel.org\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/29f9fcdd3f8edccad5809cf939ce921752460fe7"},{"sha":"c9d366287042489090da0391318df528bdce9941","author":{"name":"Arnaldo Carvalho de Melo","email":"293abb6b76d7791c0732cc517d38c4b5c734b87f@redhat.com"},"message":"perf hists: Reimplement hists__has_callchains()\n\nThere are places where we have only access to struct hists and need to\nknow if any of its hist_entries has callchains, like when drawing\nheaders for the various output modes (stdio, TUI, etc), so, when adding\na new hist_entry, check if it has callchains, storing this info for\nlater use by hists__has_callchains().\n\nThis reimplementation is necessary because not always a 'struct hists'\nis allocated together with a 'struct perf evsel', so we can't go from\n'hists' to 'perf_event_attr.sample_type & PERF_SAMPLE_CALLCHAIN'.\n\nCc: Adrian Hunter <adrian.hunter@intel.com>\nCc: David Ahern <dsahern@gmail.com>\nCc: Jin Yao <yao.jin@linux.intel.com>\nCc: Jiri Olsa <jolsa@kernel.org>\nCc: Namhyung Kim <namhyung@kernel.org>\nCc: Wang Nan <wangnan0@huawei.com>\nLink: https://lkml.kernel.org/n/tip-hg5g7yddjio3ljwyqnnaj5dt@git.kernel.org\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/c9d366287042489090da0391318df528bdce9941"},{"sha":"f7fa827f5f432a0b1f34e10fc49da93aeef9f817","author":{"name":"Jiri Olsa","email":"2c6594f608aa3d41e98d48846a6328831f7084ad@kernel.org"},"message":"perf tools: Fix error index for pmu event parser\n\nFor events we provide specific error message we need to set error column\nindex, PMU parser is missing that, adding it.\n\nBefore:\n\n  $ perf stat -e cycles,krava/cycles/ kill\n  event syntax error: 'cycles,krava/cycles/'\n                       \\___ Cannot find PMU `krava'. Missing kernel support?\n\nAfter:\n\n  $ perf stat -e cycles,krava/cycles/ kill\n  event syntax error: 'cycles,krava/cycles/'\n                              \\___ Cannot find PMU `krava'. Missing kernel support?\n\nSigned-off-by: Jiri Olsa <jolsa@kernel.org>\nTested-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nCc: Alexander Shishkin <alexander.shishkin@linux.intel.com>\nCc: Andi Kleen <andi@firstfloor.org>\nCc: David Ahern <dsahern@gmail.com>\nCc: Frederic Weisbecker <frederic@kernel.org>\nCc: Milian Wolff <milian.wolff@kdab.com>\nCc: Namhyung Kim <namhyung@kernel.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Stephane Eranian <eranian@google.com>\nLink: http://lkml.kernel.org/r/20180606221513.11302-3-jolsa@kernel.org\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/f7fa827f5f432a0b1f34e10fc49da93aeef9f817"},{"sha":"9660e08ee8cbc94ac835f2c30576c6e51fbece8f","author":{"name":"Jiri Olsa","email":"2c6594f608aa3d41e98d48846a6328831f7084ad@kernel.org"},"message":"perf stat: Add --interval-clear option\n\nAdding --interval-clear option to clear the screen before next interval.\n\nCommitter testing:\n\n  # perf stat -I 1000 --interval-clear\n\nAnd, as expected, it behaves almost like:\n\n  # watch -n 0 perf stat -a sleep 1\n\nSigned-off-by: Jiri Olsa <jolsa@kernel.org>\nTested-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nCc: Alexander Shishkin <alexander.shishkin@linux.intel.com>\nCc: Andi Kleen <andi@firstfloor.org>\nCc: David Ahern <dsahern@gmail.com>\nCc: Frederic Weisbecker <frederic@kernel.org>\nCc: Milian Wolff <milian.wolff@kdab.com>\nCc: Namhyung Kim <namhyung@kernel.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Stephane Eranian <eranian@google.com>\nLink: http://lkml.kernel.org/r/20180606221513.11302-4-jolsa@kernel.org\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/9660e08ee8cbc94ac835f2c30576c6e51fbece8f"},{"sha":"b37d33edbf41b532ddd156707c037c6f4784e40b","author":{"name":"Jiri Olsa","email":"2c6594f608aa3d41e98d48846a6328831f7084ad@kernel.org"},"message":"perf stat: Use only color_fprintf call in print_metric_only\n\nWe can call color_fprintf also for non color case, it's handled\nproperly. This change simplifies following patch.\n\nSigned-off-by: Jiri Olsa <jolsa@kernel.org>\nCc: Alexander Shishkin <alexander.shishkin@linux.intel.com>\nCc: Andi Kleen <andi@firstfloor.org>\nCc: David Ahern <dsahern@gmail.com>\nCc: Frederic Weisbecker <frederic@kernel.org>\nCc: Milian Wolff <milian.wolff@kdab.com>\nCc: Namhyung Kim <namhyung@kernel.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Stephane Eranian <eranian@google.com>\nLink: http://lkml.kernel.org/r/20180606221513.11302-5-jolsa@kernel.org\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/b37d33edbf41b532ddd156707c037c6f4784e40b"},{"sha":"f515572734fb323aa0efe9ea2c546cd7fee327f7","author":{"name":"Jiri Olsa","email":"2c6594f608aa3d41e98d48846a6328831f7084ad@kernel.org"},"message":"perf stat: Fix metric column header display alignment\n\nMake the metric only display aligned.\n\nBefore:\n  # perf stat --topdown -I 1000\n  #           time core         cpus retiring             bad speculation      frontend bound       backend bound\n       1.000394323 S0-C0           2     37.4%               12.0%               31.4%               19.2%\n       1.000394323 S0-C1           2     25.1%                9.2%               43.8%               21.9%\n       2.001521204 S0-C0           2     36.4%               11.4%               32.4%               19.8%\n       2.001521204 S0-C1           2     26.2%                9.4%               43.1%               21.3%\n       3.001930208 S0-C0           2     35.1%               10.7%               33.6%               20.6%\n       3.001930208 S0-C1           2     28.9%               10.0%               40.0%               21.1%\n\nAfter:\n  # perf stat --topdown -I 1000\n  #           time core         cpus             retiring      bad speculation       frontend bound        backend bound\n       1.000303722 S0-C0           2                34.2%                 7.6%                34.2%                24.0%\n       1.000303722 S0-C1           2                33.1%                 6.4%                36.9%                23.6%\n       2.001281055 S0-C0           2                34.6%                 6.7%                36.8%                21.8%\n       2.001281055 S0-C1           2                32.8%                 7.1%                38.1%                22.0%\n       3.001546080 S0-C0           2                39.3%                 5.5%                32.7%                22.5%\n       3.001546080 S0-C1           2                37.8%                 6.0%                33.1%                23.1%\n\nSigned-off-by: Jiri Olsa <jolsa@kernel.org>\nTested-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nCc: Alexander Shishkin <alexander.shishkin@linux.intel.com>\nCc: Andi Kleen <andi@firstfloor.org>\nCc: David Ahern <dsahern@gmail.com>\nCc: Frederic Weisbecker <frederic@kernel.org>\nCc: Milian Wolff <milian.wolff@kdab.com>\nCc: Namhyung Kim <namhyung@kernel.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Stephane Eranian <eranian@google.com>\nLink: http://lkml.kernel.org/r/20180606221513.11302-6-jolsa@kernel.org\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/f515572734fb323aa0efe9ea2c546cd7fee327f7"},{"sha":"c1a1f5d9da800dc715d8c1d8a9692c63c70c2955","author":{"name":"Jiri Olsa","email":"2c6594f608aa3d41e98d48846a6328831f7084ad@kernel.org"},"message":"perf stat: Allow to specify specific metric column len\n\nThe following change will introduce new metrics, that doesn't need such\nwide hard coded spacing. Switch METRIC_ONLY_LEN macro usage with\nmetric_only_len variable.\n\nSigned-off-by: Jiri Olsa <jolsa@kernel.org>\nCc: Alexander Shishkin <alexander.shishkin@linux.intel.com>\nCc: Andi Kleen <andi@firstfloor.org>\nCc: David Ahern <dsahern@gmail.com>\nCc: Frederic Weisbecker <frederic@kernel.org>\nCc: Milian Wolff <milian.wolff@kdab.com>\nCc: Namhyung Kim <namhyung@kernel.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Stephane Eranian <eranian@google.com>\nLink: http://lkml.kernel.org/r/20180606221513.11302-7-jolsa@kernel.org\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/c1a1f5d9da800dc715d8c1d8a9692c63c70c2955"},{"sha":"a5cfa6217c94a1f1cfad4481fc14f5fc399abde3","author":{"name":"Jiri Olsa","email":"2c6594f608aa3d41e98d48846a6328831f7084ad@kernel.org"},"message":"perf stat: Add event parsing error handling to add_default_attributes\n\nAdd missing error handling for parse_events calls in add_default_attributes\nfunctions. The error handler displays error details, like for transactions (-T):\n\nBefore:\n  $ perf stat -T\n  Cannot set up transaction events\n\nAfter:\n  $ perf stat -T\n  Cannot set up transaction events\n  event syntax error: '..cycles,cpu/cycles-t/,cpu/tx-start/,cpu/el-start/,cpu/cycles-ct/}'\n                                    \\___ unknown term\n\nSigned-off-by: Jiri Olsa <jolsa@kernel.org>\nCc: Alexander Shishkin <alexander.shishkin@linux.intel.com>\nCc: Andi Kleen <andi@firstfloor.org>\nCc: David Ahern <dsahern@gmail.com>\nCc: Frederic Weisbecker <frederic@kernel.org>\nCc: Milian Wolff <milian.wolff@kdab.com>\nCc: Namhyung Kim <namhyung@kernel.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Stephane Eranian <eranian@google.com>\nLink: http://lkml.kernel.org/r/20180606221513.11302-8-jolsa@kernel.org\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/a5cfa6217c94a1f1cfad4481fc14f5fc399abde3"},{"sha":"4c8205273626f27b9e5a64bdc194ab483a8cce66","author":{"name":"Jiri Olsa","email":"2c6594f608aa3d41e98d48846a6328831f7084ad@redhat.com"},"message":"perf c2c: Keep struct hist_entry at the end of struct c2c_hist_entry\n\nExactly as the comment just before 'struct c2c_hist_entry\" says, i.e.\nthe last entry in struct hist_entry is a zero length array, that when\nallocating space for hist_entry gets extra space if callchains are in\nuse, which, if hist_entry is not at the end of c2c_hist_entry, the\nmembers after it gets corrupted when callchains get added to the rb\ntrees collecting them, etc.\n\nSigned-off-by: Jiri Olsa <jolsa@kernel.org>\nReported-by: Arnaldo Carvalho de Melo <acme@kernel.org>\nCc: Jin Yao <yao.jin@linux.intel.com>\nFixes: 7f834c2e84bb (\"perf c2c report: Display node for cacheline address\")\nLink: http://lkml.kernel.org/n/tip-bh0ke4fh2ygpj3yowna7o1di@git.kernel.org\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/4c8205273626f27b9e5a64bdc194ab483a8cce66"},{"sha":"fad76d4333fe73cf3f73704aa34d4ce523b1c458","author":{"name":"Seeteena Thoufeek","email":"5f80ec62099299d93a0c4795447658be8fbafd16@linux.vnet.ibm.com"},"message":"perf script: Show hw-cache events\n\n'perf script' fails to report hardware cache events (PERF_TYPE_HW_CACHE)\nwhere as 'perf report' shows the samples. Fix it. Ex,\n\n  # perf record -e L1-dcache-loads ./a.out\n  [ perf record: Woken up 1 times to write data ]\n  [ perf record: Captured and wrote 0.008 MB perf.data (11 samples)]\n\nBefore patch:\n\n  # perf script | wc -l\n  0\n\nAfter patch:\n\n  # perf script | wc -l\n  11\n\nCommitter testing:\n\n  [root@jouet ~]# perf script | head -30 | tail\n        Timer 9803 [2] 8.963330:  1554 L1-dcache-loads: 7ffef89baae4 __vdso_clock_gettime+0xf4 ([vdso])\n      swapper    0 [2] 8.963343:  5626 L1-dcache-loads: ffffffffa66f4f6b cpuidle_not_av+0xb (/lib/modules/4.17.0-rc5/build/vmlinux)\n      firefox 4853 [2] 8.964070: 18935 L1-dcache-loads: 7f0b9a00dc30 xcb_poll_for_event+0x0 (/usr/lib64/libxcb.so.1.1.0)\n  Softwar~cTh 4928 [2] 8.964548: 15928 L1-dcache-loads: ffffffffa60d795c update_curr+0x10c (/lib/modules/4.17.0-rc5/build/vmlinux)\n      firefox 4853 [2] 8.964675: 14978 L1-dcache-loads: ffffffffa6897018 mutex_unlock+0x18 (/lib/modules/4.17.0-rc5/build/vmlinux)\n  gnome-shell 2026 [3] 8.964693: 50670 L1-dcache-loads: 7fa08854de6d g_source_iter_next+0x6d (/usr/lib64/libglib-2.0.so.0.5400.3)\n   Compositor 4929 [1] 8.964784: 71772 L1-dcache-loads: 7f0b936bf078 [unknown] (/usr/lib64/firefox/libxul.so)\n     Xwayland 2096 [2] 8.964919: 16799 L1-dcache-loads: 7f68ce2fcb8a glXGetCurrentContext+0x1a (/usr/lib64/libGLX.so.0.0.0)\n  gnome-shell 2026 [3] 8.964997: 50670 L1-dcache-loads: 7fa08854de6d g_source_iter_next+0x6d (/usr/lib64/libglib-2.0.so.0.5400.3)\n  [root@jouet ~]#\n\nSigned-off-by: Seeteena Thoufeek <s1seetee@linux.vnet.ibm.com>\nTested-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nCc: Alexander Shishkin <alexander.shishkin@linux.intel.com>\nCc: Jiri Olsa <jolsa@redhat.com>\nCc: Namhyung Kim <namhyung@kernel.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/1528455748-20087-1-git-send-email-s1seetee@linux.vnet.ibm.com\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/fad76d4333fe73cf3f73704aa34d4ce523b1c458"},{"sha":"918da95176beb743ff47b3bbfb0a4ee420658a95","author":{"name":"Andrew Jeffery","email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@aj.id.au"},"message":"fsi: gpio: Trace busy count\n\nAn observation from trace output of the existing FSI tracepoints was\nthat the remote device was sometimes reporting as busy. Add a new\ntracepoint reporting the busy count in order to get a better grip on how\noften this is the case.\n\nSigned-off-by: Andrew Jeffery <andrew@aj.id.au>\nAcked-by: Eddie James <eajames@linux.vnet.ibm.com>\nSigned-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nTested-by: Joel Stanley <joel@jms.id.au>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/918da95176beb743ff47b3bbfb0a4ee420658a95"},{"sha":"e212ab47bd029466ad758a24831e3046a34ebda1","author":{"name":"Andrew Jeffery","email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@aj.id.au"},"message":"fsi: gpio: Remove unused 'id' variable\n\nSigned-off-by: Andrew Jeffery <andrew@aj.id.au>\nSigned-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nTested-by: Joel Stanley <joel@jms.id.au>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/e212ab47bd029466ad758a24831e3046a34ebda1"},{"sha":"e5538139e043bcae133da1e55f02b0646eb601fa","author":{"name":"Jeremy Kerr","email":"68a658b44bbaefab3ef5cd231967195fc0ff9d69@ozlabs.org"},"message":"fsi: gpio: Use a mutex to protect transfers\n\nReduce time spent with interrupts disabled by limiting the critical\nsections to bitbanging FSI symbols. We only need to ensure exclusive use\nof the bus for an entire transfer, not that the transfer be performed in\natomic context.\n\nSigned-off-by: Jeremy Kerr <jk@ozlabs.org>\nSigned-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nTested-by: Joel Stanley <joel@jms.id.au>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/e5538139e043bcae133da1e55f02b0646eb601fa"},{"sha":"5d0d16f135c0cb7a12e417cbe12b271524ce4d40","author":{"name":"Benjamin Herrenschmidt","email":"a7089bb6e7e92505d88aaff006cbdd60cc9120b6@kernel.crashing.org"},"message":"fsi/fsi-master-gpio: Sample input data on different clock phase\n\nWe currently sample the input data right after we toggle the\nclock low, then high. The slave establishes the data on the\nrising edge, so this is not ideal. We should sample it on\nthe low phase instead.\n\nThis currently works because we have an extra delay, but subsequent\npatches will remove it.\n\nSigned-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nReviewed-by: Christopher Bostic <cbostic@linux.vnet.ibm.com>\nTested-by: Joel Stanley <joel@jms.id.au>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/5d0d16f135c0cb7a12e417cbe12b271524ce4d40"},{"sha":"bc1099d2b2519fa0f6c7613d8de398df8438a36b","author":{"name":"Benjamin Herrenschmidt","email":"a7089bb6e7e92505d88aaff006cbdd60cc9120b6@kernel.crashing.org"},"message":"fsi/fsi-master-gpio: Add \"no-gpio-delays\" option\n\nThis adds support for an optional device-tree property that\nmakes the driver skip all the delays around clocking the\nGPIOs and set it in the device-tree of common POWER9 based\nOpenPower platforms.\n\nThis useful on chips like the AST2500 where the GPIO block is\nrunning at a fairly low clock frequency (25Mhz typically). In\nthis case, the delays are unnecessary and due to the low\nprecision of the timers, actually quite harmful in terms of\nperformance.\n\nSigned-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nReviewed-by: Christopher Bostic <cbostic@linux.vnet.ibm.com>\nTested-by: Joel Stanley <joel@jms.id.au>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/bc1099d2b2519fa0f6c7613d8de398df8438a36b"},{"sha":"97a4e5c95bf762ac254209dc4808ee5138ee574e","author":{"name":"Benjamin Herrenschmidt","email":"a7089bb6e7e92505d88aaff006cbdd60cc9120b6@kernel.crashing.org"},"message":"fsi/fsi-master-gpio: Reduce turnaround clocks\n\nFSI_GPIO_PRIME_SLAVE_CLOCKS is the number of clocks if the\n\"idle\" phase between the end of a response and the beginning\nof the next one. It corresponds to tSendDelay in the FSI\nspecification.\n\nThe default value in the slave is 16 clocks. 100 is way overkill\nand significantly reduces the driver performance.\n\nThis changes it to 20 (which gives the HW a bit of margin still\njust in case).\n\nSigned-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nReviewed-by: Christopher Bostic <cbostic@linux.vnet.ibm.com>\nTested-by: Joel Stanley <joel@jms.id.au>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/97a4e5c95bf762ac254209dc4808ee5138ee574e"},{"sha":"b632642e4ce22f1fbf2094752e936565771b34f4","author":{"name":"Benjamin Herrenschmidt","email":"a7089bb6e7e92505d88aaff006cbdd60cc9120b6@kernel.crashing.org"},"message":"fsi/fsi-master-gpio: Reduce dpoll clocks\n\nFSI_GPIO_DPOLL_CLOCKS is the number of clocks before sending\na DPOLL command after receiving a BUSY status. It should be\nat least tSendDelay (16 clocks).\n\nAccording to comments in the code, it needs to also be at least\n21 clocks due to HW issues.\n\nIt's currently 100 clocks which impacts performances negatively\nin some cases. Reduces it in half to 50 clocks which seems to\nstill be solid.\n\nSigned-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nReviewed-by: Christopher Bostic <cbostic@linux.vnet.ibm.com>\nTested-by: Joel Stanley <joel@jms.id.au>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/b632642e4ce22f1fbf2094752e936565771b34f4"},{"sha":"f3ca4834ac335bbf693d424326e4c93523a0c245","author":{"name":"Benjamin Herrenschmidt","email":"a7089bb6e7e92505d88aaff006cbdd60cc9120b6@kernel.crashing.org"},"message":"fsi/fsi-master-gpio: Delay sampling of FSI data input\n\nMost SoC GPIO implementations, including the Aspeed one, have\nsynchronizers on the GPIO inputs. This means that the value\nread from a GPIO is a couple of clocks old, from whatever clock\nsource feeds those synchronizers.\n\nIn practice, this means that in no-delay mode, we are using a\nvalue that can potentially be a bit too old and too close to\nthe clock edge establishing the data on the other side of the link.\n\nThe voltage converters we use on some systems make this worse\nand sensitive to things like voltage fluctuations etc... This is,\nwe believe, the cause of occasional CRC errors encountered during\nheavy activity on the LPC bus.\n\nThis is fixed by introducing a dummy GPIO read before the actual\ndata read. It slows down SBEFIFO by about 15% (less than any delay\nprimitive) and the end result is so far solid.\n\nSigned-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nReviewed-by: Christopher Bostic <cbostic@linux.vnet.ibm.com>\nTested-by: Joel Stanley <joel@jms.id.au>","distinct":true,"url":"https://api.github.com/repos/pgwipeout/linux/commits/f3ca4834ac335bbf693d424326e4c93523a0c245"}]}
{"actor":{"display_login":"pgwipeout"}}