[PATCH] atm: firestream: Replace GFP_ATOMIC with GFP_KERNEL in fs_send

After checking all possible call chains to fs_send() here, my tool finds that fs_send() is never called in atomic context. And this function is assigned to a function pointer "dev->ops->send", which is only called by vcc_sendmsg() (net/atm/common.c) through vcc->dev->ops->send(), and vcc_sendmsg()

[PATCH] atm: firestream: Replace GFP_ATOMIC with GFP_KERNEL in fs_send

After checking all possible call chains to fs_send() here, my tool finds that fs_send() is never called in atomic context. And this function is assigned to a function pointer "dev->ops->send", which is only called by vcc_sendmsg() (net/atm/common.c) through vcc->dev->ops->send(), and vcc_sendmsg()

Re: [PATCH v4 4/8] PCI: brcmstb: Add dma-range mapping for inbound traffic

On Wed, Jan 24, 2018 at 12:04:58PM -0800, Florian Fainelli wrote: > This looks nicer than the current shape, but this still requires to > register a PCI fixup to override phys_to_dma() and dma_to_phys(), and it > would appear that you have dodged my question about how this is supposed > to fit

Re: [PATCH v4 4/8] PCI: brcmstb: Add dma-range mapping for inbound traffic

On Wed, Jan 24, 2018 at 12:04:58PM -0800, Florian Fainelli wrote: > This looks nicer than the current shape, but this still requires to > register a PCI fixup to override phys_to_dma() and dma_to_phys(), and it > would appear that you have dodged my question about how this is supposed > to fit

Re: [RFC v2 3/4] drm/nouveau: Add support for BLCG on Kepler2

On Thu, Jan 25, 2018 at 10:35 PM, Lyude Paul wrote: > Same as the previous patch, but for Kepler2 now > > Signed-off-by: Lyude Paul > --- > drivers/gpu/drm/nouveau/include/nvkm/subdev/fb.h | 1 + > drivers/gpu/drm/nouveau/nvkm/engine/device/base.c | 8 +--

Re: [RFC v2 3/4] drm/nouveau: Add support for BLCG on Kepler2

On Thu, Jan 25, 2018 at 10:35 PM, Lyude Paul wrote: > Same as the previous patch, but for Kepler2 now > > Signed-off-by: Lyude Paul > --- > drivers/gpu/drm/nouveau/include/nvkm/subdev/fb.h | 1 + > drivers/gpu/drm/nouveau/nvkm/engine/device/base.c | 8 +-- >

Re: [PATCH] MAINTAINERS: add the iommu list for swiotlb and xen-swiotlb

On Thu, Jan 25, 2018 at 09:26:18AM -0500, Konrad Rzeszutek Wilk wrote: > On Tue, Jan 16, 2018 at 08:56:24AM +0100, Christoph Hellwig wrote: > > All other discussions related to the dma mapping interfaces are on the > > iommu list, so let's make it the official list for swiotlb and the > > second

Re: [PATCH] MAINTAINERS: add the iommu list for swiotlb and xen-swiotlb

On Thu, Jan 25, 2018 at 09:26:18AM -0500, Konrad Rzeszutek Wilk wrote: > On Tue, Jan 16, 2018 at 08:56:24AM +0100, Christoph Hellwig wrote: > > All other discussions related to the dma mapping interfaces are on the > > iommu list, so let's make it the official list for swiotlb and the > > second

Re: [PATCH v2 2/2] perf stat: Add support to print counts after a period of time

On Fri, Jan 26, 2018 at 09:59:02AM +0800, 禹舟键 wrote: > 2018-01-25 20:27 GMT+08:00 Jiri Olsa : > > > On Thu, Jan 25, 2018 at 10:10:04AM +0100, ufo19890607 wrote: > > > > SNIP > > > > > --metric-only:: > > > Only print computed metrics. Print them in a single line. > > > diff

Re: [PATCH v2 2/2] perf stat: Add support to print counts after a period of time

On Fri, Jan 26, 2018 at 09:59:02AM +0800, 禹舟键 wrote: > 2018-01-25 20:27 GMT+08:00 Jiri Olsa : > > > On Thu, Jan 25, 2018 at 10:10:04AM +0100, ufo19890607 wrote: > > > > SNIP > > > > > --metric-only:: > > > Only print computed metrics. Print them in a single line. > > > diff --git

Re: Kdump kernel start failed with intel_iommu=on

On 01/23/18 at 06:20pm, Weilong Chen wrote: > Hi, > > We came across this problem: > Second kernel hang with intel_iommu=on > > We can reproduce the problem by the following steps: > 1. start the kernel with intel_iommu=on > 2. ifconfig eth6 up;ifconfig eth8 up.(eth6 is Intel Corporation 82599ES

Re: Kdump kernel start failed with intel_iommu=on

On 01/23/18 at 06:20pm, Weilong Chen wrote: > Hi, > > We came across this problem: > Second kernel hang with intel_iommu=on > > We can reproduce the problem by the following steps: > 1. start the kernel with intel_iommu=on > 2. ifconfig eth6 up;ifconfig eth8 up.(eth6 is Intel Corporation 82599ES

[RFC PATCH] vsprintf: add flag ZEROPAD handling before crng is ready

Before crng is ready, output of "%p" composes of "(ptrval)" and left padding spaces for alignment as no random address can be generated. This seems a little strange sometimes. For example, when irq domain names are built with "%p", the nodes under /sys/kernel/debug/irq/domains like this, [root@y

[RFC PATCH] vsprintf: add flag ZEROPAD handling before crng is ready

Before crng is ready, output of "%p" composes of "(ptrval)" and left padding spaces for alignment as no random address can be generated. This seems a little strange sometimes. For example, when irq domain names are built with "%p", the nodes under /sys/kernel/debug/irq/domains like this, [root@y

Re: general protection fault in tun_do_read

On Fri, Jan 26, 2018 at 4:24 AM, Jason Wang wrote: > > > On 2018年01月25日 15:59, syzbot wrote: >> >> Hello, >> >> syzbot hit the following crash on net-next commit >> 43df215d99e6049d4680309c54232689e16ddd6b (Wed Jan 24 01:24:32 2018 +) >> Merge branch

Re: general protection fault in tun_do_read

On Fri, Jan 26, 2018 at 4:24 AM, Jason Wang wrote: > > > On 2018年01月25日 15:59, syzbot wrote: >> >> Hello, >> >> syzbot hit the following crash on net-next commit >> 43df215d99e6049d4680309c54232689e16ddd6b (Wed Jan 24 01:24:32 2018 +) >> Merge branch 'bpf-and-netdevsim-test-updates' >> >> So

[PATCH v2 0/5] GICv3 Save and Restore

A lot of changes in v2. The distributor and redistributor saving and restoring is left to the PSCI/firmware implementation after discussions with ARM. This reduces the line changes by a lot and removes now unneeded patches. Patches are verified on an RK3399 platform with pending patches in the

[PATCH v2 1/5] cpu_pm: add syscore_suspend error handling

If cpu_cluster_pm_enter() fails, cpu_pm_exit() should be called. This will put the CPU in the correct state to resume from the failure. Signed-off-by: Derek Basehore --- kernel/cpu_pm.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/kernel/cpu_pm.c

[PATCH v2 2/5] irqchip/gic-v3-its: add ability to save/restore ITS state

Some platforms power off GIC logic in suspend, so we need to save/restore state. The distributor and redistributor registers need to be handled in platform code due to access permissions on those registers, but the ITS registers can be restored in the kernel. Signed-off-by: Derek Basehore

[PATCH v2 0/5] GICv3 Save and Restore

A lot of changes in v2. The distributor and redistributor saving and restoring is left to the PSCI/firmware implementation after discussions with ARM. This reduces the line changes by a lot and removes now unneeded patches. Patches are verified on an RK3399 platform with pending patches in the

[PATCH v2 1/5] cpu_pm: add syscore_suspend error handling

If cpu_cluster_pm_enter() fails, cpu_pm_exit() should be called. This will put the CPU in the correct state to resume from the failure. Signed-off-by: Derek Basehore --- kernel/cpu_pm.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/kernel/cpu_pm.c b/kernel/cpu_pm.c index

[PATCH v2 2/5] irqchip/gic-v3-its: add ability to save/restore ITS state

Some platforms power off GIC logic in suspend, so we need to save/restore state. The distributor and redistributor registers need to be handled in platform code due to access permissions on those registers, but the ITS registers can be restored in the kernel. Signed-off-by: Derek Basehore ---

[PATCH v2 3/5] DT/arm,gic-v3-its: add reset-on-suspend property

This adds documentation for the new reset-on-suspend property. This property enables saving and restoring the ITS for when it loses state in system suspend. Signed-off-by: Derek Basehore --- Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt | 3 +++ 1

[PATCH v2 3/5] DT/arm,gic-v3-its: add reset-on-suspend property

This adds documentation for the new reset-on-suspend property. This property enables saving and restoring the ITS for when it loses state in system suspend. Signed-off-by: Derek Basehore --- Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt | 3 +++ 1 file changed, 3

RE: [PATCH 2/2] thermal: imx: add i.MX7 thermal sensor support

-Original Message- From: Dong Aisheng [mailto:donga...@gmail.com] Sent: 2018年1月26日 15:00 To: Anson Huang Cc: rui.zh...@intel.com; edubez...@gmail.com; robh...@kernel.org; mark.rutl...@arm.com; shawn...@kernel.org; ker...@pengutronix.de; Fabio Estevam

RE: [PATCH 2/2] thermal: imx: add i.MX7 thermal sensor support

-Original Message- From: Dong Aisheng [mailto:donga...@gmail.com] Sent: 2018年1月26日 15:00 To: Anson Huang Cc: rui.zh...@intel.com; edubez...@gmail.com; robh...@kernel.org; mark.rutl...@arm.com; shawn...@kernel.org; ker...@pengutronix.de; Fabio Estevam ; li...@armlinux.org.uk; Jacky

[PATCH v2 4/5] irqchip/gic-v3-its: add ability to resend MAPC on resume

This adds functionality to resend the MAPC command to an ITS node on resume. If the ITS is powered down during suspend and the collections are not backed by memory, the ITS will lose that state. This just sets up the known state for the collections after the ITS is restored. This feature is

[PATCH v2 4/5] irqchip/gic-v3-its: add ability to resend MAPC on resume

This adds functionality to resend the MAPC command to an ITS node on resume. If the ITS is powered down during suspend and the collections are not backed by memory, the ITS will lose that state. This just sets up the known state for the collections after the ITS is restored. This feature is

[PATCH v2 5/5] DT/arm,gic-v3: add collections-reset-on-suspend property

This boolean property for the GIC-V3-ITS enables resending the MAP COLLECTIONS commands when resuming for when the state is reset on suspend. Signed-off-by: Derek Basehore --- Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt | 4 1 file changed,

[PATCH v2 5/5] DT/arm,gic-v3: add collections-reset-on-suspend property

This boolean property for the GIC-V3-ITS enables resending the MAP COLLECTIONS commands when resuming for when the state is reset on suspend. Signed-off-by: Derek Basehore --- Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt | 4 1 file changed, 4 insertions(+) diff

Re: [PATCH] print kdump kernel loaded status in stack dump

On 01/19/18 at 12:47pm, Dave Young wrote: > On 01/18/18 at 01:57pm, Steven Rostedt wrote: > > On Thu, 18 Jan 2018 10:02:17 -0800 > > Andi Kleen wrote: > > > > > Dave Young writes: > > > > printk("%sHardware name: %s\n", > > > >

Re: [PATCH] print kdump kernel loaded status in stack dump

On 01/19/18 at 12:47pm, Dave Young wrote: > On 01/18/18 at 01:57pm, Steven Rostedt wrote: > > On Thu, 18 Jan 2018 10:02:17 -0800 > > Andi Kleen wrote: > > > > > Dave Young writes: > > > > printk("%sHardware name: %s\n", > > > >log_lvl,

Re: [RFC PATCH 2/2] gpio: provide a consumer when requesting a gpio

On Wed, Jan 24, 2018 at 05:42:15PM +0200, Andy Shevchenko wrote: > On Wed, Jan 24, 2018 at 3:07 PM, Ludovic Desroches > wrote: > > On Thu, Jan 18, 2018 at 04:22:28PM +0100, Ludovic Desroches wrote: > >> On Thu, Jan 18, 2018 at 11:30:00AM +0100, Linus Walleij

Re: [RFC PATCH 2/2] gpio: provide a consumer when requesting a gpio

On Wed, Jan 24, 2018 at 05:42:15PM +0200, Andy Shevchenko wrote: > On Wed, Jan 24, 2018 at 3:07 PM, Ludovic Desroches > wrote: > > On Thu, Jan 18, 2018 at 04:22:28PM +0100, Ludovic Desroches wrote: > >> On Thu, Jan 18, 2018 at 11:30:00AM +0100, Linus Walleij wrote: > >> > On Mon, Jan 15, 2018 at

Re: [PATCH 2/2] usb: chipidea: imx: Fix ULPI on imx53

On Wed, Jan 24, 2018 at 06:14:39PM +0100, Sebastian Reichel wrote: > Traditionally, PORTSC should be set before initializing ULPI phys. But > setting PORTSC before powering on the phy results in a kernel freeze > on imx53 based GE PPD. As a workaround this initializes the phy early > in the imx

Re: [PATCH 2/2] usb: chipidea: imx: Fix ULPI on imx53

On Wed, Jan 24, 2018 at 06:14:39PM +0100, Sebastian Reichel wrote: > Traditionally, PORTSC should be set before initializing ULPI phys. But > setting PORTSC before powering on the phy results in a kernel freeze > on imx53 based GE PPD. As a workaround this initializes the phy early > in the imx

Re: [PATCH 2/4] usb: dwc3: add dwc3 glue layer for UniPhier SoCs

Hi, On Thu, 25 Jan 2018 11:09:30 +0900 wrote: > Hello Felipe, > > On Wed, 24 Jan 2018 14:58:12 +0200 wrote: > > > > > Hi, > > > > Kunihiko Hayashi writes: > > > Hello Felipe, > > > > > > Thank you for your

Re: [PATCH] of: use hash based search in of_find_node_by_phandle

On 1/25/2018 8:20 PM, Rob Herring wrote: On Thu, Jan 25, 2018 at 4:14 AM, Chintan Pandya wrote: of_find_node_by_phandle() takes a lot of time finding Got some numbers for what is "a lot of time"? On my SDM device, I see total saving of 400ms during boot time. For some

Re: [PATCH 2/4] usb: dwc3: add dwc3 glue layer for UniPhier SoCs

Hi, On Thu, 25 Jan 2018 11:09:30 +0900 wrote: > Hello Felipe, > > On Wed, 24 Jan 2018 14:58:12 +0200 wrote: > > > > > Hi, > > > > Kunihiko Hayashi writes: > > > Hello Felipe, > > > > > > Thank you for your comments. > > > > > > On Tue, 23 Jan 2018 15:12:36 +0200 wrote: > > > > > >> > >

Re: [PATCH] of: use hash based search in of_find_node_by_phandle

On 1/25/2018 8:20 PM, Rob Herring wrote: On Thu, Jan 25, 2018 at 4:14 AM, Chintan Pandya wrote: of_find_node_by_phandle() takes a lot of time finding Got some numbers for what is "a lot of time"? On my SDM device, I see total saving of 400ms during boot time. For some clients whose node is

Darlehen Geld für Einzelpersonen und Fachleute in weniger als 72 Stunden

Hallo, Sind Sie in einer schwierigen Situation, für die Sie sich für ein Darlehen suchen? Benötigen Sie eine Finanzierung, um eine Schuld zu begleichen oder eine Aktivität zu finanzieren? Haben Sie einen Verbraucherkredit, eine Hypothek, einen persönlichen Kredit, eine Hypothek, Investition

Darlehen Geld für Einzelpersonen und Fachleute in weniger als 72 Stunden

Hallo, Sind Sie in einer schwierigen Situation, für die Sie sich für ein Darlehen suchen? Benötigen Sie eine Finanzierung, um eine Schuld zu begleichen oder eine Aktivität zu finanzieren? Haben Sie einen Verbraucherkredit, eine Hypothek, einen persönlichen Kredit, eine Hypothek, Investition

Re: [PATCH v2] ASoC: use seq_file to dump the contents of dai_list,platform_list and codec_list

On Wed, Jan 24, 2018 at 1:37 AM, Mark Brown wrote: > On Tue, Jan 23, 2018 at 07:08:15PM +0200, Andy Shevchenko wrote: > >> If it's not critical, I would suggest to wait till v4.16-rc1, where I >> would like to push [1], and switch to DEFINE_SHOW_ATTRIBUTE() macro. > > Too

Re: [PATCH v2] ASoC: use seq_file to dump the contents of dai_list,platform_list and codec_list

On Wed, Jan 24, 2018 at 1:37 AM, Mark Brown wrote: > On Tue, Jan 23, 2018 at 07:08:15PM +0200, Andy Shevchenko wrote: > >> If it's not critical, I would suggest to wait till v4.16-rc1, where I >> would like to push [1], and switch to DEFINE_SHOW_ATTRIBUTE() macro. > > Too late, I already applied

Re: [PATCH RESENT] nvme-pci: introduce RECONNECTING state to mark initializing procedure

Thanks, applied to nvme-4.16.

Re: [PATCH RESENT] nvme-pci: introduce RECONNECTING state to mark initializing procedure

Thanks, applied to nvme-4.16.

[PATCH v4] iommu/mediatek: Move attach_device after iommu-group is ready for M4Uv1

In the commit 05f80300dc8b ("iommu: Finish making iommu_group support mandatory"), the iommu framework has supposed all the iommu drivers have their owner iommu-group, it get rid of the FIXME workarounds while the group is NULL. But the flow of Mediatek M4U gen1 looks a bit trick that it will hang

[PATCH v4] iommu/mediatek: Move attach_device after iommu-group is ready for M4Uv1

In the commit 05f80300dc8b ("iommu: Finish making iommu_group support mandatory"), the iommu framework has supposed all the iommu drivers have their owner iommu-group, it get rid of the FIXME workarounds while the group is NULL. But the flow of Mediatek M4U gen1 looks a bit trick that it will hang

Re: [PATCH] Update the RISC-V MAINTAINERS file

On Thu, Jan 25, 2018 at 08:23:15AM -0800, Palmer Dabbelt wrote: > Now that we're upstream in Linux we've been able to make some > infrastructure changes so our port works a bit more like other ports. > Specifically: > > * We now have a mailing list specific to the RISC-V Linux port, hosted > at

Re: [PATCH] Update the RISC-V MAINTAINERS file

On Thu, Jan 25, 2018 at 08:23:15AM -0800, Palmer Dabbelt wrote: > Now that we're upstream in Linux we've been able to make some > infrastructure changes so our port works a bit more like other ports. > Specifically: > > * We now have a mailing list specific to the RISC-V Linux port, hosted > at

Re: [PATCH 2/2] thermal: imx: add i.MX7 thermal sensor support

On Mon, Jan 22, 2018 at 03:25:49PM +0800, Anson Huang wrote: > This patch adds i.MX7 thermal sensor support, most > of the i.MX7 thermal sensor functions are same with > i.MX6 except the registers offset/layout, so we move > those registers offset/layout definitions to soc data > structure. > >

Re: [PATCH 2/2] thermal: imx: add i.MX7 thermal sensor support

On Mon, Jan 22, 2018 at 03:25:49PM +0800, Anson Huang wrote: > This patch adds i.MX7 thermal sensor support, most > of the i.MX7 thermal sensor functions are same with > i.MX6 except the registers offset/layout, so we move > those registers offset/layout definitions to soc data > structure. > >

Re: [PATCH 2/2] perf tools: Skip read of kernel maps once it failed

On Fri, Jan 19, 2018 at 05:11:03PM +0100, Jiri Olsa wrote: > Current perf report is real slow on newer kernels, > with following commit: > c0f3ea158939 ("stop using '%pK' for /proc/kallsyms pointer values") > > which prevent pointers in /proc/kallsyms, in case > kernel.perf_event_paranoid=2. >

Re: [PATCH 2/2] perf tools: Skip read of kernel maps once it failed

On Fri, Jan 19, 2018 at 05:11:03PM +0100, Jiri Olsa wrote: > Current perf report is real slow on newer kernels, > with following commit: > c0f3ea158939 ("stop using '%pK' for /proc/kallsyms pointer values") > > which prevent pointers in /proc/kallsyms, in case > kernel.perf_event_paranoid=2. >

Re: [PATCH 1/2] tools lib symbol: Use strtoul instead of hex2u64 in kallsyms__parse

On Fri, Jan 19, 2018 at 05:11:02PM +0100, Jiri Olsa wrote: > Current kallsyms__parse uses hex2u64, which gives > no indication of error. Using strtoul to checkup > on failed attempt to parse the number and stop the > rest of the kallsyms__parse processing early. > > Link:

Re: [PATCH 1/2] tools lib symbol: Use strtoul instead of hex2u64 in kallsyms__parse

On Fri, Jan 19, 2018 at 05:11:02PM +0100, Jiri Olsa wrote: > Current kallsyms__parse uses hex2u64, which gives > no indication of error. Using strtoul to checkup > on failed attempt to parse the number and stop the > rest of the kallsyms__parse processing early. > > Link:

Re: Back porting preemption timer patches from 4.13 to 4.9 RT kernel

On Fri, 26 Jan 2018, Wanpeng Li wrote: Folks, can you please stop this corporate email style nonsense? > On 1/26/18 12:55 AM, Arisetty, Chakravarthy wrote: > >> IIRC，the race which KVM: LAPIC: Fix reentrancy issues with preempt > >>

Re: Back porting preemption timer patches from 4.13 to 4.9 RT kernel

On Fri, 26 Jan 2018, Wanpeng Li wrote: Folks, can you please stop this corporate email style nonsense? > On 1/26/18 12:55 AM, Arisetty, Chakravarthy wrote: > >> IIRC，the race which KVM: LAPIC: Fix reentrancy issues with preempt > >>

RE: [PATCH] ARM: dts: imx6sx: add pu power domain support

-Original Message- From: Dong Aisheng [mailto:donga...@gmail.com] Sent: 2018年1月25日 23:30 To: Anson Huang Cc: shawn...@kernel.org; ker...@pengutronix.de; Fabio Estevam ; robh...@kernel.org; A.s. Dong ;

RE: [PATCH] ARM: dts: imx6sx: add pu power domain support

-Original Message- From: Dong Aisheng [mailto:donga...@gmail.com] Sent: 2018年1月25日 23:30 To: Anson Huang Cc: shawn...@kernel.org; ker...@pengutronix.de; Fabio Estevam ; robh...@kernel.org; A.s. Dong ; mark.rutl...@arm.com; li...@armlinux.org.uk; dl-linux-imx ;

Re: [PATCH] cpufreq: intel_pstate: enable HWP before manipulating on corresponding registers

On Thu, Jan 25, 2018 at 02:44:59PM -0800, Srinivas Pandruvada wrote: > On Thu, 2018-01-25 at 19:08 +0800, Yu Chen wrote: > > Thanks for debugging. > > > The following warning was triggered after resumed from S3 - > > if all the nonboot CPUs were put offline before suspend: > > > > [

Re: [PATCH] cpufreq: intel_pstate: enable HWP before manipulating on corresponding registers

On Thu, Jan 25, 2018 at 02:44:59PM -0800, Srinivas Pandruvada wrote: > On Thu, 2018-01-25 at 19:08 +0800, Yu Chen wrote: > > Thanks for debugging. > > > The following warning was triggered after resumed from S3 - > > if all the nonboot CPUs were put offline before suspend: > > > > [

Re: [PATCH arm/aspeed/ast2500 v2] ipmi: add an Aspeed KCS IPMI BMC driver

On 2018-01-25 01:48, Corey Minyard wrote: On 01/24/2018 10:06 AM, Haiyue Wang wrote: The KCS (Keyboard Controller Style) interface is used to perform in-band IPMI communication between a server host and its BMC (BaseBoard Management Controllers). This driver exposes the KCS interface on

Re: [PATCH arm/aspeed/ast2500 v2] ipmi: add an Aspeed KCS IPMI BMC driver

On 2018-01-25 01:48, Corey Minyard wrote: On 01/24/2018 10:06 AM, Haiyue Wang wrote: The KCS (Keyboard Controller Style) interface is used to perform in-band IPMI communication between a server host and its BMC (BaseBoard Management Controllers). This driver exposes the KCS interface on

Re: [PATCH arm/aspeed/ast2500 v2] ipmi: add an Aspeed KCS IPMI BMC driver

On 2018-01-25 01:48, Corey Minyard wrote: On 01/24/2018 10:06 AM, Haiyue Wang wrote: The KCS (Keyboard Controller Style) interface is used to perform in-band IPMI communication between a server host and its BMC (BaseBoard Management Controllers). This driver exposes the KCS interface on

Re: [PATCH arm/aspeed/ast2500 v2] ipmi: add an Aspeed KCS IPMI BMC driver

On 2018-01-25 01:48, Corey Minyard wrote: On 01/24/2018 10:06 AM, Haiyue Wang wrote: The KCS (Keyboard Controller Style) interface is used to perform in-band IPMI communication between a server host and its BMC (BaseBoard Management Controllers). This driver exposes the KCS interface on

[PATCH] ARM: dts: exynos: Update x and y properties for mms114 touchscreen

The mms114 binding [1] specifies that the 'x' and 'y' should be called respectively 'touchscreen-size-x' and 'touchscreen-size-y' in coherence with the touchscreen [2] binding. Update the mms114 node for trats2 and trats dts according to the binding. [1]

[PATCH] ARM: dts: exynos: Update x and y properties for mms114 touchscreen

The mms114 binding [1] specifies that the 'x' and 'y' should be called respectively 'touchscreen-size-x' and 'touchscreen-size-y' in coherence with the touchscreen [2] binding. Update the mms114 node for trats2 and trats dts according to the binding. [1]

Re: [RFC 0/4] tools lib traceevent: Install fixes

Hi Jiri and Steve, On Fri, Jan 19, 2018 at 04:15:02PM +0100, Jiri Olsa wrote: > On Fri, Jan 19, 2018 at 10:07:28AM -0500, Steven Rostedt wrote: > > On Fri, 19 Jan 2018 11:37:13 +0100 > > Jiri Olsa wrote: > > > > > hi, > > > I checked on this one and was surprised last email is

Re: [RFC 0/4] tools lib traceevent: Install fixes

Hi Jiri and Steve, On Fri, Jan 19, 2018 at 04:15:02PM +0100, Jiri Olsa wrote: > On Fri, Jan 19, 2018 at 10:07:28AM -0500, Steven Rostedt wrote: > > On Fri, 19 Jan 2018 11:37:13 +0100 > > Jiri Olsa wrote: > > > > > hi, > > > I checked on this one and was surprised last email is from 2016 ;-) > >

[RFC PATCH 1/8] media: add request API core and UAPI

The request API provides a way to group buffers and device parameters into units of work to be queued and executed. This patch introduces the UAPI and core framework. This patch is based on the previous work by Laurent Pinchart. The core has changed considerably, but the UAPI is mostly untouched.

[RFC PATCH 1/8] media: add request API core and UAPI

The request API provides a way to group buffers and device parameters into units of work to be queued and executed. This patch introduces the UAPI and core framework. This patch is based on the previous work by Laurent Pinchart. The core has changed considerably, but the UAPI is mostly untouched.

[RFC PATCH 2/8] videodev2.h: Add request field to v4l2_buffer

From: Hans Verkuil When queuing buffers allow for passing the request ID that should be associated with this buffer. Signed-off-by: Hans Verkuil [acour...@chromium.org: make request ID 32-bit] Signed-off-by: Alexandre Courbot

[RFC PATCH 3/8] media: videobuf2: add support for requests

Make vb2 aware of requests. Drivers can specify whether a given queue can accept requests or not. Queues that accept requests will block on a buffer that is part of a request until that request is submitted. Signed-off-by: Alexandre Courbot ---

[RFC PATCH 2/8] videodev2.h: Add request field to v4l2_buffer

From: Hans Verkuil When queuing buffers allow for passing the request ID that should be associated with this buffer. Signed-off-by: Hans Verkuil [acour...@chromium.org: make request ID 32-bit] Signed-off-by: Alexandre Courbot --- drivers/media/usb/cpia2/cpia2_v4l.c | 2 +-

[RFC PATCH 3/8] media: videobuf2: add support for requests

Make vb2 aware of requests. Drivers can specify whether a given queue can accept requests or not. Queues that accept requests will block on a buffer that is part of a request until that request is submitted. Signed-off-by: Alexandre Courbot --- drivers/media/v4l2-core/videobuf2-core.c | 125

[RFC PATCH 5/8] media: Document the media request API

From: Laurent Pinchart The media request API is made of a new ioctl to implement request management. Document it. Signed-off-by: Laurent Pinchart [acour...@chromium.org: adapt for newest API] Signed-off-by:

[RFC PATCH 5/8] media: Document the media request API

From: Laurent Pinchart The media request API is made of a new ioctl to implement request management. Document it. Signed-off-by: Laurent Pinchart [acour...@chromium.org: adapt for newest API] Signed-off-by: Alexandre Courbot --- Documentation/media/uapi/mediactl/media-funcs.rst | 1 +

[RFC PATCH 7/8] media: vim2m: add media device

Request API requires a media node. Add one to the vim2m driver so we can use requests with it. Signed-off-by: Alexandre Courbot --- drivers/media/platform/vim2m.c | 24 1 file changed, 24 insertions(+) diff --git a/drivers/media/platform/vim2m.c

[RFC PATCH 6/8] v4l2: document the request API interface

Document how the request API can be used along with the existing V4L2 interface. Signed-off-by: Alexandre Courbot --- Documentation/media/uapi/v4l/buffer.rst | 10 +- Documentation/media/uapi/v4l/common.rst | 1 + Documentation/media/uapi/v4l/request-api.rst

[RFC PATCH 7/8] media: vim2m: add media device

Request API requires a media node. Add one to the vim2m driver so we can use requests with it. Signed-off-by: Alexandre Courbot --- drivers/media/platform/vim2m.c | 24 1 file changed, 24 insertions(+) diff --git a/drivers/media/platform/vim2m.c

[RFC PATCH 6/8] v4l2: document the request API interface

Document how the request API can be used along with the existing V4L2 interface. Signed-off-by: Alexandre Courbot --- Documentation/media/uapi/v4l/buffer.rst | 10 +- Documentation/media/uapi/v4l/common.rst | 1 + Documentation/media/uapi/v4l/request-api.rst | 194

[RFC PATCH 8/8] media: vim2m: add request support

Set the necessary ops for supporting requests in vim2m. Signed-off-by: Alexandre Courbot --- drivers/media/platform/vim2m.c | 31 +++ 1 file changed, 31 insertions(+) diff --git a/drivers/media/platform/vim2m.c b/drivers/media/platform/vim2m.c

[RFC PATCH 8/8] media: vim2m: add request support

Set the necessary ops for supporting requests in vim2m. Signed-off-by: Alexandre Courbot --- drivers/media/platform/vim2m.c | 31 +++ 1 file changed, 31 insertions(+) diff --git a/drivers/media/platform/vim2m.c b/drivers/media/platform/vim2m.c index

[RFC PATCH 4/8] media: vb2: add support for requests in QBUF ioctl

Support the request argument of the QBUF ioctl. Signed-off-by: Alexandre Courbot --- drivers/media/v4l2-core/v4l2-ioctl.c | 79 +++- 1 file changed, 78 insertions(+), 1 deletion(-) diff --git a/drivers/media/v4l2-core/v4l2-ioctl.c

[RFC PATCH 4/8] media: vb2: add support for requests in QBUF ioctl

Support the request argument of the QBUF ioctl. Signed-off-by: Alexandre Courbot --- drivers/media/v4l2-core/v4l2-ioctl.c | 79 +++- 1 file changed, 78 insertions(+), 1 deletion(-) diff --git a/drivers/media/v4l2-core/v4l2-ioctl.c

[RFC PATCH 0/8] [media] Request API, take three

Howdy. Here is your bi-weekly request API redesign! ;) Again, this is a simple version that only implements the flow of requests, without applying controls. The intent is to get an agreement on a base to work on, since the previous versions went straight back to the redesign board. Highlights of

[RFC PATCH 0/8] [media] Request API, take three

Howdy. Here is your bi-weekly request API redesign! ;) Again, this is a simple version that only implements the flow of requests, without applying controls. The intent is to get an agreement on a base to work on, since the previous versions went straight back to the redesign board. Highlights of

[PATCH 1/2] selftests/powerpc: Add ptrace tests for Protection Key registers

This test exercises read and write access to the AMR, IAMR and UAMOR. Signed-off-by: Thiago Jung Bauermann --- tools/testing/selftests/powerpc/include/reg.h | 1 + tools/testing/selftests/powerpc/ptrace/Makefile| 5 +-

[PATCH 1/2] selftests/powerpc: Add ptrace tests for Protection Key registers

This test exercises read and write access to the AMR, IAMR and UAMOR. Signed-off-by: Thiago Jung Bauermann --- tools/testing/selftests/powerpc/include/reg.h | 1 + tools/testing/selftests/powerpc/ptrace/Makefile| 5 +- tools/testing/selftests/powerpc/ptrace/child.h | 130

[PATCH 2/2] selftests/powerpc: Add core file test for Protection Key registers

This test verifies that the AMR, IAMR and UAMOR are being written to a process' core file. Signed-off-by: Thiago Jung Bauermann --- tools/testing/selftests/powerpc/ptrace/Makefile| 5 +- tools/testing/selftests/powerpc/ptrace/core-pkey.c | 460

[PATCH 0/2] Testcases for protection keys feature in powerpc/next

Ram Pai submitted a separate series containing the rework of the x86 test and also the powerpc-specific tests: https://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=24741 There's a bug in the powerpc tests where they expect the AMR, IAMR and UAMOR registers to be zeroed when a process

[PATCH 0/2] Testcases for protection keys feature in powerpc/next

Ram Pai submitted a separate series containing the rework of the x86 test and also the powerpc-specific tests: https://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=24741 There's a bug in the powerpc tests where they expect the AMR, IAMR and UAMOR registers to be zeroed when a process

[PATCH 2/2] selftests/powerpc: Add core file test for Protection Key registers

This test verifies that the AMR, IAMR and UAMOR are being written to a process' core file. Signed-off-by: Thiago Jung Bauermann --- tools/testing/selftests/powerpc/ptrace/Makefile| 5 +- tools/testing/selftests/powerpc/ptrace/core-pkey.c | 460 + 2 files changed, 464

Re: [PATCH 6/8] kprobes/arm64: Fix %p uses in error messages

On Thu, 25 Jan 2018 16:42:31 + Will Deacon wrote: > On Thu, Jan 25, 2018 at 02:29:32PM +0900, Masami Hiramatsu wrote: > > Fix %p uses in error messages by removing it because > > those are redundant or meaningless. > > > > Signed-off-by: Masami Hiramatsu

Re: [PATCH 6/8] kprobes/arm64: Fix %p uses in error messages

On Thu, 25 Jan 2018 16:42:31 + Will Deacon wrote: > On Thu, Jan 25, 2018 at 02:29:32PM +0900, Masami Hiramatsu wrote: > > Fix %p uses in error messages by removing it because > > those are redundant or meaningless. > > > > Signed-off-by: Masami Hiramatsu > > --- > >

Re: [kernel-hardening] [PATCH 4/6] Protectable Memory

On Wed, Jan 24, 2018 at 08:10:53PM +0100, Jann Horn wrote: > I'm not entirely convinced by the approach of marking small parts of > kernel memory as readonly for hardening. It depends how significant the data stored in there are. For example, storing function pointers in read-only memory

Re: [kernel-hardening] [PATCH 4/6] Protectable Memory

On Wed, Jan 24, 2018 at 08:10:53PM +0100, Jann Horn wrote: > I'm not entirely convinced by the approach of marking small parts of > kernel memory as readonly for hardening. It depends how significant the data stored in there are. For example, storing function pointers in read-only memory

Re: [PATCH arm/aspeed/ast2500 v2] ipmi: add an Aspeed KCS IPMI BMC driver

On 2018-01-25 01:05, Andy Shevchenko wrote: On Thu, 2018-01-25 at 00:06 +0800, Haiyue Wang wrote: The KCS (Keyboard Controller Style) interface is used to perform in- band IPMI communication between a server host and its BMC (BaseBoard Management Controllers). +config ASPEED_KCS_IPMI_BMC +

Re: [PATCH arm/aspeed/ast2500 v2] ipmi: add an Aspeed KCS IPMI BMC driver

On 2018-01-25 01:05, Andy Shevchenko wrote: On Thu, 2018-01-25 at 00:06 +0800, Haiyue Wang wrote: The KCS (Keyboard Controller Style) interface is used to perform in- band IPMI communication between a server host and its BMC (BaseBoard Management Controllers). +config ASPEED_KCS_IPMI_BMC +

  1   2   3   4   5   6   7   8   9   10   >