Greg,
> When calling debugfs code, there is no need to ever check the return
> value of the call, as no logic should ever change if a call works
> properly or not. Fix up a bunch of x86-specific code to not care
> about the results of debugfs.
Applied to 5.1/scsi-queue, thank you!
--
Martin
On 29-01-19, 10:25, Amit Kucheria wrote:
> All cpufreq drivers do similar things to register as a cooling device.
> Provide a cpufreq driver flag so drivers can just ask the cpufreq core
> to register the cooling device on their behalf. This allows us to get
> rid of duplicated code in the
The implementation is broken in all the ways the unit test did not touch:
1/ The local definition of in_buf and in_obj violated C99 initializer
expectations for zeroing. By only initializing 2 out of the three
struct members the compiler was free to zero-initialize the remaining
entry
Johannes,
> I'll be moving on to different things in the storage stack and Hannes
> agreed to take over FCoE.
Applied to 5.1/scsi-queue. Thanks.
--
Martin K. Petersen Oracle Linux Engineering
On 28-01-19, 16:55, Quentin Perret wrote:
> Now that PM_OPP provides a helper function to estimate the power
> consumed by CPUs, make sure to try and register an Energy Model (EM)
> from scpi-cpufreq, hence ensuring interested subsystems (the task
> scheduler, for example) can make use of that
On 28-01-19, 16:55, Quentin Perret wrote:
> Now that PM_OPP provides a helper function to estimate the power
> consumed by CPUs, make sure to try and register an Energy Model (EM)
> from cpufreq-dt, hence ensuring interested subsystems (the task
> scheduler, for example) can make use of that
Greg,
> There's no need to export fcoe_ctlr_destroy_store as a symbol, so remove
> the EXPORT_SYMBOL() line for it.
Applied to 5.1/scsi-queue, thank you!
--
Martin K. Petersen Oracle Linux Engineering
Greg,
> We are trying to get rid of BUS_ATTR() and the usage of that in the
> fcoe driver can be trivially converted to use BUS_ATTR_WO(), so use
> that instead.
Applied to 5.1/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
On Mon, Jan 28, 2019 at 11:38:42PM +0100, Thomas Gleixner wrote:
> The original MODULE_LICENSE string for kernel modules licensed under the
> GPL v2 (only / or later) was simply "GPL", which was - and still is -
> completely sufficient for the purpose of module loading and checking
> whether the
On Mon, Dec 24, 2018 at 11:52 AM Gustavo A. R. Silva
wrote:
>
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
> struct foo {
>
On Fri, Jan 25, 2019 at 10:08 PM Borislav Petkov wrote:
>
> On Fri, Jan 25, 2019 at 09:45:18PM +0800, Dave Young wrote:
> > AFAIK, some people prefer to explictly reserve crash memory at high
> > region even if it is possible to reserve at low area. May because
> > <4G memory is limited on large
Signed-off-by: saumah
---
8250_pci.c | 162 +
1 file changed, 2 insertions(+), 160 deletions(-)
diff --git a/8250_pci.c b/8250_pci.c
index f80a300..310b1eb 100644
--- a/8250_pci.c
+++ b/8250_pci.c
@@ -519,115 +519,6 @@ static int
On 28-01-19, 11:36, Matthias Kaehlcke wrote:
> I think this patch will result in error messages at registration on
> platforms that use the cpufreq-dt driver and don't specify
> 'dynamic-power-coefficient' for the CPUs in the DT. Not sure if that's
> a problem as long as the cpufreq initialization
Hi all,
After merging the net-next tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/net/ethernet/freescale/enetc/enetc.c: In function 'enetc_alloc_txbdr':
drivers/net/ethernet/freescale/enetc/enetc.c:685:17: error: implicit
declaration of function 'vzalloc'; did
Signed-off-by: saumah
---
8250_pci.c | 162 +
1 file changed, 2 insertions(+), 160 deletions(-)
diff --git a/8250_pci.c b/8250_pci.c
index f80a300..310b1eb 100644
--- a/8250_pci.c
+++ b/8250_pci.c
@@ -519,115 +519,6 @@ static int
Hi all,
Friendly ping:
Who can take this?
Thanks
--
Gustavo
On 1/9/19 11:38 AM, Gustavo A. R. Silva wrote:
> Hi,
>
> Friendly ping:
>
> Who can ack or review this patch, please?
>
> Thanks
> --
> Gustavo
>
>
> On 12/24/18 12:22 AM, Gustavo A. R. Silva wrote:
>> One of the more common
On 28-01-19, 16:55, Quentin Perret wrote:
> diff --git a/drivers/opp/of.c b/drivers/opp/of.c
> index 06f0f632ec47..7572a2eb2fd4 100644
> --- a/drivers/opp/of.c
> +++ b/drivers/opp/of.c
> @@ -1047,3 +1047,63 @@ struct device_node *dev_pm_opp_get_of_node(struct
> dev_pm_opp *opp)
> return
The EnOcean Serial Protocol 2 used subtelegram frames different from ESP3.
It also uses ORG identifiers differing from RORG identifiers in ERP.
Only checksumming has been tested.
Signed-off-by: Andreas Färber
---
drivers/net/enocean/Makefile | 1 +
drivers/net/enocean/enocean_esp.c |
Add net_device helpers for EnOcean.
Signed-off-by: Andreas Färber
---
drivers/net/enocean/Makefile | 2 +
drivers/net/enocean/enocean.c | 124 ++
include/linux/enocean/dev.h | 23
3 files changed, 149 insertions(+)
create mode 100644
Hello,
This series implements a serdev driver for the EnOcean Serial Protocol (ESP).
It follows previous weekend's Z-Wave serdev driver [1], exploring various
wireless technologies surrounding LoRa/FSK/OOK in quest of a solid PHY layer.
The EnOcean Radio Protocol 1 (ERP1) is based on ASK; ERP2
EnOcean wireless technology is based on ASK (ERP1) and FSK (ERP2) modulations
for sub-GHz and on IEEE 802.15.4 for 2.4 GHz.
ARPHRD_ENOCEAN
ETH_P_ERP{1,2}
Signed-off-by: Andreas Färber
---
include/uapi/linux/if_arp.h | 1 +
include/uapi/linux/if_ether.h | 2 ++
2 files changed, 3
This implements the EnOcean Serial Protocol 3.
Rudimentary sending is prepared. Error handling is lacking and
reception handling is missing.
Tested with EnOcean TCM310 gateway module.
Signed-off-by: Andreas Färber
---
drivers/net/enocean/Makefile | 4 +
On Mon, Jan 28, 2019 at 2:35 PM Dmitry Voytik wrote:
>
> How to reproduce the problem:
> $ make tinyconfig
> $ make menuconfig
> then enable:
> CONFIG_COMPILE_TEST=y
> CONFIG_PINCTRL=y
> and any of these:
> CONFIG_PINCTRL_MT7622=y
> CONFIG_PINCTRL_MT7629=y
> CONFIG_PINCTRL_MT7623=y
>
> This
Use the CPUFREQ_IS_COOLING_DEV flag to allow cpufreq core to
automatically register as a thermal cooling device.
This allows removal of boiler plate code from the driver.
Signed-off-by: Amit Kucheria
Acked-by: Viresh Kumar
Reviewed-by: Daniel Lezcano
---
drivers/cpufreq/mediatek-cpufreq.c |
Use the CPUFREQ_IS_COOLING_DEV flag to allow cpufreq core to
automatically register as a thermal cooling device.
This allows removal of boiler plate code from the driver.
Signed-off-by: Amit Kucheria
Acked-by: Sudeep Holla
Acked-by: Viresh Kumar
Reviewed-by: Daniel Lezcano
---
Use the CPUFREQ_IS_COOLING_DEV flag to allow cpufreq core to
automatically register as a thermal cooling device.
This allows removal of boiler plate code from the driver.
Signed-off-by: Amit Kucheria
Acked-by: Sudeep Holla
Acked-by: Viresh Kumar
Reviewed-by: Daniel Lezcano
---
Use the CPUFREQ_IS_COOLING_DEV flag to allow cpufreq core to
automatically register as a thermal cooling device.
This allows removal of boiler plate code from the driver.
Signed-off-by: Amit Kucheria
Acked-by: Viresh Kumar
Reviewed-by: Daniel Lezcano
---
drivers/cpufreq/qoriq-cpufreq.c | 15
Use the CPUFREQ_IS_COOLING_DEV flag to allow cpufreq core to
automatically register as a thermal cooling device.
This allows removal of boiler plate code from the driver.
Signed-off-by: Amit Kucheria
Acked-by: Viresh Kumar
Reviewed-by: Daniel Lezcano
---
drivers/cpufreq/cpufreq-dt.c | 14
Use the CPUFREQ_IS_COOLING_DEV flag to allow cpufreq core to
automatically register as a thermal cooling device.
This allows removal of boiler plate code from the driver.
Signed-off-by: Amit Kucheria
Acked-by: Viresh Kumar
Reviewed-by: Daniel Lezcano
---
drivers/cpufreq/imx6q-cpufreq.c | 24
Add the CPUFREQ_IS_COOLING_DEV flag to allow the cpufreq core to
auto-register the driver as a cooling device.
Signed-off-by: Amit Kucheria
Reviewed-by: Matthias Kaehlcke
Tested-by: Matthias Kaehlcke
Reviewed-by: Stephen Boyd
Acked-by: Viresh Kumar
Reviewed-by: Daniel Lezcano
---
The CPU cooling driver (cpu_cooling.c) allows the platform's cpufreq
driver to register as a cooling device and cool down the platform by
throttling the CPU frequency. In order to be able to auto-register a
cpufreq driver as a cooling device from the cpufreq core, we need access
to code inside
All cpufreq drivers do similar things to register as a cooling device.
Provide a cpufreq driver flag so drivers can just ask the cpufreq core
to register the cooling device on their behalf. This allows us to get
rid of duplicated code in the drivers.
In order to allow this, we add a struct
Add a flag for cpufreq drivers to tell cpufreq core to auto-register
themselves as a thermal cooling device.
There series converts over all the drivers except arm_big_little.c.
Tested on SDM845 with the qcom-cpufreq-hw driver. Only compile-tested the
others.
Things needing fixing (but not a
On Mon, Jan 28, 2019 at 04:31:40PM -0700, Jason Gunthorpe wrote:
> On Mon, Jan 21, 2019 at 09:42:17AM -0800, Davidlohr Bueso wrote:
> > The driver uses mmap_sem for both pinned_vm accounting and
> > get_user_pages(). By using gup_fast() and letting the mm handle
> > the lock if needed, we can no
On 1/29/19 3:26 AM, masonccy...@mxic.com.tw wrote:
> Hi Marek,
Hi,
>> >> "Marek Vasut"
>> >> >> >> > +module_platform_driver(rpc_spi_driver);
>> >> >> >>
>> >> >> >> RPC is not a SPI controller, it's a SPI and HF controller.
>> >> >> >>
>> >> >> >> Also, how difficult will it be to add the HF
Hi Doug,
On 2019-01-29 00:54, Doug Anderson wrote:
Hi,
You can probably stop sending this one. It's in Andy's tree now. See
commit ea0edd7e63f4 ("arm64: dts: qcom: sdm845: Remove the duplicate
header inclusion").
Sorry, missed this one.
This updates bindings for MT7629 SoC, which includes very basic items
such as system timer, UART, sysirq and scpsys unit.
Signed-off-by: Ryder Lee
---
.../devicetree/bindings/interrupt-controller/mediatek,sysirq.txt | 5 +++--
Documentation/devicetree/bindings/serial/mtk-uart.txt
Add support for booting secondary CPUs on MT7629.
Signed-off-by: Ryder Lee
---
arch/arm/mach-mediatek/Kconfig| 4
arch/arm/mach-mediatek/mediatek.c | 1 +
arch/arm/mach-mediatek/platsmp.c | 1 +
3 files changed, 6 insertions(+)
diff --git a/arch/arm/mach-mediatek/Kconfig
This adds basic support for MT7629 reference board.
Signed-off-by: Ryder Lee
---
The I2C node depends on https://patchwork.kernel.org/patch/10772837/
The PCIe node depends on https://patchwork.kernel.org/patch/10773637/
---
arch/arm/boot/dts/Makefile| 1 +
Update binding document for MT7622 BPI-R64 and MT7629 reference board.
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/arm/mediatek.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/mediatek.txt
This adds missing bindings for MT7623 sysirq.
Signed-off-by: Ryder Lee
---
.../devicetree/bindings/interrupt-controller/mediatek,sysirq.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
a/Documentation/devicetree/bindings/interrupt-controller/mediatek,sysirq.txt
As we fallback to use "mediatek,mt7623" for MT7623a, remove unused
root node property "mediatek,mt7623a" in the document.
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/arm/mediatek.txt | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
This reverts commit 3b99ab7deca1e5f4229b4bdecd005d71e22cfc60.
The compatible "mediatek,mt7623a" is useless, so remove it.
Signed-off-by: Ryder Lee
---
arch/arm/mach-mediatek/mediatek.c | 2 --
arch/arm/mach-mediatek/platsmp.c | 1 -
2 files changed, 3 deletions(-)
diff --git
On Mon, Jan 28, 2019 at 5:34 PM Rafael J. Wysocki wrote:
>
> On Monday, January 28, 2019 9:32:44 AM CET Daniel Lezcano wrote:
> > On 28/01/2019 07:41, Amit Kucheria wrote:
> > > All cpufreq drivers do similar things to register as a cooling device.
> > > Provide a cpufreq driver flag so drivers
I would prefer to keep it. There are many other drivers that also use
this header file.
On 2019年01月29日 03:22, Joe Perches wrote:
On Fri, 2019-01-25 at 14:59 -0300, Paul Cercueil wrote:
On Fri, Jan 25, 2019 at 6:59 AM, Zhou Yanjie
wrote:
Warning is reported when checkpatch indicates that
Over the years, the function signature has changed, the kerneldoc block hasn't.
Signed-off-by: Valdis Kletnieks
diff --git a/kernel/bpf/core.c b/kernel/bpf/core.c
index 2a81b8af3748..2728b6247091 100644
--- a/kernel/bpf/core.c
+++ b/kernel/bpf/core.c
@@ -1216,8 +1216,9 @@ bool
Patch (b6c7a324df37b "MIPS: Fix get_frame_info() handling of
microMIPS function size.") introduces additional function size
check for microMIPS by only checking insn between ip and ip + func_size.
However, func_size in get_frame_info() is always 0 if KALLSYMS is not
enabled. This causes
OK, thanks for your suggestions. I'll drop this patch.
On 2019年01月29日 04:48, Paul Cercueil wrote:
Hi,
Hello,
This seems like a useless renaming to me, can you elaborate a bit more?
I'd also like to have Paul and Lars-Peter comment.
According to the patchset, the RTC in the X1000 does not
On Mon, 2019-01-28 at 17:41 -0800, David Rientjes wrote:
> On Thu, 24 Jan 2019, miles.c...@mediatek.com wrote:
>
> > From: Miles Chen
> >
> > When debugging slab errors in slub.c, sometimes we have to trigger
> > a panic in order to get the coredump file. Add a debug option
> >
On Tue, Jan 29, 2019 at 10:18:40AM +0800, Wei Hu (Xavier) wrote:
>
>
> On 2019/1/29 2:27, Jason Gunthorpe wrote:
> > On Sat, Jan 26, 2019 at 09:47:42AM +0800, Wei Hu (Xavier) wrote:
> >>
> >> On 2019/1/26 5:50, Jason Gunthorpe wrote:
> >>> On Fri, Jan 25, 2019 at 10:15:40AM +0800, Wei Hu
On 28/01/19 10:04 PM, Tony Lindgren wrote:
> Hi,
>
> * Randy Dunlap [190126 06:54]:
>> Hi,
>>
>> FYI, I'm seeing this Kconfig warning in 5.0-rc3:
>
> Thanks for reporting it.
>
>> WARNING: unmet direct dependencies detected for TI_SOC_THERMAL
>> Depends on [n]: THERMAL [=y] &&
On Fri, Jan 25, 2019 at 07:02:37PM +0100, Paolo Bonzini wrote:
> On 22/01/19 21:59, Yang Weijiang wrote:
> > On processors that support CET, VMX saves/restores
> > the states of IA32_S_CET, SSP and IA32_INTERRUPT_SSP_TABLE_ADDR MSR
> > to the VMCS area for Guest/Host unconditionally.
> >
> > If
On 1/28/19 11:09 PM, Thierry Reding wrote:
On Mon, Jan 28, 2019 at 05:18:11PM +0800, Joseph Lo wrote:
Add support for the Tegra210 timer that runs at oscillator clock
(TMR10-TMR13). We need these timers to work as clock event device and to
replace the ARMv8 architected timer due to it can't
On 2019/1/28 22:36, Andrew Lunn wrote:
> On Mon, Jan 28, 2019 at 09:24:09PM +0800, YueHaibing wrote:
>> Fix coccinelle warning:
>>
>> ./drivers/net/phy/mdio_bus.c:51:5-12: ERROR: PTR_ERR applied after
>> initialization to constant on line 44
>> ./drivers/net/phy/mdio_bus.c:52:5-12: ERROR:
Use struct_size() in kzalloc instead of the 'regd_to_copy'
Signed-off-by: YueHaibing
---
drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c
v2: Use struct_size in regd allocation
YueHaibing (2):
iwlwifi: Use kmemdup instead of duplicating its function
iwlwifi: Use struct_size() in kzalloc
drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c | 19 ---
1 file changed, 4 insertions(+), 15 deletions(-)
--
2.7.4
Use kmemdup rather than duplicating its implementation
Signed-off-by: YueHaibing
---
drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c
On 2019/1/29 5:57, Joe Perches wrote:
> On Mon, 2019-01-28 at 14:44 +0800, YueHaibing wrote:
>> Use struct_size() in kzalloc instead of the 'regd_to_copy'
>
> There is also the use above that in the same function
> that could also be converted.
>
> /* build a regdomain rule for every
On Mon, Jan 28, 2019 at 3:35 PM wrote:
>
> On Mon, 28 Jan 2019 09:18:45 -0800, Song Liu said:
> > On Sun, Jan 27, 2019 at 8:43 PM wrote:
>
> > > The attached patch silences the warnings, because we *know* we're
> > > overwriting
> > > the default initializer. That leaves bpf/core.c with only 6
29.01.2019 5:02, Sowjanya Komatineni пишет:
>
>
This patch adds DMA support for Tegra I2C.
Tegra I2C TX and RX FIFO depth is 8 words. PIO mode is used for
transfer size of the max FIFO depth and DMA mode is used for
transfer size higher than max FIFO depth to save CPU
Hi all,
Today's linux-next merge of the char-misc tree got a conflict in:
arch/arm64/boot/dts/qcom/sdm845.dtsi
between commits:
05556681948b ("arm64: dts: sdm845: Add videocc node")
5b6f186f0abb ("arm64: dts: sdm845: Add rpmh powercontroller node")
from the qcom tree and commit:
Hi Daniel,
Thanks for your review.
On 1/28/19 9:00 PM, Daniel Lezcano wrote:
On 28/01/2019 10:18, Joseph Lo wrote:
Add support for the Tegra210 timer that runs at oscillator clock
(TMR10-TMR13). We need these timers to work as clock event device and to
replace the ARMv8 architected timer due
Hi,
Please hold until Steven returned from Linux Conf Au. Thanks!
On Tue, Jan 29, 2019 at 12:35:20AM +, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the
Dt-bindings doc about Loongson-1 interrupt controller.
Signed-off-by: Jiaxun Yang
---
.../loongson,ls1x-intc.txt| 24 +++
1 file changed, 24 insertions(+)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/loongson,ls1x-intc.txt
diff
v1->v2: Fix SPDX-License-Identifier
v2->v3: Rework according suggestions from Marc Zyngier, Thanks.
v3->v4: Rework the driver into a single chip driver.
v4->v5: Fix minor issues.
This controller appeared on Loongson-1 family MCUs
including Loongson-1B and Loongson-1C.
Signed-off-by: Jiaxun Yang
---
drivers/irqchip/Kconfig| 9 ++
drivers/irqchip/Makefile | 1 +
drivers/irqchip/irq-ls1x.c | 192 +
3 files changed, 202
With current n_voltages setting, regulator_list_voltage will return
-EINVAL when selector >=57. The highest selector is 0x41, so the
n_voltages should be 0x41+1, i.e. 66.
Signed-off-by: Axel Lin
---
drivers/regulator/lochnagar-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/firewire/net.c:488:9:
warning: variable 'guid' set but not used [-Wunused-but-set-variable]
It not used since commit 6752c8db8e0c ("firewire net, ipv4 arp:
Extend hardware address and remove driver-level packet inspection.")
Signed-off-by:
On 2019/1/27 上午8:31, Michael S. Tsirkin wrote:
On Sat, Jan 26, 2019 at 02:37:08PM -0800, David Miller wrote:
From: Jason Wang
Date: Wed, 23 Jan 2019 17:55:52 +0800
This series tries to access virtqueue metadata through kernel virtual
address instead of copy_user() friends since they had
On 2019/1/29 2:27, Jason Gunthorpe wrote:
> On Sat, Jan 26, 2019 at 09:47:42AM +0800, Wei Hu (Xavier) wrote:
>>
>> On 2019/1/26 5:50, Jason Gunthorpe wrote:
>>> On Fri, Jan 25, 2019 at 10:15:40AM +0800, Wei Hu (Xavier) wrote:
On 2019/1/25 2:31, Jason Gunthorpe wrote:
> On Thu, Jan 24,
From: Srivatsa S. Bhat (VMware)
To disable a tracing option using the trace_options file, the option
name needs to be prefixed with 'no', and not suffixed, as the README
states. Fix it.
Signed-off-by: Srivatsa S. Bhat (VMware)
---
kernel/trace/trace.c |2 +-
1 file changed, 1
> > > This patch adds DMA support for Tegra I2C.
> > >
> > > Tegra I2C TX and RX FIFO depth is 8 words. PIO mode is used for
> > > transfer size of the max FIFO depth and DMA mode is used for
> > > transfer size higher than max FIFO depth to save CPU overhead.
> > >
> > > PIO mode needs full
Hi all,
After merging the spi tree, today's linux-next build (KCONFIG_NAME)
produced this warning:
WARNING: modpost: missing MODULE_LICENSE() in drivers/spi/spi-nxp-fspi.o
see include/linux/module.h for more information
Introduced by commit
a5356aef6a90 ("spi: spi-mem: Add driver for NXP
Hi Jonathan,
Thanks for showing the gap on tracking hot accesses from devices.
On Mon, Jan 28, 2019 at 05:42:39PM +, Jonathan Cameron wrote:
On Wed, 2 Jan 2019 12:21:10 +
Jonathan Cameron wrote:
On Fri, 28 Dec 2018 20:52:24 +0100
Michal Hocko wrote:
> [Ccing Mel and Andrea]
>
From: Rajendra Nayak
For devices with performance state, we use dev_pm_opp_set_rate()
to set the appropriate clk rate and the performance state.
We do need a way to *remove* the performance state vote when
we idle the device and turn the clocks off. Use dev_pm_opp_set_rate()
with freq=0 to
From: Rajendra Nayak
geni spi needs to express a perforamnce state requirement on CX
depending on the frequency of the clock rates. Use OPP table from
DT to register with OPP framework and use dev_pm_opp_set_rate() to
set the clk/perf state.
Signed-off-by: Rajendra Nayak
Signed-off-by: Stephen
From: Rajendra Nayak
geni serial needs to express a perforamnce state requirement on CX
depending on the frequency of the clock rates. Use OPP table from
DT to register with OPP framework and use dev_pm_opp_set_rate() to
set the clk/perf state.
Signed-off-by: Rajendra Nayak
Signed-off-by:
Doing this allows us to call this API with any rate requested and have
it not need to match in the OPP table. Instead, we'll round the rate up
to the nearest OPP that we see so that we can get the voltage or level
that's required for that OPP. This supports users of OPP that want to
specify the
From: Rajendra Nayak
qup has a requirement to vote on the performance state of the CX domain
in sdm845 devices. Add OPP tables for these and also add power-domains
property for all qup instances.
Signed-off-by: Rajendra Nayak
Signed-off-by: Stephen Boyd
---
This patch series is an RFC around how we can implement DVFS for devices
that aren't your typical OPPish device (i.e. GPU/CPU). They don't have a
strict set of frequencies that they have been tested at to derive some
operating performance point. Instead they have a coarser set of
frequency max or
On Mon, Jan 28, 2019 at 3:54 PM Minchan Kim wrote:
>
> Hi Suren,
>
> When I review first time, it was rather hard to understand due to naming
> so below comments are mostly cleanup or minor.
> I'm not strong against if you don't think it's helpful.
> Feel free to select parts.
>
> Thanks.
Thanks
Hi Alexander,
Thanks for the review.
On Mon, Jan 28, 2019 at 08:31:11AM -0800, Alexander Duyck wrote:
> On Mon, 2019-01-28 at 09:20 +0800, Feng Tang wrote:
> > Asynchronous driver probing can help much on kernel fastboot, and
> > this option can provide a flexible way to optimize and quickly
On Thu, 24 Jan 2019, miles.c...@mediatek.com wrote:
> From: Miles Chen
>
> When debugging slab errors in slub.c, sometimes we have to trigger
> a panic in order to get the coredump file. Add a debug option
> SLAB_WARN_ON_ERROR to toggle WARN_ON() when the option is set.
>
Wouldn't it be
Dave Hansen writes:
> On 1/25/19 1:18 PM, Bjorn Helgaas wrote:
>> On Thu, Jan 24, 2019 at 5:21 PM Dave Hansen
>> wrote:
>>> diff -puN kernel/resource.c~move-request_region-check kernel/resource.c
>>> --- a/kernel/resource.c~move-request_region-check 2019-01-24
>>> 15:13:14.453199539
Dear all,
Gently Ping.
Best Regards,
Chanwoo Choi
On 18. 12. 12. 오전 10:41, Chanwoo Choi wrote:
> The Samsung Exynos's device drivers have the 'SASMUNG EXYNOS' prefix
> in front of the specific device driver name. In order to keep the
> consistent naming format, change the entry name of bus
Hi Marc,
Any comments?
Thanks,
Heyi
On 2019/1/24 21:37, Heyi Guo wrote:
1. In current implementation, every VLPI will temporarily be mapped to
the first CPU in system (normally CPU0) and then moved to the real
scheduled CPU later.
2. So there is a time window and a VLPI may be sent to CPU0
On Mon, 2019-01-28 at 23:38 +0100, Thomas Gleixner wrote:
> Therefore remove the well meant, but ill defined, distinction between "GPL"
> and "GPL v2" and document that:
>
> - "GPL" and "GPL v2" both express that the module is licensed under GPLv2
> (without a distinction of 'only' and 'or
On Fri, 18 Jan 2019 14:11:30 +0100 Jürg Billeter wrote:
> This introduces a new thread group flag that can be set by calling
>
> prctl(PR_SET_KILL_DESCENDANTS_ON_EXIT, 1, 0, 0, 0)
>
> When a thread group exits with this flag set, it will send SIGKILL to
> all descendant processes. This
On Mon, Jan 28, 2019 at 04:22:16PM -0800, John Hubbard wrote:
> On 1/23/19 11:04 AM, Jerome Glisse wrote:
> > On Wed, Jan 23, 2019 at 07:02:30PM +0100, Jan Kara wrote:
> >> On Tue 22-01-19 11:46:13, Jerome Glisse wrote:
> >>> On Tue, Jan 22, 2019 at 04:24:59PM +0100, Jan Kara wrote:
> On Thu
On 2019/1/23 21:08, Zhou Wang wrote:
> This series adds HiSilicon QM and ZIP controller driver in crypto subsystem.
>
> A simple QM/ZIP driver which helps to provide an example for a general
> accelerator framework is under review in community[1]. Based on this simple
> driver, this series adds
Dave Hansen writes:
> On 1/25/19 1:02 PM, Bjorn Helgaas wrote:
>>> @@ -453,7 +453,7 @@ int walk_system_ram_range(unsigned long
>>> unsigned long flags;
>>> struct resource res;
>>> unsigned long pfn, end_pfn;
>>> - int ret = -1;
>>> + int ret = -EINVAL;
>> Can
Since there are multiple possible failures in iommu_map_page
it would be useful to know which case is being hit when the
error message is printed in map_sg. While here, fix up checkpatch
complaint about using function name in a string instead of
__func__.
Cc: Joerg Roedel
Signed-off-by: Jerry
Add the Hyper-V _DSM command set to the white list of NVDIMM command
sets.
This command set is documented at http://www.uefi.org/RFIC_LIST
(see "Virtual NVDIMM 0x1901").
Thanks Dan Williams for writing the
comment change.
Signed-off-by: Dexuan Cui
Reviewed-by: Michael Kelley
---
Changes
Hi Lukasz,
This patchset don't contain the cover-letter. Please send the
cover-letter which explains what to do on this patchset.
And is it supporting all Exynos5 for both 32bit(5420,5422)
and 64bit(5433) or only Exynos542x(32bit)? If it only support
the Exynos 542x series, you have to change
Remove the kernel's vm_area and the code that maps
buffer pages into it.
Signed-off-by: Todd Kjos
---
drivers/android/binder_alloc.c | 40 ++
1 file changed, 2 insertions(+), 38 deletions(-)
diff --git a/drivers/android/binder_alloc.c
Refactor the functions to validate and fixup struct
binder_buffer pointer objects to avoid using vm_area
pointers. Instead copy to/from kernel space using
binder_alloc_copy_to_buffer() and
binder_alloc_copy_from_buffer(). The following
functions were refactored:
binder_validate_ptr()
Remove user_buffer_offset since there is no kernel
buffer pointer anymore.
Signed-off-by: Todd Kjos
---
drivers/android/binder.c | 38 +++---
drivers/android/binder_alloc.c | 16 ++
drivers/android/binder_alloc.h | 23
3 files
When creating or tearing down a transaction, the binder driver
examines objects in the buffer and takes appropriate action.
To do this without needing to dereference pointers into the
buffer, the local copies of the objects are needed. This patch
introduces a function to validate and copy binder
Now that alloc->buffer points to the userspace vm_area
rename buffer->data to buffer->user_data and rename
local pointers that hold user addresses. Also use the
"__user" tag to annotate all user pointers so sparse
can flag cases where user pointer vaues are copied to
kernel pointers. Refactor
The binder driver uses a vm_area to map the per-process
binder buffer space. For 32-bit android devices, this is
now taking too much vmalloc space. This patch removes
the use of vm_area when copying the transaction data
from the sender to the buffer space. Instead of using
copy_from_user() for
101 - 200 of 2154 matches
Mail list logo
