Re: [GIT PULL 1/3] stm class: Fix a module refcount leak in policy creation error path

Greg Kroah-Hartman writes: > On Fri, Dec 14, 2018 at 05:53:45PM +0200, Alexander Shishkin wrote: >> Commit ccddbbf4ef27 ("stm class: Introduce framing protocol drivers") > > I don't see that commit id in Linus's tree, are you sure it is correct? No, I messed it up somehow. Sorry about that. The

Re: [PATCH] regulator: mcp16502: Fix missing n_voltages setting

Hi Axel, Thank you for the patch! However, there are not MCP16502_VSEL + 1 voltages, but VDD_HIGH_SEL - VDD_LOW_SEL + 1 (=51). Best regards, Andrei On 19.12.2018 10:58, Axel Lin wrote: > The n_voltages setting is not set, fix it. > > Signed-off-by: Axel Lin > --- > drivers/regulator/mcp16502

Re: [PATCH v4 4/9] drm/rockchip/rockchip_drm_gem.c: Convert to use vm_insert_range

On Wed, Dec 19, 2018 at 3:02 PM Russell King - ARM Linux wrote: > > On Wed, Dec 19, 2018 at 09:01:09AM +0530, Souptick Joarder wrote: > > On Tue, Dec 18, 2018 at 6:31 PM Russell King - ARM Linux > > wrote: > > > > > > On Tue, Dec 18, 2018 at 06:24:29PM +0530, Souptick Joarder wrote: > > > > On Tu

[PATCH] stm class: Fix a module refcount leak in policy creation error path

Commit c7fd62bc69d0 ("stm class: Introduce framing protocol drivers") adds a bug into the error path of policy creation, that would do a module_put() on a wrong module, if one tried to create a policy for an stm device which already has a policy, using a different protocol. IOW, | mkdir /config/st

Re: [PATCH v10 24/27] drivers: firmware: psci: Support CPU hotplug for the hierarchical model

On Wed, 19 Dec 2018 at 12:17, Lorenzo Pieralisi wrote: > > On Thu, Nov 29, 2018 at 06:46:57PM +0100, Ulf Hansson wrote: > > When the hierarchical CPU topology is used and when a CPU has been put > > offline (hotplug), that same CPU prevents its PM domain and thus also > > potential master PM domai

Re: [PATCH] drm/amd/display: Remove duplicate header

On Wed, Dec 19, 2018 at 1:27 PM Brajeswar Ghosh wrote: > > Remove custom_float.h which is included more than once > > Signed-off-by: Brajeswar Ghosh > --- Acked-by: Souptick Joarder > drivers/gpu/drm/amd/display/dc/dcn10/dcn10_hw_sequencer.c | 1 - > 1 file changed, 1 deletion(-) > > diff --gi

[PATCH 10/14] drm/bochs: drop unused gpu_addr arg from bochs_bo_pin()

It's always NULL, so just remove it. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/bochs/bochs.h | 2 +- drivers/gpu/drm/bochs/bochs_fbdev.c | 2 +- drivers/gpu/drm/bochs/bochs_kms.c | 2 +- drivers/gpu/drm/bochs/bochs_mm.c| 11 +-- 4 files changed, 4 insertions(+), 13

[PATCH 14/14] drm/bochs: move remaining fb bits to kms

bochs_fbdev.c is almost empty now. Move the remaining framebuffer bits over to bochs_kms.c. Pure code motion. No functional change. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/bochs/bochs_fbdev.c | 29 - drivers/gpu/drm/bochs/bochs_kms.c | 17

[PATCH 08/14] drm/bochs: atomic: set DRIVER_ATOMIC

Conversion to atomic modesetting, final step. Set the DRIVER_ATOMIC flag. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/bochs/bochs_drv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/bochs/bochs_drv.c b/drivers/gpu/drm/bochs/bochs_drv.c index f3dd66ae99

[PATCH 11/14] drm/bochs: add basic prime support

Generic framebuffer emulation needs this. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/bochs/bochs.h | 11 +++ drivers/gpu/drm/bochs/bochs_drv.c | 15 +- drivers/gpu/drm/bochs/bochs_mm.c | 63 +++ 3 files changed, 88 insertions(+), 1 delet

[PATCH 03/14] drm/bochs: atomic: add atomic_flush+atomic_enable callbacks.

Conversion to atomic modesetting, step one. Add atomic crtc helper callbacks. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/bochs/bochs_kms.c | 25 + 1 file changed, 25 insertions(+) diff --git a/drivers/gpu/drm/bochs/bochs_kms.c b/drivers/gpu/drm/bochs/bochs_kms.c i

[PATCH 13/14] drm/bochs: drop old fbdev emulation code

Not needed any more, bochs uses the generic emulation now. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/bochs/bochs.h | 9 --- drivers/gpu/drm/bochs/bochs_drv.c | 6 -- drivers/gpu/drm/bochs/bochs_fbdev.c | 137 3 files changed, 152 deletions(

[PATCH 12/14] drm/bochs: switch to generic drm fbdev emulation

Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/bochs/bochs_drv.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/gpu/drm/bochs/bochs_drv.c b/drivers/gpu/drm/bochs/bochs_drv.c index a9c7140e3b..f1f65324bb 100644 --- a/drivers/gpu/drm/bochs/bochs_drv.c +++ b/drive

[PATCH 06/14] drm/bochs: atomic: use atomic set_config helper

Conversion to atomic modesetting, step four. Use atomic set_config helper for crtc. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/bochs/bochs_kms.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/bochs/bochs_kms.c b/drivers/gpu/drm/bochs/bochs_kms.c index

[PATCH 02/14] drm/bochs: split bochs_hw_setmode

Create a separate bochs_hw_setformat function to configure the framebuffer format (actually just the byteorder). Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/bochs/bochs.h | 5 +++-- drivers/gpu/drm/bochs/bochs_hw.c | 19 --- drivers/gpu/drm/bochs/bochs_kms.c | 3 ++-

[PATCH 07/14] drm/bochs: atomic: use atomic page_flip helper

Conversion to atomic modesetting, step five. Use atomic page_flip helper for crtc. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/bochs/bochs_kms.c | 23 +-- 1 file changed, 1 insertion(+), 22 deletions(-) diff --git a/drivers/gpu/drm/bochs/bochs_kms.c b/drivers/gpu/drm/b

[PATCH 04/14] drm/bochs: atomic: add mode_set_nofb callback.

Conversion to atomic modesetting, step two. Add mode_set_nofb crtc helper callback. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/bochs/bochs_kms.c | 9 + 1 file changed, 9 insertions(+) diff --git a/drivers/gpu/drm/bochs/bochs_kms.c b/drivers/gpu/drm/bochs/bochs_kms.c index 59d469f

[PATCH 05/14] drm/bochs: atomic: switch planes to atomic, wire up helpers.

Conversion to atomic modesetting, step three. Wire up atomic helpers. Switch planes to atomic. We are late to the party, the transitional helpers are gone, so this can't be splitted into smaller steps any more. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/bochs/bochs_fbdev.c | 3 ++ drive

[PATCH 01/14] drm/bochs: encoder cleanup

Most unused callbacks can be NULL pointers these days. Drop a bunch of empty encoder callbacks. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/bochs/bochs_kms.c | 26 -- 1 file changed, 26 deletions(-) diff --git a/drivers/gpu/drm/bochs/bochs_kms.c b/drivers/gpu/drm/b

[PATCH 09/14] drm/bochs: remove old bochs_crtc_* functions

Remove the old, now unused crtc callbacks. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/bochs/bochs_kms.c | 81 --- 1 file changed, 81 deletions(-) diff --git a/drivers/gpu/drm/bochs/bochs_kms.c b/drivers/gpu/drm/bochs/bochs_kms.c index 9e836386e9..85dd2

Re: [PATCH] checkpatch.pl: Improve WARNING on Kconfig help

On Wed, Dec 19, 2018 at 02:44:36AM -0800, Joe Perches wrote: > On Wed, 2018-12-19 at 10:35 +0200, Igor Stoppa wrote: > > The checkpatch.pl script complains when the help section of a Kconfig > > entry is too short, but it doesn't really explain what it is looking > > for. Instead, it gives a generi

Re: [PATCH] hpet: Fix missing '=' character in the __setup() code of hpet_mmap_enable.

On 12/19/18 3:16 PM, Greg KH wrote: On Wed, Dec 19, 2018 at 02:55:02PM +0530, Buland Singh wrote: The kernel command parameter 'hpet_mmap' never takes effect due to missing '=' character in the __setup() code of hpet_mmap_enable and the memory map of the HPET registers never get expose to usersp

Re: [PATCH v2 1/3] sched/fair: fix rounding issue for asym packing

On 19/12/2018 08:32, Vincent Guittot wrote: [...] > This is another UC, asym packing is used at SMT level for now and we > don't face this kind of problem, it has been also tested and DynamiQ > configuration which is similar to SMT : 1 CPU per sched_group > The legacy b.L one was not the main targe

[PATCH] cifs: handle allocation failures early

ented. Patch was compile tested with: x86_64_defconfig + CIFS=m (with an unrelated smatch warnings and some pending cocci fixes) Patch is against v4.20-rc7 (localversion-next is next-20181219) fs/cifs/misc.c | 33 +++-- 1 file changed, 19 insertions(+), 14 deletions(-)

Re: [PATCH v4 4/9] drm/rockchip/rockchip_drm_gem.c: Convert to use vm_insert_range

On Wed, Dec 19, 2018 at 05:16:09PM +0530, Souptick Joarder wrote: > On Wed, Dec 19, 2018 at 3:02 PM Russell King - ARM Linux > wrote: > > > > On Wed, Dec 19, 2018 at 09:01:09AM +0530, Souptick Joarder wrote: > > > On Tue, Dec 18, 2018 at 6:31 PM Russell King - ARM Linux > > > wrote: > > > > > > >

Re: [PATCH v10 14/27] drivers: firmware: psci: Simplify error path of psci_dt_init()

On 29/11/2018 18:46, Ulf Hansson wrote: > Instead of having each psci init function taking care of the of_node_put(), > let's deal with that from psci_dt_init(), as this enables a bit simpler > error path for each psci init function. > > Cc: Lina Iyer > Co-developed-by: Lina Iyer > Signed-off-by

[PATCH] usb: gadget: function: sync f_uac1 ac header baInterfaceNr

f_uac1 audio control header descriptor default set baInterfaceNr[]={1,2}, but usb gadget make a configuration descriptor with more interfaces combination, it can not confirm f_uac1 function linked first. So always keep baInterfaceNr[]={1,2} is correct, and it is necessary to sync baInterfaceNr[] w

Re: [PATCH v10 13/27] drivers: firmware: psci: Support hierarchical CPU idle states

On 29/11/2018 18:46, Ulf Hansson wrote: > From: Lina Iyer > > Currently CPU's idle states are represented in a flattened model, via the > "cpu-idle-states" binding from within the CPU's device nodes. > > Support the hierarchical layout, simply by converting to calling the new OF > helper, of_get

Re: [PATCH 1/1] ARM: STi: Restore secondary CPU's bringup

On 12/19/18 12:28 PM, Russell King - ARM Linux wrote: > On Wed, Dec 19, 2018 at 10:31:35AM +, Patrice CHOTARD wrote: >> Hi Russell >> >> On 12/18/18 6:27 PM, Russell King - ARM Linux wrote: >>> On Tue, Dec 18, 2018 at 05:05:18PM +, Patrice CHOTARD wrote: Hi Russell On 12/18/1

Re: [PATCH 3/7] tracing: Use var_refs[] for hist trigger reference checking

Hi Tom, On Tue, 18 Dec 2018 14:33:22 -0600 Tom Zanussi wrote: > From: Tom Zanussi > > Since all the variable reference hist_fields are collected into > hist_data->var_refs[] array, there's no need to go through all the > fields looking for them, or in separate arrays like synth_var_refs[], > w

Re: [PATCH] drivers/regulator: fix a missing check of return value

On Tue, Dec 18, 2018 at 11:04:13PM -0600, Kangjie Lu wrote: > If palmas_smps_read() fails, we should not use the read data in "reg" > which may contain random value. The fix inserts a check for the return > value of palmas_smps_read(): If it fails, we return the error code > upstream and stop using

[PATCH 04/10] drm/virtio: move virtio_gpu_object_{attach,detach} calls.

Drop the dummy ttm backend implementation, add a real one for TTM_PL_FLAG_TT objects. The bin/unbind callbacks will call virtio_gpu_object_{attach,detach}, to update the object state on the host side, instead of invoking those calls from the move_notify() callback. With that in place the move and

[PATCH 05/10] drm/virtio: use struct to pass params to virtio_gpu_object_create()

Create virtio_gpu_object_params, use that to pass object parameters to virtio_gpu_object_create. Also drop unused "kernel" parameter (unused, always false). Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_drv.h| 15 ++- drivers/gpu/drm/virtio/virtgpu_gem.c| 1

[PATCH 09/10] drm/virtio: move virtio_gpu_cmd_create_resource call into virtio_gpu_object_create

Specifically call virtio_gpu_object_create() before ttm_bo_init(). Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_drv.h| 2 ++ drivers/gpu/drm/virtio/virtgpu_gem.c| 3 +-- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 10 ++ drivers/gpu/drm/virtio/virtgpu_object.c

[PATCH 08/10] drm/virtio: drop fencing in virtio_gpu_resource_create_ioctl

There is no need to wait for completion here. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 51 +- 1 file changed, 1 insertion(+), 50 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_ioctl.c b/drivers/gpu/drm/virtio/virtgpu_io

[PATCH 07/10] drm/virtio: params struct for virtio_gpu_cmd_create_resource_3d()

Add 3d resource parameters to virtio_gpu_object_params struct and use it for virtio_gpu_cmd_resource_create_3d() calls. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_drv.h | 10 +- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 25 ++--- drivers/gpu/drm/

[PATCH 03/10] drm/virtio: drop virtio_gpu_fence_cleanup()

Just call drm_fence_put directly instead. Also set vgfb->fence to NULL after dropping the reference. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_drv.h | 1 - drivers/gpu/drm/virtio/virtgpu_fence.c | 8 drivers/gpu/drm/virtio/virtgpu_ioctl.c | 2 +- drivers/gpu/drm/

Re: [PATCH 0/7] tracing: Hist trigger var-ref cleanup and comments

Hi Tom, On Tue, 18 Dec 2018 14:33:19 -0600 Tom Zanussi wrote: > From: Tom Zanussi > > Hi, > > This patchset is a standalone series broken out of the v8 version of > the 'tracing: Hist trigger snapshot and onchange additions' patchset. > > It's a series of changes resulting from some suggesti

[PATCH 10/10] drm/virtio: ditch virtio_gpu_object_attach() calls

With virtio_gpu_object_create() being called earlier ttm_bo_init() will handle the virtio_gpu_object_attach() (via backend binding), so we can drop the extra calls now. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_gem.c | 9 - drivers/gpu/drm/virtio/virtgpu_ioctl.c |

[PATCH 06/10] drm/virtio: params struct for virtio_gpu_cmd_create_resource()

Add format, width and height to the virtio_gpu_object_params struct and use the struct for virtio_gpu_cmd_create_resource(). Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_drv.h | 7 --- drivers/gpu/drm/virtio/virtgpu_gem.c | 8 drivers/gpu/drm/virtio/virtgpu_

[PATCH 02/10] drm/virtio: fix pageflip flush

Sending the flush command only makes sense if we actually have a framebuffer attached to the scanout (handle != 0). Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_plane.c | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtg

[PATCH 01/10] drm/virtio: log error responses

If we got an error response code from the host, print it to the log. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_vq.c | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_vq.c b/drivers/gpu/drm/virtio/virtgpu_vq.c i

Re: [PATCH] checkpatch.pl: Improve WARNING on Kconfig help

On Wed, 2018-12-19 at 11:59 +, Andy Whitcroft wrote: > On Wed, Dec 19, 2018 at 02:44:36AM -0800, Joe Perches wrote: > > On Wed, 2018-12-19 at 10:35 +0200, Igor Stoppa wrote: > > > The checkpatch.pl script complains when the help section of a Kconfig > > > entry is too short, but it doesn't real

[PATCH v2 0/9] Overview of Arm komeda display driver

This is the first patchset of ARM new komeda display driver, this patchset added all basic structure of komeda, relationship of DRM-KMS with komeda, for tring to give a brife overview of komeda-driver. komeda is for supporting the ARM display processor D71 and later IPs, Since from D71, Arm displa

[PATCH v2 1/9] drm/komeda: komeda_dev/pipeline/component definition and initialzation

1. Added a brief definition of komeda_dev/pipeline/component, this change didn't add the detailed component features and capabilities, which will be added in the following changes. 2. Corresponding resources discovery and initialzation functions. Signed-off-by: James (Qian) Wang --- driver

[PATCH v2 2/9] dt/bindings: drm/komeda: Add DT bindings for ARM display processor D71

Add DT bindings documentation for the ARM display processor D71 and later IPs. Signed-off-by: James (Qian) Wang --- .../bindings/display/arm/arm,komeda.txt | 87 +++ 1 file changed, 87 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/arm/arm,komed

[PATCH v2 3/9] drm/komeda: Build komeda to be a platform module

Implement a simple wrapper for platform module to build komeda to module, Also add a very simple D71 layer code to show how to discover a product. Komeda driver direct bind the product ENTRY function xxx_identity to DT compatible name like: d71_product = { .product_id = MALIDP_D71_PRODUCT_

[PATCH v2 5/9] drm/komeda: Add komeda_format_caps for format handling

komeda_format_caps is for describing ARM display specific features and limitations of a specific format, and format_caps will be linked into &komeda_framebuffer like a extension of &drm_format_info. And komed_format_caps_table will be initialized before the enum_resources, since the layer features

[PATCH v2 4/9] drm/komeda: Add DT parsing

Parse DT and initialize corresponding dev/pipeline attributes. Signed-off-by: James (Qian) Wang --- .../gpu/drm/arm/display/komeda/komeda_dev.c | 74 +++ .../gpu/drm/arm/display/komeda/komeda_dev.h | 3 + .../drm/arm/display/komeda/komeda_pipeline.c | 4 + .../drm/arm/disp

Re: [GIT PULL 1/3] stm class: Fix a module refcount leak in policy creation error path

On Wed, Dec 19, 2018 at 01:45:17PM +0200, Alexander Shishkin wrote: > Greg Kroah-Hartman writes: > > > On Fri, Dec 14, 2018 at 05:53:45PM +0200, Alexander Shishkin wrote: > >> Commit ccddbbf4ef27 ("stm class: Introduce framing protocol drivers") > > > > I don't see that commit id in Linus's tree,

[PATCH v2 6/9] drm/komeda: Add komeda_framebuffer

komeda_framebuffer is for extending drm_framebuffer to add komeda own attributes and komeda specific fb handling. Signed-off-by: James (Qian) Wang --- drivers/gpu/drm/arm/display/komeda/Makefile | 3 +- .../arm/display/komeda/komeda_framebuffer.c | 165 ++ .../arm/display/k

[PATCH v2 7/9] drm/komeda: Attach komeda_dev to DRM-KMS

Add komeda_kms abstracton to attach komeda_dev to DRM-KMS CRTC: according to the komeda_pipeline PLANE: according to komeda_layer (layer input pipeline) PRIVATE_OBJS: komeda_pipeline/component all will be treat as private_objs komeda_kms is for connecting DRM-KMS and komeda_dev, like reporti

[PATCH v2 8/9] drm/doc: Add initial komeda driver documentation

v2: Some editing changes according to Randy Dunlap's comments Signed-off-by: James (Qian) Wang --- Documentation/gpu/drivers.rst| 1 + Documentation/gpu/komeda-kms.rst | 488 +++ 2 files changed, 489 insertions(+) create mode 100644 Documentation/gpu/komeda-kms

[PATCH v2 9/9] MAINTAINERS: Add maintainer for arm komeda driver

v2: Adjusted the position of KOMEDA by alphabetical order Signed-off-by: James (Qian) Wang --- MAINTAINERS | 9 + 1 file changed, 9 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 254b7b267731..e48c2e5fd29f 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -1124,6 +1124,15 @@ S:

[PATCH v2] RISC-V: Make BSS section as the last section in vmlinux.lds.S

The objcopy only emits loadable sections when creating flat kernel Image. To have minimal possible size of flat kernel Image, we should have all non-loadable sections after loadable sections. Currently, execption table section (loadable section) is after BSS section (non-loadable section) in the R

Re: [PATCH] hpet: Fix missing '=' character in the __setup() code of hpet_mmap_enable.

On Wed, Dec 19, 2018 at 05:34:32PM +0530, Buland Singh wrote: > On 12/19/18 3:16 PM, Greg KH wrote: > > On Wed, Dec 19, 2018 at 02:55:02PM +0530, Buland Singh wrote: > > > The kernel command parameter 'hpet_mmap' never takes effect due to missing > > > '=' character in the __setup() code of hpet_mm

Re: [PATCH 05/16] remoteproc/pru: Add pru-specific debugfs support

On Tue, Dec 18, 2018 at 05:51:12PM +0200, Roger Quadros wrote: > We could combine control and debug into one iomap and use > 2 regmap ranges. But this is really working around the > regmap_mmio limitation of not being able to use more than one ioremaps. > Mark, any suggestions? If they're separa

[PATCH] sysfs: Disable lockdep for driver bind/unbind files

This is the much more correct fix for my earlier attempt at: https://lkml.org/lkml/2018/12/10/118 Short recap: - There's not actually a locking issue, it's just lockdep being a bit too eager to complain about a possible deadlock. - Contrary to what I claimed the real problem is recursion on

[PATCH v2 1/1] ARM: sti: remove pen_release and boot_lock

From: Patrice Chotard The pen_release implementation was created for Versatile platforms to work around boot loaders that did not differentiate between the various different secondary CPUs on this ARM development platform. This should not be true of modern platforms where we send IPIs to specific

Re: linux-next: build warnings after merge of the wireless-drivers-next tree

"Grumbach, Emmanuel" writes: >> >> Stephen Rothwell writes: >> >> > On Fri, 30 Nov 2018 12:05:55 +1100 Stephen Rothwell >> wrote: >> >> >> >> After merging the wireless-drivers-next tree, today's linux-next >> >> build >> >> (x86_64 allmodconfig) produced these warnings: >> >> >> >> drivers/n

[PATCH 00/10] PCI: DWC/Keystone: MSI configuration cleanup

This series tries to address the comments discussed in [1] w.r.t removing Keystone specific callbacks defined in dw_pcie_host_ops. This series also tries to cleanup the Keystone interrupt handling part. This series is created on top of git://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.

[REGRESSION] imx_v6_v7_defconfig: undefined reference to `__hyp_stub_vectors'

Hi there I noticed that at least today's and yesterdays -next won't build with the imx_v6_v7_defconfig giving the following error: LD arch/arm/boot/compressed/vmlinux arch/arm/boot/compressed/head.o: In function `restart': (.text+0xa8): undefined reference to `__hyp_stub_vectors' (.text+0x

[PATCH 05/10] PCI: keystone: Use hwirq to get the IRQ number offset

ks_pcie_msi_irq_handler() uses 'virq' to get the IRQ number offset. This offset is used to get the correct MSI_IRQ_STATUS register corresponding to the IRQ line that raised the interrupt. There is no guarantee that 'virq' assigned for consecutive hardware IRQ will be contiguous. And this might get

[PATCH 10/10] PCI: dwc: Do not write to MSI control registers if the platform doesn't use it

Platforms which populate msi_host_init, has it's own MSI controller logic. Writing to MSI control registers on platforms which doesn't use Designware's MSI controller logic might have side effects. To be safe, do not write to MSI control registers if the platform uses it's own MSI controller logic

[PATCH 02/10] PCI: keystone: Use "dummy_irq_chip" instead of new irqchip for legacy interrupt handling

Instead of creating a new irqchip with empty callback functions, use dummy_irq_chip. Since there is nothing to do in the irqchip callback functions, use handle_simple_irq instead of handle_level_irq. Signed-off-by: Kishon Vijay Abraham I --- drivers/pci/controller/dwc/pci-keystone.c | 24 ++-

[PATCH 03/10] PCI: keystone: Modify legacy_irq_handler to check the IRQ_STATUS of INTA/B/C/D

The legacy interrupt handler directly checks the IRQ_STATUS register corresponding to a interrupt line inorder to invoke generic_handle_irq. While this is okay for K2G platform which has separate interrupt line for each of the 4 legacy interrupts, AM654 which uses the same PCIe wrapper has a singl

Re: [PATCH v6 0/7] spi: add support for octal mode

Hi, On 19/12/18 3:41 PM, Yogesh Narayan Gaur wrote: > Add support for octal mode IO data transfer. > Micron flash, mt35xu512aba, supports octal mode data transfer and > NXP FlexSPI controller supports 8 data lines for data transfer (Rx/Tx). > > Patch series > * Add support for octal mode flags an

[PATCH 01/10] PCI: keystone: Cleanup interrupt related macros

No functional change. Change both MSI interrupt and legacy interrupt related macros to take an additional argument in order to return the correct register offset. Signed-off-by: Kishon Vijay Abraham I --- drivers/pci/controller/dwc/pci-keystone.c | 26 +++ 1 file changed, 13

[PATCH 07/10] PCI: dwc: Add support to use non default msi_irq_chip

Platforms using Designware IP uses dw_pci_msi_bottom_irq_chip for configuring the MSI controller logic within the Designware IP. However certain platforms like Keystone (K2G) which uses Desingware IP has it's own MSI controller logic. For handling such platforms, the irqchip ops uses msi_irq_ack, m

[PATCH 09/10] PCI: dwc: Remove Keystone specific dw_pcie_host_ops

Now that Keystone started using it's own msi_irq_chip, remove Keystone specific callback function defined in dw_pcie_host_ops. Signed-off-by: Kishon Vijay Abraham I --- .../pci/controller/dwc/pcie-designware-host.c | 45 ++- drivers/pci/controller/dwc/pcie-designware.h | 5 ---

[PATCH 08/10] PCI: keystone: Use Keystone specific msi_irq_chip

Use Keystone specific msi_irq_chip to configure the MSI controller logic in the PCIe keystone wrapper instead of using the default Designware msi_irq chip (dw_pci_msi_bottom_irq_chip) with callback functions for configuring the Keystone MSI controller. This will help to remove Keystone specific cal

Re: [PATCH] checkpatch.pl: Improve WARNING on Kconfig help

On 19/12/2018 14:29, Joe Perches wrote: On Wed, 2018-12-19 at 11:59 +, Andy Whitcroft wrote: On Wed, Dec 19, 2018 at 02:44:36AM -0800, Joe Perches wrote: To cover both cases perhaps: "please ensure that this config symbols is described fully (less than $min_conf_desc_

[PATCH 06/10] PCI: keystone: Cleanup ks_pcie_msi_irq_handler and ks_pcie_legacy_irq_handler

Both ks_pcie_msi_irq_handler() and ks_pcie_legacy_irq_handler() invokes ks_pcie_handle_msi_irq() and ks_pcie_handle_legacy_irq() respectively for handling the interrupts. Having two functions for handling the interrupt was used when keystone PCIe driver was implemented using two files. But with co

Re: [PATCH v3] Bluetooth: hci_bcm: Handle specific unknown packets after firmware loading

Hi Pawel, > The Broadcom controller on aries S5PV210 boards sends out a couple of > unknown packets after the firmware is loaded. This will cause > logging of errors such as: > Bluetooth: hci0: Frame reassembly failed (-84) > > This is probably also the case with other boards, as there are

Re: [LKP] 5404a7f1c2 [ 90.902541] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper:1]

On Wed, Dec 19, 2018 at 06:03:45PM +0800, Rong Chen wrote: > On 12/18/2018 08:17 PM, Matthew Wilcox wrote: > > On Tue, Dec 18, 2018 at 08:20:28AM +0800, kernel test robot wrote: > > > Greetings, > > > > > > 0day kernel testing robot got the below dmesg and the first bad commit is > > > > > > http

Re: [PATCH v2] Bluetooth: btbcm: Add entry for BCM4329B1 UART bluetooth

Hi Pawel, > This patch adds the device ID for the BCM 4329 combo module used > in the Samsung Aries based phones (Galaxy S and it's variants). > > ``` > [ 11.508980] Bluetooth: hci0: BCM: chip id 41 > [ 11.518975] Bluetooth: hci0: BCM: features 0x04 > [ 11.550132] Bluetooth: hci0: BCM4329B1

Re: [PATCH] mm: skip checking poison pattern for page_to_nid()

On 12/19/18 5:20 AM, Michal Hocko wrote: > On Tue 18-12-18 20:57:32, Qian Cai wrote: > [...] >> diff --git a/include/linux/mm.h b/include/linux/mm.h >> index 5411de93a363..f083f366ea90 100644 >> --- a/include/linux/mm.h >> +++ b/include/linux/mm.h >> @@ -985,9 +985,7 @@ extern int page_to_nid(const

Re: [WIP PATCH 03/15] drm/dp_mst: Introduce new refcounting scheme for mstbs and ports

On Tue, Dec 18, 2018 at 04:27:58PM -0500, Lyude Paul wrote: > On Fri, 2018-12-14 at 10:29 +0100, Daniel Vetter wrote: > > On Thu, Dec 13, 2018 at 08:25:32PM -0500, Lyude Paul wrote: > > > The current way of handling refcounting in the DP MST helpers is really > > > confusing and probably just plain

Re: [PATCH] sysfs: Disable lockdep for driver bind/unbind files

On Wed, Dec 19, 2018 at 01:39:09PM +0100, Daniel Vetter wrote: > --- a/include/linux/device.h > +++ b/include/linux/device.h > @@ -327,6 +327,7 @@ struct driver_attribute { > #define DRIVER_ATTR_WO(_name) \ > struct driver_attribute driver_attr_##_name = __ATTR_WO(_name) > > + > extern in

Re: [PATCH 35/63] perf trace: Allow specifying a set of events to add in perfconfig

Em Wed, Dec 19, 2018 at 05:40:24PM +0900, Namhyung Kim escreveu: > On Tue, Dec 18, 2018 at 07:07:05PM -0300, Arnaldo Carvalho de Melo wrote: > > + if (!strcmp(var, "trace.add_events")) { > > + struct trace *trace = arg; > > + struct option o = OPT_CALLBACK('e', "event", &trace

[PATCH 04/10] PCI: keystone: Add separate functions for configuring MSI and legacy interrupt

ks_pcie_get_irq_controller_info() was used to configure both MSI and legacy interrupt. This will prevent MSI or legacy interrupt specific intializations. Add separate functions to configure MSI and legacy interrupts. Signed-off-by: Kishon Vijay Abraham I --- drivers/pci/controller/dwc/pci-keysto

Re: [RFC][PATCH 0/3] arm64 relaxed ABI

On Tue, Dec 18, 2018 at 05:59:38PM +, Catalin Marinas wrote: > On Tue, Dec 18, 2018 at 04:03:38PM +0100, Andrey Konovalov wrote: > > On Wed, Dec 12, 2018 at 4:02 PM Catalin Marinas > > wrote: > > > The summary of our internal discussions (mostly between kernel > > > developers) is that we can

Re: [PATCH 2/3] dt-bindings: display: bridge: lvds-transmitter: add pwdn-gpios

On 2018-12-19 12:38, Laurent Pinchart wrote: > Hello, > > On Wednesday, 19 December 2018 11:57:32 EET Peter Rosin wrote: >> On 2018-12-19 10:12, Andrzej Hajda wrote: >>> On 19.12.2018 00:19, Peter Rosin wrote: Add optional property to specify a power-down GPIO. The pwdn-gpios name is alr

Re: [PATCH v10 13/27] drivers: firmware: psci: Support hierarchical CPU idle states

On Wed, 19 Dec 2018 at 13:11, Daniel Lezcano wrote: > > On 29/11/2018 18:46, Ulf Hansson wrote: > > From: Lina Iyer > > > > Currently CPU's idle states are represented in a flattened model, via the > > "cpu-idle-states" binding from within the CPU's device nodes. > > > > Support the hierarchical

Re: [PATCH 0/3] irq/core: Fix and expand the irq affinity descriptor

On Wed, Dec 19, 2018 at 4:23 PM Thomas Gleixner wrote: > > On Tue, 4 Dec 2018, Dou Liyang wrote: > > > Now, Spreading the interrupt affinity info by a cpumask pointer is not > > enough, meets a problem[1] and hard to expand in the future. > > > > Fix it by: > > > > +-

Re: [PATCH 0/7] drm: KMS cleanup remove drm_mode_object dependency

On Tue, 18 Dec 2018, Shayenne Moura wrote: > This patch serie removes drm_mode_object dependency from > drm_display_mode struct. This is part of KMS cleanup. For future reference: Please use git-send-email or fix the mail threading otherwise. Patches 1-7 should be in reply to the cover letter

Re: [PATCH] HID: i2c-hid: Ignore input report if there's no data present on Elan touchpanels

On Fri, 14 Dec 2018, Kai-Heng Feng wrote: > While using Elan touchpads, the message floods: > [ 136.138487] i2c_hid i2c-DELL08D6:00: i2c_hid_get_input: incomplete report > (14/65535) > > Though the message flood is annoying, the device it self works without > any issue. I suspect that the devic

Re: [PATCH 4/7] drm: i915: Delete base.id prints

On Tue, 18 Dec 2018, Shayenne Moura wrote: > This patch removes base.id prints from drm_display_mode > > objects in i915 files. It removes dependency from drm_mode_object. As said, this could expand on the *why*. With that fixed, Reviewed-by: Jani Nikula as well as ac

Re: [PATCH 1/7] drm: msm: Delete base.id prints

On Tue, Dec 18, 2018 at 11:38:03AM -0200, Shayenne Moura wrote: > This patch removes base.id prints from drm_display_mode > objects in msm files. It removes dependency from drm_mode_object. > > Signed-off-by: Shayenne Moura I think switching these over to the DRM_MODE_FMT and DRM_MODE_ARG like d

Re: [PATCH 57/63] perf beauty mmap: Print PROT_READ before PROT_EXEC to match strace output

Em Wed, Dec 19, 2018 at 06:15:00PM +0900, Namhyung Kim escreveu: > On Tue, Dec 18, 2018 at 07:07:27PM -0300, Arnaldo Carvalho de Melo wrote: > > Helps with comparing 'strace' and 'perf trace' output, for mutual > > regression testing. > > +++ b/tools/perf/trace/beauty/mmap.c > > @@ -17,8 +17,8 @

[PATCH v2 1/3] dt-bindings: display: bridge: fork out ti,ds90c185 from lvds-transmitter

From: Peter Rosin DS90C185 has a shutdown pin which does not fit in the lvds-transmitter binding, which is meant to be generic. The sister chip DS90C187 is similar to DS90C185, describe it here as well. Signed-off-by: Peter Rosin --- .../bindings/display/bridge/lvds-transmitter.txt | 8 +--

[PATCH v2 2/3] dt-bindings: display: bridge: lvds-transmitter: cleanup example

From: Peter Rosin Drop #address-cells and #size-cells from the root node in the example, they are unused. Signed-off-by: Peter Rosin --- Documentation/devicetree/bindings/display/bridge/lvds-transmitter.txt | 2 -- 1 file changed, 2 deletions(-) diff --git a/Documentation/devicetree/bindings

Re: [PATCH 2/7] drm: Remove use of drm_mode_object

On Tue, Dec 18, 2018 at 11:38:10AM -0200, Shayenne Moura wrote: > This patch removes the drm_mode_object prints, evaluation and use from > drm_display_mode objects used in drm files. It removes dependency from > drm_mode_object. > > Signed-off-by: Shayenne Moura Reviewed-by: Daniel Vetter > --

Re: [PATCH] scsi/dpt_i2o.c: Use dma_zalloc_coherent

On Sat, Dec 1, 2018 at 6:45 PM Sabyasachi Gupta wrote: > > On Sat, Nov 17, 2018 at 6:17 PM Sabyasachi Gupta > wrote: > > > > Replaced dma_alloc_coherent + memset with dma_zalloc_coherent > > > > Signed-off-by: Sabyasachi Gupta > > Any comment on this patch? Any comment on this patch? > > > ---

[PATCH v2 3/3] drm/bridge: add pwdn-gpios support to the lvds-encoder

From: Peter Rosin Optionally power down the LVDS-encoder when it is not in use. Signed-off-by: Peter Rosin --- drivers/gpu/drm/bridge/lvds-encoder.c | 34 ++ 1 file changed, 34 insertions(+) diff --git a/drivers/gpu/drm/bridge/lvds-encoder.c b/drivers/gpu/drm/

Re: [PATCH 3/7] drm: omapdrm: Delete base.id prints

On Tue, Dec 18, 2018 at 11:38:15AM -0200, Shayenne Moura wrote: > This patch removes base.id prints from drm_display_mode > > objects in omapdrm files. It removes dependency from drm_mode_object. > > Signed-off-by: Shayenne Moura Same comment as for msm, I think better

[PATCH v2 0/3] drm/bridge: various small lvds-encoder things

From: Peter Rosin Hi! I'm not sure if I should have added the texas chips to the lvds_encoder_match list in the driver, right next to the thine,thc63lvdm83d entry, but ended up not doing that. That can always be added later, it needed... Changes since v1: - fork out the bindings for the texas c

Re: [PATCH 4/7] drm: i915: Delete base.id prints

On Tue, Dec 18, 2018 at 11:38:21AM -0200, Shayenne Moura wrote: > This patch removes base.id prints from drm_display_mode > > objects in i915 files. It removes dependency from drm_mode_object. > > Signed-off-by: Shayenne Moura Again I think better to switch to DRM_MODE_

Re: [PATCH 5/7] drm: sti: Delete base.id prints

On Tue, Dec 18, 2018 at 11:38:25AM -0200, Shayenne Moura wrote: > This patch removes base.id prints from drm_display_mode > > objects in sti files. It removes dependency from drm_mode_object. > > Signed-off-by: Shayenne Moura Reviewed-by: Daniel Vetter > --- > driver

Re: [PATCH 6/7] drm: meson: Delete base.id prints

On Tue, Dec 18, 2018 at 11:38:30AM -0200, Shayenne Moura wrote: > This patch removes base.id prints from drm_display_mode > > objects in meson files. It removes dependency from drm_mode_object. > > Signed-off-by: Shayenne Moura > --- > drivers/gpu/drm/meson/meson_dw_hdm

<    1   2   3   4   5   6   7   8   9   10   >