Presently, when support for a new SoC is added, the driver ops
structures and functions are versioned with plain 1, 2, 3 etc.
Instead use the block IP version number.
Signed-off-by: Varadarajan Narayanan
---
drivers/pci/dwc/pcie-qcom.c | 124 ++--
1 file c
Add support for the IPQ8074 PCIe controller. IPQ8074 supports
Gen 1/2, one lane, two PCIe root complex with support for MSI and
legacy interrupts, and it conforms to PCI Express Base 2.1
specification.
The core init is the similar to the existing SoC, however the
clocks and reset lines differ.
S
Presently, the phy pipe clock's name is assumed to be either
usb3_phy_pipe_clk_src or pcie_XX_pipe_clk_src (where XX is the
phy lane's number). However, this will not work if an SoC has
more than one instance of the phy. Hence, instead of assuming
the name of the clock, fetch it from the DT.
Signe
Add support for the IPQ8074 PCIe controller. IPQ8074 supports Gen 1/2, one
lane, two PCIe root complex with support for MSI and legacy interrupts, and
it conforms to PCI Express Base 2.1 specification.
Signed-off-by: Varadarajan Narayanan
---
.../devicetree/bindings/pci/qcom,pcie.txt |
Add definitions required to enable QMP phy support for IPQ8074.
Signed-off-by: smuthayy
Signed-off-by: Varadarajan Narayanan
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 124
1 file changed, 124 insertions(+)
diff --git a/drivers/phy/qualcomm/phy-qcom-qmp.c
b
IPQ8074 uses QMP phy controller that provides support to PCIe and
USB. Adding dt binding information for the same.
Signed-off-by: Varadarajan Narayanan
---
Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt | 8
1 file changed, 8 insertions(+)
diff --git a/Documentation/devicetree/
v4:
phy: qcom-qmp: Fix phy pipe clock name
Based on Vivek's comments, return failure only for
PCI/USB type of phys.
Removed Ack.
phy: qcom-qmp: Handle unavailable registers
Removed this patch.
Incorrectly used a block of code that is not applicable
On Thu, 13 Jul 2017, Borislav Petkov wrote:
> On Wed, Jul 12, 2017 at 10:27:44PM -0400, Mikulas Patocka wrote:
> > It is not strictly needed, but it is annoying. I work in the console and
> > it is annoying to see these "unhandled rdmsr" messages printed over the
> > screen every time I reboot
Hi Ted,
Snipping one comment:
> Practically no one uses /dev/random. It's essentially a deprecated
> interface; the primary interfaces that have been recommended for well
> over a decade is /dev/urandom, and now, getrandom(2). We only need
> 384 bits of randomness every 5 minutes to reseed the
Hi Pavel,
>>> Is bluetooth expected to work on n900?
>>>
>>> It looks like lock init is missing somewhere:
>>>
>>> [ 402.901031] of_get_named_gpiod_flags: parsed
>>> 'bluetooth-wakeup-gpios' property of node
>>> '/ocp@6800/serial@4806c000/bluetooth[0]' - status (0)
>>> [ 403.042022] BUG: r
Em Fri, Jul 21, 2017 at 06:41:29PM +0900, Taeung Song escreveu:
> On 07/21/2017 04:19 AM, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Jul 20, 2017 at 06:36:55AM +0900, Taeung Song escreveu:
> > > Currently the --show-total-period option of perf-annotate
> > > is different from perf-report's.
> > >
Add a thermal driver for on-chip PVT (Process, Voltage and Temperature)
monitoring unit implemented on UniPhier SoCs. This driver supports
temperature monitoring and alert function.
Signed-off-by: Kunihiko Hayashi
---
drivers/thermal/Kconfig| 8 +
drivers/thermal/Makefile
Add devicetree binding documentation for thermal monitor implemented on
Socionext UniPhier SoCs.
Signed-off-by: Kunihiko Hayashi
Acked-by: Rob Herring
---
.../bindings/thermal/uniphier-thermal.txt | 64 ++
1 file changed, 64 insertions(+)
create mode 100644
Docume
This series adds support for CPU temperature monitor modules implemented
on UniPhier LD20 and PXs2 SoCs. This driver supports temperature monitoring
and alert function on the module.
Changes in v4:
- fix warnings from sparse by replacing u32 with __be32
Changes in v3:
- remove TMOD_MASK and use T
On Fri 2017-07-21 12:48:11, Enric Balletbo i Serra wrote:
> Some panels (i.e. N116BGE-L41), in their power sequence specifications,
> request a delay between set the PWM signal and enable the backlight and
> between clear the PWM signal and disable the backlight. Add support for
> the new post-pwm-
On 21/07/17 11:06, Hanjun Guo wrote:
> On 2017/7/21 17:51, Hanjun Guo wrote:
>> From: Hanjun Guo
>>
>> When running 4.13-rc1 on top of D05, I got the boot log:
>>
>> [0.00] SRAT: PXM 0 -> ITS 0 -> Node 0
>> [0.00] SRAT: PXM 0 -> ITS 1 -> Node 0
>> [0.00] SRAT: PXM 0 -> ITS
This patch fixes values of the EPLL K coefficient and changes
the EPLL output frequency values to match exactly what is
possible to achieve with given M, P, S, K coefficients.
This allows to avoid rounding errors and unexpected frequency
being set with clk_set_rate(), due to recalc_rate returning
d
Signed-off-by: Joseph Chen
---
drivers/mfd/rk808.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mfd/rk808.c b/drivers/mfd/rk808.c
index 7276555..db90471 100644
--- a/drivers/mfd/rk808.c
+++ b/drivers/mfd/rk808.c
@@ -97,6 +97,7 @@ static bool rk808_is_volatile_reg(struct device *dev
Signed-off-by: Joseph Chen
---
.../devicetree/bindings/pinctrl/pinctrl-rk805.txt | 63 ++
1 file changed, 63 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-rk805.txt
diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-rk805.txt
Signed-off-by: Joseph Chen
---
drivers/mfd/rk808.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/drivers/mfd/rk808.c b/drivers/mfd/rk808.c
index db90471..6d9f96b 100644
--- a/drivers/mfd/rk808.c
+++ b/drivers/mfd/rk808.c
@@ -94,6 +94,19 @@ static bool rk808_is_volatile_re
On 2017-07-21 07:16, Austin S. Hemmelgarn wrote:
On 2017-07-20 17:27, Nick Terrell wrote:
Well this is embarrassing, forgot to type anything before hitting send...
Hi all,
This patch set adds xxhash, zstd compression, and zstd decompression
modules. It also adds zstd support to BtrFS and Squas
RK805 is one of Rockchip PMICs family, it has 2 output only GPIOs.
This driver is also designed for other Rockchip PMICs to expend.
Different PMIC maybe have different pin features, for example,
RK816 has one pin which can be used for TS or GPIO(input/out).
The mainly difference between PMICs pins
This driver provides a input driver for the power
key on the Rockchip RK805 PMIC.
Signed-off-by: Joseph Chen
---
drivers/input/misc/Kconfig| 6 +++
drivers/input/misc/Makefile | 1 +
drivers/input/misc/rk805-pwrkey.c | 111 ++
3 files changed
From: Elaine Zhang
Add device tree bindings documentation for Rockchip's RK805 PMIC.
Signed-off-by: Elaine Zhang
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/mfd/rk808.txt | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/Documentation/d
From: Elaine Zhang
The RK808 and RK805 PMICs are using a similar register map.
We can reuse the rtc driver for the RK805 PMIC. So let's add
the RK805 in the Kconfig description.
Signed-off-by: Elaine Zhang
---
drivers/rtc/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
From: Elaine Zhang
the rk8xx chip id is:
((MSB << 8) | LSB) & 0xfff0
Signed-off-by: Elaine Zhang
---
drivers/mfd/rk808.c | 21 +++--
include/linux/mfd/rk808.h | 1 +
2 files changed, 16 insertions(+), 6 deletions(-)
diff --git a/drivers/mfd/rk808.c b/drivers/mfd/rk808.c
From: Elaine Zhang
Signed-off-by: Elaine Zhang
---
include/linux/mfd/rk808.h | 120 ++
1 file changed, 120 insertions(+)
diff --git a/include/linux/mfd/rk808.h b/include/linux/mfd/rk808.h
index 54feb14..d315659 100644
--- a/include/linux/mfd/rk808.h
From: Elaine Zhang
Add support for the rk805 regulator. The regulator module consists
of 4 DCDCs, 3 LDOs.
The output voltages are configurable and are meant to supply power
to the main processor and other components.
Signed-off-by: Elaine Zhang
Acked-by: Mark Brown
---
drivers/regulator/Kcon
From: Elaine Zhang
The RK805 chip is a Power Management IC (PMIC) for multimedia and handheld
devices. It contains the following components:
- Regulators
- RTC
- Clocking
Both RK808 and RK805 chips are using a similar register map,
so we can reuse the RTC and Clocking functionality.
On 2017-07-20 17:27, Nick Terrell wrote:
Hi all,
This patch set adds xxhash, zstd compression, and zstd decompression
modules. It also adds zstd support to BtrFS and SquashFS.
Each patch has relevant summaries, benchmarks, and tests.
Best,
Nick Terrell
Changelog:
v1 -> v2:
- Make pointer in
On Fri, 21 Jul 2017 02:09:18 +0900 wrote:
> 2017-07-21 1:53 GMT+09:00 Masahiro Yamada :
> > 2017-07-21 1:08 GMT+09:00 Masahiro Yamada :
> >> 2017-07-07 10:54 GMT+09:00 Kunihiko Hayashi
> >> :
> >>> Add a thermal driver for on-chip PVT (Process, Voltage and Temperature)
> >>> monitoring unit impl
change in v7:
PATCH V7 1/12: NO change in V7
PATCH V7 2/12: NO change in V7
PATCH V7 3/12: fix missing: Acked-by: Mark Brown
PATCH V7 4/12: NO change in V7
PATCH V7 5/12: NO change in V7
PATCH V7 6/12: NO change in V7
PATCH V7 7/12: fix missing: Acked-by: Rob Herring
PATCH V7 8/12: abandon driver
Hi Linus,
Please pull some more powerpc fixes for 4.13:
The following changes since commit 01e6a61aceb82e13bec29502a8eb70d9574f97ad:
powerpc/64: Fix atomic64_inc_not_zero() to return an int (2017-07-12 21:49:55
+1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/li
Hi!
> > Is bluetooth expected to work on n900?
> >
> > It looks like lock init is missing somewhere:
> >
> > [ 402.901031] of_get_named_gpiod_flags: parsed
> > 'bluetooth-wakeup-gpios' property of node
> > '/ocp@6800/serial@4806c000/bluetooth[0]' - status (0)
> > [ 403.042022] BUG: rwlock
From: Colin Ian King
The list stvlist and arrays padc_lookup, s1_sn_lookup and s2_sn_lookup
do not need to be in global scope, so make them all static.
Cleans up a bunch of smatch warnings:
symbol 'padc_lookup' was not declared. Should it be static?
symbol 's1_sn_lookup' was not declared. Should
Current help text check only check a config option if it is followed
by another config.
Adding check for help text if the next entry is menuconfig, choice/
endchoice, comment, menu/endmenu, if/endif, source or end of file.
Change-Id: I9f0b29cebb93df2cadaf77d1027208fd01efd976
Signed-off-by: Yingjoe
Driver can turn off clocks during runtime suspend.
Also, runtime suspend is not as a result of host mode
selective suspend then PHY can be powered off as well.
Signed-off-by: Manu Gautam
diff --git a/drivers/phy/qualcomm/phy-qcom-qmp.c
b/drivers/phy/qualcomm/phy-qcom-qmp.c
index aefb853..8394e2
Driver currently notifies only USB3 PHY for mode change.
Extend this to USB3 PHY so that driver based on the mode
can release system resources - clocks, regulators etc.
and can even turn off PHY during runtime suspend.
Signed-off-by: Manu Gautam
diff --git a/drivers/usb/dwc3/core.c b/drivers/usb
Driver can turn off clocks during runtime suspend.
Also, runtime suspend is not as a result of host mode
selective suspend then PHY can be powered off as well.
Signed-off-by: Manu Gautam
diff --git a/drivers/phy/qualcomm/phy-qcom-qusb2.c
b/drivers/phy/qualcomm/phy-qcom-qusb2.c
index fa60a99..b5
PHY must be powered on before turning ON clocks and
attempting to initialize it. Driver is exposing
separate init and power_on routines for this.
Apparently USB dwc3 core driver performs power-on
after init. Also, poweron and init for QUSB2 PHY
need to be executed together always, hence remove
powe
PHY must be powered on before turning ON clocks and
attempting to initialize it. Driver is exposing
separate init and power_on routines for this.
Apparently USB dwc3 core driver performs power-on
after init. Also, poweron and init for QMP PHY
need to be executed together always, hence remove
powero
From: Vivek Gautam
Pipe clock comes out of the phy and is available as long as
the phy is turned on. Clock controller fails to gate this
clock after the phy is turned off and generates a warning.
/ # [ 33.048561] gcc_usb3_phy_pipe_clk status stuck at 'on'
[ 33.048585] [ cut here
From: "Gautham R. Shenoy"
Currently we use the stop-api provided by the firmware to program the
SLW engine to restore the values of hypervisor resources that get lost
on deeper idle states (such as winkle). Since the deep states were
only used for CPU-Hotplug on POWER8 systems, we would program t
On Thu, 20 Jul 2017 15:07:05 -0400
Nate Watterson wrote:
> Hi Jonathan,
>
> [...]
> >
> >>> Hi All,
> >>>
> >>> I'm a bit of late entry to this discussion. Just been running some more
> >>> detailed tests on our d05 boards and wanted to bring some more numbers to
> >>> the discussio
Hi Pavel,
>>> Kernel config options should include useful help text; I had to look
>>> up the terms on wikipedia.
>>>
>>> Signed-off-by: Pavel Machek
>>>
>>> diff --git a/net/bluetooth/Kconfig b/net/bluetooth/Kconfig
>>> index 68f951b..133c8a6 100644
>>> --- a/net/bluetooth/Kconfig
>>> +++ b/ne
From: Shu Wang
Found this issue by kmemleak, a few kb mem was leaked in
megasas_alloc_cmdlist_fusion when kzalloc failed for one
megasas_cmd_fusion allocation.
unreferenced object 0x88045dbd2000 (size 8192):
comm "systemd-udevd", pid 323, jiffies 4294671759 (age 49.008s)
backtrace:
[
Hello, Dmitry,
Thanks for your valuable review - and sorry for my late response.
For this patch, I am just the submitter, and I would ask Lingfang to
make some additional comments/clarifications regarding architecture of
user-kernel protocols for relevant drivers, and also regarding similar
issue
Two different processors on a SOC need to switch memory ownership
during load/unload. To enable this, second level memory map table
need to be updated, which is done by secure layer.
This patch adds the interface for making secure monitor call for
memory ownership switching request.
Signed-off-by:
This patch refactor code to first load all firmware blobs
and then update modem proc to authenticate and boot fw.
Signed-off-by: Avaneesh Kumar Dwivedi
---
drivers/remoteproc/qcom_q6v5_pil.c | 19 ---
1 file changed, 8 insertions(+), 11 deletions(-)
diff --git a/drivers/remotepr
On 21 July 2017 at 18:06, Hanjun Guo wrote:
>
> On 2017/7/21 17:51, Hanjun Guo wrote:
> > From: Hanjun Guo
> >
> > When running 4.13-rc1 on top of D05, I got the boot log:
> >
> > [0.00] SRAT: PXM 0 -> ITS 0 -> Node 0
> > [0.00] SRAT: PXM 0 -> ITS 1 -> Node 0
> > [0.00] SR
This patch add support for mss boot on msm8996. Major changes
include initializing mss rproc for msm8996, making appropriate
change for executing mss reset sequence etc.
Signed-off-by: Avaneesh Kumar Dwivedi
---
.../devicetree/bindings/remoteproc/qcom,q6v5.txt | 1 +
drivers/remoteproc/qcom_
MSS proc on msm8996 can not access fw loaded region without stage
second translation of memory pages where mpss image are loaded.
This patch in order to enable mss boot on msm8996 invoke scm call
to switch or share ownership between apps and modem.
Signed-off-by: Avaneesh Kumar Dwivedi
---
drive
Hardware needs a delay between setting an initial (non-zero) PWM and
enabling the backlight using GPIO. The post-pwm-on-delay-ms specifies
this delay in milli seconds. Hardware also needs a delay between disabing
the backlight using GPIO and setting PWM value to 0. The pwm-off-delay-ms
is this dela
This patch set does following
1- Adds new scm call which helps in stage two translation of a memory
region
so that memory ownership sharing and switching can be achieved on
armv8 and later.
2- Enable mss remoteproc on msm8996
Changes w.r.t. last patchset
1- Use
The minnie devices comes with an AUO B101EAN01 panel which is different
from default veyron devices, thus the power on/off timing sequence is
slightly different. The datasheet specifies a pwm delay of 200 ms, so
update the PMW delay proprieties accordingly.
Signed-off-by: Enric Balletbo i Serra
-
Before this patch the enable signal was set before the PWM signal and
vice-versa on power off. This sequence is wrong, at least, it is on
the different panels datasheets that I checked, so I inverted the sequence
to follow the specs.
For reference the following panels have the mentioned sequence:
For veyron the binding should provide both PWM timings, the delay between
you enable the PWM and set the enable signal, and the delay between you
disable the PWM signal and clear the enable signal. Update the binding
accordingly, in this case the panels connected to the veyron boards have
a symmetr
Some panels (i.e. N116BGE-L41), in their power sequence specifications,
request a delay between set the PWM signal and enable the backlight and
between clear the PWM signal and disable the backlight. Add support for
the new post-pwm-on-delay-ms and pwm-off-delay-ms proprieties to meet
the timings.
From: "Gautham R. Shenoy"
The stop4 idle state on POWER9 is a deep idle state which loses
hypervisor resources, but whose latency is low enough that it can be
exposed via cpuidle.
Until now, the deep idle states which lose hypervisor resources (eg:
winkle) were only exposed via CPU-Hotplug. Hen
Hi!
> > Kernel config options should include useful help text; I had to look
> > up the terms on wikipedia.
> >
> > Signed-off-by: Pavel Machek
> >
> > diff --git a/net/bluetooth/Kconfig b/net/bluetooth/Kconfig
> > index 68f951b..133c8a6 100644
> > --- a/net/bluetooth/Kconfig
> > +++ b/net/blue
From: "Gautham R. Shenoy"
Hi,
This is the third iteration of the patchset to enable exploitation of
stop4 idle state on POWER9 via cpuidle.
The earlier version can be found here :
[v2]: https://lkml.org/lkml/2017/7/19/152
[v1]: https://lkml.org/lkml/2017/7/18/691
The changes across the version
On 07/21/2017 04:49 AM, Mike Kravetz wrote:
> On 07/20/2017 02:36 AM, Anshuman Khandual wrote:
>> This adds a test to validate mirror functionality with mremap()
>> system call on shared anon mappings.
>>
>> Suggested-by: Mike Kravetz
>> Signed-off-by: Anshuman Khandual
>> ---
>> tools/testing/s
* Baoquan He wrote:
> +/*
> + * Returns true if mirror region found (and must have been processed
> + * for slots adding)
> + */
> +static bool process_efi_entries(unsigned long minimum,
> + unsigned long image_size)
Also, please don't break the line in the middle of
* Baoquan He wrote:
> Kernel text may be located in non-mirror regions (movable zone) when both
> address range mirroring feature and KASLR are enabled.
>
> The address range mirroring feature arranges such mirror region into
> normal zone and other region into movable zone in order to locate
>
On 07/21/2017 11:54 AM, Vinod Koul wrote:
> On Fri, Jul 21, 2017 at 09:30:00AM +, Pierre Yves MORDRET wrote:
+static enum dma_slave_buswidth stm32_mdma_get_max_width(u32 buf_len, u32
tlen)
+{
+ enum dma_slave_buswidth max_width = DMA_SLAVE_BUSWIDTH_8_BYTES;
+
+
Hi,
Lu Baolu writes:
> +static void xhci_dbc_stop(struct xhci_hcd *xhci)
> +{
> + struct xhci_dbc *dbc = xhci->dbc;
> +
> + WARN_ON(!dbc);
> +
> + cancel_delayed_work_sync(&dbc->event_work);
> +
> + if (dbc->gs_port_num != GSPORT_INVAL) {
> + gserial_disconnec
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
# HEAD: db15e7f27369b81b6605a546d54eb844f87370a5 x86/devicetree: Convert to
using %pOF instead of ->full_name
Half of the fixes are for variou
On Fri, Jul 21, 2017 at 1:44 AM, Tobias Klauser wrote:
> xtensa's asm/device.h is a verbatim copy of asm-generic/device.h and
> does not add any arch specific extensions. Thus, use the asm-generic
> header directly.
>
> Signed-off-by: Tobias Klauser
Thanks, applied to my xtensa-fixes branch.
--
On Fri, Jul 21, 2017 at 1:35 AM, Tobias Klauser wrote:
> xtensa's asm/device.h is a verbatim copy of asm-generic/device.h and
> does not add any arch specific extensions. Thus, use the asm-generic
> header directly.
>
> Acked-by: Max Filippov
> Signed-off-by: Tobias Klauser
Thanks, applied to m
On Fri, Jul 21, 2017 at 09:40:02AM +, Krishna Vamsi wrote:
> Hello Greg,
>
> Really sorry that I couldn't find this earlier but there is one issue with
> this cherry-pick. In "enum nl80211_commands", there are more variables
> between NL80211_ATTR_NAN_MATCH and NL80211_ATTR_BSSID. But they a
Juergen Gross writes:
> On 21/07/17 12:12, Punit Agrawal wrote:
>> Boris Ostrovsky writes:
>>
>>> On 07/20/2017 07:04 AM, Punit Agrawal wrote:
On systems that are not booted as a Xen domain, the xenfs driver prints
the following message during boot.
[3.460595] xenfs: not
Linus,
Please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
# HEAD: 32f2fea6e77e64cd4045ec2d5deb879aada3b476
clocksource/drivers/timer-of: Handle of_irq_get_byname() result correctly
A timer_irq_i
On 21/07/17 12:12, Punit Agrawal wrote:
> Boris Ostrovsky writes:
>
>> On 07/20/2017 07:04 AM, Punit Agrawal wrote:
>>> On systems that are not booted as a Xen domain, the xenfs driver prints
>>> the following message during boot.
>>>
>>> [3.460595] xenfs: not registering filesystem on non-xe
On Thu, Jul 20, 2017 at 03:50:16PM +, Moore, Robert wrote:
> Could you post this as a pull request on our github?
>
> https://github.com/acpica/acpica
Sure, will do, thanks !
Lorenzo
> > -Original Message-
> > From: Moore, Robert
> > Sent: Thursday, July 20, 2017 8:49 AM
> > To: 'Lo
Linus,
Please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
# HEAD: 193be41e33168a3a06eb9d356d9e39c69de161d2 sched/deadline: Fix
confusing comments about selection of top pi-waiter
A cputime fix and
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
for-linus-4.13-rc2-tag
xen: features and fixes for 4.13-rc2
It contains:
- a new Xen backend driver for passing socket calls from a Xen guest to
Xen dom0
- some Xen related bug fixes and clea
Reviewed-by: Marcus Wolf
Attention: This patch is nothing new, just a combination of Patch
[PATCH 2/3][staging-next] staging: pi433: Make functions
rf69_set_bandwidth_intern static
and
[PATCH 1/1][staging-next] staging: pi433: Make functions
rf69_set_dc_cut_off_frequency_intern static
> Colin
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
# HEAD: df6c3db8d30fb1699ccbc403196b86324f4257af perf/x86/intel: Add proper
condition to run sched_task callbacks
Two hw-enablement patches,
Boris Ostrovsky writes:
> On 07/20/2017 07:04 AM, Punit Agrawal wrote:
>> On systems that are not booted as a Xen domain, the xenfs driver prints
>> the following message during boot.
>>
>> [3.460595] xenfs: not registering filesystem on non-xen platform
>>
>> As the user chose not to boot a
Linus,
Please pull the latest locking-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-urgent-for-linus
# HEAD: 69f0d429c413fe96db2c187475cebcc6e3a8c7f5 locking/rtmutex: Remove
unnecessary priority adjustment
Remove an unnecessary priorit
Linus,
Please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
# HEAD: acc80c39929b9f2ff8b45fcfe103385a3e45c1a7 irqchip/digicolor: Drop
unnecessary static
A resume_irq() fix, plus a number of static declar
On 2017/7/21 17:51, Hanjun Guo wrote:
> From: Hanjun Guo
>
> When running 4.13-rc1 on top of D05, I got the boot log:
>
> [0.00] SRAT: PXM 0 -> ITS 0 -> Node 0
> [0.00] SRAT: PXM 0 -> ITS 1 -> Node 0
> [0.00] SRAT: PXM 0 -> ITS 2 -> Node 0
> [0.00] SRAT: PXM 1 -> IT
On Fri 2017-07-21 12:15:09, Andy Shevchenko wrote:
> On Fri, 2017-07-21 at 09:59 +0800, Ye Xiaolong wrote:
> > Hi,
> >
> > On 07/19, Linus Torvalds wrote:
> > > Hmm. I wonder why the kernel test robot ends up having that annoying
> > > line doubling for the dmesg.
> > >
> >
> > Hmm, this line do
we just record the cached_hole_size now, which will be used when
the criteria meet both of 'free_vmap_cache == NULL' and 'size <
cached_hole_size'. However, under above scenario, the search will
start from the rb_root and then find the node which just in front
of the cached hole.
free_vmap_cache m
Linus,
Please pull the latest core-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
core-urgent-for-linus
# HEAD: 325cdacd03c12629aa5f9ee2ace49b1f3dc184a8 debug: Fix WARN_ON_ONCE()
for modules
A fix to WARN_ON_ONCE() done by modules, plus a MAINT
From: Hanjun Guo
When running 4.13-rc1 on top of D05, I got the boot log:
[0.00] SRAT: PXM 0 -> ITS 0 -> Node 0
[0.00] SRAT: PXM 0 -> ITS 1 -> Node 0
[0.00] SRAT: PXM 0 -> ITS 2 -> Node 0
[0.00] SRAT: PXM 1 -> ITS 3 -> Node 1
[0.00] SRAT: ITS affinity exce
Hi Pavel,
> Is bluetooth expected to work on n900?
>
> It looks like lock init is missing somewhere:
>
> [ 402.901031] of_get_named_gpiod_flags: parsed
> 'bluetooth-wakeup-gpios' property of node
> '/ocp@6800/serial@4806c000/bluetooth[0]' - status (0)
> [ 403.042022] BUG: rwlock bad magic
On 2017年07月21日 16:32, Will Deacon wrote:
On Fri, Jul 21, 2017 at 07:38:42AM +, Zhou Qiao(周侨) wrote:
Could you please help to take a look and give some comments? Thanks in
advance.
I've queued this on the arm64 for-next/fixes/core branch.
Got it. Thanks!
Will
Best Regards
Qiao
On Fri, Jul 21, 2017 at 12:41 PM, Song liwei wrote:
> [Firmware Bug]: APEI: Invalid bit width + offset in GAR [0xb2/16/0/1/1]
>
> This is due to an 8-bit access width is specified for a 16-bit register,
> Do bit_width check just like what the original commit have done.
> else if (bit_wid
Hi Pavel,
> Kernel config options should include useful help text; I had to look
> up the terms on wikipedia.
>
> Signed-off-by: Pavel Machek
>
> diff --git a/net/bluetooth/Kconfig b/net/bluetooth/Kconfig
> index 68f951b..133c8a6 100644
> --- a/net/bluetooth/Kconfig
> +++ b/net/bluetooth/Kconfi
On Fri, Jul 21, 2017 at 09:30:00AM +, Pierre Yves MORDRET wrote:
> >> +static enum dma_slave_buswidth stm32_mdma_get_max_width(u32 buf_len, u32
> >> tlen)
> >> +{
> >> + enum dma_slave_buswidth max_width = DMA_SLAVE_BUSWIDTH_8_BYTES;
> >> +
> >> + while (((buf_len % max_width) || (tlen < max
On 2017/7/19 18:23, Robin Murphy wrote:
> On 19/07/17 09:37, Ard Biesheuvel wrote:
>> On 18 July 2017 at 17:57, Robin Murphy wrote:
>>> Hi all,
>>>
>>> In the wake of the ARM SMMU optimisation efforts, it seems that certain
>>> workloads (e.g. storage I/O with large scatterlists) probably remain
Commit-ID: b569bab78d8df157a6f91070af827753e4d1787c
Gitweb: http://git.kernel.org/tip/b569bab78d8df157a6f91070af827753e4d1787c
Author: Kirill A. Shutemov
AuthorDate: Mon, 17 Jul 2017 01:59:52 +0300
Committer: Ingo Molnar
CommitDate: Fri, 21 Jul 2017 10:05:18 +0200
x86/mm: Prepare to ex
Commit-ID: 77ef56e4f0fbb350d93289aa025c7d605af012d4
Gitweb: http://git.kernel.org/tip/77ef56e4f0fbb350d93289aa025c7d605af012d4
Author: Kirill A. Shutemov
AuthorDate: Mon, 17 Jul 2017 01:59:54 +0300
Committer: Ingo Molnar
CommitDate: Fri, 21 Jul 2017 10:05:19 +0200
x86: Enable 5-level p
Commit-ID: ee00f4a32a76ef631394f31d5b6028d50462b357
Gitweb: http://git.kernel.org/tip/ee00f4a32a76ef631394f31d5b6028d50462b357
Author: Kirill A. Shutemov
AuthorDate: Mon, 17 Jul 2017 01:59:53 +0300
Committer: Ingo Molnar
CommitDate: Fri, 21 Jul 2017 10:05:19 +0200
x86/mm: Allow userspa
Commit-ID: 44b04912fa72489d403738f39e1c782614b7ae7c
Gitweb: http://git.kernel.org/tip/44b04912fa72489d403738f39e1c782614b7ae7c
Author: Kirill A. Shutemov
AuthorDate: Mon, 17 Jul 2017 01:59:51 +0300
Committer: Ingo Molnar
CommitDate: Fri, 21 Jul 2017 10:05:18 +0200
x86/mpx: Do not allow
On Friday 21 July 2017 01:47 PM, Arnd Bergmann wrote:
> On Fri, Jul 21, 2017 at 10:05 AM, Sekhar Nori wrote:
>
>>> diff --git a/arch/arm/mach-davinci/clock.c b/arch/arm/mach-davinci/clock.c
>>> index f5dce9b4e617..89586779526c 100644
>>> --- a/arch/arm/mach-davinci/clock.c
>>> +++ b/arch/arm/mach
Commit-ID: db15e7f27369b81b6605a546d54eb844f87370a5
Gitweb: http://git.kernel.org/tip/db15e7f27369b81b6605a546d54eb844f87370a5
Author: Rob Herring
AuthorDate: Tue, 18 Jul 2017 16:42:47 -0500
Committer: Ingo Molnar
CommitDate: Fri, 21 Jul 2017 10:14:15 +0200
x86/devicetree: Convert to u
Commit-ID: e8f01a8dad7cdf9ddaa792451733a45ab5d385af
Gitweb: http://git.kernel.org/tip/e8f01a8dad7cdf9ddaa792451733a45ab5d385af
Author: Kirill A. Shutemov
AuthorDate: Mon, 17 Jul 2017 01:59:50 +0300
Committer: Ingo Molnar
CommitDate: Fri, 21 Jul 2017 10:05:18 +0200
x86/mm: Rename tasksi
Commit-ID: daaa42f04178ac7b02e4d43cdfc7fac48430152e
Gitweb: http://git.kernel.org/tip/daaa42f04178ac7b02e4d43cdfc7fac48430152e
Author: Kirill A. Shutemov
AuthorDate: Mon, 17 Jul 2017 01:59:49 +0300
Committer: Ingo Molnar
CommitDate: Fri, 21 Jul 2017 10:05:18 +0200
x86/xen: Redefine XEN
501 - 600 of 711 matches
Mail list logo
