Re: [PATCH V2] thermal/drivers/hisi: Switch to interrupt mode

Hi Daniel, On Thu, Sep 28, 2017 at 07:13:44AM +0200, Daniel Lezcano wrote: > At this moment, we have both the interrupt setup and the polling enabled. The > interrupt does nothing more than forcing an update while the temperature is > polled every second. > > We can do much better than that, thre

Re: [PATCH v3 2/8] platform/x86: dell-smbios: Introduce a WMI-ACPI interface

On Thursday 28 September 2017 06:02:14 Mario Limonciello wrote: > The driver currently uses an SMI interface which grants direct access > to physical memory to the firmware SMM methods via a pointer. > > Now add a WMI-ACPI interface that is detected by WMI probe and preferred > over the SMI interf

Re: [PATCH net-next 0/3] support changing steering policies in tuntap

On 2017年09月28日 06:13, Michael S. Tsirkin wrote: On Wed, Sep 27, 2017 at 04:23:54PM +0800, Jason Wang wrote: Hi all: We use flow caches based flow steering policy now. This is good for connection-oriented communication such as TCP but not for the others e.g connectionless unidirectional worklo

[iscsiadm] iscsiadm creates multiple same sessions when run with --login option in parallel.

Hi guys, If we run iscsiadm -m node --login command through the same IP address 4 times, only one session will be created. But if we run them in parallel, then 4 same sessions could be created. ( Here, xxx.xxx.xxx.xxx is the IP address to the IPSAN. I'm using the same IP in these 4 commands. )

Re: [PATCH 2/2] cpufreq: schedutil: consolidate capacity margin calculation

On Mon, Sep 25, 2017 at 02:55:07PM +0100, Patrick Bellasi wrote: > On 23-Sep 07:04, Leo Yan wrote: > > Scheduler CFS class has variable 'capacity_margin' to calculate the > > capacity margin, and schedutil governor also needs to compensate the > > same margin for frequency tipping point. Below are

Re: [PATCH] drm/omap: Fix error handling path in 'omap_dmm_probe()'

 Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki On 24/09/17 09:01, Christophe JAILLET wrote: > If we don't find a matching device node, we must free the memory allocated > in 'omap_dmm' a few lines above. > > Fixes:

Re: [PATCH] ARM: multi_v7_defconfig: Enable USB3503 driver

On Thu, Sep 28, 2017 at 4:40 AM, Linus Lüssing wrote: > The Odroid U3 (Exynos 4412 based) for instance needs this driver, > otherwise its USB hub will not come up. > > exynos_defconfig already has this enabled as built-in, too. So > just doing the same here in multi_v7_defconfig. > > Signed-off-by

[PATCH v3] mm, sysctl: make NUMA stats configurable

This is the second step which introduces a tunable interface that allow numa stats configurable for optimizing zone_statistics(), as suggested by Dave Hansen and Ying Huang. = When page allocation performance becomes a bottlen

Script to do smart sparse diffs (was Re: [git pull] vfs.git regression fix Re: Regression related to ipc shmctl compat)

Christoph Hellwig writes: > On Mon, Sep 25, 2017 at 06:37:28PM -0700, Linus Torvalds wrote: >> Pulled and pushed out, but I'd like to note that sparse would have >> caught this. Except we are so far away from being sparse-clean that >> nobody runs it. > > I tend to run sparse over the nvme code b

Re: [PATCH v2 1/5] media: atmel_isc: Add spin lock for clock enable ops

Hi Sakari, On 2017/9/27 15:16, Sakari Ailus wrote: Hi Wenyou, On subject: s/_/-/ On Mon, Sep 18, 2017 at 02:39:21PM +0800, Wenyou Yang wrote: Add the spin lock for the clock enable and disable operations. Signed-off-by: Wenyou Yang --- Changes in v2: None drivers/media/platform/atmel/

Re: [RFC 2/3] module: Ignore delete_id parameter

On Wed, Sep 27, 2017 at 1:40 PM, Jon Derrick wrote: > The PCI driver delete_id parameter is handled in each individual driver > registration callback. > > Signed-off-by: Jon Derrick > --- > kernel/module.c | 7 +++ > 1 file changed, 7 insertions(+) > > diff --git a/kernel/module.c b/kernel/m

Re: [PATCH v4 1/2] x86/unwind: add ORC unwinder

On 27/09/17 23:08, Josh Poimboeuf wrote: > On Tue, Aug 08, 2017 at 01:09:08PM -0700, Andy Lutomirski wrote: >> On Tue, Aug 8, 2017 at 12:13 PM, Josh Poimboeuf wrote: >>> On Tue, Aug 08, 2017 at 12:03:51PM -0700, Linus Torvalds wrote: On Tue, Aug 8, 2017 at 11:58 AM, Josh Poimboeuf wrot

[GIT PULL] seccomp fix for v4.14-rc3

Hi, Please pull this seccomp fix for v4.14-rc3. Bug was introduced in v4.4, and went unnoticed until now. Thanks! -Kees The following changes since commit e19b205be43d11bff638cad4487008c48d21c103: Linux 4.14-rc2 (2017-09-24 16:38:56 -0700) are available in the git repository at: git://gi

linux-next: Tree for Sep 28

Hi all, News: I will not be doing linux-next releases from Setp 30 to Oct 30 (inclusive). Changes since 20170927: The cifs tree lost its build failure. The drm tree gained a build failure for which I applied a fix patch. The staging tree lost its build failure. The ipmi tree gained a build

Re: Vibrations in input vs. LED was Re: [PATCH v2 0/3] led: ledtrig-transient: add support for hrtimer

On September 27, 2017 10:03:28 PM PDT, David Lin wrote: >Dmitry, > >On Fri, Sep 15, 2017 at 3:30 PM, Dmitry Torokhov > wrote: >> On Fri, Sep 15, 2017 at 2:55 PM, Jacek Anaszewski >> wrote: >>> On 09/15/2017 08:34 PM, Dmitry Torokhov wrote: On Thu, Sep 14, 2017 at 1:58 PM, Pavel Machek wrote

[tip:core/urgent] objtool: Skip unreachable warnings for GCC 4.4 and older

Commit-ID: da541b20021c781f8b65492eeaee824e729599eb Gitweb: https://git.kernel.org/tip/da541b20021c781f8b65492eeaee824e729599eb Author: Josh Poimboeuf AuthorDate: Wed, 27 Sep 2017 17:34:23 -0500 Committer: Ingo Molnar CommitDate: Thu, 28 Sep 2017 07:23:02 +0200 objtool: Skip unreachabl

[tip:core/urgent] objtool: Support unoptimized frame pointer setup

Commit-ID: 607a4029d439cdfa258aff5da32bb9cd6ed1a66d Gitweb: https://git.kernel.org/tip/607a4029d439cdfa258aff5da32bb9cd6ed1a66d Author: Josh Poimboeuf AuthorDate: Wed, 27 Sep 2017 10:36:38 -0500 Committer: Ingo Molnar CommitDate: Thu, 28 Sep 2017 07:25:54 +0200 objtool: Support unoptim

Re: [PATCH v2 5/5] media: atmel-isc: Rework the format list

On 2017/9/27 16:03, Hans Verkuil wrote: On 09/27/2017 07:15 AM, Yang, Wenyou wrote: Hi Hans, Thank  you very much for your review. On 2017/9/25 21:24, Hans Verkuil wrote: Hi Wenyou, On 18/09/17 08:39, Wenyou Yang wrote: To improve the readability of code, split the format array into two,

Re: [PATCH] sparc: Provide cmpxchg64 for 32-bit builds

From: Guenter Roeck Date: Wed, 27 Sep 2017 21:55:50 -0700 > On 09/27/2017 09:38 PM, David Miller wrote: >> From: Guenter Roeck >> Date: Sun, 24 Sep 2017 10:29:31 -0700 >> >>> Fix the following build error, seen when building >>> sparc32:allmodconfig. >>> >>> drivers/net/ethernet/intel/i40e/i40e

[PATCH V2] thermal/drivers/hisi: Switch to interrupt mode

At this moment, we have both the interrupt setup and the polling enabled. The interrupt does nothing more than forcing an update while the temperature is polled every second. We can do much better than that, threshold is set to 65C in the DT and the passive cooling device enters in the dance when

Re: Vibrations in input vs. LED was Re: [PATCH v2 0/3] led: ledtrig-transient: add support for hrtimer

Dmitry, On Fri, Sep 15, 2017 at 3:30 PM, Dmitry Torokhov wrote: > On Fri, Sep 15, 2017 at 2:55 PM, Jacek Anaszewski > wrote: >> On 09/15/2017 08:34 PM, Dmitry Torokhov wrote: >>> On Thu, Sep 14, 2017 at 1:58 PM, Pavel Machek wrote: On Thu 2017-09-14 21:31:31, Jacek Anaszewski wrote: >

Re: [PATCH net-next 0/3] support changing steering policies in tuntap

On Wed, Sep 27, 2017 at 4:25 PM, Willem de Bruijn wrote: >>> In the future, both simple and sophisticated policy like RSS or other guest >>> driven steering policies could be done on top. >> >> IMHO there should be a more practical example before adding all this >> indirection. And it would be nic

Re: DMA error when sg->offset value is greater than PAGE_SIZE in Intel IOMMU

On 28-09-2017 03:43, Casey Leedom wrote: > | From: Raj, Ashok > | Sent: Wednesday, September 27, 2017 12:07 PM > | > | looking at the debug output i got from Harsh it still looks like a bug in > | the code. > | > | [ 538.284589] __domain_mapping nr_pages 0x1 > | [ 538.284600] __domain_mapping sg

[PATCH V2] power: Use a more common logging style

Convert printks to pr_. Miscellanea: o Use pr_fmt with "PM:" and remove "PM: " from format strings o Coalesce format strings and realign format arguments o Convert an embedded incorrect function name to "%s: ", __func__ o Convert a couple multi-line formats to multiple pr_ calls Signed-off-by: J

linux-next: build failure after merge of the drm tree

Hi Dave, After merging the drm tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/gpu/drm/amd/powerplay/smumgr/ci_smc.o:(.opd+0xd8): multiple definition of `ci_send_msg_to_smc' drivers/gpu/drm/radeon/ci_smc.o:(.opd+0xc0): first defined here drivers/gpu/drm/amd/powerp

Re: [PATCH] sparc: Provide cmpxchg64 for 32-bit builds

On 09/27/2017 09:38 PM, David Miller wrote: From: Guenter Roeck Date: Sun, 24 Sep 2017 10:29:31 -0700 Fix the following build error, seen when building sparc32:allmodconfig. drivers/net/ethernet/intel/i40e/i40e_ethtool.c: In function 'i40e_set_priv_flags': drivers/net/ethernet/intel/i

Re: [PATCH v6 05/11] dt-bindings: net: dwmac-sun8i: update documentation about integrated PHY

On 09/27/2017 12:34 AM, Corentin Labbe wrote: > This patch add documentation about the MDIO switch used on sun8i-h3-emac > for integrated PHY. > > Signed-off-by: Corentin Labbe > --- > .../devicetree/bindings/net/dwmac-sun8i.txt| 138 > +++-- > 1 file changed, 126 inse

Re: [PATCH] sparc: time: Remove unneeded linux/miscdevice.h include

From: Corentin Labbe Date: Mon, 18 Sep 2017 19:58:21 +0200 > arch/sparc/kernel/time_64.c does not contain any miscdevice so the > inclusion of linux/miscdevice.h is unnecessary. > > Signed-off-by: Corentin Labbe Applied.

Re: [PATCH] sparc64: mmu_context: Add missing include files

From: Guenter Roeck Date: Sun, 10 Sep 2017 13:44:47 -0700 > Fix the following build errors. > > In file included from arch/sparc/include/asm/mmu_context.h:4:0, > from include/linux/mmu_context.h:4, >from drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h:29, >

Re: [PATCH] sbus: char: Move D7S_MINOR to include/linux/miscdevice.h

From: Corentin Labbe Date: Mon, 18 Sep 2017 20:10:36 +0200 > This patch move the define for D7S_MINOR to include/linux/miscdevice.h. > It's better that all minor number are in the same place. > > Signed-off-by: Corentin Labbe Applied.

Re: [PATCH v6 11/11] of: mdio: Prevent of_mdiobus_register from scanning mdio-mux nodes

On 09/27/2017 07:12 AM, Andrew Lunn wrote: > On Wed, Sep 27, 2017 at 09:34:14AM +0200, Corentin Labbe wrote: >> Each child node of an MDIO node is scanned as a PHY when calling >> of_mdiobus_register() givint the following result: >> [ 18.175379] mdio_bus stmmac-0: /soc/ethernet@1c3/mdio/md

[PATCH v3 2/6] perf record: Get the first sample time and last sample time

In perf record, it's walked on all samples yet. So it's very easy to get the first/last samples and save the time to perf file header via the function write_sample_time(). In later, perf report/script will fetch the time from perf file header. Change log: --- v3: Remove the definitions of

[PATCH v3 3/6] perf util: Create function to parse time percent

Current perf report/script/... have a --time option to limit the time range of output. But right now it only supports absolute time. For easy using, now it can support a percent of time usage. For example: 1. Select the second 10% time slice perf report --time 10%/2 2. Select from 0% to 10%

[PATCH v3 5/6] perf report: support time percent and multiple time ranges

perf report has a --time option to limit the time range of output. It only supports absolute time. Now this option is extended to support multiple time ranges and support the percent of time. For example: 1. Select the first and second 10% time slices perf report --time 10%/1,10%/2 2. Select fr

[PATCH v3 6/6] perf script: support time percent and multiple time ranges

perf script has a --time option to limit the time range of output. It only supports absolute time. Now this option is extended to support multiple time ranges and support the percent of time. For example: 1. Select the first and second 10% time slices perf script --time 10%/1,10%/2 2. Select

[PATCH v3 1/6] perf header: Record first sample time and last sample time in perf file header

perf report/script/... have a --time option to limit the time range of output. That's very useful to slice large traces, e.g. when processing the output of perf script for some analysis. But right now --time only supports absolute time. Also there is no fast way to get the start/end times of a giv

[PATCH v3 4/6] perf util: Create function to perform multiple time range checking

Previous patch supports the multiple time range. For example, select the first and second 10% time slices. perf report --time 10%/1,10%/2 We need a function to check if a timestamp is in the ranges of [0, 10%) and [10%, 20%]. Note that it includes the last element in [10%, 20%] but it doesn't in

[PATCH v3 0/6] perf report/script: Support percent and multiple range in --time option

v3: --- 1. Move the definitions of first_sample_time/last_sample_time from perf_session and struct record to perf_evlist and update the related code. v2: --- 1. This patch creates a new header feature type HEADER_SAMPLE_TIME and related ops. Save the first sample time and the last sample

linux-next: build failure after merge of the ipmi tree

Hi Corey, After merging the ipmi tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/char/ipmi/ipmi_si_platform.c:360:1: warning: data definition has no type or storage class MODULE_DEVICE_TABLE(of, of_ipmi_match); ^ drivers/char/ipmi/ipmi_si_platform.c:360:1: error

Re: [PATCH] sparc: Provide cmpxchg64 for 32-bit builds

From: Guenter Roeck Date: Sun, 24 Sep 2017 10:29:31 -0700 > Fix the following build error, seen when building sparc32:allmodconfig. > > drivers/net/ethernet/intel/i40e/i40e_ethtool.c: > In function 'i40e_set_priv_flags': > drivers/net/ethernet/intel/i40e/i40e_ethtool.c:4150:2: error: >

[PATCH v2] irq/generic-chip: Don't replace domain's name

Currently we are replacing domain's name with irq chip's name when allocating generic chips. When the old domain's name is allocated, it would cause memory leak. Even worse the domain framework would try to free the wrong name later. Fixes: d59f6617eef0 ("genirq: Allow fwnode to carry name inform

Re: [PATCH 0/2 v8] oom: capture unreclaimable slab info in oom message

On 2017/09/28 6:46, Yang Shi wrote: > Changelog v7 —> v8: > * Adopted Michal’s suggestion to dump unreclaim slab info when unreclaimable > slabs amount > total user memory. Not only in oom panic path. Holding slab_mutex inside dump_unreclaimable_slab() was refrained since V2 because there are

Re: [PATCH] irq/generic-chip: Fix memory leak of domain->name

Hi Thomas, On 09/28/2017 11:18 AM, jeffy wrote: I don't think that this is the proper thing to do. There is no reason why the domain should have the same name as the irq chip. So we rather should do: if (!d->name) d->name = name; Along with a proper comment. that is better, will

Re: [PATCH for-next 05/20] RDMA/hns: Add command queue support for hip08 RoCE driver

On 2017/9/27 20:41, Doug Ledford wrote: On Wed, 2017-09-27 at 08:21 -0400, Doug Ledford wrote: And if you argee, after this patchset has been accepted we will send a following up patch : In hns_roce_cmq_send function, replace usleep_range(1000, 2000); with the following st

[PATCH for-next 8/9] RDMA/hns: Remove unused struct members in hns-abi.h

From: Lijun Ou This patch mainly deletes some unused struct members for hns_roce_ib_create_qp in order to match libhns, because the num of struct members of hns_roce_ib_create_qp must be the same with hns_roce_create_qp in libhns. Signed-off-by: Lijun Ou Signed-off-by: Wei Hu (Xavier) Signed-o

[PATCH for-next 6/9] RDMA/hns: Add return statement when checking error in hns_roce_v1_mr_free_work_fn

After the loop in hns_roce_v1_mr_free_work_fn function, it is possible that the local variable named hr_qp is NULL, the operation "hr_qp->qpn" will result in the exception. As a result, we add return statement when checking error. This patch fixes the smatch error as below: drivers/infiniband/hw/h

[PATCH for-next 5/9] RDMA/hns: Set rdma_ah_attr type for querying qp

From: Lijun Ou When querying qp, It needs to return RoCE device ah_attr type that may be specific to RoCE devices. Signed-off-by: Lijun Ou Signed-off-by: Wei Hu (Xavier) Signed-off-by: Shaobo Xu --- drivers/infiniband/hw/hns/hns_roce_hw_v1.c | 2 ++ drivers/infiniband/hw/hns/hns_roce_hw_v2.c

[PATCH for-next 0/9] Bug fixes & Code improvements in hip06 and hip08 RoCE driver

This patch-set introduces some bug fixes and code improvements for hip06 and hip08 RoCE driver. It includes a patch for fixing the assign algorithm of qp_attr->max_rd_atomic and qp_attr->max_dest_rd_atomic, three patches for static check errors, one for setting attr mask, one for returning RoCE dev

[PATCH for-next 9/9] RDMA/hns: Replace usleep_range with udelay when checking command status

From: Lijun Ou It replaces usleep_range with udelay to avoid using usleep_range function in spin_lock_bh spin region, because it probably cause calltrace. BUG: scheduling while atomic: insmod/1428/0x0002 Modules linked in: hns-roce-hw-v2(+) hns_roce rdma_ucm rdma_cm iw_cm ib_uverbs ib_cm ib

[PATCH for-next 3/9] RDMA/hns: Add return statement when kzalloc return NULL in hns_roce_v1_recreate_lp_qp

From: Lijun Ou When lp_qp_work is NULL, it should be returned ENOMEM. This patch mainly fixes it. Ihis patch fixes the smatch error as below: drivers/infiniband/hw/hns/hns_roce_hw_v1.c:918 hns_roce_v1_recreate_lp_qp() error: potential null dereference 'lp_qp_work'. (kzalloc returns null) Signe

[PATCH for-next 2/9] RDMA/hns: Factor out the code for checking sdb status into a new function

From: Lijun Ou It mainly places the lines for checking send doorbell status into a special functions. As a result, we can directly call it in check_qp_db_process_status function and keep consistent indenting style. It fixes: 5f110ac4bed8 ("IB/hns: Fix for checkpatch.pl comment style) The warning

[PATCH for-next 1/9] RDMA/hns: Modify the value with rd&dest_rd of qp_attr

From: Lijun Ou The value of max_rd_atomic and max_dest_rd_atomic in query_qp are incorrect. It should be assigned by left shifting of the bit in hip06 SoC. Signed-off-by: Lijun Ou Signed-off-by: Wei Hu (Xavier) --- drivers/infiniband/hw/hns/hns_roce_hw_v1.c | 4 ++-- 1 file changed, 2 inserti

Re: [PATCH v2 3/5] clk: aspeed: Add platform driver and register PLLs

On Wed, Sep 27, 2017 at 5:34 PM, Andrew Jeffery wrote: > On Wed, 2017-09-27 at 16:13 +1000, Joel Stanley wrote: >> > > + div_table, >> > >> > This doesn't seem to be correct. There's the problem of 0b000 and 0b001 >> > mapping >> > the same value of 2 for the AST2500, whose ta

[PATCH for-next 7/9] RDMA/hns: Remove unnecessarily calling unregister_inetaddr_notifier function

From: Lijun Ou When the driver doesn't call register_inetaddr_notifier function, it need not call unregister_inetaddr_notifier to unregister inet addr. This patch fixes it. Signed-off-by: Lijun Ou Signed-off-by: Wei Hu (Xavier) Signed-off-by: Shaobo Xu --- drivers/infiniband/hw/hns/hns_roce_

[PATCH for-next 4/9] RDMA/hns: Set mask for destination qp field of qp context assignment

From: Lijun Ou When only set IB_QP_DEST_QPN flag for attr_mask, the operation of assigning the dest_qp_num for dest_qp field of qp context is valid. Signed-off-by: Lijun Ou Signed-off-by: Wei Hu (Xavier) Signed-off-by: Shaobo Xu --- drivers/infiniband/hw/hns/hns_roce_hw_v1.c | 9 + 1

Re: [PATCH V2] PM / OPP: Move the OPP directory out of power/

On 27-09-17, 19:49, Rafael J. Wysocki wrote: > Actually, it is even listed in that MAINTAINERS entry already, unless > you prefer to use a different one that is. :-) Yeah, that will remain the same. Thanks. -- viresh

[PATCH 1/2] ARM: dts: Fix I2C repeated start issue on Armada-38x

All the Armada 38x(380, 385, 388) have a silicon issue in the I2C controller which violates the I2C repeated start timing (errata FE-8471889). i2c-mv64xxx driver handles this errata based on the compatible string "marvell,mv78230-a0-i2c". This patch activates the "marvell,mv78230-a0-i2c" compatib

[PATCH 2/2] dt-bindings: i2c: Update documentation for "mv78230-a0-i2c"

This commit modifies the documentation for "marvell,mv78230-a0-i2c" compatible string. The "marvell,mv78230-a0-i2c" compatible string enables the workaround for an i2c repeated start timing violation, but unlike "marvell,mv78230-i2c" it disables the i2c offload support. This is applicable to a num

[PATCH v3 3/8] platform/x86: dell-wmi-smbios: Use Dell WMI descriptor check

The Dell WMI descriptor check is used as an indication that WMI calls are safe to run both when used with the notification ASL/GUID pair as well as the SMBIOS calling ASL/GUID pair. As some code in dell-wmi-smbios is already a prerequisite for dell-wmi, move the code for performing the descriptor

[PATCH 0/2] Fix I2C repeated start timing violation on Armada-38x.

All the Armada 38x(380, 385, 388) have a silicon issue in the I2C controller which violates the I2C repeated start timing (errata FE-8471889). Activate the compatible string "marvell,mv78230-a0-i2c" in the device tree file of Armada-38x to fx this errata (FE-8471889). Updated the Documentation fo

[PATCH v3 7/8] platform/x86: Kconfig: Change the default settings for dell-wmi-smbios

The dell-wmi-smbios driver should be enabled by default when ACPI_WMI is enabled (like many other WMI drivers). Signed-off-by: Mario Limonciello --- drivers/platform/x86/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig index

[PATCH v3 0/8] Introduce support for Dell SMBIOS over WMI

The existing way that the dell-smbios helper module and associated other drivers (dell-laptop, dell-wmi) communicate with the platform really isn't secure. It requires creating a buffer in physical DMA32 memory space and passing that to the platform via SMM. Since the platform got a physical memo

[PATCH v3 2/8] platform/x86: dell-smbios: Introduce a WMI-ACPI interface

The driver currently uses an SMI interface which grants direct access to physical memory to the firmware SMM methods via a pointer. Now add a WMI-ACPI interface that is detected by WMI probe and preferred over the SMI interface. Changing this to operate over WMI-ACPI will use an ACPI OperationReg

[PATCH v3 4/8] platform/x86: wmi: create character devices when requested by drivers

For WMI operations that are only Set or Query read or write sysfs attributes created by WMI vendor drivers make sense. For other WMI operations that are run on Method, there needs to be a way to guarantee to userspace that the results from the method call belong to the data request to the method c

[PATCH v3 8/8] platform/x86: dell-wmi-smbios: clean up wmi descriptor check

Some cases the wrong type was used for errors and checks can be done more cleanly. Signed-off-by: Mario Limonciello Reviewed-by: Edward O'Callaghan --- drivers/platform/x86/dell-smbios.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/platform/x86/dell-smb

[PATCH v3 6/8] platform/x86: dell-wmi-smbios: Add a sysfs interface for SMBIOS tokens

Currently userspace tools can access system tokens via the dcdbas kernel module and a SMI call that will cause the platform to execute SMM code. With a goal in mind of deprecating the dcdbas kernel module a different method for accessing these tokens from userspace needs to be created. This is in

[PATCH v3 5/8] platform/x86: dell-wmi-smbios: introduce character device for userspace

This userspace character device will be used to perform SMBIOS calls from any applications. It provides an ioctl that will allow passing the 32k WMI calling interface buffer between userspace and kernel space. This character device is intended to deprecate the dcdbas kernel module and the interfa

[PATCH v3 1/8] platform/x86: wmi: Add new method wmidev_evaluate_method

Drivers properly using the wmibus can pass their wmi_device pointer rather than the GUID back to the WMI bus to evaluate the proper methods. Any "new" drivers added that use the WMI bus should use this rather than the old wmi_evaluate_method that would take the GUID. Signed-off-by: Mario Limoncie

Re: [PATCH v2 14/17] phy: qcom-qusb2: Set vbus sw-override signal in device mode

Hi Jack, On 9/28/2017 12:46 AM, Jack Pham wrote: > On Wed, Sep 27, 2017 at 10:57:41AM -0700, Jack Pham wrote: >> Hi Manu, >> >> On Wed, Sep 27, 2017 at 02:29:10PM +0530, Manu Gautam wrote: >>> VBUS signal coming from PHY must be asserted in device for >>> controller to start operation or assert p

[PATCH v3 2/2] livepatch: add atomic replace

Sometimes we would like to revert a particular fix. This is currently not easy because we want to keep all other fixes active and we could revert only the last applied patch. One solution would be to apply new patch that implemented all the reverted functions like in the original code. It would wo

[PATCH v3 0/2] livepatch: introduce atomic replace

Hi, In testing livepatch, I found that when doing cumulative patches, if a patched function is completed reverted by a subsequent patch (back to its original state) livepatch does not revert the funtion to its original state. Specifically, if patch A introduces a change to function 1, and patch B

[PATCH v3 1/2] livepatch: Add dynamic klp_object and klp_func iterators

In preparation to introducing atomic replace, introduce iterators for klp_func and klp_object, such that objects and functions can be dynamically allocated (needed for atomic replace). This patch is intended to effectively be a no-op until atomic replace is introduced. Signed-off-by: Jason Baron

Re: ARM64: kernel panics in DABT in sys_msync path

On 9/27/2017 12:00 PM, Richard Ruigrok wrote: > > On 9/27/2017 9:50 AM, Will Deacon wrote: >> On Tue, Sep 26, 2017 at 06:31:12PM +0100, Will Deacon wrote: >>> On Tue, Sep 26, 2017 at 08:23:35AM -0600, Ruigrok, Richard wrote: On 9/26/2017 4:23 AM, Will Deacon wrote: > On Mon, Sep 25, 2017

[PATCH v2] bloat-o-meter: provide 3 different arguments for data, function and all

This patch provides 3 new arguments for bloat-o-meter: 1) -c -> for all (showing function and data differently). 2) -d -> data. 3) -t -> function. output:- ./scripts/bloat-o-meter -c "file1" "file2" add/remove: 0/0 grow/shrink: 0/1 up/down: 0/-152 (-152) Function

Re: [PATCH] irq/generic-chip: Fix memory leak of domain->name

Hi Thomas, Thanks for your review. On 09/27/2017 09:29 PM, Thomas Gleixner wrote: On Wed, 27 Sep 2017, Jeffy Chen wrote: Free domain->name when IRQ_DOMAIN_NAME_ALLOCATED been set. I can see that from the patch, but you fail to explain what the problem is. It's actually more than just a mem

Re: [PATCH] drm/rockchip: Fix memory leak in rockchip_drm_sys_resume()

Hi Sean, On 09/28/2017 04:27 AM, Sean Paul wrote: >@@ -299,6 +300,7 @@ static int rockchip_drm_sys_resume(struct device *dev) > >priv = drm->dev_private; >drm_atomic_helper_resume(drm, priv->state); >+ drm_atomic_state_put(priv->state); Won't this be freed for you eventually in commit

Re: [PATCH] mmc:host:sdhci-pci: Addition of Arasan PCI controller with integrated phy.

On 09/27/2017 02:27 PM, Atul Garg wrote: On Sep 26, 2017 8:55 PM, "Shawn Lin" > wrote: On 2017/9/27 2:59, Atul Garg wrote: [...] ---   drivers/mmc/host/sdhci-pci-core.c | 372 ++ Fundamental

Re: [alsa-devel] [PATCH] ASoC: Intel: Skylake: Fix jack name format substitution

On Mon, Sep 18, 2017 at 08:43:18AM -0700, Chintan Patel wrote: > Jack name is not getting formatted correctly hence resulting > in invalid name for HDMI/DP input devices. > > This was recently exposed due changes brought by MST: > commit 3a13347f05fd ("ASoC: Intel: kbl: Add jack port initialize >

RE: linux-4.14-rc2/drivers/acpi/acpica/utmath.c: 2 * suspicious expression ?

Hi, David Not a fancy way, but just a bit clearing. OK, style is changed here: https://github.com/acpica/acpica/pull/321 And bug is recorded here: https://bugs.acpica.org/show_bug.cgi?id=1422 Thanks for the report. Best regards Lv > From: David Binderman [mailto:dcb...@hotmail.com] > Subject: l

[PATCH] ARM: multi_v7_defconfig: Enable USB3503 driver

The Odroid U3 (Exynos 4412 based) for instance needs this driver, otherwise its USB hub will not come up. exynos_defconfig already has this enabled as built-in, too. So just doing the same here in multi_v7_defconfig. Signed-off-by: Linus Lüssing --- Thanks to Tobias Jakobi, who indirectly made

[RFC Resend][PATCH] ACPI / LPIT: Add LPIT table support

Added functionality to read LPIT table, which provides: - Sysfs interface to read residency counters via /sys/devices/system/cpu/cpuidle/low_power_idle_cpu_residency_us /sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us Here the count "low_power_idle_cpu_residency_us" shows the ti

[RFC][PATCH] ACPI / LPIT: Add LPIT table support

Added functionality to read LPIT table, which provides: - Sysfs interface to read residency counters via /sys/devices/system/cpu/cpuidle/low_power_idle_cpu_residency_us /sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us Here the count "low_power_idle_cpu_residency_us" shows the ti

Re: [GIT PULL] KEYS: Fixes and crypto fixes

On Wed, 27 Sep 2017, Eric Biggers wrote: > On Thu, Sep 28, 2017 at 09:14:58AM +1000, James Morris wrote: > > On Wed, 27 Sep 2017, David Howells wrote: > > > > > (2) Fixing big_key to use safe crypto from Jason A. Donenfeld. > > > > > > > I'm concerned about the lack of crypto review mentioned

[PATCH v4 01/11] dmaengine: sun6i: Correct setting of clock autogating register for A83T/H3

The H83T uses a compatible string different from the A23, but requires the same clock autogating register setting. The H3 also requires setting the clock autogating register, but has the register at a different offset. Add three suitable callbacks for the existing controller generations and set i

[PATCH v4 00/11] dmaengine: sun6i: Fixes for H3/A83T, enable A64

Commit 3a03ea763a67 ("dmaengine: sun6i: Add support for Allwinner A83T (sun8i) variant") and commit f008db8c00c1 ("dmaengine: sun6i: Add support for Allwinner H3 (sun8i) variant") added support for the A83T resp. H3, but missed some differences between the original A31 and A83T/H3. The first patch

[PATCH v4 03/11] dmaengine: sun6i: Restructure code to allow extension for new SoCs

The current code mixes three distinct operations when transforming the slave config to register settings: 1. special handling of DMA_SLAVE_BUSWIDTH_UNDEFINED, maxburst == 0 2. range checking 3. conversion of raw to register values As the range checks depend on the specific SoC, move these o

[PATCH v4 04/11] dmaengine: sun6i: Enable additional burst lengths/widths on H3

The H3 supports bursts lengths of 1, 4, 8 and 16 transfers, each with a width of 1, 2, 4 or 8 bytes. The register value for the the width is log2-encoded, change the conversion function to provide the correct value for width == 8. Signed-off-by: Stefan Brüns Acked-by: Maxime Ripard --- Change

[PATCH v4 07/11] dmaengine: sun6i: Retrieve channel count/max request from devicetree

To avoid introduction of a new compatible for each small SoC/DMA controller variation, move the definition of the channel count to the devicetree. The number of vchans is no longer explicit, but limited by the highest port/DMA request number. The result is a slight overallocation for SoCs with a s

[PATCH v4 02/11] dmaengine: sun6i: Correct burst length field offsets for H3

For the H3, the burst lengths field offsets in the channel configuration register differs from earlier SoC generations. Using the A31 register macros actually configured the H3 controller do to bursts of length 1 always, which although working leads to higher bus utilisation. Signed-off-by: Stefa

[PATCH v4 05/11] dmaengine: sun6i: Move number of pchans/vchans/request to device struct

Preparatory patch: If the same compatible is used for different SoCs which have a common register layout, but different number of channels, the channel count can no longer be stored in the config. Store it in the device structure instead. Signed-off-by: Stefan Brüns Acked-by: Maxime Ripard ---

[PATCH v4 11/11] arm: allwinner: Correct unit name in devicetree binding example

Unit-names must not start with a leading 0. Signed-off-by: Stefan Brüns --- Changes in v4: - Split minor fix in devicetree example from patch 6/10 Changes in v3: None Changes in v2: None Documentation/devicetree/bindings/dma/sun6i-dma.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH v4 09/11] arm64: allwinner: a64: Add device node for DMA controller

The A64 SoC has a DMA controller that supports 8 DMA channels to and from various peripherals. The last used DRQ port is 27. Add a device node for it. Signed-off-by: Stefan Brüns --- Changes in v4: None Changes in v3: - Drop leading 0 from dma controller unit name Changes in v2: None arch/a

Re: [PATCH] scsi: libsas: remove unused variable sas_ha

Colin, > Remove unused variable sas_ha to clean up build warning > "unused variable ‘sas_ha’ [-Wunused-variable]" Applied to 4.15/scsi-queue. Thanks! -- Martin K. Petersen Oracle Linux Engineering

[PATCH v4 10/11] arm64: allwinner: a64: add dma controller references to spi nodes

The spi controller nodes omit the dma controller/channel references, add it. This does not yet enable DMA for SPI transfers, as the spi-sun6i driver lacks support for DMA, but always uses PIO to the FIFO. Signed-off-by: Stefan Brüns --- Changes in v4: None Changes in v3: None Changes in v2: Non

[PATCH v4 06/11] arm64: allwinner: a64: Add devicetree binding for DMA controller

The A64 is register compatible with the H3, but has a different number of dma channels and request ports. Attach additional properties to the node to allow future reuse of the compatible for controllers with different number of channels/requests. If dma-requests is not specified, the register lay

[PATCH v4 08/11] dmaengine: sun6i: Add support for Allwinner A64 and compatibles

The A64 SoC has the same dma engine as the H3 (sun8i), with a reduced amount of physical channels. To allow future reuse of the compatible, leave the channel count etc. in the config data blank and retrieve it from the devicetree. Signed-off-by: Stefan Brüns Acked-by: Maxime Ripard --- Changes

Re: [PATCH] scsi: ufs: fix wrong command type of UTRD for UFSHCI v2.1

kehuanlin, > Since the command type of UTRD in UFS 2.1 specification is the same with > UFS 2.0. And it assumes the future UFS specification will follow the same > definition. Applied to 4.15/scsi-queue. Thanks! -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH] scsi: ufs: continue to boot even with Boot LUN is disabled

Huanlin, > Several configurable fields of the Device Descriptor and the Unit > Descriptors determine the Boot LUN status. The bBootEnable field and > the bBootLunEn attribute is set to zero by default, so the Boot LUN is > disabled by default. > > At which point the scsi device add for Boot LUN w

Re: [RFC][PATCH v2 0/7] printk/ia64/ppc64/parisc64: let's deprecate %pF/%pf printk specifiers

On (09/27/17 16:26), Michael Ellerman wrote: [..] > > Tested-by: Santosh Sivaraj > > Thanks Santosh. > > I also gave it a quick spin. I'll give you an ack for the powerpc changes. > > Acked-by: Michael Ellerman (powerpc) > > > Thanks for cleaning this up Sergey. thanks! -ss

Re: [PATCH] mm, swap: Make VMA based swap readahead configurable

Hi, Michal, Michal Hocko writes: > On Wed 27-09-17 23:10:08, Minchan Kim wrote: >> On Wed, Sep 27, 2017 at 03:50:34PM +0200, Michal Hocko wrote: >> > On Wed 27-09-17 22:41:17, Minchan Kim wrote: >> > > On Wed, Sep 27, 2017 at 03:22:41PM +0200, Michal Hocko wrote: >> > [...] >> > > > simply canno

  1   2   3   4   5   6   7   8   9   >