tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
dev.2019.04.28a
head: a4e0e069df6e8718bf165fb009cd3a23e7a808a3
commit: a4e0e069df6e8718bf165fb009cd3a23e7a808a3 [85/85] rcu/sync: Simplify the
state machine
reproduce: make htmldocs
If you fix the issue, kindly add f
On Thu, 2017-03-30 at 10:19:25 UTC, Joe Perches wrote:
> Fix fallout too.
>
> Signed-off-by: Joe Perches
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/1e496391a8452101308a23b7395cdd49
cheers
Hi Thomas,
Thank you for the review. I read your comments. All of them look
reasonable. I'm sorry that you had to comment a lot. Will fix in the
next version.
Thanks,
Andrei
On Thu, Apr 25, 2019 at 11:28:24PM +0200, Thomas Gleixner wrote:
> On Thu, 25 Apr 2019, Dmitry Safonov wrote:
> > From: A
On Mon, 2019-03-11 at 22:47:46 UTC, Valentin Schneider wrote:
> Since the enabling and disabling of IRQs within preempt_schedule_irq()
> is contained in a need_resched() loop, we don't need the outer arch
> code loop.
>
> Signed-off-by: Valentin Schneider
> Cc: Benjamin Herrenschmidt
> Cc: Paul
On Thu, 2019-03-28 at 13:03:45 UTC, Christophe Leroy wrote:
> early_alloc_pgtable() never returns NULL as it panics on failure.
>
> This patch drops the three BUG_ON() which check the non nullity
> of early_alloc_pgtable() returned value.
>
> Signed-off-by: Christophe Leroy
Applied to powerpc n
Hi Arnd,
On 16/4/19 6:24 am, Arnd Bergmann wrote:
drivers should not rely on machine specific headers but
get their information from the platform device.
Signed-off-by: Arnd Bergmann
I dug out some old ks8695 based hardware to try this out.
I had a lot of trouble getting anything modern work
On Thu, 2 May 2019 at 20:52, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.173 release.
> There are 32 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Resp
Hi Mani
On 5/3/19 7:31 AM, Manivannan Sadhasivam wrote:
Add missing pinctrl definitions for STM32MP157 MPU.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm/boot/dts/stm32mp157-pinctrl.dtsi | 62 +++
1 file changed, 62 insertions(+)
diff --git a/arch/arm/boot/dts/stm32
On Thu, May 2, 2019 at 10:43 AM michael.kao wrote:
>
> Add dynamic power coefficients for all cores and update those of
> CPU0 and CPU4.
>
> Signed-off-by: Michael.Kao
> ---
> arch/arm64/boot/dts/mediatek/mt8183.dtsi | 16
> 1 file changed, 16 insertions(+)
>
> diff --git a/arch
On Fri, May 3, 2019 at 8:02 AM Greg Ungerer wrote:
> I dug out some old ks8695 based hardware to try this out.
> I had a lot of trouble getting anything modern working on it.
> In the end I still don't have a reliable test bed to test this properly.
What is usually used by old ARMv4 systems is O
On 02-05-19, 11:32, Matthias Kaehlcke wrote:
> The CPU load values passed to the thermal_power_cpu_get_power
> tracepoint are zero for all CPUs, unless, unless the
> thermal_power_cpu_limit tracepoint is enabled too:
>
> irq/41-rockchip-98[000] 290.972410: thermal_power_cpu_get_power:
Add wireless mode, signal strength level, and rate table index
to tell the firmware that we need to adjust the tx rate bitmap
accordingly.
---
.../net/wireless/realtek/rtl8xxxu/rtl8xxxu.h | 45 +++
.../wireless/realtek/rtl8xxxu/rtl8xxxu_core.c | 45 ++-
2 files cha
On Thu, 2 May 2019 at 20:55, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.39 release.
> There are 72 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Resp
We have 3 laptops which connect the wifi by the same RTL8723BU.
The PCI VID/PID of the wifi chip is 10EC:B720 which is supported.
They have the same problem with the in-kernel rtl8xxxu driver, the
iperf (as a client to an ethernet-connected server) gets ~1Mbps.
Nevertheless, the signal strength is
Introduce watchdog to monitor signal then update the rate mask
accordingly. The rate mask update logic comes from the rtlwifi
refresh_rate_adaptive_mask() from different chips.
---
.../net/wireless/realtek/rtl8xxxu/rtl8xxxu.h | 8 +
.../realtek/rtl8xxxu/rtl8xxxu_8723b.c | 151 ++
Updates license to use SPDX-License-Identifier.
Signed-off-by: Yangtao Li
---
drivers/iio/adc/sun4i-gpadc-iio.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/iio/adc/sun4i-gpadc-iio.c
b/drivers/iio/adc/sun4i-gpadc-iio.c
index 9b6fc592f54c..cf2bf3ab3342 100644
-
For some SOCs, the temperature data register start address may be
different, so introduce temp_data in gpadc_data.
Also modify read temperature to support multiple sensor.
Signed-off-by: Yangtao Li
---
drivers/iio/adc/sun4i-gpadc-iio.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-
> > > As you say, either is fine with me.
> > >
> > > > 2. Who is going to pull this patch: This seems a matter of where the
> > > > header
> > > > archive resides. If it is in /sys/kernel/ then I am assuming Greg will
> > > > pull
> > > > it. Masahiro has given his Reviewed-by tag, is he the on
For some SOCs, there are more than one thermal sensor, and there are
currently four sensors on the A80. So we need to do some work in order
to support multiple thermal sensors:
1) add sensor_count in gpadc_data.
2) introduce sun4i_sensor_tzd in sun4i_gpadc_iio, to support multiple
thermal
Different sensors may have different enable and disable functions, so
introduce enable and disable in gpadc_data to support soc specific
function.
Signed-off-by: Yangtao Li
---
drivers/iio/adc/sun4i-gpadc-iio.c | 37 ++-
1 file changed, 31 insertions(+), 6 deletions(-
This patch adds documentation for the H6 GPADC binding.
Signed-off-by: Yangtao Li
---
.../devicetree/bindings/mfd/sun4i-gpadc.txt | 27 +--
1 file changed, 25 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/mfd/sun4i-gpadc.txt
b/Documentation/devi
This patch adds support for the H6 ths sensor.
TODO: calibrate thermal sensor by using information from sid.
Signed-off-by: Yangtao Li
---
drivers/iio/adc/sun4i-gpadc-iio.c | 65 +++
include/linux/mfd/sun4i-gpadc.h | 9 +
2 files changed, 74 insertions(+)
dif
On Fri, May 03, 2019 at 12:19:51PM +0530, Naresh Kamboju wrote:
> On Thu, 2 May 2019 at 21:00, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 5.0.12 release.
> > There are 101 patches in this series, all will be posted as a response
> > to this one. If an
H6 has bus clock and a reset, so introduce something in
gpadc_data/sun4i_gpadc_iio and adds the process of the
clocks and resets.
This is pre-work for supprt it.
Signed-off-by: Yangtao Li
---
drivers/iio/adc/sun4i-gpadc-iio.c | 32 +--
1 file changed, 30 insertions(+
This patchset adds support for the H6 ths sensor.
Based on IIO-based thermal sensor driver for Allwinner H3 and A83T SoC,
thx to Philipp Rossak's work.
TODO: calibrate thermal sensor by using information from sid.
Yangtao Li (7):
iio: adc: sun4i-gpadc: rework for support multiple thermal senso
Hi Greg,
This is the second pull request of habanalabs driver for kernel 5.2.
As the tag describes, all of the changes are either bug fixes or simple
re-factoring of existing code, so they should all be relatively low-risk.
Thanks,
Oded
The following changes since commit 78e6427b4e7b01795178598
On Thu, May 02, 2019 at 07:39:20PM +0200, Greg Kroah-Hartman wrote:
> On Wed, Apr 24, 2019 at 09:23:43PM +0200, Eugeniu Rosca wrote:
> > From: Suresh Udipi
> >
> > It looks like v4.18-rc1 commit [0] which upstreams mld-1.8.0
> > commit [1] missed to fix the memory leak in mod_exit function.
> >
Hi,
On Thu, May 2, 2019 at 11:37 PM Błażej Szczygieł wrote:
>
> Since recent high resolution scrolling changes the A4Tech driver must
> check for the "REL_WHEEL_HI_RES" usage code.
>
> Fixes: 2dc702c991e3774af9d7ce410eef410ca9e2357e (HID: input: use the
> Resolution Multiplier for high-resolution
On Fri 2019-05-03 11:16:26, Tobin C. Harding wrote:
> On Thu, May 02, 2019 at 10:34:12AM +0200, Petr Mladek wrote:
> > On Wed 2019-05-01 09:38:03, Tobin C. Harding wrote:
> > I guess that we need two examples. I currently understand
> > it the following way:
> >
> > 1. sysfs interface and the stru
On Fri, May 3, 2019 at 10:51 AM Greg KH wrote:
>
> On Fri, May 03, 2019 at 10:36:21AM +0300, Oded Gabbay wrote:
> > Hi Greg,
> >
> > This is the second pull request of habanalabs driver for kernel 5.2.
> >
> > As the tag describes, all of the changes are either bug fixes or simple
> > re-factoring
There was NVMEM support added to of_get_mac_address, so it could now
return NULL and ERR_PTR encoded error values, so we need to adjust all
current users of of_get_mac_address to this new fact.
Signed-off-by: Petr Štetiar
---
drivers/staging/octeon/ethernet.c | 2 +-
1 file changed, 1 insertion(
On Fri, May 03, 2019 at 11:40:15AM +1000, Tobin C. Harding wrote:
> On Thu, May 02, 2019 at 10:39:22AM +0200, Johan Hovold wrote:
> > On Thu, May 02, 2019 at 06:25:39PM +1000, Tobin C. Harding wrote: > Adding
> > Jon to CC
> > >
> > > On Thu, May 02, 2019 at 09:38:23AM +0200, Johan Hovold wrote:
There was NVMEM support added to of_get_mac_address, so it could now
return NULL and ERR_PTR encoded error values, so we need to adjust all
current users of of_get_mac_address to this new fact.
Signed-off-by: Petr Štetiar
---
arch/arm/mach-mvebu/kirkwood.c | 3 ++-
1 file changed, 2 insertions(+
Hi Marcel,
On 2019-04-27 13:59, Marcel Holtmann wrote:
Hi Rob,
This patch adds an optional device property "firmware-name" to
allow
the
driver to load customized nvm firmware file based on this property.
Signed-off-by: Rocky Liao
---
Changes in v3:
* added firmware-name instead of nvm-postf
On Fri, May 03, 2019 at 10:36:21AM +0300, Oded Gabbay wrote:
> Hi Greg,
>
> This is the second pull request of habanalabs driver for kernel 5.2.
>
> As the tag describes, all of the changes are either bug fixes or simple
> re-factoring of existing code, so they should all be relatively low-risk.
On Fri, May 03, 2019 at 09:30:07AM +0200, Pavel Machek wrote:
> > > > As you say, either is fine with me.
> > > >
> > > > > 2. Who is going to pull this patch: This seems a matter of where the
> > > > > header
> > > > > archive resides. If it is in /sys/kernel/ then I am assuming Greg
> > > > > w
There was NVMEM support added directly to of_get_mac_address, and it
uses nvmem_get_mac_address under the hood, so we can remove it. As
of_get_mac_address can now return NULL and ERR_PTR encoded error values,
adjust to that as well.
Signed-off-by: Petr Štetiar
---
Changes since v2:
* ERR_PTR
hi Guenter
On 5/2/19 10:21 PM, Guenter Roeck wrote:
On Thu, May 02, 2019 at 04:08:44PM +0200, Ludovic Barre wrote:
From: Ludovic Barre
This patch updates to devm_watchdog_register_device interface
Not that easy. See below.
A more complete solution is at
https://patchwork.kernel.org/patch/1
On Thu, May 2, 2019 at 10:43 AM michael.kao wrote:
>
> Add thermal zone node to Mediatek MT8183 dts file.
>
> Signed-off-by: Michael Kao
> ---
> arch/arm64/boot/dts/mediatek/mt8183.dtsi | 64
>
> 1 file changed, 64 insertions(+)
>
> diff --git a/arch/arm64/boot/
On 01/05/2019 18:48, Guenter Roeck wrote:
> On Thu, Apr 18, 2019 at 12:58:15PM -0700, Guenter Roeck wrote:
>> thermal_of_cooling_device_register() and thermal_cooling_device_register()
>> are typically called from driver probe functions, and
>> thermal_cooling_device_unregister() is called from rem
On Fri 2019-05-03 09:56:07, Johan Hovold wrote:
> On Fri, May 03, 2019 at 11:40:15AM +1000, Tobin C. Harding wrote:
> > On Thu, May 02, 2019 at 10:39:22AM +0200, Johan Hovold wrote:
> > I am totally aware this is close to code churn and any discussion is
> > bikeshedding ... for me just because loa
On Thu, 02 May 2019 19:27:00 +0200,
Ross Zwisler wrote:
>
> Several sound related entries in MAINTAINERS refer to the old git tree
> at "git://git.alsa-project.org/alsa-kernel.git". This is no longer used
> for development, and Takashi Iwai's kernel.org tree is used instead.
>
> Signed-off-by: R
hi,
this patchset adds dso support to read and display
bpf code in intel_pt trace output. I had to change
some of the kernel maps processing code, so hopefully
I did not break too many things ;-)
It's now possible to see bpf code flow via:
# perf-with-kcore record pt -e intel_pt//ku -- sleep 1
Moving file specific code in dso__data_file_size function
into separate file_size function. I'll add bpf specific
code in following patches.
Link: http://lkml.kernel.org/n/tip-rkcsft4a0f8sw33p67llx...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/dso.c | 19 ---
1 f
On Thu, May 02, 2019 at 03:49:44PM -0400, Sean Paul wrote:
> From: Sean Paul
>
> This patch adds a helper to tease out the currently connected crtc for
> an encoder, along with its state. This follows the same pattern as the
> drm_atomic_crtc_*_for_* macros in the atomic helpers. Since the
> rela
We need to preserve eBPF maps even if they are
covered by kcore, because we need to access
eBPF dso for source data.
Adding map_groups__merge_in function to do that.
It merges map into map_groups by splitting the
new map within the existing map regions.
Suggested-by: Adrian Hunter
Link: http://l
There's no need to display "ksymbol event with" text
for PERF_RECORD_KSYMBOL event and "bpf event with" test
for PERF_RECORD_BPF_EVENT event.
Removing it so it also goes along with other side-band
events display.
Before:
# perf script --show-bpf-events
...
swapper 0 [000] 0.00:
Adding --show-bpf-events to show eBPF related events:
PERF_RECORD_KSYMBOL
PERF_RECORD_BPF_EVENT
Usage:
# perf record -a
...
# perf script --show-bpf-events
...
swapper 0 [000] 0.00: PERF_RECORD_KSYMBOL ksymbol event with addr
c0ef971d len 229 type 1 flags 0x0 nam
On Thu, May 02, 2019 at 03:49:46PM -0400, Sean Paul wrote:
> From: Sean Paul
>
> Everyone who implements connector_helper_funcs->atomic_check reaches
> into the connector state to get the atomic state. Instead of continuing
> this pattern, change the callback signature to just give atomic state
>
We mark the end of kernel based on the first module,
but that could cover some bpf program maps. Reading
_etext symbol if it's present to get precise kernel
map end.
Link: http://lkml.kernel.org/n/tip-ynut991ttyyhvo1sbhlm4...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/machine.c
Adding --show-all-events option to show all
side-bad events with single option, like:
$ perf script --show-all-events
swapper 0 [000] 0.00: PERF_RECORD_MMAP -1/0:
[0xa600(0xc00e41) @ 0xa600]: x [kernel.kallsyms]_text
...
swapper 0 [000] 0.00
Adding map_groups__merge_in to test map_groups__merge_in
function usage - merging kcore maps into existing eBPF
maps.
Link: http://lkml.kernel.org/n/tip-dj6v01kbt4upvkw3hccmc...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/tests/Build | 1 +
tools/perf/tests/builtin-test.c |
There's no need for the while loop now, also we can
connect two (ret > 0) condition legs together.
Link: http://lkml.kernel.org/n/tip-2vg28bak8euojuvq33cy2...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/dso.c | 17 ++---
1 file changed, 6 insertions(+), 11 deletions(-
With pgoff set to zero, the map__map_ip function
will return bpf address based from 0, which is
what we need when we read the data from bpf dso.
Adding bpf symbols with mapped ip addresses as well.
Link: http://lkml.kernel.org/n/tip-nqgyzbqgekvxqc5tjmsb3...@git.kernel.org
Signed-off-by: Jiri Olsa
Moving file specific code in dso_cache__read function
into separate file_read function. I'll add bpf specific
code in following patches.
Link: http://lkml.kernel.org/n/tip-7f7d717uzrqt5ka2xp29i...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/dso.c | 48
Padding dso name for --call-trace so we don't have the
indent screwed by different dso name lengths, as now
for kernel there's also bpf code displayed.
# perf-with-kcore record pt -e intel_pt//ku -- sleep 1
# perf-core/perf-with-kcore script pt --call-trace
Before:
sleep 36660 [016
Adding bpf related code into dso reading paths to return
size (bpf_size) and read the bpf code (bpf_read).
Link: http://lkml.kernel.org/n/tip-ql6jpegvv5823yc87u0hl...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/dso.c | 49 ++-
1 file change
On 5/3/19 08:26, Mark Brown wrote:
> On Thu, May 02, 2019 at 01:30:48PM +0200, Jorge Ramirez wrote:
>> On 5/2/19 04:33, Mark Brown wrote:
>
>>> I'm not sure I follow here, sorry - I can see that the driver needs a
>>> custom get/set selector operation but shouldn't it be able to use the
>>> standa
On Thu, May 02, 2019 at 05:46:08PM -0400, Joel Savitz wrote:
> > Won't be possible to use put_user here? Something like
> >
> > static int prctl_get_tasksize(unsigned long __user *uaddr)
> > {
> > return put_user(TASK_SIZE, uaddr) ? -EFAULT : 0;
> > }
>
> What would be the benefit of using
On Thu 2019-05-02 17:20:31, Greg Kroah-Hartman wrote:
> [ Upstream commit 2795e8c251614ac0784c9d41008551109f665716 ]
>
> In case alloc_ordered_workqueue fails, the fix releases
> sources and returns -ENOMEM to avoid NULL pointer dereference.
>
> Signed-off-by: Kangjie Lu
> Acked-by: Michael Henn
On Thu 2019-05-02 17:20:32, Greg Kroah-Hartman wrote:
> [ Upstream commit 19b39a25388e71390e059906c979f87be4ef0c71 ]
>
> genlmsg_reply can fail, so propagate its return code
> diff --git a/drivers/net/ieee802154/mac802154_hwsim.c
> b/drivers/net/ieee802154/mac802154_hwsim.c
> index 624bff4d3636.
The only type of IRQ triggering event that is useful to us at the moment
is the "last block" interrupt of the MSU. This interrupt can only be
enabled via "MINTCTL" register that doesn't exist in earlier version of
the Intel TH.
Enumerate the presence of MINTCTL via per-device driver data structure
2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm.git
tags/intel_th-for-greg-20190503
for you to fetch changes up to c0e8a65abd2e4ad47e5257de6bde1822e9c458b6:
intel_th: msu: Preserve
In some versions of Intel TH, the Software Trace Hub (STH) has a second
MMIO BAR dedicated to the input from Intel PT. This calls for a new
subdevice that will be enumerated if the corresponding BAR is present.
Signed-off-by: Alexander Shishkin
---
drivers/hwtracing/intel_th/core.c | 18
Now that the MSU is using scatterlist, we can support multipage blocks.
At the moment, the code assumes that all blocks are page-sized, but in
larger buffers it may make sense to chunk together larger blocks of
memory. One place where one-to-many relationship needs to be handled is
the MSU buffer's
Since Intel TH is capable of MSI interrupt signalling, make use of it.
The way it works is, each of the 7 interrupt triggering events has its
own vector in this mode, as opposed to interrupt line delivery, where
all events are signalled via the same line. Failing to enable MSI, the
driver falls bac
Add the SPDX header to the Intel TH documentation.
Signed-off-by: Alexander Shishkin
Tested-by: Mathieu Poirier
---
Documentation/trace/intel_th.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/trace/intel_th.rst b/Documentation/trace/intel_th.rst
index 19e2d633f3c7..baa1
The code that waits for the pipeline empty condition of the MSU is
currently called in the path that disables the trace. We will also
need this in the window switch trigger sequence. Therefore, factor
out this code and make it accessible to the GTH device.
Signed-off-by: Alexander Shishkin
---
d
There are a few places in the code where open-coded versions of list entry
accessors list_first_entry()/list_last_entry()/list_next_entry() are used.
Replace those with the standard macros.
Signed-off-by: Alexander Shishkin
---
drivers/hwtracing/intel_th/msu.c | 20 ++--
1 file
The MSU configuration registers may contain buffer address/size set by
the BIOS or an external hardware debugger, which may want to take over
tracing from the driver when the driver is not actively tracing.
Preserve these settings when not actively tracing.
Signed-off-by: Alexander Shishkin
---
Now that we have a way to switch between MSC buffer windows, add code to
track the current window. The hardware register NWSA that contains the
address of the next window is unfortunately not always usable, and since
the driver has full control of the window switching, there is no reason
not to kee
Introduces a concept of buffer drivers, which is a mechanism for creating
trace sinks that would receive trace data from MSC buffers and transfer it
elsewhere.
A buffer driver can implement its own window allocation/deallocation if
it has to. It must provide a callback that's used to notify it whe
Now that we have the means to trigger a window switch for the MSU trace
store, add a sysfs file to allow triggering it from userspace.
Signed-off-by: Alexander Shishkin
---
.../testing/sysfs-bus-intel_th-devices-msc| 8 ++
drivers/hwtracing/intel_th/msu.c | 28 +
In multi window mode the MSU will set "window wrap" bit to indicate block
wrapping as well. Take this into account when checking data blocks.
Signed-off-by: Alexander Shishkin
---
drivers/hwtracing/intel_th/msu.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwtraci
The trace enable/disable functions of the GTH include the code that starts
and stops trace flom from the sources. This start/stop functionality will
also be used in the window switch trigger sequence.
Factor out start/stop code from the larger trace enable/disable code in
preparation for the windo
Add support for asserting window switch trigger when tracing to MSU output
ports. This allows for software controlled switching between windows of
the MSU buffer, which can be used for double buffering while exporting the
trace data further from the MSU.
Signed-off-by: Alexander Shishkin
---
dri
Tested on socfpga cyclone5 where this is required to ensure that the
boot rom can access this flash after warm reboot.
Signed-off-by: Simon Goldschmidt
---
drivers/mtd/spi-nor/spi-nor.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/m
Commit 5768402fd9c6e87 ("perf/ring_buffer: Use high order allocations for
AUX buffers optimistically") overlooked the fact that the previous one page
granularity of the AUX buffer provided an implicit double buffering
capability to the PMU driver, which went away when the entire buffer became
one h
We intend to use the interrupt to detect Last Block condition in the MSU
driver, which we can use for double-buffering software-managed data
transfers.
Add an interrupt handler to the MSU driver.
Signed-off-by: Alexander Shishkin
---
drivers/hwtracing/intel_th/core.c | 32 ++
dr
Currently, MMIO resource numbers in the TH driver core correspond to
PCI BAR numbers, because in the beginning there was only the PCI glue
layer. This created some confusion when the ACPI glue layer was added.
To avoid confusion and remove glue-specific code from the driver core,
split the resourc
With the addition of dynamically loadable buffer drivers, there needs
to be a way of knowing the currently available ones without having to
scan the list of loaded modules or trial and error.
Add a sysfs file that lists all the currently available "modes", listing
both the MSC hardware operating m
On Fri, May 03, 2019 at 09:47:03AM +0900, Tetsuo Handa wrote:
> On 2019/05/03 5:46, Daniel Vetter wrote:
> > There's the hung_task_panic sysctl, but that's a bit an extreme measure.
> > As a fallback taint at least the machine.
> >
> > Our CI uses this to decide when a reboot is necessary, plus to
Currently, the pages that are allocated for the single mode of MSC are not
mapped into the device's dma space and the code is incorrectly using
*_to_phys() in place of a dma address. This fails with IOMMU enabled and
is otherwise bad practice.
Fix the single mode buffer allocation to map the pages
If a subdevice requires an MMIO region that wasn't in the resources passed
down from the glue layer, don't instantiate it, but don't error out. This
means that that particular subdevice doesn't exist for this instance of
Intel TH, which is a perfectly normal situation. This applies, for example,
to
Instead of using a home-grown array of pointers to the DMA pages, switch
over to scatterlist data types and accessors, which has all the convenient
accessors, can be used to batch-map DMA memory and is convenient for
passing around between different layers, which will be useful when MSU
buffer mana
Currently, the IRQ is passed between the glue layers and the core as a
separate argument, while the MMIO resources are passed as resources.
This also limits the number of IRQs thus used to one, while the current
versions of Intel TH use a different MSI vector for each interrupt
triggering event, of
This patch adds an example "sink" MSU buffer driver, which consumes trace
data from MSC buffers.
Functionally, it acts similarly to "multi" mode with automatic window
switching.
Signed-off-by: Alexander Shishkin
---
drivers/hwtracing/intel_th/Makefile | 3 +
drivers/hwtracing/intel_th/msu-s
Hi Peter,
There was a problem with 04fe30a61514 ("perf/ring_buffer: Use high order
allocations for AUX buffers optimistically") that made buffers that were
previously scattered across multiple pages into one large buffer, breaking
double buffering. In practice, this manifests easily for non-privil
Now that all AUX allocations are high-order by default, the software
double buffering PMU capability doesn't make sense any more, get rid
of it. In case some PMUs choose to opt out, we can re-introduce it.
Signed-off-by: Alexander Shishkin
---
arch/x86/events/intel/pt.c | 3 +--
include/linux/pe
Alexander Shishkin writes:
> Hi Peter,
>
> New PEBS feature: output to Intel PT stream instead of the DS area. It's
> theoretically useful in virtualized environments, where DS area can't be
> used. It's also good for those who are interested in instruction trace for
> context of the PEBS events.
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/mips/kernel/setup.c
between commit:
b93ddc4f9156 ("mips: Reserve memory for the kernel image resources")
from the mips tree and commit:
68c7c323926b ("mips: replace CONFIG_DEBUG_KERNEL with CONFIG_DEBUG_MI
Hi Mani
On 5/3/19 7:31 AM, Manivannan Sadhasivam wrote:
Add devicetree support for Avenger96 board based on STM32MP157A MPU
from ST Micro. This board is one of the 96Boards Consumer Edition board
from Arrow Electronics and has the following features:
SoC: STM32MP157AAC
PMIC: STPMIC1A
RAM: 1024
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
fs/sync.c
between commit:
22f96b3808c1 ("fs: add sync_file_range() helper")
from the block tree and commit:
9a8d18789a18 ("fs/sync.c: sync_file_range(2) may use WB_SYNC_ALL writeback")
from the akpm-current tr
This changes system reboot for socfpga to issue a cold reboot by
default instead of a warm reboot.
Warm reboot can still be used by setting reboot_mode to
REBOOT_WARM (e.g. via kernel command line 'reboot='), but this
patch ensures cold reboot is issued for both REBOOT_COLD and
REBOOT_HARD.
Also,
Sergei Shtylyov [2019-05-03 11:44:54]:
Hi Sergei,
> > diff --git a/drivers/of/of_net.c b/drivers/of/of_net.c
> > index d820f3e..258ceb8 100644
> > --- a/drivers/of/of_net.c
> > +++ b/drivers/of/of_net.c
> [...]
> > @@ -64,6 +113,9 @@ static const void *of_get_mac_addr(struct device_node
> > *np
On Fri, May 03, 2019 at 03:28:13AM -0400, Yangtao Li wrote:
> Updates license to use SPDX-License-Identifier.
>
> Signed-off-by: Yangtao Li
> ---
> drivers/iio/adc/sun4i-gpadc-iio.c | 5 +
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/drivers/iio/adc/sun4i-gpadc-iio.c
> b
Hi,
I used the hid-record tool and my results are here:
https://gitlab.com/snippets/1853568
Cheers,
Błażej
Hi,
On Thu, May 2, 2019 at 11:37 PM Błażej Szczygieł wrote:
Since recent high resolution scrolling changes the A4Tech driver must
check for the "REL_WHEEL_HI_RES" usage code.
Fixes:
On 02/05/2019 16:20, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.116 release.
> There are 49 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses s
On Thu, May 02, 2019 at 07:50:52PM -0400, Steven Rostedt wrote:
> On Thu, 2 May 2019 19:31:29 -0400
> Steven Rostedt wrote:
>
> > Digging a little further, I pinpointed it out to being kretprobes. The
> > problem I believe is the use of kernel_stack_pointer() which does some
> > magic on x86_32.
This adds compatible for the MediaTek MT6358 PMIC.
Acked-for-MFD-by: Lee Jones
Signed-off-by: Hsin-Hsiung Wang
---
Documentation/devicetree/bindings/mfd/mt6397.txt | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/mfd/mt6397.txt
b
1 - 100 of 542 matches
Mail list logo
