RE: [RESEND PATCH 1/2 v2] staging: fsl-mc: Allocate IRQ's before scanning DPRC objects

> -Original Message- > From: Nipun Gupta [mailto:nipun.gu...@nxp.com] > Sent: Monday, December 11, 2017 9:16 PM > To: Laurentiu Tudor ; stuyo...@gmail.com; > Bharat Bhushan ; gre...@linuxfoundation.org; > cakt...@gmail.com;

[PATCH v5 2/4] staging: media: Introduce NVIDIA Tegra video decoder driver

NVIDIA Tegra20/30/114/124/132 SoC's have video decoder engine that supports standard set of video formats like H.264 / MPEG-4 / WMV / VC1. Signed-off-by: Dmitry Osipenko --- MAINTAINERS |9 + drivers/staging/media/Kconfig |

[PATCH v5 1/4] media: dt: bindings: Add binding for NVIDIA Tegra Video Decoder Engine

Add binding documentation for the Video Decoder Engine which is found on NVIDIA Tegra20/30/114/124/132 SoC's. Signed-off-by: Dmitry Osipenko Acked-by: Rob Herring --- .../devicetree/bindings/media/nvidia,tegra-vde.txt | 55 ++ 1 file

[PATCH v5 4/4] ARM: dts: tegra20: Add video decoder node

Add Video Decoder Engine device node. Signed-off-by: Dmitry Osipenko --- arch/arm/boot/dts/tegra20.dtsi | 27 +++ 1 file changed, 27 insertions(+) diff --git a/arch/arm/boot/dts/tegra20.dtsi b/arch/arm/boot/dts/tegra20.dtsi index

[PATCH v5 3/4] ARM: dts: tegra20: Add device tree node to describe IRAM

From: Vladimir Zapolskiy All Tegra20 SoCs contain 256KiB IRAM, which is used to store resume code and by a video decoder engine. Signed-off-by: Vladimir Zapolskiy Signed-off-by: Dmitry Osipenko --- arch/arm/boot/dts/tegra20.dtsi | 8

[PATCH v5 0/4] NVIDIA Tegra video decoder driver

VDE driver provides accelerated video decoding to NVIDIA Tegra SoC's, it is a result of reverse-engineering efforts. Driver has been tested on Toshiba AC100 and Acer A500, it should work on any Tegra20 device. In userspace this driver is utilized by libvdpau-tegra [0] that implements VDPAU

Re: [PATCH v3] binder: fix proc->files use-after-free

On Mon, Dec 11, 2017 at 01:23:28PM -0800, Todd Kjos wrote: > Greg- when this is in, we'll want it in 4.14 as well. Ugh, missed that, I'll be sure to mark it for stable, thanks for letting me know. greg k-h ___ devel mailing list

Re: [PATCH v3] binder: fix proc->files use-after-free

Greg- when this is in, we'll want it in 4.14 as well. On Mon, Nov 27, 2017 at 9:32 AM, Todd Kjos wrote: > proc->files cleanup is initiated by binder_vma_close. Therefore > a reference on the binder_proc is not enough to prevent the > files_struct from being released while the

RE: [PATCH 1/2] vmbus: unregister device_obj->channels_kset

> From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Monday, December 11, 2017 12:59 PM > To: Dexuan Cui > Cc: Stephen Hemminger ; o...@aepfle.de; > Stephen Hemminger ; jasow...@redhat.com; >

Re: [PATCH 1/2] vmbus: unregister device_obj->channels_kset

On Mon, Dec 11, 2017 at 08:41:44PM +, Dexuan Cui wrote: > > From: devel [mailto:driverdev-devel-boun...@linuxdriverproject.org] On > > Behalf Of Stephen Hemminger > > Sent: Tuesday, November 28, 2017 9:30 AM > > To: Greg KH > > Cc: o...@aepfle.de; Stephen Hemminger

RE: [PATCH 1/2] vmbus: unregister device_obj->channels_kset

> From: devel [mailto:driverdev-devel-boun...@linuxdriverproject.org] On > Behalf Of Stephen Hemminger > Sent: Tuesday, November 28, 2017 9:30 AM > To: Greg KH > Cc: o...@aepfle.de; Stephen Hemminger ; > jasow...@redhat.com;

Re: first try to send data with pi433 on Raspberry Pi

Am 11.12.2017 um 20:40 schrieb Oliver Graute: Hello list, I just got my pi433 working somehow on Raspberry Pi Model B Rev 2. Here are my findings: first I need to enabling spi in config.txt on boot partition. dtparam=spi=on then adding this node to bcm2835-rpi-b-rev2.dts and compile.

Re: [PATCH 3/6] x86/hyper-v: reenlightenment notifications support

On Mon, Dec 11, 2017 at 10:56:33AM +0100, Vitaly Kuznetsov wrote: > Roman Kagan writes: > > On Fri, Dec 08, 2017 at 11:49:57AM +0100, Vitaly Kuznetsov wrote: > >> +void register_hv_tsc_update(void (*cb)(void)) > >> +{ > > > > The function name seems unfortunate. IMHO such a

first try to send data with pi433 on Raspberry Pi

Hello list, I just got my pi433 working somehow on Raspberry Pi Model B Rev 2. Here are my findings: first I need to enabling spi in config.txt on boot partition. dtparam=spi=on then adding this node to bcm2835-rpi-b-rev2.dts and compile. _gpio7 { pi433: pi433@0 {

[PATCH] staging: atomisp2: replace DEVICE_ATTR with DEVICE_ATTR_RO

This is a clean-up patch which replaces DEVICE_ATTR() macro with file permission specific DEVICE_ATTR_RO() macro for compaction and readability. Done using coccinelle: @r@ identifier attr, show_fn; declarer name DEVICE_ATTR; @@ DEVICE_ATTR(attr, \(S_IRUGO\|0444\), show_fn, NULL); @script:

[PATCH net-next 1/2] hv_netvsc: Fix the receive buffer size limit

From: Haiyang Zhang The max should be 31 MB on host with NVSP version > 2. On legacy hosts (NVSP version <=2) only 15 MB receive buffer is allowed, otherwise the buffer request will be rejected by the host, resulting vNIC not coming up. The NVSP version is only

[PATCH net-next 2/2] hv_netvsc: Fix the TX/RX buffer default sizes

From: Haiyang Zhang The values were not computed correctly. There are no significant visible impact, though. The intended size of RX buffer is 16 MB, and the default slot size is 1728. So, NETVSC_DEFAULT_RX should be 16*1024*1024 / 1728 = 9709. The intended size of TX

[PATCH net-next 0/2] hv_netvsc: Fix default and limit of recv buffe

The default for receive buffer descriptors is not correct, it should match the default receive buffer size and the upper limit of receive buffer size is too low. Also, for older versions of Window servers hosts, different lower limit check is necessary, otherwise the buffer request will be

Re: [PATCH 6/6] x86/kvm: support Hyper-V reenlightenment

Roman Kagan writes: > On Fri, Dec 08, 2017 at 11:50:00AM +0100, Vitaly Kuznetsov wrote: >> When we run nested KVM on Hyper-V guests we need to update masterclocks for >> all guests when L1 migrates to a host with different TSC frequency. >> Implement the procedure in the

Re: [PATCH 3/6] x86/hyper-v: reenlightenment notifications support

Roman Kagan writes: > On Fri, Dec 08, 2017 at 11:49:57AM +0100, Vitaly Kuznetsov wrote: >> Hyper-V supports Live Migration notification. This is supposed to be used >> in conjunction with TSC emulation: when we are migrated to a host with >> different TSC frequency for some

[PATCH] staging: fbtft: replace __ATTR() with DEVICE_ATTR()

This is a clean-up patch which replaces the uses of raw __ATTR(...) macro with the more conventional DEVICE_ATTR(...) for defining device attributes. Done using coccinelle- @r@ identifier foo, n; @@ struct device_attribute foo = __ATTR(n, ...); @script:python p@ id; foo << r.foo; n << r.n; @@

[RESEND PATCH 1/2 v2] staging: fsl-mc: Allocate IRQ's before scanning DPRC objects

Following is the current scenario when the devices are probed: FSL_MC Bus probe ---> dprc probe ---> dprc devices scan ---> probe devices in DPRC container ---> allocate IRQ's In case the devices being probed in the DPRC container need the IRQ's; probing of that device will fail. In

[RESEND PATCH 2/2 v2] staging: fsl-mc: do not print error in case of defer probe error

Devices on MC bus can be deferred because of dependencies on other modules (such as IOMMU). Those are not the actual errors; as probing is again done by the kernel at later stages. So this patch avoids the error print in such case. Signed-off-by: Nipun Gupta --- Resending v2

[PATCH 2/2 v2] staging: fsl-mc: do not print error in case of defer probe error

Devices on MC bus can be deferred because of dependencies on other modules (such as IOMMU). Those are not the actual errors; as probing is again done by the kernel at later stages. So this patch avoids the error print in such case. Signed-off-by: Nipun Gupta ---

[PATCH 1/2 v2] staging: fsl-mc: Allocate IRQ's before scanning DPRC objects

Following is the current scenario when the devices are probed: FSL_MC Bus probe ---> dprc probe ---> dprc devices scan ---> probe devices in DPRC container ---> allocate IRQ's In case the devices being probed in the DPRC container need the IRQ's; probing of that device will fail. In