On Sat, Mar 09, 2019 at 12:53:59PM +0300, Maxim Zhukov wrote:
> Start using new api for linkmode bitmap
>
> Fixed build after 3c1bcc8614db ("net: ethernet: Convert phydev advertize and
> supported from u32 to link mode")
>
> Signed-off-by: Maxim Zhukov
> ---
> drivers/staging/mt7621-eth/mdio.c
On Tue, Mar 12, 2019 at 7:36 AM Subhra Mazumdar
wrote:
>
>
> On 3/11/19 11:34 AM, Subhra Mazumdar wrote:
> >
> > On 3/10/19 9:23 PM, Aubrey Li wrote:
> >> On Sat, Mar 9, 2019 at 3:50 AM Subhra Mazumdar
> >> wrote:
> >>> expected. Most of the performance recovery happens in patch 15 which,
> >>> u
On Wed, Mar 13, 2019 at 06:57:17PM +, Ian Abbott wrote:
> On 04/03/2019 14:33, Ian Abbott wrote:
> > `ni_cdio_cmdtest()` validates Comedi asynchronous commands for the DIO
> > subdevice (subdevice 2) of supported National Instruments M-series
> > cards. It is called when handling the `COMEDI_C
CC: Marc Zyngier
CC: Thomas Gleixner
CC: Dou Liyang
CC: Julien Thierry
CC: Peter Xu
CC: linux-kernel@vger.kernel.org
Signed-off-by: Peter Xu
---
include/linux/irq.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/irq.h b/include/linux/irq.h
index 5e91f6bcaac
Add probe_user_read(), strncpy_from_unsafe_user() and
strnlen_unsafe_user() which allows caller to access user-space
in IRQ context.
Current probe_kernel_read() and strncpy_from_unsafe() are
not available for user-space memory, because it sets
KERNEL_DS while accessing data. On some arch, user add
Add user memory access attribute for kprobe event arguments.
If a given 'local variable' is in user-space, User can
specify memory access method by '@user' suffix. This is
not only for string but also for data structure.
If we access a field of data structure in user memory from
kernel on some arc
Support user-space dereference syntax for probe event arguments
to dereference the data-structure or array in user-space.
The syntax is just adding 'u' before an offset value.
+|-u()
e.g. +u8(%ax), +u0(+0(%si))
For example, if you probe do_sched_setscheduler(pid, policy,
param) and record para
Add a user-memory access syntax testcase which checks
new user-memory access syntax and ustring type.
Signed-off-by: Masami Hiramatsu
---
Changes in v6:
- Add $argN availability check
---
.../ftrace/test.d/kprobe/kprobe_args_user.tc | 32
1 file changed, 32 insert
Add "ustring" type for fetching user-space string from kprobe event.
User can specify ustring type at uprobe event, and it is same as
"string" for uprobe.
Note that probe-event provides this option but it doesn't choose the
correct type automatically since we have not way to decide the address
is
Hi,
Here is the v6 series of probe-event to support user-space access.
In this version, I replaced user_access_ok() patch with access_ok()
enhancement, which allows user to call access_ok() in IRQ context
if it disables pagefault. In the result of this change, I also
removed user_access_ok() rela
WARN_ON_IN_IRQ() assumes that the access_ok() and following
user memory access can sleep. But this assumption is not
always correct; when the pagefault is disabled, following
memory access will just returns -EFAULT and never sleep.
Add pagefault_disabled() check in WARN_ON_ONCE() so that
it can ig
On 2019/3/17 3:42, Andrea Arcangeli wrote:
> On Sat, Mar 16, 2019 at 05:38:54PM +0800, zhong jiang wrote:
>> On 2019/3/16 5:39, Andrea Arcangeli wrote:
>>> On Fri, Mar 08, 2019 at 03:10:08PM +0800, zhong jiang wrote:
I can reproduce the issue in arm64 qemu machine. The issue will leave
Hi, Christoph & all,
I noticed that starting from commit 0d9f0a52c8b9 ("virtio_scsi: use
virtio IRQ affinity", 2017-02-27) the virtio scsi driver is using a
new way (via irq_create_affinity_masks()) to automatically initialize
IRQ affinities for the multi-queues, which is different comparing to
al
On Sun, Mar 17, 2019 at 10:15:34PM -0300, Ignacio Losiggio wrote:
> Signed-off-by: Ignacio Losiggio
> ---
> drivers/staging/gdm724x/gdm_mux.c | 28 ++--
> 1 file changed, 6 insertions(+), 22 deletions(-)
I can not take patches without any changelog text, sorry.
greg k-h
Hi Marc,
On 07/03/19 5:32 PM, Marc Zyngier wrote:
> On Thu, 07 Mar 2019 09:12:30 +,
> Kishon Vijay Abraham I wrote:
>>
>> Hi,
>>
>> On 23/02/19 5:41 PM, Marc Zyngier wrote:
>>> On Thu, 21 Feb 2019 16:24:14 +
>>> Lorenzo Pieralisi wrote:
>>>
On Thu, Feb 21, 2019 at 03:45:12PM +0530,
Hi, Naga,
On 03/13/2019 12:30 PM, Naga Sureshkumar Relli wrote:
> Hi,
>
>
>
> Currently I am facing an issue with is25wp256d part.
>
> 1. With u-boot the data integrity is working(erase, write, read and verify)
> with out any issues
> 2. Don’t probe the qspi at u-boot, and boot Linux an
Dmitry Vyukov wrote:
> > Then, we need to find what test is changing console_loglevel.
> > Maybe add debug BUG_ON() in linux-next.git using
> > CONFIG_DEBUG_AID_FOR_SYZBOT ?
>
> Is there a single place to catch this? I could run syzkaller locally
> first with the check.
>
There is no such place
On Mon, 2019-03-11 at 08:45 +0200, Jarkko Sakkinen wrote:
> Hi
>
> Just wondering what will happen if kzalloc() fails in scif_mmap.c. How
> it is recovered? I don't see anything in the VMA callbacks taking care
> of this.
Hi Jarkko,
scif_insert_vma(..) is called from scif_mmap(..) and scif_vma_o
Hi Alex,
In commit
4dc982bbdaad ("drm/amd/powerplay: fix memdup.cocci warnings")
Fixes tag
Fixes: 76760fe3c00d ("drm/amd/powerplay: add function to store overdrive
information for smu11")
has these problem(s):
- Target SHA1 does not exist
Did you mean:
ec95996ed982 ("drm/amd/powerp
Hi Alex,
Commits
b208c3a940b9 ("drm/amdkfd: avoid HMM change cause circular lock")
8a3397a108e5 ("drm/amdgpu: use HMM callback to replace mmu notifier")
are missing a Signed-off-by from their committers.
--
Cheers,
Stephen Rothwell
pgpA4QWP9wuEX.pgp
Description: OpenPGP digital signature
On Sun, Mar 17, 2019 at 07:22:17PM -0500, Alex G wrote:
> On 3/17/19 4:18 PM, Linus Torvalds wrote:
> > On Fri, Mar 8, 2019 at 9:31 AM Bjorn Helgaas wrote:
> > >
> > >- Report PCIe links that become degraded at run-time (Alexandru
> > > Gagniuc)
> >
> > Gaah. Only now as I'm about to do the
We should use SoC compatible string in stead of wildcard string for
PMIC child devices.
Signed-off-by: Baolin Wang
---
Hi Lee,
Could you merge this patch into v5.1-rc if no objection from you?
Since our DTS patches had been merged into v5.1, our PMIC can not
work without this patch. Thanks.
---
On Fri, Mar 15, 2019 at 7:13 PM Luis Henriques wrote:
>
> I'm occasionally seeing a kmemleak warning in xfstest generic/013:
>
> unreferenced object 0x8881fccca940 (size 32):
> comm "kworker/0:1", pid 12, jiffies 4295005883 (age 130.648s)
> hex dump (first 32 bytes):
> 01 00 00 00 00 0
On Mon, Mar 18, 2019 at 10:10:20AM +0800, kbuild test robot wrote:
> Hi Jacky,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on ipvs-next/master]
> [also build test WARNING on v5.1-rc1 next-20190306]
> [if your patch is applied to the wrong git tree, plea
Add i.MX system controller RTC alarm support, the RTC alarm
is implemented via SIP(silicon provider) runtime service call
and ARM-Trusted-Firmware will communicate with system controller
via MU(message unit) IPC to set RTC alarm. When RTC alarm fires,
system controller will generate a common MU irq
On i.MX8QXP, SCU uses MU1 general interrupt channel #3 to notify
user for IRQs of RTC alarm, thermal alarm and WDOG etc., mailbox
RX doorbell mode is used for this function, this patch adds
support for it.
Signed-off-by: Anson Huang
Reviewed-by: Dong Aisheng
---
No changes.
---
arch/arm64/boot/
Would anyone please give some suggestions ?
It looks like there somethings wrong in the read-in data,
/* skip all the enclosure descriptors */
for (i = 0; i < num_enclosures && type_ptr < buf + len; i++) {
types += type_ptr[2];
type_ptr += type_ptr
Add scu general interrupt function support.
Signed-off-by: Anson Huang
Reviewed-by: Rob Herring
Reviewed-by: Dong Aisheng
---
Changes since V4:
- add mu aliase info and example in binding doc.
---
.../devicetree/bindings/arm/freescale/fsl,scu.txt | 29 +-
1 file ch
The System Controller Firmware (SCFW) controls RTC, thermal
and WDOG etc., these resources' interrupt function are managed
by SCU. When any IRQ pending, SCU will notify Linux via MU general
interrupt channel #3, and Linux kernel needs to call SCU APIs
to get IRQ status and notify each module to han
Hi Steven, Catalin and Will:
>
> in the previous case, initrd_start and initrd_end can be successfully
> returned either (base < memblock_start_of_DRAM()) or (base + size >
> memblock_start_of_DRAM() + linear_region_size).
>
> That means even linear mapping range check fail for initrd_start and
> i
Hi guys,
> -Original Message-
> From: linux-arm-kernel On
> Behalf Of Mark Rutland
> Sent: Saturday, March 16, 2019 12:13 AM
> To: Okamoto, Takayuki/岡本 高幸
> Cc: 'Catalin Marinas' ; 'Will Deacon'
> ; 'linux-kernel@vger.kernel.org'
> ; Zhang, Lei/張 雷 ;
> 'James Morse' ; hange-folder>?
> ;
Best Regards!
Anson Huang
> -Original Message-
> From: Aisheng Dong
> Sent: 2019年3月15日 19:05
> To: Anson Huang ; robh...@kernel.org;
> mark.rutl...@arm.com; shawn...@kernel.org; s.ha...@pengutronix.de;
> ker...@pengutronix.de; feste...@gmail.com; a.zu...@towertech.it;
> alexandre.bell...
Hi all,
Changes since 20190306:
The cisco tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree): 591
502 files changed, 14759 insertions(+), 4153 deletions(-)
I have created today's
Document some things of note to gcov users:
1. GCC gcov and Clang llvm-cov tools are not compatible.
2. The use of GCC vs Clang is transparent at build-time.
Also adjust the documentation to account for the removal of config
symbol CONFIG_GCOV_FORMAT_AUTODETECT by commit 6a61b70b43c9
("gcov: remov
This patch series adds Clang support for gcov.
Patch 1 refactors existing code in preparation for Clang support.
Patch 2 implements necessary LLVM runtime hooks and gcov kernel interfaces.
Patch 3 updates documentation.
Greg Hackmann (2):
gcov: Clang: move common GCC code into gcc_base.c
gcov
From: Greg Hackmann
base.c contains a few callbacks specific to GCC's gcov implementation.
Move these into their own module in preparation for Clang support.
Signed-off-by: Greg Hackmann
Signed-off-by: Nick Desaulniers
Signed-off-by: Tri Vo
Tested-by: Trilok Soni
Tested-by: Prasad Sodagudi
From: Greg Hackmann
LLVM uses profiling data that's deliberately similar to GCC, but has a very
different way of exporting that data. LLVM calls llvm_gcov_init() once per
module, and provides a couple of callbacks that we can use to ask for more
data.
We care about the "writeout" callback, whic
On Tue, 12 Mar 2019, I wrote:
> ... I did another experiment with the latter (forced inline) approach,
> to see if some optimizations can still be used with -ffreestanding.
>
> diff --git a/include/linux/string.h b/include/linux/string.h
> index 7927b875f80c..25b5bf689018 100644
> --- a/include/
On 15-03-19, 13:29, Peter Zijlstra wrote:
> On Fri, Mar 15, 2019 at 02:43:07PM +0530, Viresh Kumar wrote:
> > diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c
> > index 3fae23834069..cff8779fc0d2 100644
> > --- a/arch/x86/kernel/tsc.c
> > +++ b/arch/x86/kernel/tsc.c
> > @@ -956,28 +956,38
> -Original Message-
> From: Aisheng Dong
> Sent: 2019年3月15日 21:39
> To: Peng Fan ; shawn...@kernel.org;
> s.ha...@pengutronix.de; ker...@pengutronix.de; feste...@gmail.com;
> dl-linux-imx ; Anson Huang ;
> a...@arndb.de; linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.or
From: chen jie
sendfile() softlockup for big files
[34922.213193] [Softlockup Clock][34922213187422]
[34922.213204] BUG: soft lockup - CPU#1 stuck for 60008ms! [trinity-c1:20239]
[34922.213211] Modules linked in: rtos_snapshot(O) rsm(O) nfsv3 veth(O)
higmac(O) comm(O) nand mtdblock mtd_blkdevs
When the entire expression can be shown in the same line breaking it
makes it more difficult to read.
Signed-off-by: Ignacio Losiggio
---
drivers/staging/gdm724x/gdm_mux.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/gdm724x/gdm_mux.c
b/drivers/stag
Signed-off-by: Ignacio Losiggio
---
drivers/staging/gdm724x/gdm_mux.c | 28 ++--
1 file changed, 6 insertions(+), 22 deletions(-)
diff --git a/drivers/staging/gdm724x/gdm_mux.c
b/drivers/staging/gdm724x/gdm_mux.c
index e2a050ba6fbb..fa8585ea1572 100644
--- a/drivers/stag
On (03/17/19 16:35), Greg Kroah-Hartman wrote:
> On Mon, Mar 18, 2019 at 12:20:14AM +0900, Sergey Senozhatsky wrote:
> > cpu_to_le16() is capable enough to detect __builtin_constant_p()
> > and to use an appropriate compile time ___constant_swahbXX()
> > function.
> >
> > So we can use cpu_to_le16
Hi Linus,
First rc pull request - nothing too special, just some driver bug
fixes that have been sitting during the merge window.
Thanks,
Jason
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repo
Describe AUTOFS_EXP_FORCED in addition to AUTOFS_EXP_IMMEDIATE in the
description of the AUTOFS_DEV_IOCTL_EXPIRE_CMD ioctl.
Signed-off-by: Ian Kent
---
Documentation/filesystems/autofs-mount-control.txt |6 --
Documentation/filesystems/autofs.txt |5 +
2 files chang
Add a idescription of the "ignore" pseudo mount option that can be
used to provide a generic indicator to applications that the mount
entry should be ignored when displaying mount information.
Signed-off-by: Ian Kent
---
Documentation/filesystems/autofs.txt | 15 +++
1 file changed
Update the description of AUTOFS_EXP_LEAVES to cover its possible
future use with amd format mount maps.
Signed-off-by: Ian Kent
---
Documentation/filesystems/autofs.txt |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/Documentation/filesystems/autofs.txt
b/Documen
A "strictexpire" mount option has been added to the autofs file
system.
It is meant to be used in cases where a GUI continually accesses
or an application frquently scans an automount directory tree
causing an accumulation of otherwise unused mounts.
Signed-off-by: Ian Kent
---
Documentation/fi
Alter a few word usages in Documentation/filesystems/autofs.txt
and correct some spelling mistakes.
Signed-off-by: Ian Kent
---
Documentation/filesystems/autofs.txt | 25 -
1 file changed, 12 insertions(+), 13 deletions(-)
diff --git a/Documentation/filesystems/autofs.
Hi all,
Today's linux-next merge of the cisco tree got a conflict in:
arch/powerpc/configs/skiroot_defconfig
between commit:
805bf3b75529 ("powerpc/configs: Sync skiroot defconfig")
from Linus' tree and commit:
5d4514a9c291 ("powerpc: convert config files to generic cmdline")
from the
El dom, 17 de mar 2019 a las 8:23 AM, Greg KH
escribió:
For some of these, there is no real change needed, it's all up to the
author's "taste", so they are not needed.
Thanks for the feedback! I will send a revised version.
On Sun, Mar 17, 2019 at 08:40:19AM -0700, Daniel Colascione wrote:
> On Sun, Mar 17, 2019 at 4:42 AM Christian Brauner
> wrote:
> >
> > On Sat, Mar 16, 2019 at 09:53:06PM -0400, Joel Fernandes wrote:
> > > On Sat, Mar 16, 2019 at 12:37:18PM -0700, Suren Baghdasaryan wrote:
> > > > On Sat, Mar 16,
On 3/17/19 4:18 PM, Linus Torvalds wrote:
On Fri, Mar 8, 2019 at 9:31 AM Bjorn Helgaas wrote:
- Report PCIe links that become degraded at run-time (Alexandru Gagniuc)
Gaah. Only now as I'm about to do the rc1 release am I looking at new
runtime warnings, and noticing that this causes
Currently we reach inside the list_head. This is a violation of the
layer of abstraction provided by the list_head. It makes the code
fragile. More importantly it makes the code wicked hard to understand.
The code logic is based on the page in which an allocation was made, we
want to modify the
SLUB allocator makes heavy use of ifdef/endif pre-processor macros.
The pairing of these statements is at times hard to follow e.g. if the
pair are further than a screen apart or if there are nested pairs. We
can reduce cognitive load by adding a comment to the endif statement of
form
#ifd
Linus Torvalds wrote on Sun, Mar 17, 2019:
> Hmm. I wonder what makes it valid to have concurrent updates to
> i_size? Yes, yes, you added that spinlock to make the update itself
> atomic on 32-bit, but it sounds a bit odd in the first place to have
> two things possibly changing the size of a file
Currently we use the page->lru list for maintaining lists of slabs. We
have a list in the page structure (slab_list) that can be used for this
purpose. Doing so makes the code cleaner since we are not overloading
the lru list.
Use the slab_list instead of the lru list for maintaining lists of
sl
We now use the slab_list list_head instead of the lru list_head. This
comment has become stale.
Remove stale comment from page struct slab_list list_head.
Acked-by: Christoph Lameter
Signed-off-by: Tobin C. Harding
---
include/linux/mm_types.h | 2 +-
1 file changed, 1 insertion(+), 1 deletio
Currently if we wish to rotate a list until a specific item is at the
front of the list we can call list_move_tail(head, list). Note that the
arguments are the reverse way to the usual use of list_move_tail(list,
head). This is a hack, it depends on the developer knowing how the
list_head operate
Hi,
v4 fixes patch 3 (change _all_ instances of ->lru to ->slab_list) as
noticed by Roman. Built, booted, and tested with the test modules
mentioned below.
Roman,
I kept your reviewed-by tag on patch 3 since functionally its the same
patch (and the additional changes were pointed out by you :).
Currently we use the page->lru list for maintaining lists of slabs. We
have a list_head in the page structure (slab_list) that can be used for
this purpose. Doing so makes the code cleaner since we are not
overloading the lru list.
The slab_list is part of a union within the page struct (include
Currently we use the page->lru list for maintaining lists of slabs. We
have a list in the page structure (slab_list) that can be used for this
purpose. Doing so makes the code cleaner since we are not overloading
the lru list.
Use the slab_list instead of the lru list for maintaining lists of
sl
Hi all,
On Mon, 4 Feb 2019 09:33:34 +1100 Stephen Rothwell
wrote:
>
> After merging the vfs tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> In file included from include/linux/printk.h:7,
> from include/linux/kernel.h:14,
>
Am Montag, 18. März 2019, 00:09:09 CET schrieb Colin King:
> From: Colin Ian King
>
> The function link_file declaration in the header file has the order
> of the two arguments (from, to) swapped when compared to the definition
> arguments of (to, from). Fix this by swapping them around to match
Hi all,
After merging the bluetooth tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/bluetooth/btmtksdio.c: In function 'btmtksdio_interrupt':
drivers/bluetooth/btmtksdio.c:470:2: warning: 'old_len' may be used
uninitialized in this function [-Wmaybe-uninitiali
This should never have been defined in the arch tree to begin with,
and now uapi/linux/audit.h header is going to use EM_UNICORE
in order to define AUDIT_ARCH_UNICORE which is needed to implement
syscall_get_arch() which in turn is required to extend
the generic ptrace API with PTRACE_GET_SYSCALL_I
From: Colin Ian King
The function snd_opl3_drum_switch declaration in the header file
has the order of the two arguments on_off and vel swapped when
compared to the definition arguments of vel and on_off. Fix this
by swapping them around to match the definition.
This error predates the git hist
From: Colin Ian King
The function link_file declaration in the header file has the order
of the two arguments (from, to) swapped when compared to the definition
arguments of (to, from). Fix this by swapping them around to match
the definition.
This error predates the git history, so no idea whe
The assembler option -mauto-it is no longer a valid option. The last
remaining references have been removed from the documentation in
July 2009 [0].
The currently supported binutils version is 2.20 (released in
September 2009) or higher where gas supports -mimplicit-it=always.
Drop the fallback to
Currently LLVM's integrated assembler does not recognize .w form
of the pld instructions (LLVM Bug 40972 [0]):
./arch/arm/include/asm/processor.h:133:5: error: invalid instruction
"pldw.w\t%a0 \n"
^
:2:1: note: instantiated into assembly her
CPU always jumps into reset handler in ARM-mode from the Trusted
Foundations firmware, hence let's make CPU to always jump into kernel
in ARM-mode regardless of the firmware presence. This is required to
make Thumb-2 kernel working with the Trusted Foundations firmware on
Tegra30.
Tested-by: Rober
CPU isn't allowed to touch secure registers while running under secure
monitor. Hence skip applying of CPU erratas in the reset handler if
Trusted Foundations firmware presents.
Partially based on work done by Michał Mirosław [1].
[1] https://www.spinics.net/lists/arm-kernel/msg594768.html
Teste
In order to suspend-resume CPU with Trusted Foundations firmware being
present on Tegra30, the LP1/LP2 boot vectors and CPU caches need to be
set up using the firmware calls and then suspend code shall avoid
re-disabling parts that were disabled by the firmware.
Tested-by: Robert Yang
Tested-by:
On Tegra30 L2 cache should be initialized using firmware call if CPU
is running in insecure mode. Set up the required outer-cache write_sec()
callback early during boot using the firmware API, it is always a NO-OP
on T114+ and is NO-OP on T20/30 if Trusted Foundations firmware node
isn't present in
Implement L2 cache initialization firmware callback that should be
invoked early during boot in order to set up the required outer cache
driver's callbacks and add the callback required for L2X0 maintenance.
Partially based on work done by Michał Mirosław [1].
[1] https://www.spinics.net/lists/ar
Hi Kieran,
Thank you for the patch.
On Fri, Mar 15, 2019 at 05:01:05PM +, Kieran Bingham wrote:
> The rcar_du_crtc functions have a heavy reliance on the rcar_du_group
> structure, in many cases just to access the DU device context.
>
> To better separate the groups out of the CRTC handling
Hello,
This patchset adds support for the Trusted Foundations firmware on
NVIDIA Tegra30. Pretty much all of Tegra30 consumer devices have that
firmware and upstream kernel can't boot on those devices without the
firmware support. This series was tested on Nexus 7, TF300T and Ouya
Tegra30 devices.
The Trusted Foundations firmware call varies depending on the required
suspend-mode. Make the firmware API to take the mode argument in order
to expose all of the modes to firmware user.
Tested-by: Robert Yang
Tested-by: Michał Mirosław
Signed-off-by: Dmitry Osipenko
---
arch/arm/firmware/trus
Add a helper that provides information about whether Trusted Foundations
firmware operations have been registered.
Tested-by: Robert Yang
Tested-by: Michał Mirosław
Signed-off-by: Dmitry Osipenko
---
arch/arm/firmware/trusted_foundations.c| 5 +
arch/arm/include/asm/trusted_foundations
On Sun, Mar 17, 2019 at 10:16 AM Serge E. Hallyn wrote:
>
> On Sun, Mar 17, 2019 at 10:11:10AM -0700, Daniel Colascione wrote:
> > On Sun, Mar 17, 2019 at 9:35 AM Serge E. Hallyn wrote:
> > >
> > > On Sun, Mar 17, 2019 at 12:42:40PM +0100, Christian Brauner wrote:
> > > > On Sat, Mar 16, 2019 at
It's Sunday, and two weeks have passed, and everything is normal. You
all know the drill by now - the merge window is closed, and things are
supposed to calm down.
The merge window felt fairly normal to me. And looking at the stats,
nothing really odd stands out either. It's a regular sized releas
On Fri, Mar 8, 2019 at 9:31 AM Bjorn Helgaas wrote:
>
> - Report PCIe links that become degraded at run-time (Alexandru Gagniuc)
Gaah. Only now as I'm about to do the rc1 release am I looking at new
runtime warnings, and noticing that this causes
genirq: Threaded irq requested with handler=N
The pull request you sent on Mon, 18 Mar 2019 00:59:54 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
> tags/kbuild-v5.1-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/28d747f266fb73cd28a1b9a174cc3738fc177b00
Thank you!
--
Deet-
add a maintainer for the newly created ultrasonic driver family of maxbotix
Signed-off-by: Andreas Klinger
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index dce5c099f43c..fa054f8cc7fb 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9234,6 +
Add I2CXL-MaxSonar ultrasonic distance sensors of types mb1202, mb1212,
mb1222, mb1232, mb1242, mb7040, mb7137 using an i2c interface
Implemented functionality:
- reading the distance via in_distance_raw
- buffered mode with trigger
- make use of interrupt to announce completion of ranging
Add mb
Add doc for dt binding maxbotix,mb1232. This binding is for MaxBotix
I2CXL-MaxSonar ultrasonic rangers which share a common i2c interface.
Signed-off-by: Andreas Klinger
---
.../bindings/iio/proximity/maxbotix,mb1232.txt | 31 ++
1 file changed, 31 insertions(+)
create m
Add MaxBotix, which is a vendor of ultrasonic rangers in different
varieties and interfaces.
Signed-off-by: Andreas Klinger
Reviewed-by: Andreas Färber
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documen
This patch series adds support for I2CXL-MaxSonar ultrasonic distance
sensors with i2c interface of vendor MaxBotix
Supported types are:
mb1202, mb1212, mb1222, mb1232, mb1242, mb7040, mb7137
Implemented and tested functionality:
- reading the distance via in_distance_raw
- buffered mode with
Dear Friend,
I am Mrs Alice Johnson.am sending you this brief letter to solicit your
partnership to transfer $23.5 million US Dollars.I shall send you more
information and procedures when I receive positive response from you.
please send me a message in my Email box (mrsalicejohns...@gmail.com)
as
Dear Friend,
I am Mrs Alice Johnson.am sending you this brief letter to solicit your
partnership to transfer $23.5 million US Dollars.I shall send you more
information and procedures when I receive positive response from you.
please send me a message in my Email box (mrsalicejohns...@gmail.com)
as
This patch refactors the code that is responsible to set the DMA mask for
the device.
Upon each change of the dma mask, the driver will save the new value that
was set. This is needed in order to make sure we don't try to increase the
mask a second time, in case we failed in the first time. This i
This patch removes some old defines which are not in use anymore.
Signed-off-by: Oded Gabbay
---
drivers/misc/habanalabs/goya/goyaP.h | 14 ++
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/drivers/misc/habanalabs/goya/goyaP.h
b/drivers/misc/habanalabs/goya/goyaP.h
in
From: Tomer Tayar
This patch moves the code that is responsible of the communication
vs. the F/W to a dedicated file. This will allow us to share the code
between different ASICs.
Signed-off-by: Tomer Tayar
Signed-off-by: Oded Gabbay
---
drivers/misc/habanalabs/Makefile | 2 +-
dr
At the start of some IOCTLs we check if the device is disabled or in reset.
If it is, we return -EBUSY and print a message to kernel log.
Because these IOCTLs can be called at very high frequency, use ratelimit
to avoid spamming the kernel log. Also use the same type of message -
dev_warn - in all
From: Omer Shpigelman
This patch adds shadow mapping to the MMU module. The shadow mapping
allows traversing the page table in host memory rather reading each PTE
from the device memory.
It brings better performance and avoids reading from invalid device
address upon PCI errors.
Only at the end o
From: Tomer Tayar
Remove pointers to ASIC-specific functions and instead call the functions
explicitly as they are not accessed from outside the ASIC-specific files.
Signed-off-by: Tomer Tayar
Signed-off-by: Oded Gabbay
---
drivers/misc/habanalabs/goya/goya.c | 12 +++-
drivers/misc/
This patch adds two comments in uapi/habanalabs.h:
- From which queue id the internal queues begin
- Invalid values that can be returned in the seq field from the CS IOCTL
Signed-off-by: Oded Gabbay
---
include/uapi/misc/habanalabs.h | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
From: Tomer Tayar
Print the name of a busy engine when checking if a device is idle.
The change is done mainly to help a user to pinpoint problems in his
topology's recipe.
Signed-off-by: Tomer Tayar
Signed-off-by: Oded Gabbay
---
drivers/misc/habanalabs/goya/goya.c| 24 --
Hard-reset of our device should never fail, due to dangers of permanent
damage to the H/W.
This patch removes the last place in the reset path where the driver might
exit before doing the actual reset.
Signed-off-by: Oded Gabbay
---
drivers/misc/habanalabs/device.c | 19 +--
1 f
1 - 100 of 200 matches
Mail list logo
