On 2016-11-07 16:07:45 [+0100], Borislav Petkov wrote:
> On Mon, Nov 07, 2016 at 02:25:01PM +0100, Sebastian Andrzej Siewior wrote:
> > This moves it 1:1 (well, more or less). Wouldn't you prefer doing it as
> > separate patch/change?
>
> Ontop of all of yours so that you don't have to redo yours?
On Thu, 3 Nov 2016 14:58:38 +0100
Heiko Carstens wrote:
> Commit 345ddcc882d8 ("ftrace: Have set_ftrace_pid use the bitmap like
> events do") added a couple of this_cpu_read calls to the ftrace code.
>
> On x86 this is not a problem, since it has single instructions to read
> percpu data. Other
Tested-by: Neil Armstrong
Acked-by: Neil Armstrong
Signed-off-by: Andrey Smirnov
---
drivers/pinctrl/pinctrl-sx150x.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/pinctrl/pinctrl-sx150x.c b/drivers/pinctrl/pinctrl-sx150x.c
index 9466777..3ccd048 100644
--- a/d
Hi,
Thanks for reviewing.
On 07/11/2016 08:12 πμ, Viresh Kumar wrote:
> For the record, I have never got the original mail with this subject.
I'm sorry for inconvenience. It seems that I had an issue on my mail
server.
> On 06-11-16, 11:19, Stratos Karafotis wrote:
>> Conservative governor cha
On 2016-11-07 12:19:39 [-0500], Steven Rostedt wrote:
> I agree, but if this creates a boot time regression in large machines,
> it may not be warranted.
>
> I know Linus usually doesn't like options with default y, but this may
> be one of those exceptions. Perhaps we should make it on by default
This scm call is used to change the video core state, more
specifically it is used to suspend and resume the core.
Signed-off-by: Stanimir Varbanov
---
drivers/firmware/qcom_scm-32.c | 18 ++
drivers/firmware/qcom_scm-64.c | 16
drivers/firmware/qcom_scm.c| 1
Hi,
here is v2 of the Venus remoteproc driver, the changes are:
- removed page table size and page table init SCM calls.
regards,
Stan
Stanimir Varbanov (3):
firmware: qcom: scm: add a video command for state setting
dt-binding: remoteproc: venus rproc dt binding document
remotepro
Makefile and Kconfig files to build the Venus video codec driver.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/Kconfig| 7 +++
drivers/media/platform/qcom/Makefile | 1 +
drivers/media/platform/qcom/venus/Makefile | 15 +++
3 files changed, 23
On Monday 07 November 2016 05:09 PM, Catalin Marinas wrote:
diff --git a/arch/arm64/kernel/probes/decode-insn.c
> b/arch/arm64/kernel/probes/decode-insn.c
> index 8a29d29..6bf6657 100644
> --- a/arch/arm64/kernel/probes/decode-insn.c
> +++ b/arch/arm64/kernel/probes/decode-insn.c
> @@ -17,7 +17
Here is the implementation of Venus video accelerator low-level
functionality. It contanins code which setup the registers and
startup uthe processor, allocate and manipulates with the shared
memory used for sending commands and receiving messages.
Signed-off-by: Stanimir Varbanov
---
drivers/me
This is the implementation of HFI. It is charged with the
responsibility to comunicate with the firmware through an
interface commands and messages.
- hfi.c has interface functions used by the core, decoder
and encoder parts to comunicate with the firmware. For example
there are functions for ses
This adds encoder part of the driver plus encoder controls.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/venc.c | 1212
drivers/media/platform/qcom/venus/venc.h | 32 +
drivers/media/platform/qcom/venus/venc_ctrls.c | 396
This adds changes in v4l2 platform directory to include the
vidc driver and show it in kernel config.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/Kconfig | 1 +
drivers/media/platform/Makefile | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/media/platform/Kconfig b
For whatever reason, the X1 Yoga doesn't support the normal method of
querying for tablet mode. Instead of providing the MHKG method under the
hotkey handle, we're instead given the CMMD method under the EC handle.
Values on this handle are either 0x1, laptop mode, or 0x6, tablet mode.
Cc: Daniel
On Mon, Nov 07, 2016 at 02:27:14PM +0100, Allan W. Nielsen wrote:
> Hi,
>
> I tried to get this "lkp" up and running, but I had some troubles gettting
> these scripts to work.
>
> But it seems like it can be reproduced using th eprovided config file, and
> qemu.
>
> Here is what I did:
>
> # r
The hotkey events and ACPI handles used for detecting tablet mode on a
few of the newer thinkpad models (Yoga X1 and the Yoga 260 specifically)
have been changed around, so unfortunately this means we're definitely
going to need to probe for multiple types of tablet mode support. Since
the hotkey_i
This driver will load and authenticate the Venus firmware and
bringing it core out of reset. Those two functionalities are
via secure monitor calls to trusted environment.
Signed-off-by: Stanimir Varbanov
---
drivers/remoteproc/Kconfig | 12 ++
drivers/remoteproc/Makefile | 1
On Mon, 07 Nov 2016, Eric Engestrom wrote:
> On Monday, 2016-11-07 10:10:13 +0200, Jani Nikula wrote:
>> On Mon, 07 Nov 2016, Eric Engestrom wrote:
>> > Fixes: 90844f00049e9f42573fd31d7c32e8fd31d3fd07
>> >
>> > drm: make drm_get_format_name thread-safe
>> >
>> > Signed-off-by: Eric Engest
There's no need to have multiple copies of the logic we use for checking
whether or not we're in tablet mode, so just use
hotkey_get_tablet_mode() when checking the initial state in
hotkey_init_tablet_mode().
Cc: Daniel Martin
Signed-off-by: Lyude
---
drivers/platform/x86/thinkpad_acpi.c | 5 ++
Add devicetree binding document for Venus remote processor.
Signed-off-by: Stanimir Varbanov
---
.../devicetree/bindings/remoteproc/qcom,venus.txt | 33 ++
1 file changed, 33 insertions(+)
create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,venus.txt
diff
On Mon, 07 Nov 2016, Martin Kepplinger wrote:
> Am 2016-11-07 um 17:01 schrieb Martin Steigerwald:
>> Hello.
>>
>> Am Montag, 7. November 2016, 16:34:35 CET schrieb Martin Kepplinger:
>>> Chris Clayton wrote off list and the mentioned patch fixes the problem
>>> for me too, as it does for others.
Add binding document for Venus video encoder/decoder driver
Cc: Rob Herring
Cc: Mark Rutland
Cc: devicet...@vger.kernel.org
Signed-off-by: Stanimir Varbanov
---
.../devicetree/bindings/media/qcom,venus.txt | 98 ++
1 file changed, 98 insertions(+)
create mode 100644
On Mon, Nov 7, 2016 at 12:08 PM, Konstantin Khlebnikov wrote:
> On Mon, Nov 7, 2016 at 1:04 PM, Miklos Szeredi wrote:
>> On Mon, Nov 7, 2016 at 10:58 AM, Konstantin Khlebnikov
>> wrote:
>>
>>> I've stumbled on somehow related problem - concurrent copy-ups are
>>> strictly serialized by rename l
* Linus Walleij [161104 14:55]:
> On Thu, Nov 3, 2016 at 5:35 PM, Tony Lindgren wrote:
>
> > Drivers using pinctrl-single,pins have #pinctrl-cells = <1>, while
> > pinctrl-single,bits need #pinctrl-cells = <2>.
> >
> > Note that this patch can be optionally applied separately from the
> > driver
On Mon, Nov 07, 2016 at 06:30:30PM +0100, Sebastian Andrzej Siewior wrote:
> On 2016-11-07 12:19:39 [-0500], Steven Rostedt wrote:
> > I agree, but if this creates a boot time regression in large machines,
> > it may not be warranted.
> >
> > I know Linus usually doesn't like options with default
* core.c has implemented the platform dirver methods, file
operations and v4l2 registration.
* helpers.c has implemented common helper functions for:
- buffer management
- vb2_ops and functions for format propagation,
- functions for allocating and freeing buffers for
internal usag
* Russell King - ARM Linux [161107 04:05]:
> On Thu, Oct 27, 2016 at 01:56:09PM -0500, Dave Gerlach wrote:
> > There are several instances when one would want to execute out of on-chip
> > SRAM, such as PM code on ARM platforms, so once again revisiting this
> > series to allow that in a generic m
Hi,
Here is v3 of the Venus v4l2 video encoder/decoder driver.
The changes since v2 are:
- return queued buffers on stream_on error.
- changed name of the driver vidc -> venus and reflect that in
querycap.
- fix video_device::release to point to video_device_release.
This consists of video decoder implementation plus decoder
controls.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/vdec.c | 1108
drivers/media/platform/qcom/venus/vdec.h | 32 +
drivers/media/platform/qcom/venus/vdec_ctrls.c | 197
Add an entry for Venus video encoder/decoder accelerator driver.
Signed-off-by: Stanimir Varbanov
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 93e9f4227c53..5c2e70e83ff5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9986,6 +9986,14
On 11/07/16 17:49, Alex Williamson wrote:
> On Tue, 25 Oct 2016 21:24:25 +0200
> Laszlo Ersek wrote:
>
>> On 10/25/16 20:42, Alex Williamson wrote:
>>> On Tue, 25 Oct 2016 20:24:19 +0200
>>> Laszlo Ersek wrote:
>>>
Some systems have multiple instances of the exact same kind of PCI device
Fix the following warn:
fs/nfs/nfs4session.c: In function ‘nfs4_slot_seqid_in_use’:
fs/nfs/nfs4session.c:203:54: warning: ‘cur_seq’ may be used uninitialized in
this function [-Wmaybe-uninitialized]
if (nfs4_slot_get_seqid(tbl, slotid, &cur_seq) == 0 &&
~~~
> So, get rid of all that and simply log an MCE with a TSC value always.
> Simplifies the code a bit too.
I'm not necessarily opposed to this ... but there was once some logic behind
when
logged TSC, and when we didn't. Essentially we wanted the TSC when we were
logging from #CMCI or #MC be
On 07/11/16 13:05, gabriel.fernan...@st.com wrote:
From: Gabriel Fernandez
This patch introduces PLL_I2S and PLL_SAI.
Vco clock of these PLLs can be modify by DT (only n multiplicator,
m divider is still fixed by the boot-loader).
Each PLL has 3 dividers. PLL should be off when we modify the ra
When using AES-XTS on a Wandboard, we receive a Mode error:
caam_jr 2102000.jr1: 20001311: CCB: desc idx 19: AES: Mode error.
According to the Security Reference Manual, the Low Power AES units
of the i.MX6 do not support the XTS mode. Therefore we must not
register XTS implementations in the Cryp
This patch fix open parenthesis alignment matching in prism2fw.c file
to comply with the standard kernel coding style.
Signed-off-by: Sergio Paracuellos
---
drivers/staging/wlan-ng/prism2fw.c | 51 --
1 file changed, 27 insertions(+), 24 deletions(-)
diff --g
This patch fix open parenthesis alignment in hfa384x_usb.c file to
comply with the standard kernel coding style.
Signed-off-by: Sergio Paracuellos
---
drivers/staging/wlan-ng/hfa384x_usb.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/staging/wlan
This patch removes unnecessary blank lines in prism2fw.c file to
comply with the standard kernel coding style.
Signed-off-by: Sergio Paracuellos
---
drivers/staging/wlan-ng/prism2fw.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/staging/wlan-ng/prism2fw.c
b/drivers/staging/w
This patchset fix several style issues to comply with
the standard kernel coding style.
Sergio Paracuellos (11):
staging: wlan-ng: fix line style issue in macro WLAN_GET_FC_FSTYPE
staging: wlan-ng: remove unnecessary out of memory message in
p80211conv.c
staging: wlan-ng: remove unneces
This patch avoids using BUG_ON() from driver,
and return from hfa384x_usbin_callback with WARN_ON()
if skb was NULL or data in skb is different from expected one.
Signed-off-by: Sergio Paracuellos
---
drivers/staging/wlan-ng/hfa384x_usb.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
This patch fix open parenthesis alignment in p80211req.c file to
comply with the standard kernel coding style.
Signed-off-by: Sergio Paracuellos
---
drivers/staging/wlan-ng/p80211req.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/wlan-ng/p80211re
This patch removes unnecessary blank line in p80211wep.c file to
comply with the standard kernel coding style.
Signed-off-by: Sergio Paracuellos
---
drivers/staging/wlan-ng/p80211wep.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/staging/wlan-ng/p80211wep.c
b/drivers/staging/w
This patch removes unnecessary parentheses in different statements of
prism2fw.c file in order to to comply with the standard kernel
coding style.
Signed-off-by: Sergio Paracuellos
---
drivers/staging/wlan-ng/prism2fw.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/
Comparison to NULL could be written in preferred form.
Change it to comply with the standard kernel coding style.
Signed-off-by: Sergio Paracuellos
---
drivers/staging/wlan-ng/p80211wep.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wlan-ng/p80211wep.c
b/d
This patch fix the following checkpatch script warning:
WARNING: Possible unnecessary 'out of memory' message.
Signed-off-by: Sergio Paracuellos
---
drivers/staging/wlan-ng/p80211conv.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/wlan-ng/p80211conv.c
b/drivers/staging/w
This patch removes unnecessary parentheses in different statements of
hfa384x_usb.c file in order to to comply with the standard kernel
coding style.
Signed-off-by: Sergio Paracuellos
---
drivers/staging/wlan-ng/hfa384x_usb.c | 24
1 file changed, 12 insertions(+), 12 de
> -Ursprüngliche Nachricht-
> Von: Horia Geanta Neag [mailto:horia.gea...@nxp.com]
> Gesendet: Montag, 7. November 2016 08:14
> An: Sven Ebenfeld ; linux-
> cry...@vger.kernel.org; linux-kernel@vger.kernel.org
> Cc: herb...@gondor.apana.org.au; da...@davemloft.net; Cata Vasile
>
> Betreff:
Hi Linus,
It's been pretty quiet on the fixes side of things for us, but Artem
reported a build failure introduced during the merge window that appears
with older GCCs that do not support asm goto. The fix is bigger than I'd
like, but it's a mechnical move of some constants to break an include
dep
This patch fix the following checkpatch.pl script warning:
WARNING: line over 80 characters
It also add spaces between or operators inside the macro to
comply with the standard kernel coding style.
Signed-off-by: Sergio Paracuellos
---
drivers/staging/wlan-ng/p80211hdr.h | 3 ++-
1 file changed
On 07/11/2016 14:51, Daniel Bristot de Oliveira wrote:
Hi Tommaso,
Hi,
I'm cc-ing Luca for GRUB et al., pls find a few further notes below...
On 11/07/2016 11:31 AM, Tommaso Cucinotta wrote:
as anticipated live to Daniel:
-) +1 for the general concept, we'd need something similar also for
S
From: Markus Mayer
Allow CPUfreq statistics to be cleared by writing anything to
/sys/.../cpufreq/stats/reset.
Signed-off-by: Markus Mayer
---
Changes since v2:
- changed name of write-only macro to cpufreq_freq_attr_wo()
- removed "perm" parameter from write-only macro
- squashed
On Nov 7, 2016, at 3:21 AM, Li Wang wrote:
>
> statfs64() does NOT return -1 and setting errno to EOVERFLOW when some
> variables(like: f_bsize) overflowed in the returned struct.
>
> reproducer:
> step1. mount hugetlbfs with two different pagesize on ppc64 arch.
>
> $ hugeadm --pool-pages-max
From: Asbjoern Sloth Toennesen
Date: Fri, 4 Nov 2016 22:48:34 +
> L2TP_ATTR_UDP_CSUM is a flag, and gets read with
> nla_get_flag, but it is defined as NLA_U8 in
> the nla_policy.
>
> It appears that this is only publicly used in
> iproute2, where it's broken, because it's used as
> a NLA_F
On 11/07/2016 12:16 PM, Dmitry Safonov wrote:
> On 11/07/2016 08:00 PM, Christopher Covington wrote:
>> Hi Dmitry,
>>
>> On 11/01/2016 01:22 PM, Dmitry Safonov wrote:
>>> Add vdso_mremap hook which will fix context.vdso pointer after mremap()
>>> on vDSO vma. This is needed for correct landing af
On Mon, Nov 07, 2016 at 05:48:46PM +, Luck, Tony wrote:
> > So, get rid of all that and simply log an MCE with a TSC value always.
> > Simplifies the code a bit too.
>
> I'm not necessarily opposed to this ... but there was once some logic behind
> when
> logged TSC, and when we didn't. Esse
Hi Eric,
On Fri, Nov 4, 2016 at 6:37 PM, Eric Biggers wrote:
> I agree, and the current code is wrong; but do note that this proposal is
> correct for poly1305_setrkey() but not for poly1305_setskey() and
> poly1305_blocks(). In the latter two cases, 4-byte alignment of the source
> buffer is *n
On Mon, Nov 07, 2016 at 10:05:13AM -0800, Paul E. McKenney wrote:
> On Mon, Nov 07, 2016 at 09:35:46AM -0800, Josh Triplett wrote:
> > On Mon, Nov 07, 2016 at 06:30:30PM +0100, Sebastian Andrzej Siewior wrote:
> > > On 2016-11-07 12:19:39 [-0500], Steven Rostedt wrote:
> > > > I agree, but if this
From: Jon Mason
Date: Fri, 4 Nov 2016 01:10:55 -0400
> Changes in v6:
> * Use a common bgmac_phy_connect_direct (per Rafal Milecki)
> * Rebased on latest net-next
> * Added Reviewed-by to the relevant patches
>
>
> Changes in v5:
> * Change a pr_err to netdev_err (per Scott Branden)
> * Rewor
Thomas has already acked the earlier version, but in case you need
it for this one, too.
vmwgfx portion: Acked-by: Sinclair Yeh
On Mon, Nov 07, 2016 at 12:48:09AM +, Eric Engestrom wrote:
> Fixes: 90844f00049e9f42573fd31d7c32e8fd31d3fd07
>
> drm: make drm_get_format_name thread-safe
>
Hi Matt,
On Fri, Nov 4, 2016 at 2:13 AM, Matt Redfearn wrote:
> Hi Wendy,
>
> Replies inline
>
>
>
> On 03/11/16 23:40, Wendy Liang wrote:
>>
>> HI Matt,
>>
>> Thanks for your patch. I am trying it.
>>
>> Please see my questions inline.
>>
>> Thanks,
>> Wendy
>>
>> On Wed, Oct 19, 2016 at 5:05 AM
This patch adds the DT binding documentation for the FDMA constroller
found on STi based chipsets from STMicroelectronics.
Signed-off-by: Ludovic Barre
Signed-off-by: Peter Griffin
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/dma/st_fdma.txt | 87 +++
1 file
From: Johan Hovold
Date: Thu, 3 Nov 2016 18:40:18 +0100
> This series fixes a number of device reference leaks (and one of_node
> leak) due to failure to drop the references taken by bus_find_device()
> and friends.
>
> Note that the final two patches have been compile tested only.
...
> v2
>
This header file will also be used by the dma xbar driver in the
future.
Signed-off-by: Ludovic Barre
Signed-off-by: Peter Griffin
---
drivers/dma/st_fdma.h | 249 ++
1 file changed, 249 insertions(+)
create mode 100644 drivers/dma/st_fdma.h
dif
Hi Vinod and Bjorn,
This patchset adds support for the Flexible Direct Memory Access (FDMA) core
found on STi chipsets from STMicroelectronics. The FDMA is a slim core CPU
with a dedicated firmware. It is a general purpose DMA controller supporting
16 independent channels and data can be moved fro
The st231 remote coprocessors are found on all STi chipsets.
Signed-off-by: Peter Griffin
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index 538c326..0a06af9 100644
--- a/arc
During randconfig builds you can get the following warning
"warning: (ST_FDMA) selects ST_SLIM_REMOTEPROC which has unmet direct
dependencies (REMOTEPROC)"
randconfig builds should always build without any warnings so
update fdma to depend on REMOTEPROC so this can not happen.
Signed-off-by: Pet
This DMA controller is found on all STi chipsets.
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index 0a06af9..ce9ab5a 100644
On Mon, Nov 07, 2016 at 06:26:17PM +0100, Sebastian Andrzej Siewior wrote:
> Subject: x86/mcheck: Split threshold_cpu_callback into two callbacks
> From: Sebastian Andrzej Siewior
> Date: Tue, 25 Oct 2016 18:04:25 +0200
>
> The threshold_cpu_callback callbacks looks like one of the notifier and
>
This patch adds the FDMA driver files to the STi
section of the maintainers file.
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 78b7f8b..e93762d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -
This patch adds support for the Flexible Direct Memory Access (FDMA) core
driver. The FDMA is a slim core CPU with a dedicated firmware.
It is a general purpose DMA controller capable of supporting 16
independent DMA channels. Data moves maybe from memory to memory
or between memory and paced laten
- On Nov 7, 2016, at 1:06 PM, Paul E. McKenney paul...@linux.vnet.ibm.com
wrote:
> On Mon, Nov 07, 2016 at 05:08:59PM +, Mathieu Desnoyers wrote:
>> - On Nov 3, 2016, at 1:49 PM, Paul E. McKenney paul...@linux.vnet.ibm.com
>> wrote:
>>
>> > On Thu, Nov 03, 2016 at 10:29:28AM -0600,
From: Wei Yongjun
In case of error, the function st_slim_rproc_alloc() returns ERR_PTR()
and never returns NULL. The NULL test in the return value check should
be replaced with IS_ERR().
Signed-off-by: Wei Yongjun
Acked-by: Peter Griffin
---
drivers/dma/st_fdma.c | 2 +-
1 file changed, 1 ins
On Mon, 7 Nov 2016 09:17:55 +0100
Daniel Bristot de Oliveira wrote:
> The rt throttling mechanism prevents the starvation of non-real-time
> tasks by CPU intensive real-time tasks. In terms of percentage,
> the default behavior allows real-time tasks to run up to 95% of a
> given period, leaving
On 11/07/2016 03:49 AM, Joel Holdsworth wrote:
> The Lattice iCE40 is a family of FPGAs with a minimalistic architecture
> and very regular structure, designed for low-cost, high-volume consumer
> and system applications.
[...]
> +static int ice40_fpga_ops_write_init(struct fpga_manager *mgr, u32
Make REMOTEPROC core a selectable kconfig option, and update
remoteproc client drivers to 'depends on' the core. This avoids
some nasty Kconfig recursive dependency issues. Also when using
menuconfig client drivers will be hidden until the core has been
enabled.
Documentation/kbuild/kconfig-langua
This patch adds the slim core rproc driver to the STi section
of the MAINTAINERS file.
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 1cd38a7..78b7f8b 100644
--- a/MAINTAINERS
+++ b/MAINTAINE
On 11/07/2016 03:49 AM, Joel Holdsworth wrote:
> This adds documentation of the device tree bindings of the Lattice iCE40
> FPGA driver for the FPGA manager framework.
>
> Signed-off-by: Joel Holdsworth
> ---
> .../bindings/fpga/lattice-ice40-fpga-mgr.txt| 21
> +
>
On Mon, Nov 7, 2016 at 7:08 PM, Jason A. Donenfeld wrote:
> Hmm... The general data flow that strikes me as most pertinent is
> something like:
>
> struct sk_buff *skb = get_it_from_somewhere();
> skb = skb_share_check(skb, GFP_ATOMIC);
> num_frags = skb_cow_data(skb, ..., ...);
> struct scatterli
slim core is used as a basis for many IPs in the STi
chipsets such as fdma and demux. To avoid duplicating
the elf loading code in each device driver a slim
rproc driver has been created.
This driver is designed to be used by other device drivers
such as fdma, or demux whose IP is based around a s
This patch enables the STi ALSA drivers found on STi platforms
as well as the simple-card driver which is a dependency to have
working sound.
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
arch/arm/configs/multi_v7_defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/
Now that remoteproc core is selectable it needs to be enabled
in the multi_v7 build.
Signed-off-by: Peter Griffin
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index 437d074..
Hi Eric,
Are you still working in this patch set?
Now I know why maps section is not a simple array
from a patch set from Joe Stringer:
https://www.mail-archive.com/netdev@vger.kernel.org/msg135088.html
So I think this patch is really useful.
Are you going to resend the whole patch set? If no
On Mon, 7 Nov 2016 19:03:08 +0100
Tommaso Cucinotta wrote:
> On 07/11/2016 14:51, Daniel Bristot de Oliveira wrote:
> > Hi Tommaso,
>
> Hi,
>
> I'm cc-ing Luca for GRUB et al., pls find a few further notes below...
Thanks Tommaso! I've seen the email on the linux-rt-users mailing list,
and I'll
Hi Joel,
couple of nits inline below:
On Sun, Nov 6, 2016 at 6:49 PM, Joel Holdsworth
wrote:
> The Lattice iCE40 is a family of FPGAs with a minimalistic architecture
> and very regular structure, designed for low-cost, high-volume consumer
> and system applications.
>
> This patch adds support
From: Arnd Bergmann
The newly added st_fdma driver introduces a build warning for
allmodconfig when we add '-Wmaybe-uninitialized':
drivers/dma/st_fdma.c: In function 'st_fdma_probe':
drivers/dma/st_fdma.c:777:5: error: 'ret' may be used uninitialized in this
function [-Werror=maybe-uninitializ
On 11/07/2016 11:21 AM, Paul Burton wrote:
Hi Larry,
On Monday, 7 November 2016 09:26:37 GMT Larry Finger wrote:
A revert was already submitted by Hans de Goede & is being discussed over
here:
https://marc.info/?l=linux-kernel&m=147826151427455&w=2
I am a little surprised that I was not CCd
On Tue, Nov 01, 2016 at 08:22:14PM +0300, Dmitry Safonov wrote:
> diff --git a/arch/arm/kernel/vdso.c b/arch/arm/kernel/vdso.c
> index 53cf86cf2d1a..d1001f87c2f6 100644
> --- a/arch/arm/kernel/vdso.c
> +++ b/arch/arm/kernel/vdso.c
> @@ -54,8 +54,11 @@ static const struct vm_special_mapping vdso_dat
On Mon, Nov 07, 2016 at 06:07:03PM +0800, Chen-Yu Tsai wrote:
> The SinA31s routes the SoC's LINEOUT pins to a line out jack, and MIC1
> to a microphone jack, with MBIAS providing phantom power.
>
> Signed-off-by: Chen-Yu Tsai
Applied, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded L
On Mon, Nov 07, 2016 at 06:07:01PM +0800, Chen-Yu Tsai wrote:
> The A31 SoC includes the Allwinner audio codec, capable of 24-bit
> playback up to 192 kHz and 24-bit capture up to 48 kHz.
>
> Signed-off-by: Chen-Yu Tsai
> ---
> arch/arm/boot/dts/sun6i-a31.dtsi | 13 +
> 1 file change
On Mon, Nov 07, 2016 at 06:07:02PM +0800, Chen-Yu Tsai wrote:
> The Hummingbird A31 has headset and line in audio jacks and an onboard
> mic routed to the pins for the SoC's internal codec. The line out pins
> are routed to an onboard speaker amp, whose output is available on a
> pin header.
>
> S
On Mon, Nov 07, 2016 at 09:35:46AM -0800, Josh Triplett wrote:
> On Mon, Nov 07, 2016 at 06:30:30PM +0100, Sebastian Andrzej Siewior wrote:
> > On 2016-11-07 12:19:39 [-0500], Steven Rostedt wrote:
> > > I agree, but if this creates a boot time regression in large machines,
> > > it may not be warr
On Mon, 7 Nov 2016 12:22:21 -0600
Clark Williams wrote:
> I'm still reviewing the patch, but I have to wonder why bother with making it
> a scheduler feature?
>
> The SCHED_FIFO definition allows a fifo thread to starve others
> because a fifo task will run until it yields. Throttling was added
On Sun, Nov 06, 2016 at 12:05:12AM -0200, Marcos Paulo de Souza wrote:
> Hi Darren,
>
> On Sat, Nov 05, 2016 at 11:24:04AM -0700, Darren Hart wrote:
> > On Mon, Oct 31, 2016 at 11:56:10PM -0200, Marcos Paulo de Souza wrote:
> > > Without this patch, the Asus X45U wireless card can't be turned
> >
On Mon, Nov 07, 2016 at 10:35:31AM +0100, Geert Uytterhoeven wrote:
> On Mon, Oct 31, 2016 at 12:30 PM, Geert Uytterhoeven
> wrote:
> > Some Renesas SoCs may exist in different revisions, providing slightly
> > different functionalities (e.g. R-Car H3 ES1.x and ES2.0), and behavior
> > (errate and
On 11/07/2016 06:04 AM, Jiri Slaby wrote:
> This is the start of the stable review cycle for the 3.12.67 release.
> There are 72 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be
On 11/05/2016 06:43 AM, Joel Fernandes wrote:
> On Mon, Oct 24, 2016 at 8:44 AM, Andrey Ryabinin
> wrote:
>>
>>
>> On 10/22/2016 06:17 PM, Christoph Hellwig wrote:
>>> We want to be able to use a sleeping lock for freeing vmap to keep
>>> latency down. For this we need to use the deferred vfree m
On Mon, Nov 07, 2016 at 07:08:22PM +0100, Jason A. Donenfeld wrote:
> Hmm... The general data flow that strikes me as most pertinent is
> something like:
>
> struct sk_buff *skb = get_it_from_somewhere();
> skb = skb_share_check(skb, GFP_ATOMIC);
> num_frags = skb_cow_data(skb, ..., ...);
> struct
> One other possibility would be to use ->time and write ->tsc *only*
> when exact - i.e., in the handler - and this is then enough info about
> timing.
>
> ->time will give you somewhere around where it happened and ->tsc - only
> if set - will give you exact, well, *timestamp* :)
>
> This sounds
On Mon, 7 Nov 2016 10:55:38 -0600 (CST)
Christoph Lameter wrote:
> On Mon, 7 Nov 2016, Daniel Bristot de Oliveira wrote:
>
> > With these two options set, the user will guarantee some runtime
> > for non-rt-tasks on all CPUs, while keeping real-time tasks running
> > as much as possible.
>
>
Ping?
What's the current status of this? Do we need this for 4.9?
On Mon, Oct 31, 2016 at 1:07 PM, Oleg Nesterov wrote:
> On 10/28, Oleg Nesterov wrote:
>>
>> I'll try to kill to_live_kthread() tomorrow, didn't have time to do this
>> today.
>
> Hmm. And this looks even simpler than I thought,
101 - 200 of 1069 matches
Mail list logo
