On Thu 19-07-18 09:23:10, Shakeel Butt wrote:
> On Thu, Jul 19, 2018 at 3:43 AM Michal Hocko wrote:
> >
> > [CC Andrew]
> >
> > On Thu 19-07-18 18:06:47, Jing Xia wrote:
> > > It was reported that a kernel crash happened in mem_cgroup_iter(),
> > > which can be triggered if the legacy cgroup-v1
On Fri, Jul 20, 2018 at 06:22:49PM +0300, Alexander Kapshuk wrote:
> On Fri, Jul 20, 2018 at 6:16 PM Jiri Olsa wrote:
> >
> > On Fri, Jul 20, 2018 at 11:57:45AM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Fri, Jul 20, 2018 at 01:00:35PM +0200, Jiri Olsa escreveu:
> > > > The warning message
On Mon, 23 Jul 2018 02:47:18 +0200,
He, Bo wrote:
>
> Hi, Takashi:
> we tested for the whole weekend, your patch works, no panic issue seen.
> You can safe merge you patch.
OK, thanks for testing! Now it's merged.
Takashi
>
> -Original Message-
> From: Takashi Iwai
> Sent:
Hi all,
Today's linux-next merge of the xarray tree got a conflict in:
fs/dax.c
between commit:
55f25ced654c ("filesystem-dax: Introduce dax_lock_mapping_entry()")
from the nvdimm tree and several commits from the xarray tree.
I have no idea how to fix this up, please discuss it and give
Hi Naga,
Naga Sureshkumar Relli wrote on Sun, 22 Jul 2018
07:04:41 +:
> Hi Miquel,
>
> Could you please provide your review comments?
> I will address if any.
We are almost at the end of a pretty big release, I ran out of time to
do another review of your series, sorry for the delay.
Hey David,
On Sun, Jul 22, 2018 at 11:49:00PM -0400, David H. Gutteridge wrote:
> Unfortunately, I can trigger a bug in KVM+QEMU with the Bochs VGA
> driver. (This is the same VM definition I shared with you in a PM
> back on Feb. 20th, except note that 4.18 kernels won't successfully
> boot with
On Fri, 20 Jul 2018 at 16:32, Paolo Bonzini wrote:
>
> On 20/07/2018 05:58, KY Srinivasan wrote:
> >
> >
> >> -Original Message-
> >> From: Tianyu Lan
> >> Sent: Thursday, July 19, 2018 1:40 AM
> >> Cc: Tianyu Lan ; de...@linuxdriverproject.org;
> >> Haiyang Zhang ; h...@zytor.com;
> >>
On 2018-07-23 09:24, Andy Shevchenko wrote:
> On Mon, Jul 23, 2018 at 9:12 AM, Peter Rosin wrote:
>> On 2018-07-23 05:40, Manivannan Sadhasivam wrote:
>>> + /* Handle the remaining bytes which were not sent */
>>> + while (!(readl(i2c_dev->base + OWL_I2C_REG_FIFOSTAT) &
Dear Sir/Madam,
How are you doing today? My name is Billy Wilfred. I am California, United
States of America. I am a broker of Project Financing Firm who has cutting edge
and group capital fund, they can finance any lucrative project and help you to
enhance your business plan. Are you in need
On Mon, Jul 23, 2018 at 9:59 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:d72e90f33aa4 Linux 4.18-rc6
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1324f79440
> kernel config:
On Mon, 23 Jul 2018 at 14:00, Wanpeng Li wrote:
>
> On Mon, 23 Jul 2018 at 13:52, Paolo Bonzini wrote:
> >
> > On 20/07/2018 18:28, Wanpeng Li wrote:
> > > +a0: ipi_bitmap low 64 bits
> > > +a1: ipi_bitmap high 64 bits
> > > +a2: the lowest APIC ID in bitmap
> > > +a3: APIC ICR
> > > +
> > >
On Sun, 22 Jul 2018 08:22:48 -0700
Matthew Wilcox wrote:
> On Sun, Jul 22, 2018 at 07:11:09PM +0530, Souptick Joarder wrote:
> > use new return type vm_fault_t for fault handler vdso_fault.
> >
> > Signed-off-by: Souptick Joarder
>
> Reviewed-by: Matthew Wilcox
I modified the patch
The SC27xx breathing light controller can support 3 outputs:
red LED, green LED and blue LED.
Signed-off-by: Baolin Wang
---
arch/arm64/boot/dts/sprd/sc2731.dtsi | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm64/boot/dts/sprd/sc2731.dtsi
On 23/07/2018 08:00, Wanpeng Li wrote:
> On Mon, 23 Jul 2018 at 13:52, Paolo Bonzini wrote:
>>
>> On 20/07/2018 18:28, Wanpeng Li wrote:
>>> +a0: ipi_bitmap low 64 bits
>>> +a1: ipi_bitmap high 64 bits
>>> +a2: the lowest APIC ID in bitmap
>>> +a3: APIC ICR
>>> +
>>> +The hypercall lets a guest
On 23/07/2018 08:10, Wanpeng Li wrote:
>>> On 20/07/2018 18:28, Wanpeng Li wrote:
+a0: ipi_bitmap low 64 bits
+a1: ipi_bitmap high 64 bits
+a2: the lowest APIC ID in bitmap
+a3: APIC ICR
+
+The hypercall lets a guest send multicast IPIs at most can handle
+128
Hi Niklas,
On Tue, Jul 3, 2018 at 12:50 PM, Niklas Cassel wrote:
> Since commit cab673583d96 ("soc: Unconditionally include qcom Makefile"),
> we unconditionally include the soc/qcom/Makefile.
>
> This opens up the possibility to compile test the code even when
> building for other
From: Yue Wang
Signed-off-by: Yue Wang
---
sound/usb/quirks.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/usb/quirks.c b/sound/usb/quirks.c
index 02b6cc02767f..c51e2dee3075 100644
--- a/sound/usb/quirks.c
+++ b/sound/usb/quirks.c
@@ -1374,6 +1374,7 @@ u64
On Sunday 22 July 2018 17:58:24 Liu Xiang wrote:
> The URL of bq27441-g1 and bq27426 are missing and bq27520-g4 is duplicated.
>
> Signed-off-by: Liu Xiang
Looks good, you can add my:
Reviewed-by: Pali Rohár
> ---
> drivers/power/supply/bq27xxx_battery.c | 3 ++-
> 1 file changed, 2
This patch is to avoid compilation warning when CONFIG_HYPERV isn't enabled.
Signed-off-by: Lan Tianyu
---
arch/x86/kvm/vmx.c | 84 +++---
1 file changed, 42 insertions(+), 42 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
Add enable/disable support for switch regulators on pfuze100.
Based on commit 5fe156f1cab4 ("regulator: pfuze100: add enable/disable for
switch") which is reverted due to boot regressions by commit 464a5686e6c9
("regulator: Revert "regulator: pfuze100: add enable/disable for switch"").
Disabling
This binding is used to keep the backward compatibility with the current
dtb's [1]. The binding informs the driver that the unused switch regulators
can be disabled.
If it is not specified, the driver doesn't disable the switch regulators.
[1] https://patchwork.kernel.org/patch/10490381/
Hi,
Anson had added the support to disable the switched regulators, but
there were regressions [1] with old dtb's, so the commit was reverted [2].
At all, the support to disable the switch regulators seems to me to be a
good feature. But we have to add a special dt-property to avoid
regressions
On 2018-07-18 19:04, Bharat Kumar Gogada wrote:
On 2018-07-13 19:25, Bharat Kumar Gogada wrote:
>> > Currently PCI_BRIDGE_CTL_SERR is being enabled only in ACPI flow.
>> > This bit is required for forwarding errors reported by EP devices
>> > to upstream device.
>> > This patch enables SERR# for
From: Wanpeng Li
Implement paravirtual apic hooks to enable PV IPIs.
apic->send_IPI_mask
apic->send_IPI_mask_allbutself
apic->send_IPI_allbutself
apic->send_IPI_all
This patch lets a guest send multicast IPIs, with at most 128 destinations
per hypercall in 64-bit mode and 64 vCPUs per
From: Wanpeng Li
The NMI delivery mode of ICR is used to deliver an NMI to the processor,
and the vector information is ignored.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: Vitaly Kuznetsov
Signed-off-by: Wanpeng Li
---
arch/x86/kernel/kvm.c | 15 ---
arch/x86/kvm/x86.c| 16
From: Wanpeng Li
Fallback to original apic hooks when unlikely kvm fails to add the
pending IRQ to lapic.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: Vitaly Kuznetsov
Signed-off-by: Wanpeng Li
---
arch/x86/kernel/kvm.c | 20 +---
1 file changed, 13 insertions(+), 7 deletions(-)
From: Wanpeng Li
Add kvm hypervisor init time platform setup callback which
will be used to replace native apic hooks by pararvirtual
hooks.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: Vitaly Kuznetsov
Signed-off-by: Wanpeng Li
---
arch/x86/kernel/kvm.c | 10 ++
1 file changed, 10
Using hypercall to send IPIs by one vmexit instead of one by one for
xAPIC/x2APIC physical mode and one vmexit per-cluster for x2APIC cluster
mode. Intel guest can enter x2apic cluster mode when interrupt remmaping
is enabled in qemu, however, latest AMD EPYC still just supports xapic
mode
From: Wanpeng Li
Expose PV_SEND_IPI feature bit to guest, the guest can check this feature
bit before using paravirtualized send IPIs.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: Vitaly Kuznetsov
Signed-off-by: Wanpeng Li
---
Documentation/virtual/kvm/cpuid.txt | 4
arch/x86/kvm/cpuid.c
From: Wanpeng Li
Using hypercall to send IPIs by one vmexit instead of one by one for
xAPIC/x2APIC physical mode and one vmexit per-cluster for x2APIC cluster
mode. Intel guest can enter x2apic cluster mode when interrupt remmaping
is enabled in qemu, however, latest AMD EPYC still just
Hi Matthew,
Today's linux-next merge of the xarray tree got a conflict in:
MAINTAINERS
between commits:
30153e5ba54d ("MAINTAINERS: update Ross Zwisler's email address")
212a28b4dae9 ("MAINTAINERS: Add Jan Kara for filesystem DAX")
from the nvdimm tree and commit:
40c8f8eed61c
On 17 July 2018 at 19:16, Adrian Hunter wrote:
> On 09/07/18 06:19, Chunyan Zhang wrote:
>> As SD Host Controller Specification v4.10 documents:
>> Host Controller Version 4.10 defines this "Auto CMD Auto Select" mode.
>> Selection of Auto CMD depends on setting of CMD23 Enable in the Host
>>
On 17 July 2018 at 16:29, Adrian Hunter wrote:
> On 09/07/18 06:19, Chunyan Zhang wrote:
>> When Host Version 4 is enabled, SDMA System Address register is
>> re-defined as 32-bit Block Count, and SDMA uses ADMA System
>> Address register (05Fh-058h) instead.
>>
>> Signed-off-by: Chunyan Zhang
On Mon, Jul 23, 2018 at 9:12 AM, Peter Rosin wrote:
> On 2018-07-23 05:40, Manivannan Sadhasivam wrote:
>> + /* Handle the remaining bytes which were not sent */
>> + while (!(readl(i2c_dev->base + OWL_I2C_REG_FIFOSTAT) &
>> +OWL_I2C_FIFOSTAT_TFF) &&
Hi Peter,
On Mon, Jul 23, 2018 at 08:12:17AM +0200, Peter Rosin wrote:
> On 2018-07-23 05:40, Manivannan Sadhasivam wrote:
> > + /* Handle the remaining bytes which were not sent */
> > + while (!(readl(i2c_dev->base + OWL_I2C_REG_FIFOSTAT) &
> > +
On Mon, 23 Jul 2018 09:25:34 +0200,
wrote:
>
> From: Yue Wang
>
> Signed-off-by: Yue Wang
Please give more explanation.
No commit message already indicates that something is very wrong, no
matter what the change is.
thanks,
Takashi
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
mm/mmap.c
between commit:
490fc053865c ("mm: make vm_area_alloc() initialize core fields")
from Linus' tree and commit:
97478b56e246 ("mm: Fix vma_is_anonymous() false-positives")
from the akpm-current tree.
On Mon, 23 Jul 2018 at 13:52, Paolo Bonzini wrote:
>
> On 20/07/2018 18:28, Wanpeng Li wrote:
> > +a0: ipi_bitmap low 64 bits
> > +a1: ipi_bitmap high 64 bits
> > +a2: the lowest APIC ID in bitmap
> > +a3: APIC ICR
> > +
> > +The hypercall lets a guest send multicast IPIs at most can handle
> >
This patch adds the vibrator device node for Spreadtrum SC27XX PMICs.
Signed-off-by: Baolin Wang
---
arch/arm64/boot/dts/sprd/sc2731.dtsi |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/sprd/sc2731.dtsi
b/arch/arm64/boot/dts/sprd/sc2731.dtsi
index
This patch adds the eFuse device node for Spreadtrum SC27XX PMICs.
The SC27XX eFuse contains 32 blocks and each block's data width is
16 bits.
Signed-off-by: Baolin Wang
---
arch/arm64/boot/dts/sprd/sc2731.dtsi |8
1 file changed, 8 insertions(+)
diff --git
On Spreadtrum platform, the current clocksource for timekeeping will be
stopped in suspend state, thus add one always-on timer to calculate the
suspend time.
Signed-off-by: Baolin Wang
---
arch/arm64/boot/dts/sprd/whale2.dtsi |6 ++
1 file changed, 6 insertions(+)
diff --git
Add the Spreadtrum SC27XX PMICs ADC device node which contains 32 channels.
Signed-off-by: Baolin Wang
---
arch/arm64/boot/dts/sprd/sc2731.dtsi |9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm64/boot/dts/sprd/sc2731.dtsi
b/arch/arm64/boot/dts/sprd/sc2731.dtsi
index
On Fri, Jul 20, 2018 at 08:50:22AM +, Zhangfei (Tyler) wrote:
> Hi Naoya：
> We have a similar problem, the difference is that we did not Enable
> hugepage, the soft-offline was executed in the case of normal 4K pages, and
> finally the MCE kill was triggered（find hwpoison flag is
On 2018-07-23 05:40, Manivannan Sadhasivam wrote:
> + /* Handle the remaining bytes which were not sent */
> + while (!(readl(i2c_dev->base + OWL_I2C_REG_FIFOSTAT) &
> +OWL_I2C_FIFOSTAT_TFF) && i2c_dev->msg_ptr < msg->len) {
You moved the OWL_ line to
When handling ept misconfig exit, it will call emulate instruction
with insn_len = 0. The decode instruction function may return a fetch
fault and should propagate to guest.
The problem will result to emulation fail.
KVM internal error. Suberror: 1
emulation failure
EAX=f81a0024 EBX=f6a07000
Hi Pavel,
On 20 July 2018 at 04:20, Pavel Machek wrote:
> Hi!
>
>> > >Please keep in mind that this is ABI documentation for the pattern file
>> > >to be exposed by LED core, and not by the pattern trigger, that, as we
>> > >agreed, will be implemented later. In this case, I'd go for
>> >
>> >
On Sun, Jul 22, 2018 at 03:53:24PM +0800, kernel test robot wrote:
>
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 600b7378cf43f522e88027874f11f63b6fbf53d8 ("[PATCH 2/4] perf tools:
> Add threads__get_last_match function")
> url:
>
On Sun, Jul 22, 2018 at 7:52 PM, Andy Lutomirski wrote:
> Hi all-
>
> It would be really nice to make KASAN compatible with VMAP_STACK.
> Both are valuable memory debugging features, and the fact that you
> can't use both is disappointing.
>
> As far as I know, there are only two problems:
>
> 1.
Hi Takashi
My apologies, it's my first time sending a patch to the kernel, so
there're quite a few things I need to improve.
This patch adds the support for native DSD for Topping DX7s DAC. The
product description is on
http://en.tpdz.net/products_detail/productId=32.html and it's
available on
On 7/23/2018 3:39 PM, Wanpeng Li wrote:
> On Fri, 20 Jul 2018 at 16:32, Paolo Bonzini wrote:
>>
>> On 20/07/2018 05:58, KY Srinivasan wrote:
>>>
>>>
-Original Message-
From: Tianyu Lan
Sent: Thursday, July 19, 2018 1:40 AM
Cc: Tianyu Lan ; de...@linuxdriverproject.org;
On Mon, 23 Jul 2018 09:41:15 +0200,
Yue Wang wrote:
>
> Hi Takashi
>
> My apologies, it's my first time sending a patch to the kernel, so
> there're quite a few things I need to improve.
>
> This patch adds the support for native DSD for Topping DX7s DAC. The
> product description is on
>
On Fri, Jul 20, 2018 at 03:36:41PM -0700, Nick Desaulniers wrote:
> native_save_fl() is marked static inline, but by using it as
> a function pointer in arch/x86/kernel/paravirt.c, it MUST be outlined.
>
> paravirt's use of native_save_fl() also requires that no GPRs other than
> %rax are
Hello,
syzbot found the following crash on:
HEAD commit:d72e90f33aa4 Linux 4.18-rc6
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1324f79440
kernel config: https://syzkaller.appspot.com/x/.config?x=68af3495408deac5
dashboard link:
On Mon, Jul 23, 2018 at 1:04 AM Randy Dunlap wrote:
> From: Randy Dunlap
>
> Building drivers/mtd/nand/raw/nandsim.c on arch/hexagon/ produces a
> printk format build warning. This is due to hexagon's ffs() being
> coded as returning long instead of int.
>
> Fix the printk format warning by
2018-06-21 9:37 GMT+02:00 Bartosz Golaszewski :
> From: Bartosz Golaszewski
>
> Switch to using the reset framework instead of handcoded reset routines
> we used so far.
>
> Signed-off-by: Bartosz Golaszewski
> Reviewed-by: Sekhar Nori
> Reviewed-by: Philipp Zabel
> ---
>
This patch adds the support for native DSD for Topping DX7s DAC. The
product description is on
http://en.tpdz.net/products_detail/productId=32.html and it's
available on
https://www.amazon.com/Balanced-Headphone-Amplifier-Topping-2ES9038Q2M/dp/B07B4VFS21
The DAC uses XMOS chip but uses a special
On Thu, 2018-07-19 at 10:09 -0700, Paul E. McKenney wrote:
>
> Of course, the real reason for the lack of fault on your part will not
> because I believe I found the bug elsewhere, but instead because I will
> be dropping your patch (and mine as well) on Frederic's advice. ;-)
You're keeping
On 23.7.2018 05:19, Tony Xie wrote:
Add device tree bindings documentation for Rockchip's RK809 & RK817 PMIC.
Signed-off-by: Tony Xie
---
Documentation/devicetree/bindings/mfd/rk808.txt | 55 +
1 file changed, 55 insertions(+)
Hi Tony,
Seems something went wrong
On 2018-07-22 12:55, Dmitry Osipenko wrote:
On Friday, 20 July 2018 16:45:30 MSK Ben Dooks wrote:
The 2D and 3D clocks have an IDLE field in bits 15:8 so add these
clocks by making a 2D and 3D mux, and split the divider into the
standard 2D/3D ones and 2D/3D idle clocks.
Signed-off-by: Ben
Hi Jonathan,
On Sun, Jul 22, 2018 at 09:11:11AM +0100, Jonathan Cameron wrote:
> On Sat, 21 Jul 2018 21:59:22 +0200
> Marcus Folkesson wrote:
>
[snip]
> > +Optional properties:
> > + - device-addr: Device address when multiple MCP3911 chips are present on
> > the
> > + same SPI bus. Valid
On Fri 20-07-18 12:03:27, Oscar Salvador wrote:
> On Thu, Jul 19, 2018 at 10:52:35PM +0200, Oscar Salvador wrote:
> > On Thu, Jul 19, 2018 at 05:15:55PM +0200, Michal Hocko wrote:
> > > Your changelog doesn't really explain the motivation. Does the change
> > > help performance? Is this a pure
On Mon, Jul 23, 2018 at 01:39:30PM +0800, Chen Lin wrote:
> From: Chen Lin
>
> NUMA balancing has not taken *isolcpus(isolated cpus)* into
> consideration. It may migrate tasks onto isolated cpus and the
> migrated tasks will never escape from the isolated cpus, which will
> break the
Thanks for the comment Jussi. Let's drop this patch, and I will send a
new patch with this generic approach shortly. The new patch will have
a different commit title and message.
On Mon, Jul 23, 2018 at 1:26 AM Jussi Laako wrote:
>
> Hi,
>
> > + case USB_ID(0x152a, 0x8750): /* Topping DX7s */
Thesycon provides solutions to XMOS chips, and has its own device vendor id.
In this patch, we use generic method to detect DSD capability of Thesycon-based
UAC2
implementations in order to support a wide range of current and future devices.
The patch will enable the SNDRV_PCM_FMTBIT_DSD_U32_BE
Hi Adam,
On Sat, Jul 21, 2018 at 11:39 PM Adam Borowski wrote:
> Technically, every console can be made to blink by drawing/clearing affected
> characters a few times per second, but that'd be quite a waste of coding
> time and kernel size. There's a reason browsers dropped support for
> and
On Sun, Jul 22, 2018 at 8:29 AM, Boris Brezillon
wrote:
> +Arnd, Rob and the DT ML.
>
> On Sat, 21 Jul 2018 14:53:47 -0700
> Randy Dunlap wrote:
>
>> On 07/21/2018 01:00 PM, Anders Roxell wrote:
>> > JZ4780_NEMC doesn't depend on OF, and if OF isn't enabled we get this
>> > error:
>> >
Hi Jonathan,
Thanks for your comments.
> -Original Message-
> From: Jonathan Cameron [mailto:ji...@kernel.org]
> Sent: Saturday, July 21, 2018 9:54 PM
> To: Lars-Peter Clausen
> Cc: Manish Narani ; knaac...@gmx.de;
> pme...@pmeerw.net; Michal Simek ; linux-
> i...@vger.kernel.org;
On Wed, Jul 18, 2018 at 04:53:27PM -0700, Dave Hansen wrote:
> The description doesn't mention the potential performance implications
> of this patch. That's criminal at this point.
>
> > --- a/arch/x86/mm/mktme.c
> > +++ b/arch/x86/mm/mktme.c
> > @@ -1,4 +1,5 @@
> > #include
> > +#include
>
On Wed, Jul 18, 2018 at 05:01:37PM -0700, Dave Hansen wrote:
> On 07/17/2018 04:20 AM, Kirill A. Shutemov wrote:
> > arch/x86/include/asm/mktme.h | 8 +
> > arch/x86/mm/init_64.c| 10 +
> > arch/x86/mm/mktme.c | 437 +++
> > 3 files changed, 455
On 2018-07-21 05:07, kbuild test robot wrote:
Hi Girish,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on spi/for-next]
[also build test ERROR on v4.18-rc5 next-20180720]
[if your patch is applied to the wrong git tree, please drop us a note
to help improve the
On Wed, Jun 20, 2018 at 10:32:52PM +0530, Srikar Dronamraju wrote:
> Since task migration under numa balancing can happen in parallel, more
> than one task might choose to move to the same node at the same time.
> This can cause load imbalances at the node level.
>
> The problem is more likely if
The SID controller on H3 is one of it's kind (at least from what we
know).
Add a compatible string for it in the SoC dtsi.
Signed-off-by: Emmanuel Vadot
---
arch/arm/boot/dts/sun8i-h3.dtsi | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-h3.dtsi
The SID controller on H5 look the same as the one present in the A64.
But in case we find some difference one day at a compatible string
of it's own and a fallback to the A64 one.
Signed-off-by: Emmanuel Vadot
---
.../devicetree/bindings/nvmem/allwinner,sunxi-sid.txt| 1 +
On Mon, Jul 23, 2018 at 06:34:36PM +0800, shaochun chen wrote:
> I have a question: we will try_module_get in __netlink_dump_start(),
> but why we need to call try_module_get again in nft_netlink_dump_start ??
Because they refer to two different modules. nfnetlink is multiplexing
all netfilter
Both H3 and H5 and a SID controller at the same address.
They are know to be different, the H5 one is the same as the A64 so add
a node in the common dtsi and we will override the compatible string in
the SoC dts.
Signed-off-by: Emmanuel Vadot
---
arch/arm/boot/dts/sunxi-h3-h5.dtsi | 4
1
Hi,
+ case USB_ID(0x152a, 0x8750): /* Topping DX7s */
0x152a is Thesycon's VID and if it's based on XMOS I'd recommend to try
adding the 0x152a VID to the generic DSD capability auto-detect list
instead of this old device specific list.
I consider it very likely that it would work
On Sat, Jul 21, 2018 at 1:57 AM, Alex Williamson
wrote:
> On Thu, 19 Jul 2018 21:49:48 +0530
> Srinath Mannam wrote:
>
>> HI Alex,
>>
>> On Thu, Jul 19, 2018 at 8:42 PM, Alex Williamson
>> wrote:
>> > On Thu, 19 Jul 2018 20:17:11 +0530
>> > Srinath Mannam wrote:
>> >
>> >> HI Alex,
>> >>
>> >>
RK809 and RK817 are power management IC chips for multimedia products.
most of their functions and registers are same, including the clkout
funciton.
Signed-off-by: Tony Xie
---
drivers/clk/Kconfig | 6 ++---
drivers/clk/clk-rk808.c | 62 -
2
On 07/20/2018 05:08 PM, Boris Ostrovsky wrote:
On 07/20/2018 05:01 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
This work is in response to my previous attempt to introduce Xen/DRM
zero-copy driver [1] to enable Linux dma-buf API [2] for Xen based
frontends/backends. There
Use clock-frequency property given in _DSD object
of ACPI device to calculate Watchdog rate as binding
clock devices are not available as device tree.
Note: There is no formal review process for _DSD
properties
Signed-off-by: Srinath Mannam
Signed-off-by: Guenter Roeck
Reviewed-by: Guenter
On Fri, Jul 20, 2018 at 02:45:27PM +0100, Ben Dooks wrote:
> The clocks vde, vi, epp, mpe, 2d and 3d are all fractional
> divisors, and not integer divisors as setup in the current
> kernel. This seems to be the same for tegra2 and tegra3.
>
Same comment as the host1x clock patch.
>
firmware_map_add_hotplug() is only called by add_memory_resource(),
which is never called in atomic context.
firmware_map_add_hotplug() calls kzalloc() with GFP_ATOMIC,
which is not necessary.
GFP_ATOMIC can be replaced with GFP_KERNEL.
This is found by a static analysis tool named DCNS written
If 'CONFIG_MEMORY_HOTREMOVE' specified, walk the acpi srat memory
tables, store the immovable memory regions, so that kaslr can get
the information abouth where can be selected or not.
If 'CONFIG_MEMORY_HOTREMOVE' not specified, go on the old code.
Signed-off-by: Chao Fan
---
On Wed, Jul 04, 2018 at 11:27:27AM +0800, 王贇 wrote:
> @@ -6788,6 +6790,12 @@ static int cpu_cfs_stat_show(struct seq_file *sf, void
> *v)
> seq_printf(sf, "nr_throttled %d\n", cfs_b->nr_throttled);
> seq_printf(sf, "throttled_time %llu\n", cfs_b->throttled_time);
>
> + if
If 'CONFIG_MEMORY_HOTREMOVE' specified and the account of immovable
memory regions is not zero. Calculate the intersection between memory
regions from e820/efi memory table and immovable memory regions.
Or go on the old code.
Rename process_mem_region to slots_count to match slots_fetch_random,
In order to parse ACPI tables, reuse the head file linux/acpi.h,
so that the files in 'compressed' directory can read ACPI table
by including this head file.
Signed-off-by: Chao Fan
---
arch/x86/boot/compressed/acpitb.h | 7 +++
1 file changed, 7 insertions(+)
create mode 100644
***Background:
People reported that kaslr may randomly chooses some positions
which are located in movable memory regions. This will break memory
hotplug feature and make the memory can't be removed.
***Solutions:
There should be a method to limit kaslr to choosing immovable memory
regions, so
Add MEMCPY capability for imx-sdma driver.
Signed-off-by: Robin Gong
---
drivers/dma/imx-sdma.c | 93 --
1 file changed, 90 insertions(+), 3 deletions(-)
diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c
index e3d5e73..b4ec2d2 100644
On Wed, Jul 18, 2018 at 04:38:02PM -0700, Dave Hansen wrote:
> On 07/17/2018 04:20 AM, Kirill A. Shutemov wrote:
> > Store KeyID in bits 31:16 of extended page flags. These bits are unused.
>
> I'd love a two sentence remind of what page_ext is and why you chose to
> use it. Yes, you need this.
Add macro SDMA_BD_MAX_CNT to replace '0x'.
Signed-off-by: Robin Gong
---
drivers/dma/imx-sdma.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c
index 3b622d6..e3d5e73 100644
--- a/drivers/dma/imx-sdma.c
+++
This patchset is to add memcpy interface for imx-sdma, besides,to
support dmatest and enable config by default, so that could test dma
easily without any other device support such as uart/audio/spi...
Change from v2:
1. remove 'copy_align' since sdma script for memory_2_memory will handle
If multi-bds used in one transfer, all bds should be consisten
memory.To easily follow it, enlarge the dma pool size into 20 bds,
and it will report error if the number of bds is over than 20. For
dmatest, the max count for single transfer is NUM_BD *
SDMA_BD_MAX_CNT = 20 * 65535 = ~1.28MB.
Viele Grüße von mir. Wie geht es Ihnen heute? Verzeih mir, dass ich deinen
Frieden gestört habe, ich verstehe meine Herangehensweise vielleicht sehr
ungeschickt und unhöflich, bitte ich bitte, dass du mir verzeihst, ein
Eindringling zu sein. Ich bin Wesley mit Namen, ich bin aus dem Vereinigten
Viele Grüße von mir. Wie geht es Ihnen heute? Verzeih mir, dass ich deinen
Frieden gestört habe, ich verstehe meine Herangehensweise vielleicht sehr
ungeschickt und unhöflich, bitte ich bitte, dass du mir verzeihst, ein
Eindringling zu sein. Ich bin Wesley mit Namen, ich bin aus dem Vereinigten
For SD host controller version 4.00 or later ones, there're two
modes of implementation - Version 3.00 compatible mode or
Version 4 mode. This patch introduced an interface to enable
v4 mode.
Signed-off-by: Chunyan Zhang
---
drivers/mmc/host/sdhci.c | 28
From: Chunyan Zhang
This patch adds the initial support of Secure Digital Host Controller
Interface compliant controller found in some latest Spreadtrum chipsets.
This patch has been tested on the version of SPRD-R11 controller.
R11 is a variant based on SD v4.0 specification.
With this
Dear Jörg,
On 07/20/18 14:31, Jörg Rödel wrote:
> On Tue, Jul 17, 2018 at 06:02:07PM +0200, Paul Menzel wrote:
>> $ dmesg
>> […]
>> [0.145696] calling pci_iommu_init+0x0/0x3f @ 1
>> [0.145719] AMD-Vi: Unable to write to IOMMU perf counter.
>
> This is likely a firmware issue. Either
Host Controller Version 4.10 re-defines SDMA System Address register
as 32-bit Block Count for v4 mode, and SDMA uses ADMA System
Address register (05Fh-058h) instead if v4 mode is enabled. Also
when using 32-bit block count, 16-bit block count register need
to be set to zero.
Signed-off-by:
As SD Host Controller Specification v4.10 documents:
Host Controller Version 4.10 defines this "Auto CMD Auto Select" mode.
Selection of Auto CMD depends on setting of CMD23 Enable in the Host
Control 2 register which indicates whether card supports CMD23. If CMD23
Enable =1, Auto CMD23 is used
From: Chunyan Zhang
This patch adds the device-tree binding documentation for Spreadtrum
SDHCI driver.
Signed-off-by: Chunyan Zhang
---
.../devicetree/bindings/mmc/sdhci-sprd.txt | 41 ++
1 file changed, 41 insertions(+)
create mode 100644
401 - 500 of 1916 matches
Mail list logo
