Drop the use of tc_write() as well as "magicly" used "ret" and "err:"
and replace it with a simple call to regmap_write(). No functional
change intended.
Signed-off-by: Andrey Smirnov
Cc: Archit Taneja
Cc: Andrzej Hajda
Cc: Laurent Pinchart
Cc: Chris Healy
Cc: Lucas Stach
Cc: dri-de...@lists
On Tue, Feb 26, 2019 at 10:40:05AM -0500, Shravan Kumar Ramani wrote:
> EMC1444 is compatible with EMC1404. Add it to device ID table.
>
Is that some super-secretive chip ? The Microchip website completely fails
to provide information about it. It lists a chip with that name under
"Microcontrolle
On Tue 26-02-19 14:19:42, Qian Cai wrote:
> On Tue, 2019-02-26 at 19:20 +0100, Michal Hocko wrote:
> > Btw. what happens if the offlined pfn range is removed completely? Is
> > the range still mapped? What kind of consequences does this have?
>
> Well, the pages are still marked as reserved as wel
On 2/25/19 10:20 PM, Len Brown wrote:
> -/* leaf 0xb sub-leaf types */
> +/* extended topology sub-leaf types */
> #define INVALID_TYPE 0
> #define SMT_TYPE 1
> #define CORE_TYPE2
> +#define DIE_TYPE 5
Looking in the SDM, Vol. 3A "8.9.1 Hierarchical Mapping of Shared
Resources", the
After sending a power on pulse the driver has a delay of 100ms
to allow the host controller to boot. Move the delay into
qca_send_power_pulse(), since it is directly related with the
power-on pulse.
Signed-off-by: Matthias Kaehlcke
Reviewed-by: Balakrishna Godavarthi
---
Changes in v2:
- added '
There are only two types of power pulses 'on' or 'off', pass a boolean
instead of the power pulse 'command'.
Signed-off-by: Matthias Kaehlcke
Reviewed-by: Balakrishna Godavarthi
---
Changes in v2:
- added 'Reviewed-by: Balakrishna Godavarthi ' tag
---
drivers/bluetooth/hci_qca.c | 9 +
Initialization of the QCA WCN3990 often fails at boot time:
[ 15.205224] Bluetooth: hci0: setting up wcn3990
[ 17.341062] Bluetooth: hci0: command 0xfc00 tx timeout
[ 22.101453] ERROR: Bluetooth initialization failed
[ 25.337740] Bluetooth: hci0: Reading QCA version information failed
During initialization the power-on pulse is currently sent inmediately
after the prior power-off pulse. With this initialization often fails
at boot time:
[ 15.205224] Bluetooth: hci0: setting up wcn3990
[ 17.341062] Bluetooth: hci0: command 0xfc00 tx timeout
[ 22.101453] ERROR: Bluetooth in
On Mon, Feb 25, 2019 at 10:32 PM Yang Weijiang wrote:
>
> Guest queries CET SHSTK and IBT support by CPUID.(EAX=0x7,ECX=0),
> in return, ECX[bit 7] corresponds to SHSTK feature, and EDX[bit 20]
> corresponds to IBT feature.
> CR4.CET[bit 23] is CET master enable bit, it controls CET feature
> avai
Marc,
> The resolution is simple: we keep the HEAD version, and simply remove
> ufshcd_set_vccq_rail_unused() and its error-handling.
>
>
> Is that the information you were after?
Yes.
> Do you prefer the patch subject to be:
> Revert "scsi: ufs: disable vccq if it's not needed by UFS device"
On Sun, Feb 24, 2019 at 11:45:35AM -0800, Andy Lutomirski wrote:
> On Thu, Feb 21, 2019 at 2:57 PM Yu, Fenghua wrote:
> >
> > > From: Fenghua Yu [mailto:fenghua...@intel.com]
> > > On Wed, Feb 20, 2019 at 10:37:27PM -0800, Andy Lutomirski wrote:
> > > Or to simplify the situation, how about we sti
Hi,
Looks like commit d222e42e8816 ("dma-contiguous: do not allocate a
single page from CMA area") caused a regression at least for
omap dss where we now get the following error on init:
omapdss_dispc 58001000.dispc:
dispc_errata_i734_wa_init: dma_alloc_writecombine failed
Any ideas what might b
The current 300ms delay after a baudrate change is extremely long.
For WCM3990 it is sufficient to wait 10ms after the baudrate change
request has been sent over the wire.
Also use msleep() instead of a set_current_state() / schedule_timeout()
combo.
Matthias Kaehlcke (2):
hci_qca: Use msleep()
Call msleep() in qca_set_baudrate() instead of reimplementing it.
Signed-off-by: Matthias Kaehlcke
---
drivers/bluetooth/hci_qca.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c
index 26efc2ef98d9a..703e099515f24 1
The current 300ms delay after a baudrate change is extremely long.
For WCM3990 it is sufficient to wait 10ms after the baudrate change
request has been sent over the wire.
Signed-off-by: Matthias Kaehlcke
---
drivers/bluetooth/hci_qca.c | 28 +---
1 file changed, 21 inser
On Tue, 2019-02-26 at 20:40 +0100, Michal Hocko wrote:
> It seems you have missed the point of my question. It simply doesn't
> make much sense to have offline memory mapped. That memory is not
> accessible in general. So mapping it at the offline time is dubious at
> best.
Well, kernel_map_pages
On Tue, Feb 26, 2019 at 12:01:55PM -0800, Tony Lindgren wrote:
> Looks like commit d222e42e8816 ("dma-contiguous: do not allocate a
> single page from CMA area") caused a regression at least for
> omap dss where we now get the following error on init:
>
> omapdss_dispc 58001000.dispc:
> dispc_erra
Thanks for the review!
On 20/02/2019 19:22, Joe Perches wrote:
On Wed, 2019-02-20 at 09:49 +, Jonathan Cameron wrote:
On Mon, 18 Feb 2019 13:01:23 -0800 Joe Perches wrote:
On Mon, 2019-02-18 at 14:22 -0300, Lucas Oshiro wrote:
Add missing '\n' at the end of dev_err message on line 215.
On Tue, Feb 26, 2019 at 12:08:48PM -0800, Matthias Kaehlcke wrote:
> The current 300ms delay after a baudrate change is extremely long.
> For WCM3990 it is sufficient to wait 10ms after the baudrate change
> request has been sent over the wire.
>
> Signed-off-by: Matthias Kaehlcke
> ---
> driver
This reverts commit d222e42e88168fd67e6d131984b86477af1fc256.
The original change breaks omap dss:
omapdss_dispc 58001000.dispc:
dispc_errata_i734_wa_init: dma_alloc_writecombine failed
Let's revert it first and then find a safer solution instead.
Reported-by: Tony Lindgren
Signed-o
On 02/26/2019 12:30 PM, Linus Torvalds wrote:
> On Tue, Feb 26, 2019 at 12:17 AM Huang, Ying wrote:
>> As for fixing. Should we care about the cache line alignment of struct
>> inode? Or its size is considered more important because there may be a
>> huge number of struct inode in the system?
>
From: Li Yang
Date: Tue, 26 Feb 2019 13:03:17 -0600
> On Mon, Feb 25, 2019 at 1:01 AM Ioana Ciornei wrote:
>>
>> > Subject: Re: [PATCH 0/3] soc: fsl: dpio: enable and configure cache
>> > stashing
>> >
>> > From: Ioana Ciornei
>> > Date: Sat, 23 Feb 2019 08:48:42 +
>> >
>> > > The first tw
Quoting Brendan Higgins (2019-02-14 13:37:20)
> Add support for aborting/bailing out of test cases. Needed for
> implementing assertions.
Can you add some more text here with the motivating reasons for
implementing assertions and bailing out of test cases?
For example, I wonder why unit tests can
On Tue, 2019-02-26 at 10:33 -0800, Tony Lindgren wrote:
> Hi,
>
> * Trond Myklebust [700101 00:00]:
> > On Mon, 2019-02-25 at 22:27 +, Jon Hunter wrote:
> > > On 25/02/2019 21:03, Trond Myklebust wrote:
> > > This is nfsroot. I don't specify any particular NFS version from
> > > the kernel c
On Tue 26-02-19 15:10:39, Qian Cai wrote:
> On Tue, 2019-02-26 at 20:40 +0100, Michal Hocko wrote:
> > It seems you have missed the point of my question. It simply doesn't
> > make much sense to have offline memory mapped. That memory is not
> > accessible in general. So mapping it at the offline t
Hi all,
In commit
8af6c521cc23 ("ASoC: rsnd: gen: fix SSI9 4/5/6/7 busif related register
address")
Fixes tag
Fixes: commit 8c9d75033340 ("ASoC: rsnd: ssiu: Support BUSIF other than
BUSIF0")
has these problem(s):
- leading word 'commit' unexpected
--
Cheers,
Stephen Rothwell
pgp4C
On Mon, Feb 25, 2019 at 11:19 PM Ard Biesheuvel
wrote:
>
> On Tue, 26 Feb 2019 at 05:03, wrote:
> >
> > Clang warns: vector initializers are not compatible with NEON intrinsics
> > in big endian mode [-Wnonportable-vector-initialization]
> >
> > While this is usually the case, it's not an issue f
We'll have to fix them at some point.
Acked-by: Jason Wessel
Cheers,
Jason.
On 2/26/19 1:16 PM, Gustavo A. R. Silva wrote:
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warnings:
kernel/debug/gdbs
On Wed, Feb 20, 2019 at 10:37:27PM -0800, Andy Lutomirski wrote:
> On Wed, Feb 20, 2019 at 7:44 PM Tao Xu wrote:
> >
> > From: Fenghua Yu
>
> >
> > From patchwork Wed Jan 16 21:18:41 2019
> > Content-Type: text/plain; charset="utf-8"
>
> [snipped more stuff like this]
>
> What happened here?
>
Recent "New LSM Hooks" discussion has led me to the
thought that it might be a good idea to slightly
update the current documentation. The patchset adds
nothing new to the documentation, only fixes the old
description of hooks to reflect their current state.
V2 adds the clarification on arguments
From: Eric Biggers
If drm_gem_handle_create() fails in vgem_gem_create(), then the
drm_vgem_gem_object is freed twice: once when the reference is dropped
by drm_gem_object_put_unlocked(), and again by __vgem_gem_destroy().
This was hit by syzkaller using fault injection.
Fix it by skipping the
The @type argument of the sb_copy_data hook was removed
in the commit "LSM/SELinux: Interfaces to allow FS to control
mount options" (e0007529893c). This commit removes the description
of the @type argument from the LSM documentation.
Signed-off-by: Denis Efremov
---
include/linux/lsm_hooks.h |
The syslog hook was changed in the commit
"capabilities/syslog: open code cap_syslog logic to
fix build failure" (12b3052c3ee8). The argument @from_file
was removed from the hook. This patch updates the
documentation for the syslog hook accordingly.
Signed-off-by: Denis Efremov
---
include/linux
The task_setscheduler hook was changed in the commit
"security: remove unused parameter from security_task_setscheduler()"
(b0ae19811375). The arguments @policy, @lp were removed from the hook.
This patch updates the documentation accordingly.
Signed-off-by: Denis Efremov
---
include/linux/lsm_h
This patch slightly fixes the documentation for the
socket_post_create hook. The documentation states that
i_security field is accessible through inode field of socket
structure (i.e., 'sock->inode->i_security'). There is no inode
field in the socket structure. The i_security field is accessible
th
The path_chmod hook was changed in the commit
"switch security_path_chmod() to struct path *" (cdcf116d44e7).
The argument @mnt was removed from the hook, @dentry was changed
to @path. This patch updates the documentation accordingly.
Signed-off-by: Denis Efremov
---
include/linux/lsm_hooks.h |
The socket_getpeersec_dgram hook was changed in the commit
"[AF_UNIX]: Kernel memory leak fix for af_unix datagram
getpeersec patch" (dc49c1f94e34). The arguments @secdata
and @seclen were changed to @sock and @secid. This patch
updates the documentation accordingly.
Signed-off-by: Denis Efremov
This patch updates the documentation for the audit_* hooks
to use the same arguments names as in the hook's declarations.
Signed-off-by: Denis Efremov
---
include/linux/lsm_hooks.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/linux/lsm_hooks.h b/include/lin
The msg_queue_* hooks were changed in the commit
"msg/security: Pass kern_ipc_perm not msg_queue into the msg_queue
security hooks" (d8c6e8543294). The type of the argument msq was changed
from msq_queue to kern_ipc_perm. This patch updates the documentation
for the hooks accordingly.
Signed-off-b
Fix for name mismatch and omitted colons in the
security_list_options documentation.
Signed-off-by: Denis Efremov
---
include/linux/lsm_hooks.h | 23 +--
1 file changed, 9 insertions(+), 14 deletions(-)
diff --git a/include/linux/lsm_hooks.h b/include/linux/lsm_hooks.h
index
The shm_* hooks were changed in the commit
"shm/security: Pass kern_ipc_perm not shmid_kernel into the
shm security hooks" (7191adff2a55). The type of the argument
shp was changed from shmid_kernel to kern_ipc_perm. This patch
updates the documentation for the hooks accordingly.
Signed-off-by: Den
The sem_* hooks were changed in the commit
"sem/security: Pass kern_ipc_perm not sem_array into the
sem security hooks" (aefad9593ec5). The type of the argument
sma was changed from sem_array to kern_ipc_perm. This patch
updates the documentation for the hooks accordingly.
Signed-off-by: Denis Efr
On Tue, 26 Feb 2019 at 21:44, Nick Desaulniers wrote:
>
> On Mon, Feb 25, 2019 at 11:19 PM Ard Biesheuvel
> wrote:
> >
> > On Tue, 26 Feb 2019 at 05:03, wrote:
> > >
> > > Clang warns: vector initializers are not compatible with NEON intrinsics
> > > in big endian mode [-Wnonportable-vector-init
/habanalabs/habanalabs.ko] undefined!
> ERROR: "gen_pool_free" [drivers/misc/habanalabs/habanalabs.ko] undefined!
>
> Signed-off-by: Randy Dunlap
> Cc: Oded Gabbay
> ---
> drivers/misc/habanalabs/Kconfig |1 +
> 1 file changed, 1 insertion(+)
>
> --- l
On Tue, Feb 26, 2019 at 11:58:35AM -0600, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warning:
>
> drivers/watchdog/sbc60xxwdt.c: In function ‘fop_ioctl’:
> drivers/w
On Tue, Feb 26, 2019 at 12:01:14PM -0600, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warning:
>
> drivers/watchdog/sc520_wdt.c: In function ‘fop_ioctl’:
> drivers/wa
On Tue, Feb 26, 2019 at 01:07:43PM -0600, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warning:
>
> drivers/watchdog/w83877f_wdt.c: In function ‘fop_ioctl’:
> drivers/
Quoting Eric Biggers (2019-02-26 20:47:26)
> From: Eric Biggers
>
> If drm_gem_handle_create() fails in vgem_gem_create(), then the
> drm_vgem_gem_object is freed twice: once when the reference is dropped
> by drm_gem_object_put_unlocked(), and again by __vgem_gem_destroy().
>
> This was hit by
Hi,
On 26-02-19 20:23, Gustavo A. R. Silva wrote:
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
drivers/virt/vboxguest/vboxguest_core.c: In function ‘vbg_core_ioctl’:
drivers/virt/vboxguest/v
On Tue, Feb 26, 2019 at 5:55 AM Jisheng Zhang
wrote:
>
> Currently, the PCI dwc host users don't support the remove, but nothing
> prevent us from supporting it. To achieve this goal, we need to ensure
> we can do necessary clean up work.
>
> Jisheng Zhang (5):
> PCI: dwc: fix dw_pcie_free_msi()
On 2/26/19 2:47 PM, Jason Wessel wrote:
> We'll have to fix them at some point.
>
Yep. And we're about to fix them all.
> Acked-by: Jason Wessel
>
Thanks, Jason.
--
Gustavo
>
> Cheers,
> Jason.
>
> On 2/26/19 1:16 PM, Gustavo A. R. Silva wrote:
>> In preparation to enabling -Wimplicit-
On Tue, Feb 26, 2019 at 09:01:29PM +, Chris Wilson wrote:
> Quoting Eric Biggers (2019-02-26 20:47:26)
> > From: Eric Biggers
> >
> > If drm_gem_handle_create() fails in vgem_gem_create(), then the
> > drm_vgem_gem_object is freed twice: once when the reference is dropped
> > by drm_gem_objec
On Tue, 26 Feb 2019 at 18:50, Rafael J. Wysocki wrote:
>
> On Tue, Feb 26, 2019 at 3:55 PM Ulf Hansson wrote:
> >
> > Changes in v11:
> > - This version contains only the infrastructure changes that is needed for
> > deployment. The PSCI/ARM changes have also been updated and tested, but I
> >
On Tue, 2019-02-26 at 10:11 +, Vabhav Sharma wrote:
> From: Yogesh Gaur
>
> Add clockgen support for lx2160a.
> Added entry for compat 'fsl,lx2160a-clockgen'.
>
> Signed-off-by: Tang Yuantian
> Signed-off-by: Yogesh Gaur
> Signed-off-by: Vabhav Sharma
> Acked-by: Stephen Boyd
> Acked-by:
On Tue, 2019-02-26 at 10:11 +, Vabhav Sharma wrote:
> From: Yogesh Gaur
>
> Increase size of cmux_to_group array, to accomdate entry of
> -1 termination.
>
> Added -1, terminated, entry for 4080_cmux_grpX.
>
> Signed-off-by: Yogesh Gaur
> Signed-off-by: Vabhav Sharma
> Acked-by: Stephen B
On Sun, Feb 24, 2019 at 8:26 PM Anson Huang wrote:
>
> Hi, Guenter
>
> Best Regards!
> Anson Huang
>
> > -Original Message-
> > From: Guenter Roeck [mailto:groe...@gmail.com] On Behalf Of Guenter
> > Roeck
> > Sent: 2019年2月24日 11:20
> > To: Anson Huang ; Rob Herring
> > Cc: mark.rutl...@a
On Mon, Feb 25, 2019 at 11:04:42PM +0900, Masami Hiramatsu wrote:
> Hi,
>
> Here is an RFC series of probe-event to support user-space access
> methods, which we discussed in previous thread.
>
> https://lkml.kernel.org/r/20190220171019.5e81a4946b56982f324f7...@kernel.org
>
> So in this thread,
On Tue, 2017-09-05 at 14:12 +0900, Jiada Wang wrote:
> Previously i.MX SPI controller only works in Master mode.
> This patch adds support to i.MX51, i.MX53 and i.MX6 ECSPI
> controller to work also in Slave mode.
Recently DMA has been enabled for imx6/7 with SPI. This results in
memory corruptio
On Sun, Feb 24, 2019 at 5:26 PM Andrew Jeffery wrote:
>
> On Fri, 22 Feb 2019, at 08:55, Patrick Venture wrote:
> > The ASPEED AST2400, and AST2500 in some configurations include a
> > PCI-to-AHB MMIO bridge. This bridge allows a server to read and write
> > in the BMC's memory space.
>
> Bit of
From: Eric Biggers
If drm_gem_handle_create() fails in vgem_gem_create(), then the
drm_vgem_gem_object is freed twice: once when the reference is dropped
by drm_gem_object_put_unlocked(), and again by __vgem_gem_destroy().
This was hit by syzkaller using fault injection.
Fix it by skipping the
On Tue, 26 Feb 2019 18:58:03 +0900 Tetsuo Handa
wrote:
> Since commit a2e514453861dd39 ("kernel/hung_task.c: allow to set checking
> interval separately from timeout") added hung_task_check_interval_secs,
> setting a value different from hung_task_timeout_secs
>
> echo 0 > /proc/sys/kernel/hu
On Tue, Feb 26, 2019 at 10:31 PM Ulf Hansson wrote:
>
> On Tue, 26 Feb 2019 at 18:50, Rafael J. Wysocki wrote:
> >
> > On Tue, Feb 26, 2019 at 3:55 PM Ulf Hansson wrote:
> > >
> > > Changes in v11:
> > > - This version contains only the infrastructure changes that is needed
> > > for
> > > dep
On Tue, Feb 26, 2019 at 05:25:46PM +, Ghannam, Yazen wrote:
> From: Yazen Ghannam
>
> Define and use a macro for looping over the number of Unified Memory
> Controllers.
>
> No functional change.
>
> Signed-off-by: Yazen Ghannam
> ---
> Link:
> https://lkml.kernel.org/r/20190219202536.1546
On Tue, Feb 26, 2019 at 1:42 PM Patrick Venture wrote:
>
> On Sun, Feb 24, 2019 at 5:26 PM Andrew Jeffery wrote:
> >
> > On Fri, 22 Feb 2019, at 08:55, Patrick Venture wrote:
> > > The ASPEED AST2400, and AST2500 in some configurations include a
> > > PCI-to-AHB MMIO bridge. This bridge allows a
On Tue, 26 Feb 2019 10:13:14 +0100 Oscar Salvador wrote:
> When using mremap() syscall in addition to MREMAP_FIXED flag,
> mremap() calls mremap_to() which does the following:
>
> 1) unmaps the destination region where we are going to move the map
> 2) If the new region is going to be smaller, w
On Tue, 26 Feb 2019 at 22:52, Rafael J. Wysocki wrote:
>
> On Tue, Feb 26, 2019 at 10:31 PM Ulf Hansson wrote:
> >
> > On Tue, 26 Feb 2019 at 18:50, Rafael J. Wysocki wrote:
> > >
> > > On Tue, Feb 26, 2019 at 3:55 PM Ulf Hansson
> > > wrote:
> > > >
> > > > Changes in v11:
> > > > - This ver
On Tue, Feb 26, 2019 at 06:36:38PM +0300, Andrey Ryabinin wrote:
>
>
> On 2/25/19 7:03 AM, Roman Gushchin wrote:
> > On Fri, Feb 22, 2019 at 08:58:25PM +0300, Andrey Ryabinin wrote:
> >> In a presence of more than 1 memory cgroup in the system our reclaim
> >> logic is just suck. When we hit memo
On Tue, Feb 26, 2019 at 3:54 PM Ulf Hansson wrote:
>
> A common piece of data used by cpuidle governors, is the information about
> when the next timer/tick is going to fire. Rather than having each governor
> calling tick_nohz_get_next_timer|hrtimer() separately, let's consolidate
> the code by c
From: Eric Biggers
If drm_gem_handle_create() fails in vkms_gem_create(), then the
vkms_gem_object is freed twice: once when the reference is dropped by
drm_gem_object_put_unlocked(), and again by the extra calls to
drm_gem_object_release() and kfree().
Fix it by skipping the second release and
On Tue, Feb 26, 2019 at 11:06 PM Ulf Hansson wrote:
>
> On Tue, 26 Feb 2019 at 22:52, Rafael J. Wysocki wrote:
> >
> > On Tue, Feb 26, 2019 at 10:31 PM Ulf Hansson wrote:
> > >
> > > On Tue, 26 Feb 2019 at 18:50, Rafael J. Wysocki wrote:
> > > >
> > > > On Tue, Feb 26, 2019 at 3:55 PM Ulf Hanss
Quoting Eric Biggers (2019-02-26 22:08:58)
> From: Eric Biggers
>
> If drm_gem_handle_create() fails in vkms_gem_create(), then the
> vkms_gem_object is freed twice: once when the reference is dropped by
> drm_gem_object_put_unlocked(), and again by the extra calls to
> drm_gem_object_release() a
On Tue, Feb 26, 2019 at 11:08 PM Rafael J. Wysocki wrote:
>
> On Tue, Feb 26, 2019 at 3:54 PM Ulf Hansson wrote:
> >
> > A common piece of data used by cpuidle governors, is the information about
> > when the next timer/tick is going to fire. Rather than having each governor
> > calling tick_nohz
Hi Greg,
Thanks for the comments.
On Tue, 2019-02-26 at 03:53:11 -0800, Greg Kroah-Hartman wrote:
> On Sat, Feb 23, 2019 at 12:28:17PM -0800, Hyun Kwon wrote:
> > Add the dmabuf map / unmap interfaces. This allows the user driver
> > to be able to import the external dmabuf and use it from user s
This patch increase the size field in the uapi structure of the Memory
IOCTL from 32-bit to 64-bit. This is to allow the user to allocate and/or
map memory in chunks that are larger then 4GB.
Goya's device memory (DRAM) can be up to 16GB, and for certain
topologies, the user may want an allocation
On Wed, 27 Feb 2019, at 08:26, Patrick Venture wrote:
> On Tue, Feb 26, 2019 at 1:42 PM Patrick Venture wrote:
> >
> > On Sun, Feb 24, 2019 at 5:26 PM Andrew Jeffery wrote:
> > >
> >
> > >
> > > > +
> > > > + /* Access to these needs to be locked, held via probe, mapping
> > > > ioctl,
>
Hi Daniel,
Thanks for the comment.
On Tue, 2019-02-26 at 04:06:13 -0800, Daniel Vetter wrote:
> On Tue, Feb 26, 2019 at 12:53 PM Greg Kroah-Hartman
> wrote:
> >
> > On Sat, Feb 23, 2019 at 12:28:17PM -0800, Hyun Kwon wrote:
> > > Add the dmabuf map / unmap interfaces. This allows the user driver
On Tue, Feb 26, 2019 at 03:34:12PM -0600, Rob Herring wrote:
> > >
> > > I think Rob suggested that the SCU parent driver should instantiate the
> > > watchdog without explicit watchdog node. That would be possible, but it
> > > currently uses
> > > devm_of_platform_populate() to do the instantiati
On Fri, Feb 22, 2019 at 06:24:40PM -0800, Brian Norris wrote:
> Documentation/devicetree/bindings/usb/usb-device.txt describes the
> 'usbVID,...' compatible format, where VID is lower-case hexadecimal,
> with leading zeroes suppressed. Allow it here without complaining about
> lack of documentation
On Tue, Feb 26, 2019 at 2:20 PM Andrew Jeffery wrote:
>
>
>
> On Wed, 27 Feb 2019, at 08:26, Patrick Venture wrote:
> > On Tue, Feb 26, 2019 at 1:42 PM Patrick Venture wrote:
> > >
> > > On Sun, Feb 24, 2019 at 5:26 PM Andrew Jeffery wrote:
> > > >
> > >
> > > >
> > > > > +
> > > > > + /* Ac
On Fri, 22 Feb 2019 14:53:44 -0800, Brian Norris wrote:
> There are two USB PID/VID variations I've seen for this chip, and I want
> to utilize the 'interrupts' property defined here already.
>
> Signed-off-by: Brian Norris
> Reviewed-by: Matthias Kaehlcke
> ---
> v2:
> * drop leading zeroes fr
On Mon, Feb 25, 2019 at 07:04:01PM -0800, Andi Kleen wrote:
> [Changes:
> Removed already merged patches.
> Address review feedback, see individual patches.
> Now compiles with gcc 8.
> Some minor bug fixes and improvements.]
>
> We currently have two ways to look at sample data in perf:
> either
We want to get struct clk_hw pointers from a DT clk specifier (i.e. a
clocks property) so that we can find parent clks without searching for
globally unique clk names. This should save time by avoiding the global
string search for clks that are external to the clock controller
providing the clk and
From: Miquel Raynal
Currently, the core->dev entry is populated only if runtime PM is
enabled. Doing so prevents accessing the device structure in any
case.
Keep the same logic but instead of using the presence of core->dev as
the only condition, also check the status of
pm_runtime_enabled(). Th
The common clk framework is lacking in ability to describe the clk
topology without specifying strings for every possible parent-child
link. There are a few drawbacks to the current approach:
1) String comparisons are used for everything, including describing
topologies that are 'local' to a sin
TODO: Fully convert driver
Cc: Miquel Raynal
Cc: Jerome Brunet
Cc: Russell King
Cc: Michael Turquette
Cc: Jeffrey Hugo
Cc: Chen-Yu Tsai
Signed-off-by: Stephen Boyd
---
drivers/clk/qcom/gcc-sdm845.c | 180 +-
1 file changed, 90 insertions(+), 90 deletions(-)
This is an example patch to show how DT nodes are updated to specify the
clocks which are external to the clock controller can be specified in DT
and then found by the clk core to do parent-child linkage.
Cc: Miquel Raynal
Cc: Jerome Brunet
Cc: Russell King
Cc: Michael Turquette
Cc: Jeffrey Hu
The __clk_get() function is practically a private clk implementation
detail now. No architecture defines it, and given that new code should
be using the common clk framework there isn't a need for it to keep
existing just to serve clkdev purposes. Let's fold it into the
__clk_create_clk() function
The API between clk.c and clkdev.c is purely getting the clk_hw
structure (or the struct clk if it's not CCF) and then turning that
struct clk_hw pointer into a struct clk pointer via clk_hw_create_clk().
There's no need to complicate clkdev.c with these DT parsing details
that are only relevant to
We'd like to have a pointer to the device that's consuming a particular
clk in the clk framework so we can link the consumer to the clk provider
with a PM device link. Add a device argument to clk_hw_create_clk() for
this so it can be used in subsequent patches to add and remove the link.
Cc: Miqu
There are a couple warts with clk parent handling in the common clk
framework. This patch series addresses one of those warts, parent-child
linkages. We use strings for all parent-child linkages, and this leads
to poorly written code that extracts clk names from struct clk pointers
and makes clk pr
>
> The number of node specific huge pages can be set via a file such as:
> /sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages
> When a node specific value is specified, the global number of huge
> pages must also be adjusted. This adjustment is calculated as the
> specified n
On 2/25/19 9:55 AM, Keith Busch wrote:
> On Sun, Feb 24, 2019 at 03:27:09PM -0800, alex_gagn...@dellteam.com wrote:
>> [ 57.680494] {1}[Hardware Error]: Hardware error from APEI Generic
>> Hardware Error Source: 1
>> [ 57.680495] {1}[Hardware Error]: event severity: fatal
>> [ 57.680496] {1
On Mon, Feb 25, 2019 at 02:19:10AM +, Anson Huang wrote:
> i.MX8QXP is an ARMv8 SoC which has a Cortex-M4 system controller
> inside, the system controller is in charge of controlling power,
> clock and watchdog etc..
>
> This patch adds i.MX system controller watchdog driver support,
> watchd
On Sun, 24 Feb 2019 12:33:51 -0800, Robert Eshleman wrote:
> Adds device tree bindings for the ap3216c ambient light and proximity
> sensor.
>
> Signed-off-by: Robert Eshleman
> ---
> .../devicetree/bindings/iio/light/ap3216c.txt | 22 +++
> 1 file changed, 22 insertions(+)
> cr
On Sun, 24 Feb 2019 12:33:29 -0800, Robert Eshleman wrote:
> This patch adds a vendor-prefix for the Lite-On Semiconductor
> Corporation.
>
> Signed-off-by: Robert Eshleman
> ---
> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob
From: Haiyang Zhang
Date: Fri, 22 Feb 2019 18:25:03 +
> From: Haiyang Zhang
>
> Incoming packets may have IP header checksum verified by the host.
> They may not have IP header checksum computed after coalescing.
> This patch re-compute the checksum when necessary, otherwise the
> packets m
Jiri Olsa writes:
>
> im still getting compile error the new branch:
>
> CC ui/browsers/hists.o
> ui/browsers/hists.c: In function ‘perf_evsel__hists_browse’:
> ui/browsers/hists.c:2567:8: error: ‘%s’ directive output may be truncated
> writing up to 63 bytes into a region of size between
Changes v4 -> v5:
1. Rebase upon latest tip/perf/core.
2. Remove prototype from v4 (2/2).
Changes v3 -> v4:
1. In __perf_install_in_context() always reprogram ctx for cpu and cgroup
events to make sure event duplications set up properly.
2. Add a prototype (2/2) to show potential solu
This patch tries to enable PMU sharing. To make perf event scheduling
fast, we use special data structures.
An array of "struct perf_event_dup" is added to the perf_event_context,
to remember all the duplicated events under this ctx. All the events
under this ctx has a "dup_id" pointing to its per
On Tue, Feb 26, 2019 at 02:49:05PM +0800, Huang, Ying wrote:
> Do you have time to take a look at this patch?
Hi Ying, is this handling all places where swapoff might cause a task to read
invalid data? For example, why don't other reads of swap_map (for example
swp_swapcount, page_swapcount, swap
601 - 700 of 929 matches
Mail list logo
