Hi Jacopo,
On Tue, Feb 20, 2018 at 4:12 PM, Jacopo Mondi wrote:
> Add documentation for r8a77965 compatible string to rcar-dmac device
> tree bindings documentation.
>
> Signed-off-by: Jacopo Mondi
> Reviewed-by: Geert Uytterhoeven
> Reviewed-by: Simon Horman
Can you please resend to the DMA
Implement HvFlushVirtualAddress{List,Space} hypercalls in a simplistic way:
do full TLB flush with KVM_REQ_TLB_FLUSH and kick vCPUs which are currently
IN_GUEST_MODE.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/kvm/hyperv.c | 74
Hello Nick/ Yann,
Any inputs regarding LZ4 dyn results & lz4 dyn approach.
>Hello Nick/Sergey,
>
>Any suggestion or comments, so that we can change code and resend the patch?
>
>> Hi Nick / Sergey,
>>
>>
>> We have compared LZ4 Dyn with Original LZ4 using some samples of realtime
>> applic
Hyper-V TLB flush hypercalls definitions will be required for KVM so move
them hyperv-tlfs.h. Structures also need to be renamed as '_pcpu' suffix is
invalid for a general-purpose definition.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/hyperv/mmu.c | 40 ++--
Changes since v2:
- Fixed a sparse warning in PATCH1 [kbuild test robot]
Description:
This is both a new feature and a bugfix.
Bugfix description:
It was found that Windows 2016 guests on KVM crash when they have > 64
vCPUs, non-flat topology (>1 core/thread per socket; in case it has >64
sock
Avoid open-coding offsets for hypercall input parameters, we already
have defines for them.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/kvm/hyperv.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c
index 98618e397342..3cb3bb
On 15/04/2018 23:53, KarimAllah Ahmed wrote:
> Guest memory can either be directly managed by the kernel (i.e. have a "struct
> page") or they can simply live outside kernel control (i.e. do not have a
> "struct page"). KVM mostly support these two modes, except in a few places
> where the code see
Hello all,
I know this proposal has already been made great many times but I'd like
to repeat it and have a healthy discussion about it.
The current kernel numbering scheme makes no sense at all because the
first two numbers don't represent anything at all. They had some meaning
back in the
On 15/04/2018 23:53, KarimAllah Ahmed wrote:
> + dst = vmcs12->pml_address + sizeof(u64) *
> vmcs12->guest_pml_index;
>
> - page = kvm_vcpu_gpa_to_page(vcpu, vmcs12->pml_address);
> - if (is_error_page(page))
> + if (kvm_write_guest_page(vcpu->kvm,
Hi Jacopo,
On Tue, Feb 20, 2018 at 4:12 PM, Jacopo Mondi wrote:
> Add compatible string for R-Car M3-N (r8a77965) in gpio-rcar.
>
> Signed-off-by: Jacopo Mondi
> Reviewed-by: Geert Uytterhoeven
Can you please resend to the GPIO maintainer?
Thanks!
Gr{oetje,eeting}s,
G
On 04/15/2018 11:22 PM, Tony Krowiak wrote:
> The VFIO AP device model exploits interpretive execution of AP
> instructions (APIE) to provide guests passthrough access to AP
> devices. This patch introduces a new interface to enable and
> disable APIE.
>
> Signed-off-by: Tony Krowiak
LGTM, but
On 16/04/2018 12:51, Pierre Morel wrote:
On 15/04/2018 23:22, Tony Krowiak wrote:
The VFIO AP device model exploits interpretive execution of AP
instructions (APIE) to provide guests passthrough access to AP
devices. This patch introduces a new interface to enable and
disable APIE.
Signed-off-b
On Sat, Apr 14, 2018 at 8:25 PM, Linus Torvalds
wrote:
> Coming back to this now that the merge window is almost over ]
>
> On Mon, Mar 26, 2018 at 1:46 AM, Dmitry Vyukov wrote:
>>
>> I've switched emails to links instead of attachments, here are few
>> recent examples:
>> https://lkml.org/lkml/2
On Fri, 13 Apr 2018, Joe Lawrence wrote:
> On 04/13/2018 07:20 AM, Miroslav Benes wrote:
> > Hi,
> >
> > On Thu, 12 Apr 2018, Joe Lawrence wrote:
> >
> >> Add a few livepatch modules and simple target modules that the included
> >> regression suite can run tests against.
> >
> > Could you inclu
On Mon, 2018-04-09 at 22:37 +0800, Yixun Lan wrote:
> We try to refactor the common code into one dedicated file,
> while preparing to add new Meson-AXG aoclk driver, this would
> help us to better share the code by all aoclk drivers.
>
> Suggested-by: Jerome Brunet
> Signed-off-by: Yixun Lan
>
On 2018-04-16 09:52, Ladislav Michl wrote:
> dma_map_single doesn't get the proper DMA address for vmalloced area,
Which is not a big surprise as vmalloc will allocate contiguous virtual
memory (which might corresponds to non-contiguous physical memory). Even
if you somehow get the physical addr
On Sun, Apr 15, 2018 at 12:32:29AM -0700, Christoph Hellwig wrote:
> On Fri, Apr 13, 2018 at 12:19:27PM +0100, Mark Brown wrote:
> > On Thu, Apr 12, 2018 at 11:14:35PM +0200, Peter Rosin wrote:
> > > @@ -1,3 +1,4 @@
> > > +// SPDX-License-Identifier: GPL-2.0
> > > /*
> > > * Driver for the MAX9
Hello.
On Fri, Mar 23, 2018 at 9:42 AM, Oleksandr Natalenko
wrote:
>> Actually, rechecking the bug description, I might have rushed. The bug that
>> I encountered is related to the vunmap() but it is only caused when batching
>> is off, while the bug you reported has batching on.
>>
>> It seems t
The existing API allows to pass a sample data to initialize the shadow
data. It works well when the data are position independent. But it fails
miserably when we need to set a pointer to the shadow structure itself.
Unfortunately, we might need to initialize the pointer surprisingly
often because
We might need to do some actions before the shadow variable is freed.
For example, we might need to remove it from a list or free some data
that it points to.
This is already possible now. The user can get the shadow variable
by klp_shadow_get(), do the necessary actions, and then call
klp_shadow_
Nikolai started to use shadow variables and found that list_head
is not initialized correctly using the existing API.
The problem is that LIST_HEAD_INIT() set pointers to itself.
klp_shadow_alloc() then copies these pointers to another location.
It would be possible to solve this by a late initia
Hi Dominique,
Thanks for your quick reply and comment.
在 2018年4月16日，下午3:56，Dominique Martinet 写道：
>
> Chengguang Xu wrote on Mon, Apr 16, 2018:
>> default:
>> +p9_debug(P9_DEBUG_ERROR,
>> +"unrecognized mount option \"%s\" or missing
The patch
ASoC: max9860: switch to SPDX license tag
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Lin
The patch
ASoC: tfa9879: switch to SPDX license tag
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Lin
The patch
ASoC: tfa9879: switch to using .probe_new
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Lin
The patch
ASoC: tfa9879: fix whitespace issues caused by mindless conversion
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
On 04/16/2018 08:23 AM, Christian Borntraeger wrote:
> FWIW, this breaks at least perf capability to resolve module symbols.
> Adding some more CCs for perf and module.
>
>
> On 04/16/2018 07:51 AM, Thomas-Mich Richter wrote:
>> I just installed 4.16.0 and discovered the module .text address is
>
On Fri 13-04-18 10:37:16, Johannes Weiner wrote:
> On Fri, Apr 13, 2018 at 04:28:21PM +0200, Michal Hocko wrote:
> > On Fri 13-04-18 16:20:00, Vlastimil Babka wrote:
> > > We would need kmalloc-reclaimable-X variants. It could be worth it,
> > > especially if we find more similar usages. I suspect
On Mon, Apr 16, 2018 at 11:34:03AM +0200, Romain Izard wrote:
> When converting to GPIO descriptors, gpiod_get_value automatically
> handles the line inversion flags from the device tree.
Thanks, I totally missed it.
Regards
>
> Do not invert the line twice.
>
> Fixes: 3df034081021fa4b6967ce33
On Mon, Apr 16, 2018 at 11:34:04AM +0200, Romain Izard wrote:
> The include defines the private platform_data structure used with AVR
> platforms. It has no user since 7c55984e191f. Remove it.
>
> Signed-off-by: Romain Izard
Acked-by: Ludovic Desroches
> ---
> drivers/usb/gadget/udc/atmel_usba_
On Mon, Apr 16, 2018 at 11:34:05AM +0200, Romain Izard wrote:
> Fix the fallout of the conversion to GPIO descriptors in 3df034081021.
>
> Signed-off-by: Romain Izard
Acked-by: Ludovic Desroches
> ---
> drivers/usb/gadget/udc/atmel_usba_udc.c | 18 +-
> 1 file changed, 9 inserti
On Mon, 2018-04-09 at 22:37 +0800, Yixun Lan wrote:
> From: Qiufang Dai
>
> Adds a Clock and Reset controller driver for the Always-On part
> of the Amlogic Meson-AXG SoC.
>
> Signed-off-by: Qiufang Dai
> Signed-off-by: Yixun Lan
> ---
> drivers/clk/meson/Kconfig | 1 +
> drivers/clk/me
On 04/16/2018 01:13 PM, Pierre Morel wrote:
> On 16/04/2018 12:51, Pierre Morel wrote:
>> On 15/04/2018 23:22, Tony Krowiak wrote:
>>> The VFIO AP device model exploits interpretive execution of AP
>>> instructions (APIE) to provide guests passthrough access to AP
>>> devices. This patch introduc
Hi all,
We have observed kernel panics on several master kubernetes clusters, where we
run
kubernetes API services and not application workloads.
Those clusters use kernel version 4.14.14 and 4.14.32, but we switched
everything
to kernel version 4.14.32 as a way to address the issue.
We have H
On 2018 Apr 14, Johannes Hirte wrote:
> On 2018 Feb 01, Yazen Ghannam wrote:
> > From: Yazen Ghannam
> >
> > The block address is saved after the block is initialized when
> > threshold_init_device() is called.
> >
> > Use the saved block address, if available, rather than trying to
> > rediscov
On Mon, Apr 16, 2018 at 02:46:40PM +0800, sxauwsk wrote:
> In case of xspi work in busy condition, may send bytes failed.
> once something wrong, spi controller did't work any more
>
> My test found this situation appear in both of read/write process.
> so when TX FIFO is full, add one byte delay
On Mon, Apr 16, 2018 at 11:43:02AM +0200, Jiri Kosina wrote:
> On Thu, 12 Apr 2018, Kirill A. Shutemov wrote:
>
> > > Commits 9b46a051e4 ("x86/mm: Initialize vmemmap_base at boot-time") and
> > > a7412546d8 ("x86/mm: Adjust vmalloc base and size at boot-time") lost the
> > > type information for
On Mon, 16 Apr 2018 11:48:09 +0200,
David Wang wrote:
>
> This patch is used to tell kernel that new VIA HDAC controller also
> support no-snoop path.
>
> Signed-off-by: David Wang
Applied now. Thanks.
Takashi
Hi Gabriel,
On 03/15/2018 08:18 AM, gabriel.fernan...@st.com wrote:
From: Gabriel Fernandez
This patch enables stm32mp1 clock driver.
Signed-off-by: Gabriel Fernandez
Applied on stm32-next.
Thanks.
Alex
The patch
ASoC: tfa9879: switch to SPDX license tag
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Lin
The patch
ASoC: max9860: switch to SPDX license tag
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Lin
On Sat, Apr 14, 2018 at 5:26 PM, Tetsuo Handa
wrote:
> OK. The patch was sent to linux.git as commit 1e047eaab3bb5564.
>
> #syz fix: block/loop: fix deadlock after loop_set_status
>
> Dmitry Vyukov " wrote:
>> On Tue, Apr 10, 2018 at 3:04 PM, Tetsuo Handa
>> wrote:
>> > Dmitry Vyukov wrote:
>> >>
Sorry for the delay. Things are pretty hectic at the moment.
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git ib-mfd-hwmo
The patch
ASoC: fsl_esai: Add freq check in set_dai_sysclk()
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and se
On 16/04/2018 12:11, Bartlomiej Zolnierkiewicz wrote:
> From: Marek Szyprowski
>
> When thermal sensor is not yet enabled, reading temperature might return
> random value. This might even result in stopping system booting when such
> temperature is higher than the critical value. Fix this by chec
The patch
regulator: ab8500: Drop AB8540/9540 support
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
On 04/16/2018 01:41 PM, Michal Hocko wrote:
> On Fri 13-04-18 10:37:16, Johannes Weiner wrote:
>> On Fri, Apr 13, 2018 at 04:28:21PM +0200, Michal Hocko wrote:
>>> On Fri 13-04-18 16:20:00, Vlastimil Babka wrote:
We would need kmalloc-reclaimable-X variants. It could be worth it,
especial
Ok, confusion around backend is I think cleared up. The other
confusion seems to be around dma-buf:
dma-buf is the cross subsystem zerocopy abstraction. PRIME is the
drm-specific support for it, 100% based on top of the generic struct
dma_buf.
You need a dma_buf exporter to convert a xen grant re
On 4/13/2018 5:31 PM, Anshuman Khandual wrote:
On 04/13/2018 05:03 PM, Chintan Pandya wrote:
Client can call vunmap with some intermediate 'addr'
which may not be the start of the VM area. Entire
unmap code works with vm->vm_start which is proper
but debug object API is called with 'addr'. Thi
On Mon, 2018-04-16 at 13:10 +0200, Paolo Bonzini wrote:
> On 15/04/2018 23:53, KarimAllah Ahmed wrote:
> >
> > Guest memory can either be directly managed by the kernel (i.e. have a
> > "struct
> > page") or they can simply live outside kernel control (i.e. do not have a
> > "struct page"). KVM m
On Wed, Apr 11, 2018 at 08:38:37PM -0500, Rob Landley wrote:
> You can build a kernel in a cross compiling environment that doesn't have perl
> in the $PATH. Commit 429f7a062e3b broke that for 32 bit arm. Fix it.
>
> Signed-off-by: Rob Landley
> ---
>
> arch/arm/boot/compressed/Makefile |9
On Mon, 16 Apr 2018 10:44:53 +0200
Pierre Morel wrote:
> On 15/04/2018 23:22, Tony Krowiak wrote:
> > If the AP instructions are not available on the linux host, then
> > AP devices can not be interpreted by the SIE. The AP bus has a
> > function it uses to determine if the AP instructions are
>
On 16/04/2018 12:10, Viresh Kumar wrote:
> On 16-04-18, 12:03, Daniel Lezcano wrote:
>> On 16/04/2018 11:50, Viresh Kumar wrote:
>>> On 16-04-18, 11:45, Daniel Lezcano wrote:
Can you elaborate a bit ? I'm not sure to get the point.
>>>
>>> Sure. With your current code on Hikey960 (big/LITTLE),
On 16/04/2018 12:11, Bartlomiej Zolnierkiewicz wrote:
> From: Marek Szyprowski
>
> tmu_read() in case of Exynos4210 might return error for out of bound
> values. Current code ignores such value, what leads to reporting critical
> temperature value. Add proper error code propagation to exynos_get_
On Mon, Apr 16, 2018 at 12:12 PM, Bartlomiej Zolnierkiewicz
wrote:
> Remove no longer needed samsung thermal properties.
>
> There should be no functional changes caused by this patch.
>
> Signed-off-by: Bartlomiej Zolnierkiewicz
> ---
> arch/arm/boot/dts/exynos3250.dtsi | 2 +-
Older Tegra's do not support planes z position handling in hardware,
but HW provides knobs for zPos implementation in software.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/tegra/dc.c| 134 ---
drivers/gpu/drm/tegra/plane.c | 193 --
This patchset adds new custom plane / CRTC properties that are very useful
for displaying video overlay, they will be used by Opentegra Xorg driver.
Also generic zPos property is implemented for older Tegra's.
Dmitry Osipenko (4):
drm/tegra: plane: Implement zPos plane property for older Tegra's
Colorkey'ing allows to draw on top of overlapping planes, like for example
on top of a video plane. Older Tegra's have a limited colorkey'ing
capability such that blending features are reduced when colorkey'ing is
enabled. In particular dependent weighting isn't possible, meaning that
cursors plane
This new property allows userspace to apply custom color conversion
coefficients per plane, making possible to utilize display controller
for color adjustments of a video overlay.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/tegra/dc.c| 86 +++
drivers/g
Older Tegra's support blending. Rename SoC info entry supports_blending
to legacy_blending to eliminate confusion.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/tegra/dc.c | 20 ++--
drivers/gpu/drm/tegra/dc.h | 2 +-
2 files changed, 11 insertions(+), 11 deletions(-)
diff
On Monday, April 16, 2018 02:06:41 PM Daniel Lezcano wrote:
> On 16/04/2018 12:11, Bartlomiej Zolnierkiewicz wrote:
> > From: Marek Szyprowski
> >
> > When thermal sensor is not yet enabled, reading temperature might return
> > random value. This might even result in stopping system booting when
On 16/04/2018 12:11, Bartlomiej Zolnierkiewicz wrote:
> From: Maciej Purski
>
> Device context's field data->soc is currently obtained by comparing
> of_compatible's. Provide soc_type as .data field in device's match
> table, as it is done in most drivers.
>
> Signed-off-by: Maciej Purski
> Sig
On 04/16/2018 07:09 AM, Russell King - ARM Linux wrote:
> On Wed, Apr 11, 2018 at 08:38:37PM -0500, Rob Landley wrote:
>> You can build a kernel in a cross compiling environment that doesn't have
>> perl
>> in the $PATH. Commit 429f7a062e3b broke that for 32 bit arm. Fix it.
...
> This looks more
On Fri, 30 Mar 2018, Fabrice Gasnier wrote:
> STM32 Timers can support up to 7 DMA requests:
> - 4 channels, update, compare and trigger.
> Optionally request part, or all DMAs from stm32-timers MFD core.
>
> Also add routine to implement burst reads using DMA from timer registers.
> This is expo
On Fri, 30 Mar 2018, Fabrice Gasnier wrote:
> Add support for DMAs to STM32 timers. STM32 Timers can support up to 7
> dma requests: up to 4 channels, update, compare and trigger.
> DMAs may be used to transfer data from pwm capture for instance.
> DMA support is made optional, PWM capture support
On Mon, 16 Apr 2018, Lee Jones wrote:
> On Fri, 30 Mar 2018, Fabrice Gasnier wrote:
>
> > Add support for DMAs to STM32 timers. STM32 Timers can support up to 7
> > dma requests: up to 4 channels, update, compare and trigger.
> > DMAs may be used to transfer data from pwm capture for instance.
>
On Fri, 30 Mar 2018, Fabrice Gasnier wrote:
> Add support for PMW input mode on pwm-stm32. STM32 timers support
> period and duty cycle capture as long as they have at least two PWM
> channels. One capture channel is used for period (rising-edge), one
> for duty-cycle (falling-edge).
> When there'
On Mon, 16 Apr 2018, Daniel Vetter wrote:
> On Thu, Apr 12, 2018 at 07:54:10AM +0200, Julia Lawall wrote:
> > From: Fengguang Wu
> >
> > Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference() and
> > drm_*_unreference() helpers.
> >
> > Generated by: scripts/coccinelle/api/drm-g
On 16/04/18 08:24, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> Introduce skeleton of the para-virtualized Xen sound
> frontend driver.
>
> Initial handling for Xen bus states: implement
> Xen bus state machine for the frontend driver according to
> the state diagram and re
On Fri, 30 Mar 2018, Fabrice Gasnier wrote:
> Using input prescaler, capture unit will trigger DMA once every
> configurable /2, /4 or /8 events (rising edge). This helps improve
> period (only) capture accuracy at high rates.
>
> Signed-off-by: Fabrice Gasnier
> Reviewed-by: Benjamin Gaignard
On 16/04/2018 14:09, Raslan, KarimAllah wrote:
>> I assume the caching will also be a separate patch.
> Yup, do you want me to include it in this one? I already have it, I
> just thought that I get those bits out first.
It's the same for me.
Paolo
>> It looks good except that I'd squash patches
On Mon 16-04-18 14:06:21, Vlastimil Babka wrote:
> On 04/16/2018 01:41 PM, Michal Hocko wrote:
> > On Fri 13-04-18 10:37:16, Johannes Weiner wrote:
> >> On Fri, Apr 13, 2018 at 04:28:21PM +0200, Michal Hocko wrote:
> >>> On Fri 13-04-18 16:20:00, Vlastimil Babka wrote:
> We would need kmalloc-
Hello! This is reroll v9 of the Steam Controller driver.
@Pierre-Loup, @Clément, could you please check if this driver is acceptable by
Valve? I think this could be the one ;-).
I've rolled back the synthetic LPAD diagonals. It happens that the actual
coordinates of the pads are rotated about 15
The wireless Steam Controller is battery operated, so add the battery
device and power information.
---
drivers/hid/hid-steam.c | 141 +++-
1 file changed, 140 insertions(+), 1 deletion(-)
diff --git a/drivers/hid/hid-steam.c b/drivers/hid/hid-steam.c
index 36f
There are two ways to connect the Steam Controller: directly to the USB
or with the USB wireless adapter. Both methods are similar, but the
wireless adapter can connect up to 4 devices at the same time.
The wired device will appear as 3 interfaces: a virtual mouse, a virtual
keyboard and a custom
On Mon, Apr 16, 2018 at 03:20:06PM +0530, Viresh Kumar wrote:
> On 16-04-18, 11:45, Daniel Lezcano wrote:
> > Can you elaborate a bit ? I'm not sure to get the point.
>
> Sure. With your current code on Hikey960 (big/LITTLE), you end up
> creating two cooling devices, one for the big cluster and o
> Subject: Re: [kbuild-all] [PATCH] drm: fix drm-get-put.cocci warnings
>
> On Thu, Apr 12, 2018 at 07:54:10AM +0200, Julia Lawall wrote:
> > From: Fengguang Wu
> >
> > Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference() and
> > drm_*_unreference() helpers.
> >
> > Generated by
On Mon, Apr 16, 2018 at 02:10:30PM +0200, Daniel Lezcano wrote:
> On 16/04/2018 12:10, Viresh Kumar wrote:
> > On 16-04-18, 12:03, Daniel Lezcano wrote:
> >> On 16/04/2018 11:50, Viresh Kumar wrote:
> >>> On 16-04-18, 11:45, Daniel Lezcano wrote:
> Can you elaborate a bit ? I'm not sure to get
On Mon, Apr 16, 2018 at 02:10:30PM +0200, Daniel Lezcano wrote:
> On 16/04/2018 12:10, Viresh Kumar wrote:
> > On 16-04-18, 12:03, Daniel Lezcano wrote:
> >> On 16/04/2018 11:50, Viresh Kumar wrote:
> >>> On 16-04-18, 11:45, Daniel Lezcano wrote:
> Can you elaborate a bit ? I'm not sure to get
On Mon, Apr 16, 2018 at 05:26:56PM +0800, David Wang wrote:
> PCI bridges integrated in new VIA chipset/SoC have no DAC issue.
> Enable DAC for the platforms with these chipset/SoC can improve DMA
> performance about
> 20% when DRAM size > 4GB.
>
So we get an exception to an exception? Is there
On Monday, April 16, 2018 02:16:56 PM Daniel Lezcano wrote:
> On 16/04/2018 12:11, Bartlomiej Zolnierkiewicz wrote:
> > From: Marek Szyprowski
> >
> > tmu_read() in case of Exynos4210 might return error for out of bound
> > values. Current code ignores such value, what leads to reporting critical
On 16/04/2018 14:17, Bartlomiej Zolnierkiewicz wrote:
> On Monday, April 16, 2018 02:06:41 PM Daniel Lezcano wrote:
>> On 16/04/2018 12:11, Bartlomiej Zolnierkiewicz wrote:
>>> From: Marek Szyprowski
>>>
>>> When thermal sensor is not yet enabled, reading temperature might return
>>> random value.
On Tue, Apr 03, 2018 at 08:08:32PM +0200, Daniel Vetter wrote:
> I did not mean you should dma_map_sg/page. I just meant that using
> dma_map_resource to fill only the dma address part of the sg table seems
> perfectly sufficient.
But that is not how the interface work, especially facing sg_dma_le
On Monday, April 16, 2018 02:19:30 PM Daniel Lezcano wrote:
> On 16/04/2018 12:11, Bartlomiej Zolnierkiewicz wrote:
> > From: Maciej Purski
> >
> > Device context's field data->soc is currently obtained by comparing
> > of_compatible's. Provide soc_type as .data field in device's match
> > table,
On 16/04/2018 14:35, Bartlomiej Zolnierkiewicz wrote:
> On Monday, April 16, 2018 02:16:56 PM Daniel Lezcano wrote:
>> On 16/04/2018 12:11, Bartlomiej Zolnierkiewicz wrote:
>>> From: Marek Szyprowski
>>>
>>> tmu_read() in case of Exynos4210 might return error for out of bound
>>> values. Current c
Hey Guenter,
On 04/13/2018 07:56 PM, Guenter Roeck wrote:
On Fri, Apr 13, 2018 at 05:40:18PM +, Vitaly Wool wrote:
On Fri, Apr 13, 2018, 7:35 PM Guenter Roeck wrote:
On Fri, Apr 13, 2018 at 05:21:02AM +, Vitaly Wool wrote:
Hi Guenter,
Den fre 13 apr. 2018 kl 00:01 skrev Guenter R
The commit that switches x86 to dma_direct_ops stopped using and building
this file, but accidentally left it in the tree. Remove it.
Signed-off-by: Christoph Hellwig
---
arch/x86/kernel/pci-nommu.c | 90 -
1 file changed, 90 deletions(-)
delete mode 100644
On 04/16/2018 02:22 PM, Lee Jones wrote:
> On Fri, 30 Mar 2018, Fabrice Gasnier wrote:
>
>> STM32 Timers can support up to 7 DMA requests:
>> - 4 channels, update, compare and trigger.
>> Optionally request part, or all DMAs from stm32-timers MFD core.
>>
>> Also add routine to implement burst rea
On 16/04/2018 14:41, Bartlomiej Zolnierkiewicz wrote:
> On Monday, April 16, 2018 02:19:30 PM Daniel Lezcano wrote:
>> On 16/04/2018 12:11, Bartlomiej Zolnierkiewicz wrote:
>>> From: Maciej Purski
>>>
>>> Device context's field data->soc is currently obtained by comparing
>>> of_compatible's. Prov
On Monday, April 16, 2018 02:41:48 PM Daniel Lezcano wrote:
> On 16/04/2018 14:35, Bartlomiej Zolnierkiewicz wrote:
> > On Monday, April 16, 2018 02:16:56 PM Daniel Lezcano wrote:
> >> On 16/04/2018 12:11, Bartlomiej Zolnierkiewicz wrote:
> >>> From: Marek Szyprowski
> >>>
> >>> tmu_read() in case
On 16/04/2018 14:31, Sudeep Holla wrote:
> On Mon, Apr 16, 2018 at 02:10:30PM +0200, Daniel Lezcano wrote:
>> On 16/04/2018 12:10, Viresh Kumar wrote:
>>> On 16-04-18, 12:03, Daniel Lezcano wrote:
On 16/04/2018 11:50, Viresh Kumar wrote:
> On 16-04-18, 11:45, Daniel Lezcano wrote:
>> C
On Thu 2018-04-12 10:54:31, Joe Lawrence wrote:
> Add a few livepatch modules and simple target modules that the included
> regression suite can run tests against.
>
>
> diff --git a/Documentation/livepatch/callbacks.txt
> b/Documentation/livepatch/callbacks.txt
> index c9776f48e458..6ca2801a6bb
On 16/04/2018 12:11, Bartlomiej Zolnierkiewicz wrote:
> Remove unused "type" field from struct exynos_tmu_platform_data.
>
> There should be no functional changes caused by this patch.
>
> Signed-off-by: Bartlomiej Zolnierkiewicz
> ---
Reviewed-by: Daniel Lezcano
> drivers/thermal/samsung/e
On 16/04/2018 14:49, Bartlomiej Zolnierkiewicz wrote:
> On Monday, April 16, 2018 02:41:48 PM Daniel Lezcano wrote:
>> On 16/04/2018 14:35, Bartlomiej Zolnierkiewicz wrote:
>>> On Monday, April 16, 2018 02:16:56 PM Daniel Lezcano wrote:
On 16/04/2018 12:11, Bartlomiej Zolnierkiewicz wrote:
>>>
On 16/04/18 08:24, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> Read configuration values from Xen store according
> to xen/interface/io/sndif.h protocol:
> - introduce configuration structures for different
> components, e.g. sound card, device, stream
> - read PCM
On 16/04/2018 12:11, Bartlomiej Zolnierkiewicz wrote:
> Trimming (one point based or two points based) is always used for
> the temperature calibration and the default non-trimming code is
> never reached. Remove it and then remove no longer needed parsing
> of samsung,tmu_default_temp_offset prope
... with and without platform ID.
Signed-off-by: Lee Jones
Acked-by: Linus Walleij
---
drivers/mfd/ab8500-core.c | 138 ++
1 file changed, 42 insertions(+), 96 deletions(-)
diff --git a/drivers/mfd/ab8500-core.c b/drivers/mfd/ab8500-core.c
index 30d0
... with and without 'resources'.
Signed-off-by: Lee Jones
Acked-by: Linus Walleij
---
drivers/mfd/db8500-prcmu.c | 24 +++-
1 file changed, 7 insertions(+), 17 deletions(-)
diff --git a/drivers/mfd/db8500-prcmu.c b/drivers/mfd/db8500-prcmu.c
index 5970b8def548..91259addab5
Not a lot to it really. The idea is to save lines.
Lee Jones (3):
mfd: Provide MACRO to declare commonly defined MFD cell attributes
mfd: ab8500: Example using new OF_MFD_CELL MACRO
mfd: db8500-prcmu: Example using new OF_MFD_CELL/MFD_CELL_BASIC MACROs
drivers/mfd/ab8500-core.c | 138 +++
On 16/04/2018 12:11, Bartlomiej Zolnierkiewicz wrote:
> All SoCs use the same values (25, 85) for trim points (except
> Exynos5440 which currently specifices value 70 for the second trim
> point -> it seems to be a mistake because documentation uses value
> 85 and two points based trimming has neve
201 - 300 of 1099 matches
Mail list logo
