We expect a quiescent state of TASKS_RCU when cond_resched_tasks_rcu_qs()
is called, no matter whether it actually be scheduled or not. However,
it currently doesn't report the quiescent state when the task enters
into __schedule() as it's called with preempt = true. So make it report
the quiescent
Hi Kent,
I haven't really had time to digest this in any real detail,
but I've noticed a couple of things that worry me...
On Tue, May 08, 2018 at 06:17:59PM -0400, Kent Overstreet wrote:
> Signed-off-by: Kent Overstreet
> ---
> fs/bcachefs/bcachefs_format.h | 1448 +
On Fri, May 11, 2018 at 03:25:18PM +0800, Xiao Guangrong wrote:
>
> Hi,
>
> Currently, there is no read barrier between reading the index
> (kfifo.in) and fetching the real data from the fifo.
>
> I am afraid that will cause the vfifo is observed as not empty
> however the data is not actually r
Hi Samuel,
On Thu, May 10, 2018 at 10:01:23PM -0500, Samuel Holland wrote:
> Enable the following board hardware features:
> - Gigabit Ethernet
> - SDIO Wi-Fi on mmc1
> - SPI flash on spi0
> - Status LED
> - Dual-role micro-USB connection
>
> Also provide nodes for the UARTs exposed by the 40-pin
Le 11/05/2018 à 08:12, Alastair D'Silva a écrit :
From: Alastair D'Silva
This patch adds a CPU feature bit to show whether the CPU has
the TIDR register available, enabling as_notify/wait in userspace.
Signed-off-by: Alastair D'Silva
---
Reviewed-by: Frederic Barrat
arch/powerpc/in
On Wed, May 09, 2018 at 07:04:51PM -0700, Srikar Dronamraju wrote:
> * Mel Gorman [2018-05-09 17:31:15]:
>
> > This reverts commit 7347fc87dfe6b7315e74310ee1243dc222c68086.
> >
> > Signed-off-by: Mel Gorman
>
>
> Reviewed-by: Srikar Dronamraju
>
Thanks Srikar.
Can someone pick this up bef
On 11-May 11:14, Viresh Kumar wrote:
> On 10-05-18, 16:05, Patrick Bellasi wrote:
> > When a task is enqueue the estimated utilization of a CPU is updated
> > to better support the selection of the required frequency.
> > However, schedutil is (implicitly) updated by update_load_avg() which
> > alw
On 11-May 11:13, Viresh Kumar wrote:
> On 10-05-18, 16:05, Patrick Bellasi wrote:
> > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> > -static void attach_entity_load_avg(struct cfs_rq *cfs_rq, struct
> > sched_entity *se, int flags)
> > +static void attach_entity_load_avg(struct cfs_rq
On 24/03/18 17:46, chinnikishore...@gmail.com wrote:
From: Nava kishore Manne
This patch add the bindings document of zynqmp silicon id driver.
Signed-off-by: Nava kishore Manne
I see that you have not included DT maintainers in to/cc list, I can not
accept new drivers whose bindings ar
From: Martijn Coenen
New devices launching with Android P need to use the 64-bit
binder interface, even on 32-bit SoCs [0].
This change removes the Kconfig option to select the 32-bit
binder interface. We don't think this will affect existing
userspace for the following reasons:
1) The latest An
Le 11/05/2018 à 08:12, Alastair D'Silva a écrit :
From: Alastair D'Silva
Switch the use of TIDR on it's CPU feature, rather than assuming it
is available based on architecture.
Signed-off-by: Alastair D'Silva
---
Reviewed-by: Frederic Barrat
arch/powerpc/kernel/process.c | 6 +++---
[+Mark, who co-maintains the arch timer code with me]
Hi Samuel,
On 11/05/18 03:27, Samuel Holland wrote:
> The Allwinner A64 SoC is known [1] to have an unstable architectural
> timer, which manifests itself most obviously in the time jumping forward
> a multiple of 95 years [2][3]. This coincid
Le 11/05/2018 à 08:12, Alastair D'Silva a écrit :
From: Alastair D'Silva
The current implementation of TID allocation, using a global IDR, may
result in an errant process starving the system of available TIDs.
Instead, use task_pid_nr(), as mentioned by the original author. The
scenario descr
Le 11/05/2018 à 08:13, Alastair D'Silva a écrit :
From: Alastair D'Silva
The function removes the process element from NPU cache.
Signed-off-by: Alastair D'Silva
---
Acked-by: Frederic Barrat
arch/powerpc/include/asm/pnv-ocxl.h | 2 +-
arch/powerpc/platforms/powernv/ocxl.c | 4 ++-
On Wed, May 09, 2018 at 08:47:27PM +1000, Stephen Rothwell wrote:
> > True. It's currently only those -fixes branches that people have asked
> > him to merge separately which isn't as big a proportion of trees as have
> > them (perhaps fortunately given people's enthusiasm for fixes branches
> > t
Am 10.05.2018 um 19:15 schrieb Logan Gunthorpe:
On 10/05/18 11:11 AM, Stephen Bates wrote:
Not to me. In the p2pdma code we specifically program DMA engines with
the PCI bus address.
Ah yes of course. Brain fart on my part. We are not programming the P2PDMA
initiator with an IOVA but with th
On Wed, May 09, 2018 at 01:31:23PM +0200, Paul Kocialkowski wrote:
> On Wed, 2018-05-09 at 09:12 +0200, Maxime Ripard wrote:
> > On Tue, May 08, 2018 at 12:04:11AM +0200, Paul Kocialkowski wrote:
> > > This adds timings for the RGB666 variant of the Innolux AT070TN90 panel,
> > > as found on the Ai
On Thu, May 10, 2018 at 1:22 AM, Dave Chinner wrote:
> On Wed, May 09, 2018 at 10:43:05AM +0200, Dmitry Vyukov wrote:
>> Does "xfstests fuzzing infrastructure" use coverage-guidance?
>
> It's guided manually to fuzz a substantial proportion of the fields
> in the on-disk format that are susceptibl
On Fri, May 11, 2018 at 09:59:29AM +0200, Christoph Hellwig wrote:
> Switch to the generic noncoherent direct mapping implementation for
> the nommu dma map implementation.
>
> Signed-off-by: Christoph Hellwig
> ---
> arch/arc/Kconfig| 1 +
> arch/arm/Kconfig|
On 11-May 11:14, Viresh Kumar wrote:
> On 10-05-18, 16:05, Patrick Bellasi wrote:
> > Since the refactoring introduced by:
> >
> >commit 8f111bc357aa ("cpufreq/schedutil: Rewrite CPUFREQ_RT support")
> >
> > we aggregate FAIR utilization only if this class has runnable tasks.
> > This was mai
On 11/05/2018 07:57, Roman Kagan wrote:
>>> Should radix-tree be compilable in userspace, so that we can add unit
>>> tests for it?...
>> Good point.
>>
>> For my education, what/where are the tests that run as user-space code?
> Actually there are userspace tests for it under tools/tests/radix-tre
Add support for MSI.
Signed-off-by: Yao Chen
---
drivers/pci/dwc/pcie-kirin.c | 39 +++
1 file changed, 39 insertions(+)
diff --git a/drivers/pci/dwc/pcie-kirin.c b/drivers/pci/dwc/pcie-kirin.c
index d2970a0..8daab1f 100644
--- a/drivers/pci/dwc/pcie-kirin.c
Add pcie msi interrupt attribute for hi3660 SOC.
Signed-off-by: Yao Chen
---
arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/hisilicon/hi3660.dtsi
b/arch/arm64/boot/dts/hisilicon/hi3660.dtsi
index ec3eb8e..2cef8f4 100644
--- a/
Before Version Patches
==
patch v2
https://www.spinics.net/lists/kernel/msg2797610.html
patch v1
https://www.spinics.net/lists/kernel/msg2796410.html
Changes between V3 and V2
=
1. fix issues according to review comments
(1)from Bjorn Helgaas: Check
On Fri, May 11, 2018 at 8:21 AM, Sergey Senozhatsky
wrote:
> On (05/11/18 11:38), Tetsuo Handa wrote:
>> >
>> > So you basically want to have one more con_msg_format_flags? Do
>> > you want to track a context which prints out a messages or the
>> > context which "generated" the message? A CPU/task
From: Rafał Miłecki
SSB_PCICORE_HOSTMODE protects MIPS specific code that calls not exported
symbols pcibios_enable_device and register_pci_controller. This code is
supposed to be compiled only with ssb builtin.
This fixes:
ERROR: "pcibios_enable_device" [drivers/ssb/ssb.ko] undefined!
ERROR: "r
From: Rafał Miłecki
This reverts commit 882164a4a928bcaa53280940436ca476e6b1db8e.
Above commit added "SSB = y" dependency to the wrong symbol
SSB_DRIVER_PCICORE_POSSIBLE and prevented SSB_DRIVER_PCICORE from being
selected when needed. PCI core driver for core running in clienthost
mode is impor
On 11/05/18 09:12, Julien Thierry wrote:
On 09/05/18 22:52, Suzuki K Poulose wrote:
On 05/04/2018 11:06 AM, Julien Thierry wrote:
Hi,
In order to prepare the v3 of this patchset, I'd like people's opinion on what
this patch does. More below.
On 17/01/18 11:54, Julien Thierry wrote:
From:
On Thu, May 10, 2018 at 12:23 PM, Dan Streetman wrote:
>>> wrote:
On 20.02.2018 18:26, Neil Horman wrote:
>
> On Tue, Feb 20, 2018 at 09:14:41AM +0100, Dmitry Vyukov wrote:
>>
>> On Tue, Feb 20, 2018 at 8:56 AM, Tommi Rantala
>> wrote:
>>>
On 11 May 2018 at 00:12, Stefan Schake wrote:
> The overlay code is non-functional since it relies on firmware control
> of the HVS.
>
> Signed-off-by: Stefan Schake
> ---
> Dave, does this match your understanding?
Yes, the overlay only works if you are not running the vc4 driver,
therefore dro
On 11 May 2018 at 11:17, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> This reverts commit 882164a4a928bcaa53280940436ca476e6b1db8e.
>
> Above commit added "SSB = y" dependency to the wrong symbol
> SSB_DRIVER_PCICORE_POSSIBLE and prevented SSB_DRIVER_PCICORE from being
> selected when needed. P
On Thu, May 10, 2018 at 08:34:48PM +0530, Souptick Joarder wrote:
> Use new return type vm_fault_t for fault handler in
> struct vm_operations_struct. For now, this is just
> documenting that the function returns a VM_FAULT
> value rather than an errno. Once all instances are
> converted, vm_fault_
Le 11/05/2018 à 08:13, Alastair D'Silva a écrit :
From: Alastair D'Silva
In order to successfully issue as_notify, an AFU needs to know the TID
to notify, which in turn means that this information should be
available in userspace so it can be communicated to the AFU.
Signed-off-by: Alastair
Hi,
On 11/05/18 03:27, Samuel Holland wrote:
> Hello,
>
> Several people (including me) have experienced extremely large system
> clock jumps on their A64-based devices, apparently due to the
> architectural timer going backward, which is interpreted by Linux as
> the timer wrapping around after
On 05/10/2018 03:01 PM, argus@mediatek.com wrote:
> From: Argus Lin
>
> PWRAP_DEW_CIPHER_LOAD and PWRAP_DEW_CIPHER_START only exist at
> PMIC_mt6397 datasheet. We fix it before merge PMIC_mt6351 driver.
Please don't put info like "We fix it before merge PMIC_mt6351 driver." in the
commit m
Dear Doug,
在 2018年05月11日 04:59, Doug Anderson 写道:
Hi,
On Wed, May 9, 2018 at 1:55 AM, wlf wrote:
+ } else if (hsotg->params.host_dma) {
Are you sure this is "else if"? Can't you have descriptor DMA enabled
in the controller and still need to do a normal DMA transfer if you
plug in a
Le 11/05/2018 à 08:13, Alastair D'Silva a écrit :
From: Alastair D'Silva
In order for a userspace AFU driver to call the POWER9 specific
OCXL_IOCTL_ENABLE_P9_WAIT, it needs to verify that it can actually
make that call.
Signed-off-by: Alastair D'Silva
---
Acked-by: Frederic Barrat
d
Le 11/05/2018 à 08:13, Alastair D'Silva a écrit :
From: Alastair D'Silva
Signed-off-by: Alastair D'Silva
---
Acked-by: Frederic Barrat
Documentation/accelerators/ocxl.rst | 11 +++
1 file changed, 11 insertions(+)
diff --git a/Documentation/accelerators/ocxl.rst
b/Document
Hi Finn,
Am 11.05.2018 um 17:28 schrieb Finn Thain:
> On Fri, 11 May 2018, Michael Schmitz wrote:
>
>>
>> I'm afraid using platform_device_register() (which you already use for
>> the SCC devices) is the only option handling this on a per-device basis
>> without touching platform core code, whi
On 10-05-18, 14:26, Daniel Lezcano wrote:
> Initially, the cpu_cooling device for ARM was changed by adding a new
> policy inserting idle cycles. The intel_powerclamp driver does a
> similar action.
>
> Instead of implementing idle injections privately in the cpu_cooling
> device, move the idle in
On 09/05/2018 17:48, Cornelia Huck wrote:
Currently, vfio-ccw only relays start subchannel requests to the real
hardware, which is enough in many cases but falls short e.g. during
error recovery.
Fortunately, it is easy to add support for halt and clear subchannel
requests to the existing infras
Dear Doug,
在 2018年05月11日 05:01, Doug Anderson 写道:
Hi,
On Wed, May 9, 2018 at 3:11 AM, William Wu wrote:
The commit 3bc04e28a030 ("usb: dwc2: host: Get aligned DMA in
a more supported way") rips out a lot of code to simply the
allocation of aligned DMA. However, it also introduces a new
issue
On 09/05/2018 17:48, Cornelia Huck wrote:
The vfio-ccw code will need this, and it matches treatment of ssch
and csch.
Signed-off-by: Cornelia Huck
---
drivers/s390/cio/ioasm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/s390/cio/ioasm.c b/drivers/s390/cio/ioasm.c
index 14d32
On Fri, 2018-05-11 at 10:29 +0200, Matthias Brugger wrote:
> Hi Erin,
>
> Please include the linux-mediatek and arm-linux-kernel mailinglists in the
> next
> round.
>
> Some comments in the patches.
>
> Regards,
> Matthias
I will add linux-mediatek, linux-arm-kernel, linux-kernel, linux-serial
On Wed, May 9, 2018 at 9:16 PM, Oleg Keri wrote:
Oleg, thank you for the patch, thoiugh it contains two issues, i.e.
- each new attribute in sysfs is ABI, *must* be documented; if there
is no such file present at all, you may start a new one;
- the commit message is formatted rather as in SVN s
Greetings!
Preface:
This is RFC v5 to modernize procfs and make it able to support multiple
private instances per the same pid namespace.
RFC v1 is here:
https://lkml.org/lkml/2017/3/30/670
RFC v2 is here:
https://lkml.org/lkml/2017/4/25/282
This RFC v5 can be applied on top of v4.17-r
From: Djalal Harouni
This is a preparation patch that adds proc_fs_info to be able to store
different procfs options and informations. Right now some mount options
are stored inside the pid namespace which makes it hard to change or
modernize procfs without affecting pid namespaces. Plus we do wa
From: Djalal Harouni
This is a preparation patch that moves /proc/{self|thread-self} dentries
to be stored inside procfs fs_info struct instead of making them per pid
namespace. Since we want to support multiple procfs instances we need to
make sure that these dentries are also per-superblock ins
From: Djalal Harouni
This is a cleaning patch to add helpers to set and get proc mount
options instead of directly using them. This make it easy to track
what's happening and easy to update in future.
Cc: Kees Cook
Cc: Andy Lutomirski
Signed-off-by: Djalal Harouni
---
fs/proc/base.c
From: Djalal Harouni
This patch allows to have multiple private procfs instances inside the
same pid namespace. Lot of other areas in the kernel and filesystems
have been updated to be able to support private instances, devpts is one
major example. The aim here is lightweight sandboxes, and to al
From: Djalal Harouni
If "limit_pids=1" mount option is set then do not instantiate pids that
we can not ptrace. "limit_pids=1" means that procfs should only contain
pids that the caller can ptrace.
Cc: Kees Cook
Cc: Andy Lutomirski
Signed-off-by: Djalal Harouni
---
fs/proc/base.c | 9 +++
This allows to hide all files and directories in the procfs that are not
related to tasks.
Signed-off-by: Alexey Gladkov
---
fs/proc/generic.c | 20
fs/proc/inode.c | 7 +++
fs/proc/root.c | 12 ++--
include/linux/proc_fs.h | 21 ++
From: Djalal Harouni
This allows to flush dcache entries of a task on multiple procfs mounts
per pid namespace.
Cc: Kees Cook
Cc: Andy Lutomirski
Signed-off-by: Djalal Harouni
---
fs/proc/base.c| 27 ++-
fs/proc/inode.c | 9 -
fs
On Thu, May 10, 2018 at 11:07:01AM -0700, Doug Oucharek wrote:
> Under upstream staging commit 5a2ca43fa54f561c252c2, the list handling
> code in kiblnd_handle_early_rxs() got changed to list_for_each_safe().
> That protects against the current thread from deleting the current entry
> it is looking
This patch fix dma unaligned problem and data lost problem for
isoc split in transfer.
Test on rk3288 platform, use an usb hs Hub (GL852G-12) and an usb
fs audio device (Plantronics headset) to capture and playback.
William Wu (2):
usb: dwc2: alloc dma aligned buffer for isoc split in
usb: dw
The commit 3bc04e28a030 ("usb: dwc2: host: Get aligned DMA in
a more supported way") rips out a lot of code to simply the
allocation of aligned DMA. However, it also introduces a new
issue when use isoc split in transfer.
In my test case, I connect the dwc2 controller with an usb hs
Hub (GL852G-12
If isoc split in transfer with no data (the length of DATA0
packet is zero), we can't simply return immediately. Because
the DATA0 can be the first transaction or the second transaction
for the isoc split in transaction. If the DATA0 packet with no
data is in the first transaction, we can return im
On (05/11/18 11:17), Dmitry Vyukov wrote:
>
> From what I see, it seems that interrupts can be nested:
Hm, I thought that in general IRQ handlers run with local IRQs
disabled on CPU. So, generally, IRQs don't nest. Was I wrong?
NMIs can nest, that's true; but I thought that at least IRQs
don't.
On 09/05/2018 17:49, Cornelia Huck wrote:
The initial version of vfio-ccw did not support forwarding of the
halt or clear functions to the device, and we had to emulate them
instead.
For versions of the vfio-ccw kernel implementation that indeed do
support halt/clear (by indicating them in the f
Add compatible string for R-Car D3 R8A7795 to list of SoCs supported by
rcar-vin driver.
Signed-off-by: Jacopo Mondi
---
Documentation/devicetree/bindings/media/rcar_vin.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/media/rcar_vin.txt
b/Documentation/
Hello,
this series enables HDMI input and VIN4 on R-Car D3 Draak board.
The Draak board has an HDMI input connected to an HDMI decoder that feeds
the VIN capture interface through its parallel video interface.
The series requires the just sent:
[PATCH 0/5] rcar-vin: Add support for digital inp
On Mon, Apr 30, 2018 at 8:09 PM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:5d1365940a68 Merge
> git://git.kernel.org/pub/scm/linux/kerne...
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?id=5667997129637888
> kernel co
Describe VIN4 interface for R-Car D3 R8A77995 SoC.
Signed-off-by: Jacopo Mondi
---
arch/arm64/boot/dts/renesas/r8a77995.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a77995.dtsi
b/arch/arm64/boot/dts/renesas/r8a77995.dtsi
index 82aed7e..bdf7
Describe HDMI input connected to VIN4 interface for R-Car D3 Draak
development board.
Signed-off-by: Jacopo Mondi
---
arch/arm64/boot/dts/renesas/r8a77995-draak.dts | 68 ++
1 file changed, 68 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a77995-draak.dts
b/a
On Fri, 11 May 2018, Michael Schmitz wrote:
>
> I wasn't proposing to follow platform_device_register() with the mask
> assignment,
I see.
> but rather to use the same strategy from the Coldfire FEC patch
> (f61e64310b75): set pdev.dev.coherent_dma_mask and pdev.dev.dma_mask
> _before_ calli
> -Original Message-
> From: Frederic Barrat
> Sent: Friday, 11 May 2018 7:25 PM
> To: Alastair D'Silva ; linuxppc-...@lists.ozlabs.org
> Cc: linux-kernel@vger.kernel.org; linux-...@vger.kernel.org;
> mi...@neuling.org; vaib...@linux.vnet.ibm.com;
> aneesh.ku...@linux.vnet.ibm.com; ma...@
Rafał Miłecki writes:
> On 11 May 2018 at 11:17, Rafał Miłecki wrote:
>> From: Rafał Miłecki
>>
>> This reverts commit 882164a4a928bcaa53280940436ca476e6b1db8e.
>>
>> Above commit added "SSB = y" dependency to the wrong symbol
>> SSB_DRIVER_PCICORE_POSSIBLE and prevented SSB_DRIVER_PCICORE from
Larry Finger writes:
> On 05/10/2018 06:14 AM, Rafał Miłecki wrote:
>> From: Rafał Miłecki
>>
>> SSB_PCICORE_HOSTMODE protects MIPS specific code that calls not exported
>> symbols pcibios_enable_device and register_pci_controller. This code is
>> supposed to be compiled only with ssb builtin.
>
On Wed, May 09, 2018 at 09:49:49PM +, Winkler, Tomas wrote:
> >
> > On Sat, May 05, 2018 at 09:07:21PM +, Winkler, Tomas wrote:
> > > There is already one 'out' label in that function, what would you prefer
> > > for
> > this new label name?
> > > Thanks
> > > Tomas
> >
> > Aah, of cours
On Thu, May 10, 2018 at 01:21:39PM +0200, Laurent Bigonville wrote:
> Le 05/05/18 à 22:03, Jerry Snitselaar a écrit :
> > On Sat May 05 18, Jerry Snitselaar wrote:
> > > [...]
> > >
> >
> > Laurent,
>
> Hello Jerry,
>
> > Can you try this patch with your system since it is the one
> > that has
The use of GPIO descriptors takes care of inversion flags declared in
the device tree. The conversion of the Atmel USBA UDC driver introduced
in 4.17-rc1 missed it, and as a result the inversion will not work.
In addition, cleanup the code to remove an include left behind after
the suppression of
When converting to GPIO descriptors, gpiod_get_value automatically
handles the line inversion flags from the device tree.
Do not invert the line twice.
Fixes: 3df034081021 ("usb: gadget: udc: atmel: convert to use GPIO descriptors")
Acked-by: Ludovic Desroches
Acked-by: Nicolas Ferre
Signed-off
Fix the fallout of the conversion to GPIO descriptors in 3df034081021.
Acked-by: Ludovic Desroches
Acked-by: Nicolas Ferre
Signed-off-by: Romain Izard
---
drivers/usb/gadget/udc/atmel_usba_udc.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/usb/
On Thu, May 10, 2018 at 10:05:33PM -0700, Chen-Yu Tsai wrote:
> On Mon, May 7, 2018 at 5:44 AM, Paul Kocialkowski
> wrote:
> > This introduces platform-specific compatibles for the A13, A20 and A33
> > SRAM driver. No particular adaptation for these platforms is required at
> > this point, althoug
The include defines the private platform_data structure used with AVR
platforms. It has no user since 7c55984e191f. Remove it.
Acked-by: Ludovic Desroches
Acked-by: Nicolas Ferre
Signed-off-by: Romain Izard
---
drivers/usb/gadget/udc/atmel_usba_udc.c | 1 -
include/linux/usb/atmel_usba_udc.h
Le 17/04/2018 à 16:53, Souptick Joarder a écrit :
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Reference id -> 1c8f4
On 11 May 2018 at 12:13, Kalle Valo wrote:
> Rafał Miłecki writes:
>
>> On 11 May 2018 at 11:17, Rafał Miłecki wrote:
>>> From: Rafał Miłecki
>>>
>>> This reverts commit 882164a4a928bcaa53280940436ca476e6b1db8e.
>>>
>>> Above commit added "SSB = y" dependency to the wrong symbol
>>> SSB_DRIVER_
> On 11 May 2018, at 01:31, Qing Huang wrote:
>
> When a system is under memory presure (high usage with fragments),
> the original 256KB ICM chunk allocations will likely trigger kernel
> memory management to enter slow path doing memory compact/migration
> ops in order to complete high order
On 05/11/2018 04:00 AM, Mark Brown wrote:
On Wed, May 09, 2018 at 01:49:21PM +0200, Jorge Ramirez-Ortiz wrote:
On 05/09/2018 10:39 AM, Mark Brown wrote:
I don't understand what voltile access means for write only devices.
Volatile means that we don't read the cache but go direct to the
hardware
Added entry for at91 usart mfd driver.
Signed-off-by: Radu Pirea
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8e2a2fddbd19..ca06c6f58299 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9192,6 +9192,13 @@ S: Supported
F: driv
Hello,
This is the second version of driver. I added a mfd driver which by
default probes atmel_serial driver and if in dt is specified to probe
the spi driver, then the spi-at91-usart driver will be probed. The
compatible for atmel_serial is now the compatible for at91-usart mfd
driver and compat
These are bindings for at91-usart IP in spi spi mode. There is no support for
internal chip select. Only kind of chip selects available are gpio chip
selects.
Signed-off-by: Radu Pirea
---
.../bindings/spi/microchip,at91-usart-spi.txt | 28 +++
1 file changed, 28 insertions(+)
c
This mfd driver is just a wrapper over atmel_serial driver and
spi-at91-usart driver. Selection of one of the drivers is based on a
property from device tree. If the property is not specified, the default
driver is atmel_serial.
Signed-off-by: Radu Pirea
---
drivers/mfd/Kconfig
601 - 683 of 683 matches
Mail list logo
