On Fri, Jun 14, 2019 at 1:43 PM Qian Cai wrote:
>
> On Fri, 2019-06-14 at 12:48 -0700, Dan Williams wrote:
> > On Fri, Jun 14, 2019 at 12:40 PM Qian Cai wrote:
> > >
> > > On Fri, 2019-06-14 at 11:57 -0700, Dan Williams wrote:
> > > > On Fri, Jun 14, 2019 at 11:03 AM Dan Williams
> > > > wrote:
> On Jun 14, 2019, at 13:11, Bae, Chang Seok wrote:
>>
>> On May 8, 2019, at 10:25, Bae, Chang Seok wrote:
>>
>>> On May 8, 2019, at 03:02, Bae, Chang Seok wrote:
>>>
>>> diff --git a/arch/x86/kernel/ptrace.c b/arch/x86/kernel/ptrace.c
>>> index 4b8ee05..3309cfe 100644
>>> --- a/arch/x86/ker
On Fri, 14 Jun 2019 13:43:02 -0600
Rob Herring wrote:
> On Fri, 24 May 2019 22:26:30 -0300, Renato Lui Geh wrote:
> > This patch adds a YAML binding for the Analog Devices AD7780/1 and
> > AD7170/1 analog-to-digital converters.
> >
> > Signed-off-by: Renato Lui Geh
> > ---
> > Changes in v2:
>
Hi!
> > > In fact, I detected this issue by the following patch:
> > > https://patchwork.kernel.org/patch/10974669/
> > >
> > > When I worked on it, I wondered which
> > > c-dialect flags should be used.
> > >
> > > This code:
> > >
> > > > # Unlike the kernel space, uapi headers are written in mo
Hi!
> Am Donnerstag, 23. Mai 2019, 14:08:11 CEST schrieb Dan Murphy:
> > leds: multicolor: Add sysfs interface definition
> > dt: bindings: Add multicolor class dt bindings documention
> > documention: leds: Add multicolor class documentation
> > dt-bindings: leds: Add multicolor ID to the
Hi,
On 6/13/19 11:54 PM, Thomas Gleixner wrote:
>
> 8<--
> From: Thomas Gleixner
> Subject: Documentation/x86/64: Add documentation for GS/FS addressing mode
> Date: Thu, 13 Jun 2019 22:04:24 +0300
>
>
> Originally-by: Andi Kleen
> Signed-off-by: Thomas Gleixner
> ---
> Doc
On Sun, 16 Jun 2019, Bae, Chang Seok wrote:
>
> > On Jun 16, 2019, at 05:34, Thomas Gleixner wrote:
> >
> > On Sun, 16 Jun 2019, Thomas Gleixner wrote:
> >>
> >> Please dont. Send me a delta patch against the documentation. I have queued
> >> all the other patches already internally. I did not
On Sun, 16 Jun 2019, Randy Dunlap wrote:
> On 6/13/19 11:54 PM, Thomas Gleixner wrote:
> > +
> > +There exist two mechanisms to read and write the FS/FS base address:
>
> should this be... FS/GS
Indeed.
> > +FSGSBASE instructions enablement
> > +
This patchset fixes the following errors reported by checkpatch in the
staging/rtl8723bs driver.
Patch[1/3]: Fix check patch error "that open brace { should be on the previous
line"
Patch[2/3]: Fix the error else should follow close brace '}'
Patch[3/3]: Fix Indentation Error
version 3 chang
Cleaned up the code to resolve the checkpatch error else should follow
close brace '}' from the following files:
mlme_linux.c
recv_linux.c
sdio_intf.c
Signed-off-by: Shobhit Kukreti
---
drivers/staging/rtl8723bs/os_dep/mlme_linux.c | 6 ++
drivers/staging/rtl8723bs/os_dep/recv_linux.c | 21
Resolve indentation errors which were caused by a mix of space and tabs
for indentation. Previous patch to fix if-else brace styles revealed
the indentation error
Signed-off-by: Shobhit Kukreti
---
drivers/staging/rtl8723bs/os_dep/recv_linux.c | 6 ++---
drivers/staging/rtl8723bs/os_dep/sdio_in
Cleaned up the code from the following files to get rid of
check patch error "that open brace { should be on the previous line"
drivers/staging/rtl8723bs/os_dep/mlme_linux.c
drivers/staging/rtl8723bs/os_dep/recv_linux.c
drivers/staging/rtl8723bs/os_dep/rtw_proc.c
drivers/staging/rtl8723bs/os_dep/s
On Tue, Jun 11, 2019 at 04:18:09PM -0700, Roman Gushchin wrote:
> There is no point in checking the root_cache->memcg_params.dying
> flag on kmem_cache creation path. New allocations shouldn't be
> performed using a dead root kmem_cache, so no new memcg kmem_cache
> creation can be scheduled after
On Tue, Jun 11, 2019 at 04:18:10PM -0700, Roman Gushchin wrote:
> Currently the memcg_params.dying flag and the corresponding
> workqueue used for the asynchronous deactivation of kmem_caches
> is synchronized using the slab_mutex.
>
> It makes impossible to check this flag from the irq context,
>
Hi Jan,
On 6/4/19 7:31 AM, Steve Magnani wrote:
In some cases, using the 'truncate' command to extend a UDF file results
in a mismatch between the length of the file's extents (specifically, due
to incorrect length of the final NOT_ALLOCATED extent) and the information
(file) length. The discre
On Tue, Jun 11, 2019 at 04:18:13PM -0700, Roman Gushchin wrote:
> Let's reparent non-root kmem_caches on memcg offlining. This allows us
> to release the memory cgroup without waiting for the last outstanding
> kernel object (e.g. dentry used by another application).
>
> Since the parent cgroup is
On Sun, 16 Jun 2019, Bae, Chang Seok wrote:
> > On Jun 14, 2019, at 13:11, Bae, Chang Seok wrote:
>
> Looks build error was reported with this. Sorry again for the noise.
Well. This has not built when it was posted. Can't you run your stuff
through the Intel zero day infrastructure _BEFORE_ post
On Sun, Jun 16, 2019 at 06:50:20AM -0500, Eric W. Biederman wrote:
> Dmitry Torokhov writes:
>
> > Hi Christian,
> >
> > On Sun, Apr 29, 2018 at 3:45 AM Christian Brauner
> > wrote:
> >>
> >> commit 07e98962fa77 ("kobject: Send hotplug events in all network
> >> namespaces")
> >>abhishe...@goog
Hi Eric,
On Sun, Jun 16, 2019 at 4:50 AM Eric W. Biederman wrote:
>
> Dmitry Torokhov writes:
>
> > Hi Christian,
> >
> > On Sun, Apr 29, 2018 at 3:45 AM Christian Brauner
> > wrote:
> >>
> >> commit 07e98962fa77 ("kobject: Send hotplug events in all network
> >> namespaces")
> >>abhishe...@go
On 2019-06-14 21:48, Fletcher Woodruff wrote:
From: Ben Zhang
The rt5677 jack detection function has a requirement that the polarity
of an interrupt be flipped after it fires in order to clear the
interrupt.
This patch implements an irq_chip with irq_domain directly instead of
using regmap-i
Hi Christian,
On Sun, Jun 16, 2019 at 9:50 AM Christian Brauner
wrote:
>
> Hey Dmitry,
>
> Crostini on ChromeOS is making heavy use of this patchset and of LXD. So
> reverting this almost 1.5 years after the fact will regress all of
> Google's ChromeOS Crostini users, and all LXD/LXC users.
>
> L
AVX512 Vector Neural Network Instructions (VNNI) in Intel Deep Learning
Boost support BFLOAT16 format (BF16). BF16 is a short version of FP32 and
has several advantages over FP16. BF16 offers more than enough range for
deep learning training tasks and doesn't need to handle hardware exception
as th
Although x86_cache_max_rmid and x86_cache_occ_scale are only read once
during resctrl initialization, they are always stored in cpuinfo_x86 for
each CPU during run time without usage. Even if resctrl is not
configured, they still occupy space in cpuinfo_x86.
To save cpuinfo_x86 space and make CPU
It's a waste for the four X86_FEATURE_CQM_* features to occupy two
pure feature bits words. To better utilize feature words, re-define
word 11 to host scattered features and move the four X86_FEATURE_CQM_*
features into Linux defined word 11. More scattered features can be added
in word 11 in the f
To enumerate AVX512 BFLOAT16 feature CPUID.7.1:EAX[5] and other future
features in CPUID.7.1:EAX, Boris suggests to create a new pure feature
bits word.
Boris further suggests to re-define word 11 as scattered features word
and move the four X86_FEATURE_CQM_* features in existing word 11 and
word
The pull request you sent on Sun, 16 Jun 2019 11:29:52 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ras-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f763cf8e47d3aa4b081e0537d060c12818de8d0f
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 16 Jun 2019 11:29:52 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/963172d9c7e862654d3d24cbcafb33f33ae697a8
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 16 Jun 2019 11:29:52 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> timers-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/efba92d58fa37d714d665deddb5cc6458b39bb88
Thank you!
--
Deet-doot-dot,
On 6/14/19 2:37 PM, Thomas Gleixner wrote:
> On Wed, 12 Jun 2019, Dmitry Safonov wrote:
>> ---
>> fs/timerfd.c | 3 +++
>> include/linux/time_namespace.h | 18 ++
>> kernel/time_namespace.c| 27 +++
>> 3 files changed, 48 insertion
On 6/14/19 2:42 PM, Thomas Gleixner wrote:
> On Wed, 12 Jun 2019, Dmitry Safonov wrote:
>
>> Subject: posix-timers/timens: Take into account clock offsets
>
> Please avoid that '/timens' appendix. It's not really a new subsystem or
> subfunction of posix-timers.
>
> posix-timers: Add time namesp
On 16/06/2019 11:31, Krzysztof Kozlowski wrote:
> On Fri, Jun 14, 2019 at 04:30:13PM +0200, Daniel Lezcano wrote:
>> On 14/06/2019 16:02, Robin Murphy wrote:
>>> On 14/06/2019 14:03, Daniel Lezcano wrote:
On 14/06/2019 11:35, Heiko Stuebner wrote:
> Hi Daniel,
>
> Am Dienstag, 4. J
On 6/14/19 2:50 PM, Thomas Gleixner wrote:
> On Wed, 12 Jun 2019, Dmitry Safonov wrote:
>
> Again, please use the usual prefix and bolt not everything to
> timens. timens: is the proper prefix for the actual time namespace core
> code.
Yep, will do.
Thanks,
Dmitry
This Makefile repeats very similar rules.
Let's use pattern rules. $(UNROLL) can be replaced with $*.
No intended change in behavior.
Signed-off-by: Masahiro Yamada
---
lib/raid6/Makefile | 97 ++
1 file changed, 11 insertions(+), 86 deletions(-)
d
On 6/14/19 2:58 PM, Thomas Gleixner wrote:
> On Wed, 12 Jun 2019, Dmitry Safonov wrote:
>>
>> +#ifdef CONFIG_TIME_NS
>> +notrace static __always_inline void clk_to_ns(clockid_t clk, struct
>> timespec *ts)
>> +{
>> +struct timens_offsets *timens = (struct timens_offsets *) &timens_page;
>> +
No intended change in behavior.
Signed-off-by: Masahiro Yamada
---
lib/raid6/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/lib/raid6/Makefile b/lib/raid6/Makefile
index e723eacf7868..74004037033f 100644
--- a/lib/raid6/Makefile
+++ b/lib/raid6/Makefile
@@ -26,7 +26,6 @@ CFLAGS_REM
On 6/14/19 3:05 PM, Thomas Gleixner wrote:
> On Wed, 12 Jun 2019, Dmitry Safonov wrote:
>>
>> +#ifdef CONFIG_TIME_NS
>> +int vdso_join_timens(struct task_struct *task)
>> +{
>> +struct mm_struct *mm = task->mm;
>> +struct vm_area_struct *vma;
>> +
>> +if (down_write_killable(&mm->mmap
On Sun, Jun 16, 2019 at 10:14:08AM -0700, Fenghua Yu wrote:
> @@ -617,13 +617,20 @@ static void l3_mon_evt_init(struct rdt_resource *r)
> list_add_tail(&mbm_local_event.list, &r->evt_list);
> }
>
> -int rdt_get_mon_l3_config(struct rdt_resource *r)
> +int __init rdt_get_mon_l3_conf
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
tags/samsung-dt-5.3
for you to fetch changes up to d2cac68e0d9b038da
On 19-06-07 15:22:22, Palmer Dabbelt wrote:
> The comment describes why in detail. This was found because QEMU never
> gives up load reservations, the issue is unlikely to manifest on real
> hardware.
Makes sense, however it obviously will not help until qemu actually
clears load reservations on
On Sun, 9 Jun 2019, Antony Pavlov wrote:
> On Sun, 2 Jun 2019 01:05:00 -0700
> Paul Walmsley wrote:
>
> Hi!
>
> > Add initial board data for the SiFive HiFive Unleashed A00.
...
> > new file mode 100644
> > index ..1de4ea1577d5
> > --- /dev/null
> > +++ b/arch/riscv/boot/dts/sifi
On Mon, 10 Jun 2019, Rob Herring wrote:
> On Sun, Jun 2, 2019 at 2:05 AM Paul Walmsley wrote:
> >
> > Add YAML DT binding documentation for the SiFive FU540 SoC.
...
> > ---
> > .../devicetree/bindings/riscv/sifive.yaml | 25 +++
> > MAINTAINERS
On Sun 02 Jun 18:04 PDT 2019, Brian Masney wrote:
> From: Jonathan Marek
>
> Add support for the Synaptics RMI4 touchscreen that is found on the
> Nexus 5.
>
> Signed-off-by: Jonathan Marek
> Signed-off-by: Brian Masney
Applied for 5.3
PS. Please use a --cover-letter when sending multiple p
Hi Hans,
On Thu, Jun 13, 2019 at 07:44:15AM +0200, Hans Verkuil wrote:
> On 5/24/19 5:31 AM, Shuah Khan wrote:
> > media_device is embedded in struct vimc_device and when vimc is removed
> > vimc_device and the embedded media_device goes with it, while the active
> > stream and vimc_capture contin
Hi Shuah,
On Fri, Jun 14, 2019 at 05:26:46PM -0600, Shuah Khan wrote:
> On 6/13/19 7:24 AM, Helen Koike wrote:
> > On 6/13/19 2:44 AM, Hans Verkuil wrote:
> >> On 5/24/19 5:31 AM, Shuah Khan wrote:
> >>> media_device is embedded in struct vimc_device and when vimc is removed
> >>> vimc_device and
On Fri 14 Jun 16:14 PDT 2019, John Stultz wrote:
> Add support for gen2 pon register so "reboot bootloader" can
> work on pixel3 and db845.
>
> Cc: Andy Gross
> Cc: David Brown
> Cc: Bjorn Andersson
> Cc: Amit Pundir
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: Sebastian Reichel
> Cc: linux-
"It's Sunday afternoon somewhere in the world".
In fact, it's _barely_ Sunday afternoon back home, where I'll be later
today. But not quite yet, and I continue my slightly flaky release
schedule due to my normal release time being spent on an airplane once
again.
In fact, that will happen the _ne
Hi!
stable removed from cc.
On Thu 2019-06-13 10:32:35, Greg Kroah-Hartman wrote:
> [ Upstream commit 63f55fcea50c25ae5ad45af92d08dae3b84534c2 ]
>
> Currently IRQ remains enabled after .remove, later if device is probed,
> IRQ is requested before .thermal_init, this may cause IRQ function be
>
Hi!
> [ Upstream commit 3f54c447df34ff9efac7809a4a80fd3208efc619 ]
>
> Disabling the SMMU when probing from within a kdump kernel so that all
> incoming transactions are terminated can prevent the core of the crashed
> kernel from being transferred off the machine if all I/O devices are
> behind
Hi!
> [ Upstream commit 05573d6ccf702df549a7bdeabef31e4753df1a90 ]
>
> As Jungyeon reported in bugzilla:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=203239
>
> - Overview
> When mounting the attached crafted image and running program, following
> errors are reported.
> Additionally, it han
On Thu 2019-06-13 10:33:18, Greg Kroah-Hartman wrote:
> [ Upstream commit 9dc1a38ef1925d23c2933c5867df816386d92ff8 ]
>
> We do not restart a controller in a deleting state for timeout errors.
> When in this state, unblock potential request dispatchers with failed
> completions by shutting down th
Hi!
> ---
> fs/overlayfs/file.c | 44
> 1 file changed, 40 insertions(+), 4 deletions(-)
>
> --- a/fs/overlayfs/file.c
> +++ b/fs/overlayfs/file.c
> @@ -146,11 +146,47 @@ static int ovl_release(struct inode *ino
>
> static loff_t ovl_llseek(struc
Hi!
> diff --git a/drivers/pci/controller/dwc/pcie-designware-ep.c
> b/drivers/pci/controller/dwc/pcie-designware-ep.c
> index de8635af4cde..739d97080d3b 100644
> --- a/drivers/pci/controller/dwc/pcie-designware-ep.c
> +++ b/drivers/pci/controller/dwc/pcie-designware-ep.c
> @@ -385,6 +385,7 @@ in
[FYI: This was in my spam folder. I'll reserve judgement on whether that's
the right decision.]
On Sun, Jun 16, 2019 at 09:42:36PM +0200, Pavel Machek wrote:
> > [ Upstream commit 3f54c447df34ff9efac7809a4a80fd3208efc619 ]
> >
> > Disabling the SMMU when probing from within a kdump kernel so that
On Sun, 16 Jun 2019, Fenghua Yu wrote:
> Although x86_cache_max_rmid and x86_cache_occ_scale are only read once
> during resctrl initialization, they are always stored in cpuinfo_x86 for
> each CPU during run time without usage. Even if resctrl is not
> configured, they still occupy space in cpuin
> On Jun 16, 2019, at 09:05, Thomas Gleixner wrote:
>
> On Sun, 16 Jun 2019, Bae, Chang Seok wrote:
>>
>> Thanks. This is the diff though.
>> ...
>
> WHAT? How is this related ?
No. Sigh on me.. Instead of the garbage, I hoped to point out these small
version things.
(The delta against the
From: Ivan Vecera
Date: Fri, 14 Jun 2019 17:48:36 +0200
> Number of Rx queues used for flow hashing returned by the driver is
> incorrect and this bug prevents user to use the last Rx queue in
> indirection table.
...
> Fixes: 594ad54a2c3b ("be2net: Add support for setting and getting rx flow
>
The Mecer Xtreme Mini S6 features a Rockchip RK3229 SoC,
1GB DDR3 RAM, 8GB eMMC, MicroSD port, 10/100Mbps Ethernet,
Realtek 8723BS WLAN module, 2 x USB 2.0 ports, HDMI output,
and S/PDIF output.
Signed-off-by: Justin Swartz
---
arch/arm/boot/dts/Makefile| 1 +
arch/arm/boot/dts/rk3229-
From: Martin Blumenstingl
Date: Sat, 15 Jun 2019 12:09:27 +0200
> This is a successor to my previous series "stmmac: honor the GPIO flags
> for the PHY reset GPIO" from [0]. It contains only the "cleanup"
> patches from that series plus some additional cleanups on top.
>
> I broke out the actual
From: Dexuan Cui
Date: Sat, 15 Jun 2019 03:22:32 +
> These warnings are not introduced by this patch from Sunil.
>
> I'm not sure why I didn't notice these warnings before.
> Probably my gcc version is not new eought?
>
> Actually these warnings are bogus, as I checked the related functi
On 6/16/19 10:13 AM, Jiri Olsa wrote:
> On Fri, Jun 14, 2019 at 09:45:21AM -0400, Liang, Kan wrote:
>>
>>
>> On 6/14/2019 7:28 AM, Jiri Olsa wrote:
>>> hi,
>>> the HPE server can do POST tracing and have enabled LBR
>>> tracing during the boot, which makes check_msr fail falsly.
>>>
>>> It looks
From: Dexuan Cui
Date: Sat, 15 Jun 2019 05:00:57 +
> gcc 8.2.0 may report these bogus warnings under some condition:
>
> warning: ‘vnew’ may be used uninitialized in this function
> warning: ‘hvs_new’ may be used uninitialized in this function
>
> Actually, the 2 pointers are only initializ
From: Ivan Khoronzhuk
Date: Sat, 15 Jun 2019 14:01:32 +0300
> While data pass suspend, reuse of rx descriptors can be disabled using
> channel state & lock from cpdma layer. For this, submit to a channel
> has to be disabled using state != "not active" under lock, what is done
> with this patch.
On Sat, Jun 15, 2019 at 04:18:21PM +0200, Ard Biesheuvel wrote:
> Yes, I am using the same saturation point as x86. In this example, I
> am not entirely sure I understand why it matters, though: the atomics
> guarantee that the write by CPU2 fails if CPU1 changed the value in
> the mean time, regar
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/cpu
head: 60152cedb1bd1fa603528d53d1eec0279a74223f
commit: 2902fa1280ff6b1ecac1d41d1ab81239393e09fb [12/18] x86/entry/64: Handle
FSGSBASE enabled paranoid entry/exit
config: x86_64-alldefconfig (attached as .config)
comp
On Mon, 17 Jun 2019, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> WIP.x86/cpu
> head: 60152cedb1bd1fa603528d53d1eec0279a74223f
> commit: 2902fa1280ff6b1ecac1d41d1ab81239393e09fb [12/18] x86/entry/64: Handle
> FSGSBASE enabled paranoid entry/e
On Sun, 16 Jun 2019, Bae, Chang Seok wrote:
> > On Jun 16, 2019, at 09:05, Thomas Gleixner wrote:
> diff --git a/Documentation/x86/x86_64/fsgs.rst
> b/Documentation/x86/x86_64/fsgs.rst
> index 380c0b5..d5588e00 100644
> --- a/Documentation/x86/x86_64/fsgs.rst
> +++ b/Documentation/x86/x86_64/fsgs
On Fri, Jun 14, 2019 at 8:38 AM Sean Christopherson
wrote:
>
> On Thu, Jun 13, 2019 at 05:46:00PM -0700, Sean Christopherson wrote:
> > On Thu, Jun 13, 2019 at 01:02:17PM -0400, Stephen Smalley wrote:
> > > On 6/11/19 6:02 PM, Sean Christopherson wrote:
> > > >On Tue, Jun 11, 2019 at 09:40:25AM -0
On Fri, Jun 14, 2019 at 10:16 AM Xing, Cedric wrote:
>
> > From: Christopherson, Sean J
> > Sent: Thursday, June 13, 2019 5:46 PM
> >
> > On Thu, Jun 13, 2019 at 01:02:17PM -0400, Stephen Smalley wrote:
> > > On 6/11/19 6:02 PM, Sean Christopherson wrote:
> > > >On Tue, Jun 11, 2019 at 09:40:25AM
On Fri, Jun 14, 2019 at 7:21 AM Thomas Gleixner wrote:
>
> On Wed, 12 Jun 2019, Andy Lutomirski wrote:
> > > On Jun 12, 2019, at 12:55 PM, Dave Hansen wrote:
> > >
> > >> On 6/12/19 10:08 AM, Marius Hillenbrand wrote:
> > >> This patch series proposes to introduce a region for what we call
> > >>
On Fri, 14 Jun 2019, Kees Cook wrote:
> On Fri, Jun 14, 2019 at 04:57:36PM +0200, Thomas Gleixner wrote:
> > Wouldn't it make sense to catch situations where a regular caller provides
> > @val with pinned bits unset? I.e. move the OR into this code path after
> > storing bits_missing.
>
> I menti
On Sun, 16 Jun 2019, Andy Lutomirski wrote:
> On Fri, Jun 14, 2019 at 7:21 AM Thomas Gleixner wrote:
> > On Wed, 12 Jun 2019, Andy Lutomirski wrote:
> > >
> > > Fair warning: Linus is on record as absolutely hating this idea. He might
> > > change his mind, but it’s an uphill battle.
> >
> > Yes I
Hi Andrey,
On Fri, Jun 14, 2019 at 5:03 AM Andrey Smirnov wrote:
> diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml
> b/Documentation/devicetree/bindings/arm/fsl.yaml
> index 407138ebc0d0..8fb4dc1d55e7 100644
> --- a/Documentation/devicetree/bindings/arm/fsl.yaml
> +++ b/Documentatio
Hi Andrey,
On Fri, Jun 14, 2019 at 5:03 AM Andrey Smirnov wrote:
> + mdio {
> + fec1_phy: phy@0 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_enet1_phy_reset>,
> + <&pinctrl_enet1_phy_i
Hello,
This series introduces driver for the External Memory Controller (EMC)
found on Tegra30 chips, it controls the external DRAM on the board. The
purpose of this driver is to program memory timing for external memory on
the EMC clock rate change. The driver was tested using the ACTMON devfreq
There is no problem for drivers to request pll_m and pll_p clocks for
the device, hence there is no need to use clk_get_sys() and it could be
replaced with devm_clk_get() for consistency.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra20-emc.c | 12
1 file changed, 4 i
The Memory Controller registers definition is sparse and duplicated,
let's consolidate everything into a common place for consistency.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/mc.c | 30 ---
drivers/memory/tegra/mc.h | 52 +--
The memory frequency scaling will be managed by tegra20-devfreq driver
and PM QoS once all the prerequisite patches will get upstreamed.
The parent clock is now managed by the clock driver and we also should
assume that PLLM rate can't be changed on some devices (Galaxy Tab 10.1
for example). Altog
Introduce driver for the External Memory Controller (EMC) found on Tegra30
chips, it controls the external DRAM on the board. The purpose of this
driver is to program memory timing for external memory on the EMC clock
rate change.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/Kconfig
The emc_mux clock is gone now and EMC driver should provide the clock
rounding functionality.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra20-emc.c | 55 --
1 file changed, 45 insertions(+), 10 deletions(-)
diff --git a/drivers/memory/tegra/tegra20-em
Timing control debug features should be disabled at a boot time, but you
never now and hence it's better to disable them explicitly because some of
those features are crucial for the driver to do a proper thing.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/mc.c | 3 +++
drivers/memory
A proper External Memory Controller clock rounding and parent selection
functionality is required by the EMC drivers. It is not available using
the generic clock implementation, hence add a custom one. The clock rate
rounding shall be done by the EMC drivers because they have information
about avai
Add External Memory Controller node to the device-tree.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra30.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/tegra30.dtsi b/arch/arm/boot/dts/tegra30.dtsi
index e074258d4518..92c4aeafab29 100644
--- a
The register polling code was gone, but the included header change was
missed. Fix it up for consistency.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra20-emc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/memory/tegra/tegra20-emc.c
b/drivers/memory
Add device-tree binding for NVIDIA Tegra30 External Memory Controller.
The binding is based on the Tegra124 EMC binding since hardware is
similar, although there are couple significant differences.
Note that the memory timing description is given in a platform-specific
form because there is no det
The minimum number of "cycles" is limited to 1 by
clockevents_config_and_register().
Signed-off-by: Dmitry Osipenko
---
drivers/clocksource/timer-tegra.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/clocksource/timer-tegra.c
b/drivers/clocksource/timer-tegra.c
Tegra's timer has 29 bits for the counter. The counter's value is smaller
than the actual value by 1, hence the maximum equals to 29 bits + 1.
Signed-off-by: Dmitry Osipenko
---
drivers/clocksource/timer-tegra.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clocksou
Hi, Bibby:
On Wed, 2019-06-12 at 16:53 +0800, Bibby Hsieh wrote:
> GCE cannot know the register base address, this function
> can help cmdq client to get the cmdq_client_reg structure.
>
> Signed-off-by: Bibby Hsieh
> ---
> drivers/soc/mediatek/mtk-cmdq-helper.c | 24
>
On Tue, May 21, 2019 at 10:10:29AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> The bug is in the driver, so ...
>
> > Bisecting the issue for commits to drivers/gpu/drm/bochs/ points to:
> > 6579c39594ae ("drm/bochs: atomic: switch planes to atomic, wire up
> > helpers.")
> > ... but the issue also
On 2019/6/16 21:11, Jonathan Cameron wrote:
> On Fri, 14 Jun 2019 23:28:46 +0800
> YueHaibing wrote:
>
>> Fix build error:
>>
>> drivers/staging/iio/addac/adt7316.c: In function adt7316_store_update_DAC:
>> drivers/staging/iio/addac/adt7316.c:949:3: error: implicit declaration of
>> function gpi
Hi Pali,
Since design architecture change of CS19, input device connection has been
changed to below architecture,
Touchpad has been moved to I2C connection.
kernel/host <--PS/2--> EC <--PS/2--> external PS/2 mouse
| |
|<--PS/2--> tra
Hello Qian,
On 06/14/2019 05:45 PM, Qian Cai wrote:
> On Fri, 2019-06-14 at 11:20 +0100, Will Deacon wrote:
>> Hi Qian,
>>
>> On Thu, Jun 13, 2019 at 05:34:01PM -0400, Qian Cai wrote:
>>> LTP hugemmap05 test case [1] could not exit itself properly and then degrade
>>> the
>>> system performance on
Zhaoxin CPUs have NONSTOP TSC feature, so enable the ACPI
driver support for it.
Signed-off-by: Tony W Wang-oc
---
drivers/acpi/acpi_pad.c | 1 +
drivers/acpi/processor_idle.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/acpi/acpi_pad.c b/drivers/acpi/acpi_pad.c
index a476
Same as Intel, Zhaoxin MP CPUs support C3 share cache and on all
recent Zhaoxin platforms ARB_DISABLE is a nop. So set related
flags correctly in the same way as Intel does.
Signed-off-by: Tony W Wang-oc
---
arch/x86/kernel/acpi/cstate.c | 15 +++
1 file changed, 15 insertions(+)
di
> On Jun 16, 2019, at 9:32 PM, Anshuman Khandual
> wrote:
>
> Hello Qian,
>
> On 06/14/2019 05:45 PM, Qian Cai wrote:
>> On Fri, 2019-06-14 at 11:20 +0100, Will Deacon wrote:
>>> Hi Qian,
>>>
>>> On Thu, Jun 13, 2019 at 05:34:01PM -0400, Qian Cai wrote:
LTP hugemmap05 test case [1] cou
Hi all,
Today's linux-next merge of the net-next tree got conflicts in:
arch/sh/configs/se7712_defconfig
arch/sh/configs/se7721_defconfig
arch/sh/configs/titan_defconfig
between commit:
7c04efc8d2ef ("sh: configs: Remove useless UEVENT_HELPER_PATH")
from the sh tree and commit:
a514
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
net/mac80211/cfg.c
between commit:
28c61a66abd6 ("treewide: Replace GPLv2 boilerplate/reference with SPDX - rule
432")
from Linus' tree and commit:
bd718fc11d5b ("mac80211: use STA info in rate_control_send_low()"
> -Original Message-
> From: Rob Herring
> Sent: 2019年6月14日 4:08
> To: Wen He
> Cc: linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org; shawn...@kernel.org; Leo Li
>
> Subject: [EXT] Re: [v1 1/4] dt-bindings: display: Add DT bindings for LS
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
net/vmw_vsock/hyperv_transport.c
between commit:
d424a2afd7da ("hv_sock: Suppress bogus "may be used uninitialized" warnings")
from the net tree and commit:
ac383f58f3c9 ("hv_sock: perf: Allow the socket buffer siz
On 06/14/19 at 09:15pm, Lendacky, Thomas wrote:
> The memory occupied by the kernel is reserved using memblock_reserve()
> in setup_arch(). Currently, the area is from symbols _text to __bss_stop.
> Everything after __bss_stop must be specifically reserved otherwise it
> is discarded. This is not c
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
net/wireless/nl80211.c
between commit:
180aa422ef27 ("nl80211: fill all policy .type entries")
from the net tree and commit:
1a28ed213696 ("nl80211: fill all policy .type entries")
from the net-next tree.
I fixed
101 - 200 of 299 matches
Mail list logo
