From: Jérôme Glisse
Convert ODP to use HMM so that we can build on common infrastructure
for different class of devices that want to mirror a process address
space into a device. There is no functional changes.
Signed-off-by: Jérôme Glisse
Cc: linux-r...@vger.kernel.org
Cc: Jason Gunthorpe
Cc:
From: Jérôme Glisse
This patchset convert RDMA ODP to use HMM underneath this is motivated
by stronger code sharing for same feature (share virtual memory SVM or
Share Virtual Address SVA) and also stronger integration with mm code to
achieve that. It depends on HMM patchset posted for inclusion
On 1/29/19 8:57 AM, Srinivas Kandagatla wrote:
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?h=for-5.1&id=a8233b6c1972e1959cf84a021aeb61ddcd23cc26
>
> This should fix the issue! It should be in next today!
Looks good. Thanks.
> Thanks,
> srini
>
>
> On 29/0
On Tue, Jan 29, 2019 at 08:48:13AM -0800, Tony Lindgren wrote:
> regulator-dummy: Underflow of regulator enable count
> Are these bogus warnings for dummy regulator or do we have
> real unpaired regulator calls or somewhere?
Given that this is a new warning my first guess would be that it's
legi
> > Hi
> >
> > This points to an issue with the Generic 10G PHY driver. The following
> > patch seems to be missing from the 4.19 stable tree and should be merged:
> > f802912 net: phy: genphy_10g_driver: Avoid NULL pointer dereference
>
> But that patch says it:
> Fixes: 719655a14971 ("net: phy
On Tue, Jan 29, 2019 at 03:26:26PM +0200, Joel Nider wrote:
> Add a new handler for new uverb reg_remote_mr. The purpose is to register
> a memory region in a different address space (i.e. process) than the
> caller.
>
> The main use case which motivated this change is post-copy container
> migrat
On 1/28/19 10:11 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190125:
>
on x86_64:
ld: security/safesetid/lsm.o:(.data+0x10): undefined reference to
`security_hook_heads'
ld: security/safesetid/lsm.o:(.data+0x38): undefined reference to
`security_hook_heads'
ld: security/safeseti
Hi,
On Tue, Jan 29, 2019 at 8:48 AM Tony Lindgren wrote:
>
> Hi,
>
> Looks like commit 5451781dadf8 ("regulator: core: Only count load for
> enabled consumers") started showing new warnings with v5.0-rc cycle:
>
> regulator-dummy: Underflow of regulator enable count
>
> I'm seeing this at least w
On Tue, Jan 29, 2019 at 10:19:59AM -0600, Gustavo A. R. Silva wrote:
> Yeah. But I don't want to send patches to every person that has touched the
> file.
Yes but you should *definitely* CC supporters and reviewers.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting
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 {
int stuff;
struct boo entry[];
};
instance = kvzalloc(sizeof(stru
Fix incorrect event names for the Load_Miss_Real_Latency metric for
Cascadelake server in the same manner as commit 91b2b97025 for SKL/SKX.
Signed-off-by: William Cohen
---
tools/perf/pmu-events/arch/x86/cascadelakex/clx-metrics.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
Hi Krzysztof,
On 1/29/19 4:13 PM, Krzysztof Kozlowski wrote:
> On Mon, 28 Jan 2019 at 20:21, Lukasz Luba wrote:
>>
>> Add description of Dynamic Memory Controller and PPMU counters.
>> They are used by exynos5-dmc driver.
>>
>> CC: Rob Herring
>> CC: Mark Rutland
>> CC: Kukjin Kim
>> CC: Krzys
This adds optional regulator support to the pwm-fan driver. This is
necessary for pwm fans which are powered by a switchable supply.
Signed-off-by: Stefan Wahren
---
drivers/hwmon/pwm-fan.c | 35 +++
1 file changed, 35 insertions(+)
diff --git a/drivers/hwmon/pwm
This adds an optional regulator support (e.g. switchable supply) to the
pwm fan binding.
Signed-off-by: Stefan Wahren
---
Documentation/devicetree/bindings/hwmon/pwm-fan.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/hwmon/pwm-fan.txt
b/Documentatio
Hello,
With Christoph's rework of the DMA API that recently landed, the patch
below is the only change needed in virtio to make it work in a POWER
secure guest under the ultravisor.
The other change we need (making sure the device's dma_map_ops is NULL
so that the dma-direct/swiotlb code is use
On 1/29/19 11:04 AM, Borislav Petkov wrote:
> On Tue, Jan 29, 2019 at 10:19:59AM -0600, Gustavo A. R. Silva wrote:
>> Yeah. But I don't want to send patches to every person that has touched the
>> file.
>
> Yes but you should *definitely* CC supporters and reviewers.
>
Okay. I'll take note o
* Doug Anderson [190129 17:05]:
> Hi,
>
> On Tue, Jan 29, 2019 at 8:48 AM Tony Lindgren wrote:
> >
> > Hi,
> >
> > Looks like commit 5451781dadf8 ("regulator: core: Only count load for
> > enabled consumers") started showing new warnings with v5.0-rc cycle:
> >
> > regulator-dummy: Underflow of
On 29/01/2019 15:44, Keith Busch wrote:
On Tue, Jan 29, 2019 at 03:25:48AM -0800, John Garry wrote:
Hi,
I have a question on $subject which I hope you can shed some light on.
According to commit c5cb83bb337c25 ("genirq/cpuhotplug: Handle managed
IRQs on CPU hotplug"), if we offline the last CP
On Fri, Jan 25, 2019 at 11:59:00AM -0800, Tony Luck wrote:
> From: Qiuxu Zhuo
>
> Part of the skx_edac driver codes are carved to the skx_comm_edac.c
> file, which are used by both skx_edac driver and i10nm_edac driver.
> Delete the duplicated codes from the skx_edac.c file and rename
> skx_edac.
On Tue, Jan 29, 2019 at 09:43:38AM +0100, Joerg Roedel wrote:
> From: Joerg Roedel
>
> The function returns the maximum size that can be remapped
> by the SWIOTLB implementation. This function will be later
> exposed to users through the DMA-API.
>
> Reviewed-by: Konrad Rzeszutek Wilk
> Signed-
On Tue, Jan 29, 2019 at 09:43:40AM +0100, Joerg Roedel wrote:
> From: Joerg Roedel
>
> The function returns the maximum size that can be mapped
> using DMA-API functions. The patch also adds the
> implementation for direct DMA and a new dma_map_ops pointer
> so that other implementations can expo
On Tue, Jan 29, 2019 at 09:43:42AM +0100, Joerg Roedel wrote:
> From: Joerg Roedel
>
> Segments can't be larger than the maximum DMA mapping size
> supported on the platform. Take that into account when
> setting the maximum segment size for a block device.
>
> Reviewed-by: Konrad Rzeszutek Wilk
On Tue, Jan 29, 2019 at 09:11:51AM -0800, Tony Lindgren wrote:
> OK. Let's see if Sebastian spots where pwm_vibrator_start()
> and pwm_vibrator_stop() might get called multiple times
> or something similar.
Given that nobody has noticed that the driver stops working entirely
it's possible that th
The patch
regulator: max77650: add regulator 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 s
On 1/28/19 10:11 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190125:
>
on i386:
ld: security/integrity/digsig.o: in function `integrity_init_keyring':
digsig.c:(.init.text+0x14b): undefined reference to `set_platform_trusted_keys'
Full randconfig file is attached.
--
~Randy
#
On Mon, Jan 28, 2019 at 04:24:26PM -0500, Dennis Zhou wrote:
> As mentioned above, a requirement that differs zstd from zlib is that
> higher levels of compression require more memory. To manage this, each
> compression level has its own queue of workspaces. A global LRU is used
> to help with recl
dts at all
w2sg0004 bindings are in next-20190129
https://git.kernel.org/pub/scm/linux/kernel/git/johan/gnss gnss-next
arch/arm/boot/dts/omap3-gta04.dtsi | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi
b/arch/arm/boot/dts/omap3-gta04.dtsi
Hi Piotr,
On Tue, 29 Jan 2019 16:10:40 +
Piotr Sroka wrote:
> Signed-off-by: Piotr Sroka
> ---
> .../devicetree/bindings/mtd/cadence-nand.txt | 35
> ++
> 1 file changed, 35 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mtd/cadence-nand.tx
On Tue, Jan 29, 2019 at 05:12:40PM +, John Garry wrote:
> On 29/01/2019 15:44, Keith Busch wrote:
> >
> > Hm, we used to freeze the queues with CPUHP_BLK_MQ_PREPARE callback,
> > which would reap all outstanding commands before the CPU and IRQ are
> > taken offline. That was removed with commi
On Tue, Jan 29, 2019 at 09:43:39AM +0100, Joerg Roedel wrote:
> From: Joerg Roedel
>
> This function will be used from dma_direct code to determine
> the maximum segment size of a dma mapping.
>
> Reviewed-by: Konrad Rzeszutek Wilk
> Signed-off-by: Joerg Roedel
Looks good,
Reviewed-by: Chris
Hi,
On Tue, Jan 29, 2019 at 08:48:13AM -0800, Tony Lindgren wrote:
> Looks like commit 5451781dadf8 ("regulator: core: Only count load for
> enabled consumers") started showing new warnings with v5.0-rc cycle:
>
> regulator-dummy: Underflow of regulator enable count
>
> I'm seeing this at least
* Mark Brown [190129 17:15]:
> On Tue, Jan 29, 2019 at 09:11:51AM -0800, Tony Lindgren wrote:
>
> > OK. Let's see if Sebastian spots where pwm_vibrator_start()
> > and pwm_vibrator_stop() might get called multiple times
> > or something similar.
>
> Given that nobody has noticed that the driver
The patch
dt-bindings: regulator: add DT bindings for max77650
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 ho
On 2019-01-29 16:10:58 [+0100], Heiko Carstens wrote:
> Finally... the trace output is quite large with 26 MB... Therefore an
> xz compressed attachment. Hope that's ok.
>
> The kernel used was linux-next 20190129 + your patch.
|ld64.so.1-10237 [006] 14232.031726
Sargu reported a crash:
"I picked up c40f7d74c741a907cfaeb73a7697081881c497d0 sched/fair: Fix
infinite loop in update_blocked_averages() by reverting a9e7f6544b9c
and put it on top of 4.19.13. In addition to this, I uninlined
list_add_leaf_cfs_rq for debugging.
This revealed a new bu
On Tue, Jan 29, 2019 at 09:43:41AM +0100, Joerg Roedel wrote:
> From: Joerg Roedel
>
> This function returns the maximum segment size for a single
> dma transaction of a virtio device. The possible limit comes
> from the SWIOTLB implementation in the Linux kernel, that
> has an upper limit of (cu
The patch
regmap: Remove attribute packed from struct 'regcache_rbtree_node'
has been applied to the regmap tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the ne
On 1/16/19 3:29 AM, Eugeniy Paltsev wrote:
> Even though we do enable AD bit in arc_init_IRQ() we need to do
> it in early ASM code otherwise we may face unaligned data until
> we reach arc_init_IRQ() because GCC starting from v8.1.0 actively
> generates unaligned data as it assumes that:
> * ARCv
On Tue, Jan 29, 2019 at 05:57:38PM +0100, Holger Hoffstätte wrote:
> On 1/29/19 5:33 PM, Greg Kroah-Hartman wrote:
> > On Tue, Jan 29, 2019 at 04:05:16PM +, Camelia Alexandra Groza wrote:
> > > > -Original Message-
> > > > From: Holger Hoffstätte
> > > > Sent: Tuesday, January 29, 2019
On 29/01/2019 16:27, Thomas Gleixner wrote:
On Tue, 29 Jan 2019, John Garry wrote:
On 29/01/2019 12:01, Thomas Gleixner wrote:
If the last CPU which is associated to a queue (and the corresponding
interrupt) goes offline, then the subsytem/driver code has to make sure
that:
1) No more reque
On Tue, Jan 29, 2019 at 12:05:36PM -0500, William Cohen wrote:
> Fix incorrect event names for the Load_Miss_Real_Latency metric for
> Cascadelake server in the same manner as commit 91b2b97025 for SKL/SKX.
Reviewed-by: Andi Kleen
>
> Signed-off-by: William Cohen
> ---
> tools/perf/pmu-events
On Tue, Jan 29, 2019 at 11:45:43AM +0100, Arnaldo Carvalho de Melo wrote:
> Em Mon, Jan 28, 2019 at 09:40:28AM +0300, Alexey Budankov escreveu:
> > The patch set implements runtime trace compression for record mode and
> > trace file decompression for report mode. Zstandard API [1] is used for
>
Hi all,
Friendly ping:
Who can take this?
Thanks
--
Gustavo
On 1/7/19 5:01 PM, Song Liu wrote:
> On Mon, Jan 7, 2019 at 10:35 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
On Tue, 2019-01-29 at 09:21 -0800, Vineet Gupta wrote:
> On 1/16/19 3:29 AM, Eugeniy Paltsev wrote:
> > Even though we do enable AD bit in arc_init_IRQ() we need to do
> > it in early ASM code otherwise we may face unaligned data until
> > we reach arc_init_IRQ() because GCC starting from v8.1.0 ac
* Sebastian Reichel [190129 17:18]:
> Hi,
>
> On Tue, Jan 29, 2019 at 08:48:13AM -0800, Tony Lindgren wrote:
> > Looks like commit 5451781dadf8 ("regulator: core: Only count load for
> > enabled consumers") started showing new warnings with v5.0-rc cycle:
> >
> > regulator-dummy: Underflow of re
On Tue, Jan 29, 2019 at 12:34:37PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.19 release.
> There are 103 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me kno
On 1/29/19 9:26 AM, Eugeniy Paltsev wrote:
>> I presume there is no specific reason to include this conditionally.
>> irqflags.h already includes the right version.
> Agree.
> I've just forgotten about common irqflags.h
No need for this series. Given Alexey's request, I've pushed the minimal patch
On Tue, Jan 29, 2019 at 8:43 PM Maxime Ripard wrote:
>
> On Mon, Jan 28, 2019 at 03:06:10PM +0530, Jagan Teki wrote:
> > On Sat, Jan 26, 2019 at 2:54 AM Maxime Ripard
> > wrote:
> > >
> > > On Fri, Jan 25, 2019 at 01:28:49AM +0530, Jagan Teki wrote:
> > > > Minimum PLL used for MIPI is 500MHz, a
On Tue, 2019-01-29 at 09:28 -0800, Vineet Gupta wrote:
> On 1/29/19 9:26 AM, Eugeniy Paltsev wrote:
> > > I presume there is no specific reason to include this conditionally.
> > > irqflags.h already includes the right version.
> >
> > Agree.
> > I've just forgotten about common irqflags.h
>
> No
Hello,
syzbot found the following crash on:
HEAD commit:4aa9fc2a435a Revert "mm, memory_hotplug: initialize struct..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=168581ef40
kernel config: https://syzkaller.appspot.com/x/.config?x=4fceea9e2d99ac20
da
Hi all,
Friendly ping:
Who can take this?
Thanks
--
Gustavo
On 1/4/19 10:29 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
Read efi_page_tables debugfs triggering an out-of-bounds access here,
arch/arm64/mm/dump.c: 282
if (addr >= st->marker[1].start_address) {
from,
arch/arm64/mm/dump.c: 331
note_page(st, addr, 2, pud_val(pud));
because st->marker++ is is called after "UEFI runtime end" which is the
last element i
> On Mon, Jan 28, 2019 at 1:10 PM Elena Reshetova
> wrote:
> >
> > This adds an smp_acquire__after_ctrl_dep() barrier on successful
> > decrease of refcounter value from 1 to 0 for refcount_dec(sub)_and_test
> > variants and therefore gives stronger memory ordering guarantees than
> > prior versi
On Mon, Jan 28, 2019 at 05:45:28PM -0500, Joel Fernandes wrote:
> On Thu, Jan 24, 2019 at 12:56:48PM +0100, Uladzislau Rezki (Sony) wrote:
> > commit 763b218ddfaf ("mm: add preempt points into
> > __purge_vmap_area_lazy()")
> >
> > introduced some preempt points, one of those is making an
> > allo
Commit-ID: 691b9ab6c9676e5868a4787be9041dd990005311
Gitweb: https://git.kernel.org/tip/691b9ab6c9676e5868a4787be9041dd990005311
Author: Shaokun Zhang
AuthorDate: Tue, 29 Jan 2019 15:36:57 +0800
Committer: Borislav Petkov
CommitDate: Tue, 29 Jan 2019 18:32:30 +0100
x86/mm/tlb: Remove un
On Fri, Jan 25, 2019 at 07:34:31PM +0100, Heiner Kallweit wrote:
> On 25.01.2019 11:18, Thierry Reding wrote:
> > From: Thierry Reding
> >
> > If the system was booted using a device tree and if the device tree
> > contains a MAC address, use it instead of reading one from the EEPROM.
> > This is
From: Harini Katakam
Date: Tue, 29 Jan 2019 15:20:03 +0530
> The interrupt handler contains a workaround for RX hang applicable
> to Zynq and AT91RM9200 only. Subsequent versions do not need this
> workaround. This workaround unnecessarily resets RX whenever RX used
> bit read is observed, which
Fixing address of powerpc mailing list.
Thiago Jung Bauermann writes:
> Hello,
>
> With Christoph's rework of the DMA API that recently landed, the patch
> below is the only change needed in virtio to make it work in a POWER
> secure guest under the ultravisor.
>
> The other change we need (ma
On Wed, Jan 23, 2019 at 6:06 AM Yang Weijiang wrote:
> Note: Although these VMCS fields are 64-bit, they don't have high fields.
This statement directly contradicts the SDM, volume 3, appendix B.2:
"A value of 1 in bits 14:13 of an encoding indicates a 64-bit field.
There are 64-bit fields only
From: Jérôme Glisse
This patchset add support for peer to peer between device in two manner.
First for device memory use through HMM in process regular address space
(ie inside a regular vma that is not an mmap of device file or special
file). Second for special vma ie mmap of a device file, in t
From: Jérôme Glisse
device_test_p2p() return true if two devices can peer to peer to
each other. We add a generic function as different inter-connect
can support peer to peer and we want to genericaly test this no
matter what the inter-connect might be. However this version only
support PCIE for
From: Jérôme Glisse
device_test_p2p() return true if two devices can peer to peer to
each other. We add a generic function as different inter-connect
can support peer to peer and we want to genericaly test this no
matter what the inter-connect might be. However this version only
support PCIE for
From: Jérôme Glisse
Allow mmap of device file to export device memory to peer to peer
devices. This will allow for instance a network device to access a
GPU memory or to access a storage device queue directly.
The common case will be a vma created by userspace device driver
that is then share to
From: Jérôme Glisse
Special device vma (mmap of a device file) can correspond to device
driver object that some device driver might want to share with other
device (giving access to). This add support for HMM to map those
special device vma if the owning device (exporter) allows it.
Signed-off-b
From: Jérôme Glisse
Signed-off-by: Jérôme Glisse
Cc: Logan Gunthorpe
Cc: Greg Kroah-Hartman
Cc: Rafael J. Wysocki
Cc: Bjorn Helgaas
Cc: Christian Koenig
Cc: Felix Kuehling
Cc: Jason Gunthorpe
Cc: linux-...@vger.kernel.org
Cc: dri-de...@lists.freedesktop.org
Cc: Christoph Hellwig
Cc: Mare
Hi Jean-Philippe,
On 1/28/19 6:32 PM, Jean-Philippe Brucker wrote:
> Hi Eric,
>
> On 25/01/2019 16:49, Auger Eric wrote:
> [...]
diff --git a/include/uapi/linux/iommu.h b/include/uapi/linux/iommu.h
index 7a7cf7a3de7c..4605f5cfac84 100644
--- a/include/uapi/linux/iommu.h
+++ b/
Hi Quentin,
On Tue, Jan 29, 2019 at 09:03:34AM +, Quentin Perret wrote:
> Hi Matthias,
>
> On Monday 28 Jan 2019 at 11:02:51 (-0800), Matthias Kaehlcke wrote:
> > > +/**
> > > + * of_dev_pm_opp_get_cpu_power() - Estimates the power of a CPU
> > > + * @mW: pointer to the power estimat
Hi all,
This is v2 of the patch set which adds support of Dynamic Memory Controller
for Exynos5422 SoC.
The driver supports Dynamic Voltage and Frequency Scalling
for the DMC and DRAM. It also provides needed timings for different
speed operations of the DRAM memory.
The patch set is based on tag:
Enable driver for Dynamic Memory Controller dynamic frequency and
voltage scaling in Exynos5422 SoCs.
CC: Russell King
CC: Kukjin Kim
CC: Krzysztof Kozlowski
CC: Marek Szyprowski
CC: Guenter Roeck
CC: Benson Leung
CC: linux-arm-ker...@lists.infradead.org
CC: linux-samsung-...@vger.kernel.org
Define new IDs for clocks used by Dynamic Memory Controller in
Exynos5422 SoC.
CC: Sylwester Nawrocki
CC: Chanwoo Choi
CC: Rob Herring
CC: Mark Rutland
CC: Kukjin Kim
CC: Krzysztof Kozlowski
CC: linux-samsung-...@vger.kernel.org
CC: devicet...@vger.kernel.org
CC: linux-arm-ker...@lists.infra
This patch adds driver for Exynos5422 Dynamic Memory Controller.
The driver provides support for dynamic frequency and voltage scaling for
DMC and DRAM. It supports changing timings of DRAM running with different
frequency.
The patch also contains needed MAINTAINERS file update.
CC: MyungJoo Ham
This patch provides support for clocks needed for Dynamic Memory Controller
in Exynos5422 SoC. It adds CDREX base register addresses, new DIV, MUX and
GATE entries.
CC: Sylwester Nawrocki
CC: Chanwoo Choi
CC: Michael Turquette
CC: Stephen Boyd
CC: Kukjin Kim
CC: Krzysztof Kozlowski
CC: linux
Define new performance events supported by Exynos5422 SoC counters.
The counters are built-in in Dynamic Memory Controller and provide
information regarding memory utilization.
CC: Chanwoo Choi
CC: MyungJoo Ham
CC: Kyungmin Park
CC: Kukjin Kim
CC: Krzysztof Kozlowski
CC: linux...@vger.kernel.
Add description of Dynamic Memory Controller and PPMU counters.
They are used by exynos5422-dmc driver.
CC: Rob Herring
CC: Mark Rutland
CC: Kukjin Kim
CC: Krzysztof Kozlowski
CC: devicet...@vger.kernel.org
CC: linux-arm-ker...@lists.infradead.org
CC: linux-samsung-...@vger.kernel.org
CC: linu
The patch adds description for DT binding for a new Exynos5422 Dynamic
Memory Controller device.
It also contains needed MAINTAINERS file update.
CC: MyungJoo Ham
CC: Kyungmin Park
CC: Chanwoo Choi
CC: Rob Herring
CC: Mark Rutland
CC: Kukjin Kim
CC: Krzysztof Kozlowski
CC: linux...@vger.ker
Add new table rate for BPLL for Exynos5422 SoC supporting Dynamic Memory
Controller frequencies for driver's DRAM timings.
CC: Sylwester Nawrocki
CC: Chanwoo Choi
CC: Michael Turquette
CC: Stephen Boyd
CC: Kukjin Kim
CC: Krzysztof Kozlowski
CC: linux-samsung-...@vger.kernel.org
CC: linux-...
On Mon, Jan 28, 2019 at 04:24:27PM -0500, Dennis Zhou wrote:
> It is very easy to miss places that rely on a certain bitshifting for
> decyphering the type_level overloading. Make macros handle this instead.
>
> Signed-off-by: Dennis Zhou
Reviewed-by: Josef Bacik
Thanks,
Josef
On Mon, Jan 28, 2019 at 04:24:28PM -0500, Dennis Zhou wrote:
> This is in preparation for zstd compression levels. As each level will
> require different sized workspaces, workspaces_list is no longer a
> really fitting name.
>
> Signed-off-by: Dennis Zhou
> ---
Reviewed-by: Josef Bacik
Thanks
On Tue, Jan 29, 2019 at 9:47 AM Jim Mattson wrote:
>
> On Wed, Jan 23, 2019 at 6:06 AM Yang Weijiang wrote:
> > Note: Although these VMCS fields are 64-bit, they don't have high fields.
>
> This statement directly contradicts the SDM, volume 3, appendix B.2:
>
> "A value of 1 in bits 14:13 of an
On Mon, Jan 28, 2019 at 04:24:29PM -0500, Dennis Zhou wrote:
> While the heuristic workspaces aren't really compression workspaces,
> they use the same interface for managing them. So rather than branching,
> let's just handle them once again as the index 0 compression type.
>
> Signed-off-by: Den
On Tue, 29 Jan 2019 17:17:54 +0100 Uladzislau Rezki wrote:
> > > + resched_threshold = (int) lazy_max_pages() << 1;
> >
> > Is the typecast really needed?
> >
> > Perhaps resched_threshold shiould have unsigned long type and perhaps
> > vmap_lazy_nr should be atomic_long_t?
> >
> I think so. E
On Mon, Jan 28, 2019 at 04:24:30PM -0500, Dennis Zhou wrote:
> Make the workspace_manager own the interface operations rather than
> managing index-paired arrays for the workspace_manager and compression
> operations.
>
> Signed-off-by: Dennis Zhou
Reviewed-by: Josef Bacik
Thanks,
Josef
On Mon, Jan 28, 2019 at 04:24:31PM -0500, Dennis Zhou wrote:
> Workspace manager init and cleanup code is open coded inside a for loop
> over the compression types. This forces each compression type to rely on
> the same workspace manager implementation. This patch creates helper
> methods that wil
Thanks for review Peter!
On Tue, Jan 29, 2019 at 2:44 AM Peter Zijlstra wrote:
>
> On Thu, Jan 24, 2019 at 01:15:18PM -0800, Suren Baghdasaryan wrote:
> > static void psi_update_work(struct work_struct *work)
> > {
> > struct delayed_work *dwork;
> > struct psi_group *group;
> > +
Quoting Jerome Brunet (2019-01-28 10:04:20)
> Signed-off-by: Jerome Brunet
> ---
And also make clk-regmap.c a module? Having any commit text would be
good.
Quoting Jerome Brunet (2019-01-28 10:04:17)
> clk-provider.h provides clk_hw_is_prepared(), clk_hw_is_enabled() and
> clk_hw_is_prepared() but these symbols are not exported for the
> modules which prevents a clock driver using them to be compiled as
> a module. Export them to fix the problem.
>
>
On Tue, Jan 29, 2019 at 09:54:38AM +, Charles Keepax wrote:
> Hmm... I think this might need a little more investigation, it
> does indeed fail at present (amazing that it works upto exactly 1.2V
> which is common the usecase) but this feels more like a core
> problem. There are indeed only 57
On Mon, Jan 28, 2019 at 04:24:32PM -0500, Dennis Zhou wrote:
> There are two levels of workspace management. First, alloc()/free()
> which are responsible for actually creating and destroy workspaces.
> Second, at a higher level, get()/put() which is the compression code
> asking for a workspace fr
Quoting Jerome Brunet (2019-01-28 10:04:18)
> Use CONFIG_ARCH_MESON to let make enter the meson clock directory.
> As part of a rework, CONFIG_COMMON_CLK_AMLOGIC is about to be removed.
>
> Signed-off-by: Jerome Brunet
> ---
Acked-by: Stephen Boyd
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch fixes the following warnings:
drivers/net/can/peak_canfd/peak_pciefd_main.c:668:3: warning: this statement
may fall through [-Wimplicit-fallthrough=]
drivers/net/can/spi/mcp251
On Tue, 2019-01-22 at 14:51 +, Matthew Whitehead wrote:
> On Fri, Jan 18, 2019 at 9:07 PM tedheadster
> wrote:
> > I do not see this problem with the upstream kernel, so 3.16
> > probably
> > needs a missing upstream patch.
>
> This was indeed fixed by Andy Lutomirski's follow-up patch "x86/v
Quoting Jerome Brunet (2019-01-28 10:04:21)
> Signed-off-by: Jerome Brunet
> ---
Why?
On Tue, Jan 29, 2019 at 09:38:43AM +0100, Jonas Bonn wrote:
> Some devices are slow and cannot keep up with the SPI bus and therefore
> require a short delay between words of the SPI transfer.
This doesn't apply against current code, please rebase against for-next
and resend.
signature.asc
Descr
On Tue, 2019-01-29 at 10:04 -0800, Stephen Boyd wrote:
> Quoting Jerome Brunet (2019-01-28 10:04:20)
> > Signed-off-by: Jerome Brunet
> > ---
>
> And also make clk-regmap.c a module? Having any commit text would be
> good.
Stephen,
As stated in the cover-letter, this patch (and several others)
On 28.01.19 08:34, Christoph Hellwig wrote:
> On Sat, Jan 26, 2019 at 06:11:24PM +0100, Helge Deller wrote:
>> Thanks for doing that!
>> I tested it. Your patches work, but you need the fixup below (0-day
>> testing complained as well).
>
> I actually sent a v2 series since then which makes sure t
On Tue, 2019-01-22 at 14:51 +, tedheadster wrote:
> Ben, please backport Thomas Gleixner's patch to the 3.16 series.
This was already in my queue for the next update.
Ben.
> commit ef1d4deab953ecb1dfcf9f167043bda8b3f14a11
> Author: Thomas Gleixner
> Date: Thu Aug 31 20:08:16 2017 +0200
>
Quoting Jerome Brunet (2019-01-28 10:04:30)
> Initially, the meson clock directory only hosted 2 controllers drivers,
> for meson8 and gxbb. At the time, both used the same set of clock drivers
> so managing the dependencies was not a big concern.
>
> Since this ancient time, entropy did its job,
From: Mika Westerberg
Date: Tue, 29 Jan 2019 18:01:16 +0300
> The XDomain protocol messages may start as soon as Thunderbolt control
> channel is started. This means that if the other host starts sending
> ThunderboltIP packets early enough they will be passed to the network
> driver which then g
Hi,
Could you please copy the whole description from the cover letter to the
actual patch and only send one email (full description as in here
together with the patch)? If we commit this to the kernel, it would be
useful to have the information in the log for reference later on.
More comments bel
The patch
ASoC: sprd: Add Spreadtrum audio DMA platfrom driver
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
901 - 1000 of 1483 matches
Mail list logo
