Subscribe: lkml.org
http://lkml.org/rss.php
Added By: Feedage Forager Feedage Grade B rated
Language: English
Tags:
arch arm  arm  ceu  exynos  git  jan  kernel  media  patch  renesas  summary  tue jan  tue  writes summary  writes  wrote 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: lkml.org

lkml.org



lkml.org - the realtime linux kernel mailinglist archive



Last Build Date: Wed, 17 Jan 2018 00:44:55 +0100

 



Re: [PATCH v4 13/17] ASoC: fsl_ssi: Setup AC97 in fsl_ssi_hw_init()
"Maciej S. Szmigiero" writes: (Summary) On 16.01.2018 00:16, Nicolin Chen wrote:
+ regmap_write(ssi->regs, REG_SSI_SOR, 0);
These writes cause a hard SoC lockup when unloading the driver. These writes cause a hard SoC lockup when unloading the driver. RE) and also as a separate step) but this still caused a lockup. > @@ -1587,6 +1599,8 @@ static int fsl_ssi_remove(struct platform_device *pdev) > { > > > > > > > if (ssi->pdev) >



Re: [PATCH v4 00/17] ASoC: fsl_ssi: Clean up - program flow level
"Maciej S. Szmigiero" writes: On 16.01.2018 00:16, Nicolin Chen wrote:
Example of uncovered tests: AC97, PowerPC and FIQ.
I've tested the whole series in the AC'97 mode on an i.MX6 UDOO board and everything seems to work fine as long as few small changes are made to patches 13 and 16.
to patches 13 and 16.
Maciej
Maciej
Maciej



Re: [ANNOUNCE] 4.9.76-rt61
Bernhard Landauer writes: Ah. Working now after adding in validpgpkeys array in the PKGBUILD. Ah. Working now after adding in validpgpkeys array in the PKGBUILD. Sorry.
Sorry.
B
B
B
On 16.01.2018 23:08, Bernhard Landauer wrote:
More majordomo info at http://vger.kernel.org/majordomo-info.html More majordomo info at http://vger.kernel.org/majordomo-info.html



Re: [ANNOUNCE] 4.9.76-rt61
Bernhard Landauer writes: (Summary) Hi Julia.
Seems I have a problem with your gpg key:
Seems I have a problem with your gpg key:
unknown public key 8CDAC2E1454D746F
unknown public key 8CDAC2E1454D746F
$ gpg --receive-key 8CDAC2E1454D746F
gpg: key 0A120DD923EEDD5F: 9 signatures not checked due to missing keys gpg: key 0A120DD923EEDD5F: public key "Julia J. Cartwright (Julia Cartwright) " imported gpg: marginals needed: 3ÿ¿¿¿¿¿ completes needed: 1ÿ¿¿¿¿¿ trust model: pgp gpg: depth: 0ÿ¿¿¿¿¿ valid:ÿ¿¿¿¿¿ÿ¿¿¿¿¿ 1ÿ¿¿¿¿¿ signed:ÿ¿¿¿¿¿ÿ¿¿¿¿¿ 0ÿ¿¿¿¿¿ trust: 0-, 0q, 0n, 0m, 0f, 1u gpg: Total number processed: 1
gpg:ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ imported: 1
gpg:ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ imported: 1
==>



Re: [ANNOUNCE] 4.9.76-rt61
Julia Cartwright writes: On Tue, Jan 16, 2018 at 11:11:32PM +0000, Bernhard Landauer wrote: > Ah. Working now after adding in validpgpkeys array in the PKGBUILD. This was the first v4.9-rt release since Steven handed over his maintainership , so that would explain why it would be signed by a different key (although, my key has been signed by Steven's). Thanks, Julia



[PATCH net-next] net: stmmac: Fix reception of Broadcom switches tags
Florian Fainelli writes: (Summary) diff --git a/drivers/net/ethernet/stmicro/stmmac/dwmac4_core.c b/drivers/net/ethernet/stmicro/stmmac/dwmac4_core.c index f3ed8f7853eb..6af5100d3cb2 100644 --- a/drivers/net/ethernet/stmicro/stmmac/dwmac4_core.c +++ b/drivers/net/ethernet/stmicro/stmmac/dwmac4_core.c @@ -20,13 +20,22 @@ #include "stmmac_pcs.h" #include "dwmac4.h" -static void dwmac4_core_init(struct mac_device_info *hw, int mtu) +static void dwmac4_core_init(struct mac_device_info *hw, + struct net_device *dev) { void __iomem *ioaddr = hw->pcsr; 2000) diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c index f99f14c35063..7ad841434ec8 100644 --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c @@ -2527,7 +2527,7 @@ static int stmmac_hw_setup(struct net_device *dev, bool init_ptp) } /* Initialize the MAC Core */ - priv->hw->mac->core_init(priv->hw, dev->mtu);



Re: [PATCH] samples/bpf: Fix trailing semicolon
Daniel Borkmann writes: On 01/16/2018 03:15 PM, Luis de Bethencourt wrote:
Signed-off-by: Luis de Bethencourt Applied to bpf-next, thanks Luis!
Applied to bpf-next, thanks Luis!
Applied to bpf-next, thanks Luis!



Re: [PATCH] reset: ti-rstctrl: use the reset-simple driver
Tony Lindgren writes: (Summary) But then what resets the context lost state as we don't need to reset the device?
state as we don't need to reset the device?
It almost seems like the RSTST and CONTEXT should be client device PM state related registers instead of reset controller registers? We keep ocp softreset internal to the interconnect target module driver and if child device drivers really need to access that we can implement reset driver in the interconnect target module can implement reset driver in the interconnect target module 2.



[bpf-next PATCH 1/3] libbpf: install the header file libbpf.h
Jesper Dangaard Brouer writes: (Summary) It seems like an oversight not to install the header file for libbpf, given the libbpf.so + libbpf.a files are installed. 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tools/lib/bpf/Makefile b/tools/lib/bpf/Makefile index 8ed43ae9db9b..54370654c708 100644 --- a/tools/lib/bpf/Makefile +++ b/tools/lib/bpf/Makefile @@ -192,7 +192,8 @@ install_lib: all_cmd install_headers: $(call QUIET_INSTALL, headers) \ - $(call do_install,bpf.h,$(prefix)/include/bpf,644) + $(call do_install,bpf.h,$(prefix)/include/bpf,644);



[bpf-next PATCH 3/3] libbpf: Makefile set specified permission mode
Jesper Dangaard Brouer writes: (Summary) The use of a third parameter was introduced in commit eb54e522a000 ("bpf: install libbpf headers on 'make install'").
install libbpf headers on 'make install'").
Without this change, the header files are install as executables files (755). 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/lib/bpf/Makefile b/tools/lib/bpf/Makefile index 8e15e48cb8f8..83714ca1f22b 100644 --- a/tools/lib/bpf/Makefile +++ b/tools/lib/bpf/Makefile @@ -172,7 +172,7 @@ define do_install if [ ! \ - $(INSTALL) $1 '$(DESTDIR_SQ)$2' + $(INSTALL) $1 $(if $3,-m $3,) '$(DESTDIR_SQ)$2' endef install_lib: all_cmd



[bpf-next PATCH 2/3] libbpf: cleanup Makefile, remove unused elements
Jesper Dangaard Brouer writes: (Summary) 15 ++------------- 1 file changed, 2 insertions(+), 13 deletions(-) diff --git a/tools/lib/bpf/Makefile b/tools/lib/bpf/Makefile index 54370654c708..8e15e48cb8f8 100644 --- a/tools/lib/bpf/Makefile +++ b/tools/lib/bpf/Makefile @@ -93,7 +93,6 @@ export prefix libdir src obj # Shell quotes libdir_SQ = $(subst ','\'',$(libdir)) libdir_relative_SQ = $(subst ','\'',$(libdir_relative)) -plugin_dir_SQ = $(subst ','\'',$(plugin_dir)) LIB_FILE = libbpf.a libbpf.so @@ -150,7 +149,7 @@ CMD_TARGETS = $(LIB_FILE) TARGETS = $(CMD_TARGETS) -all: fixdep $(VERSION_FILES) all_cmd +all: fixdep all_cmd all_cmd: $(CMD_TARGETS) @@ -169,16 +168,6 @@ $(OUTPUT)libbpf.so: $(BPF_IN) $(OUTPUT)libbpf.a: $(BPF_IN) $(QUIET_LINK)$(RM) $@;



[bpf-next PATCH 0/3] libbpf: cleanups to Makefile
Jesper Dangaard Brouer writes: (Summary) This patchset contains some small improvements and cleanup for the Makefile in tools/lib/bpf/.
the Makefile in tools/lib/bpf/.
It worries me that the libbpf.so shared library is not versioned, but it not addressed in this patchset.
it not addressed in this patchset.
--- Jesper Dangaard Brouer (3): libbpf: install the header file libbpf.h libbpf: cleanup Makefile, remove unused elements libbpf: Makefile set specified permission mode tools/lib/bpf/Makefile |



Re: [PATCH][next] gpiolib: remove redundant initialization of poin ...
Linus Walleij writes: On Tue, Jan 16, 2018 at 12:56 PM, Colin King wrote: On Tue, Jan 16, 2018 at 12:56 PM, Colin King wrote: Signed-off-by: Colin Ian King Patch applied.
Patch applied.
Yours,
Linus Walleij
Linus Walleij
Linus Walleij



Re: [PATCH] arm64: defconfig: enable MESON EFUSE
Kevin Hilman writes: Jerome Brunet writes:
Jerome Brunet writes:
Signed-off-by: Jerome Brunet Queued for v4.17, Applied to v4.17/defconfig
Queued for v4.17, Applied to v4.17/defconfig
Kevin
Kevin
Kevin



Re: [REGRESSION] mux/gpio.c is not able to get any gpio pins
Linus Walleij writes: (Summary) wrote: +gpio-mux mux-controller: failed to get gpios: -517 It would be clearer with a trace, really.
It would be clearer with a trace, really.
Not that I'm especially good at using ftrace myself :/ Not that I'm especially good at using ftrace myself :/ I think gpiod_set_transitory() calls chip->set_config(chip, gpio, packed); To fix this, I think sx150x_probe() need to be rewritten to register the pin controller first, then the GPIO chip, so the range mapping is up and kicking when the chip gets initialized.
initialized.
Yours,
Linus Walleij
Linus Walleij
Linus Walleij



Re: [PATCH v3] input: pxrc: new driver for PhoenixRC Flight Contro ...
Dmitry Torokhov writes: (Summary) + { USB_DEVICE(PXRC_VENDOR_ID, PXRC_PRODUCT_ID) }, > + { } > + switch (urb->status) { > + "%s - urb timed out - was the device unplugged?\n", > + dev_dbg(&pxrc->intf->dev, "%s - urb shutting down with status: %d\n", > + dev_dbg(&pxrc->intf->dev, "%s - nonzero urb status received: %d\n", > + } > + if (urb->actual_length == 8) { > + } >



Re: LKML admins (syzbot emails are not delivered)
Theodore Ts'o writes: (Summary) On Tue, Jan 16, 2018 at 09:31:26AM +0100, Dmitry Vyukov wrote: repro.c...
My personal opinion is that if there is no way to force the content type except by using magic extensions --- which is super-surprising to me; that seems like a broken API and a feature request bug should be filed against the relevant API --- using repro.c.txt would be the best of bad alternatives. So at least for me, it really isn't a big deal for you to use repro.c.txt.
you to use repro.c.txt.
Cheers,
Cheers,
- Ted
- Ted
- Ted



Re: [PATCH arm/aspeed/ast2500 v1] ipmi: add an Aspeed KCS IPMI BMC ...
Joel Stanley writes: (Summary) On Tue, Jan 16, 2018 at 2:59 PM, Corey Minyard wrote: renamed.)
Yes, we had a group of openbmc people get together recently and spoke about this. Unfortunately Haiyue wasn't there (but other Intel BMC people were).
people were).
We've got code coming from another BMC vendor who will use the same userspace API. The intention is to unify ASPEED's KCS and BT, along with Nuvoton's KCS and BT, as you outlined above.
with Nuvoton's KCS and BT, as you outlined above.
Cheers,
Cheers,
Joel
Joel
Joel



Re: [PATCH] Input: trackpoint - force 3 buttons if 0 button is rep ...
Dmitry Torokhov writes: (Summary) From https://bugzilla.kernel.org/show_bug.cgi?id=196253
https://bugzilla.kernel.org/show_bug.cgi?id=196253
thinkpad_acpi: ThinkPad BIOS R0DET87W (1.87 ), EC unknown thinkpad_acpi: Lenovo ThinkPad E470, model 20H1004SGE thinkpad_acpi: Lenovo ThinkPad E470, model 20H1004SGE psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 0/0 psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 0/0 I'll ask them to try my patch and if it is indeed 0x01 device I'll apply your patch.
your patch.
Thanks.
Thanks.



Re: [PATCH v2 03/10] x86: Add a type field to alt_instr
Josh Poimboeuf writes: On Tue, Jan 16, 2018 at 11:53:25PM +0100, Borislav Petkov wrote: You could reuse that...
We could, but it can be a real PITA to keep those files in sync, as they often change for minor changes which don't even matter. So it might not be worth the trouble. Objtool seems to complain when the alternatives struct size changes anyway, so it's probably not a big deal. struct size changes anyway, so it's probably not a big deal.



Re: [PATCH RFC tip/core/rcu] Make SRCU be once again optional
Arnd Bergmann writes: (Summary) On Tue, Jan 16, 2018 at 11:55 PM, Arnd Bergmann wrote: On Tue, Jan 16, 2018 at 11:55 PM, Arnd Bergmann wrote: fixed the rest
Now with my workaround applied and the original randconfig that triggered the failure, I get another problem:
the failure, I get another problem:
drivers/base/power/wakeup.c:68:1: error: data definition has no type or storage class [-Werror]
DEFINE_STATIC_SRCU(wakeup_srcu);
DEFINE_STATIC_SRCU(wakeup_srcu);
Evidently there is at least one driver that uses SRCU but doesn't 'select SRCU' in Kconfig.



Re: [PATCH v2 06/10] objtool: Implement jump_assert for _static_cp ...
Josh Poimboeuf writes: (Summary) On Tue, Jan 16, 2018 at 03:28:31PM +0100, Peter Zijlstra wrote: + if (special_alt->static_feat)
s/static_feat/static_cpu_has/ ?
s/static_feat/static_cpu_has/ ?
+ }
So I think this is trying to assert the fact that you're only expecting a single instruction which is an unconditional jump. We already weeded out non-jumps earlier in the loop, so would it make sense to do this check before the INSN_JUMP_CONDITIONAL/INSN_JUMP_UNCONDITIONAL check a little higher up?
little higher up?
+ }
The error message doesn't seem to match the condition, so I'm not sure which one you're trying to check, or why.
which one you're trying to check, or why.
IIRC, 'insn->jump_dest == fake_jump' means we reached the end of the alternative code block without hitting a jump.
alternative code block without hitting a jump.
But based on the loop exit condition, I don't think it's ever possible for insn->jump_dest to ever point to th



Re: [PATCH RFC tip/core/rcu] Make SRCU be once again optional
Arnd Bergmann writes: (Summary) wrote:
using an older kernel (if so, please let me know the version.) This is using today's linux-next, but I got the same thing pretty much for every step of the bisection since May.
every step of the bisection since May.
My configuration has
My configuration has
CONFIG_TINY_RCU=y
# CONFIG_RCU_EXPERT is not set
# CONFIG_TASKS_RCU is not set
# CONFIG_RCU_STALL_COMMON is not set
# CONFIG_RCU_NEED_SEGCBLIST is not set
# CONFIG_PHY_LANTIQ_RCU_USB2 is not set
# CONFIG_PROVE_RCU is not set
# CONFIG_RCU_PERF_TEST is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_TRACE is not set
# CONFIG_RCU_EQS_DEBUG is not set
# CONFIG_PROVE_RCU is not set
CONFIG_DEBUG_LOCK_ALLOC=y
CONFIG_DEBUG_LOCK_ALLOC=y
#else /* #ifdef CONFIG_DEBUG_LOCK_ALLOC */
That fixed the first warning for me, doing the same thing for all three fixed the rest:
fixed the rest:
diff --git a/include/linux/



Re: [GIT PULL] isolation: 1Hz residual tick offloading v3
Frederic Weisbecker writes: On Tue, Jan 16, 2018 at 06:58:18PM +0100, Mike Galbraith wrote: what cpusets was born to do.  That's sad, dynamic wasn't that far away. Hence why we need to propagate "isolcpus=" to cpusets. Hence why we need to propagate "isolcpus=" to cpusets. Hence why we need to propagate "isolcpus=" to cpusets.



Re: [PATCH v2 03/10] x86: Add a type field to alt_instr
Borislav Petkov writes: On Tue, Jan 16, 2018 at 04:49:55PM -0600, Josh Poimboeuf wrote: this, or have a duplicated header file which needs to be kept in sync. Yeah, and AFAIR, perf tool guys already have machinery that does check whether stuff went out of sync and they resync the required definitions. whether stuff went out of sync and they resync the required definitions. You could reuse that...
You could reuse that...



Re: [PATCH 06/16] x86/mm/ldt: Reserve high address-space range for ...
Andy Lutomirski writes: (Summary) On Tue, Jan 16, 2018 at 8:52 AM, Peter Zijlstra wrote: 64K*2*64=8M > 2M.
If this works like it does on 64-bit, it only needs 128k regardless of the number of CPUs. The LDT mapping is specific to the mm. The LDT mapping is specific to the mm. That is, what's your pagetable layout? What parts of the address space are owned by what code? What parts of the address space are owned by what code? What parts of the address space are owned by what code?



Re: [GIT PULL] isolation: 1Hz residual tick offloading v3
Frederic Weisbecker writes: (Summary) On Tue, Jan 16, 2018 at 11:52:11AM -0500, Luiz Capitulino wrote: feature will force everyone back to using isolcpus= again. Then in fact, why not using "isolcpus=" and give it a second life. Just like they do with CONFIG_NO_HZ_FULL.
CONFIG_NO_HZ_FULL.
I think this should give you a great relief :)
Not at all :)
Not at all :)
What would be a great relief to me is that we can finally propagate isolcpus= to cpusets so that we can continue to expand it without a second thought.



Re: [PATCH v2 03/10] x86: Add a type field to alt_instr
Josh Poimboeuf writes: (Summary) On Tue, Jan 16, 2018 at 03:28:28PM +0100, Peter Zijlstra wrote: } __packed;
Should we put a comment above the struct with a reminder to also update objtool ALT_ENTRY_SIZE (and possibly the ALT_*_OFFSET macros) when they change the struct?
change the struct?
Unfortunately it's against policy to include kernel headers from the tools subdirectory, so we generally have to either hard code things like this, or have a duplicated header file which needs to be kept in sync. this, or have a duplicated header file which needs to be kept in sync.



Re: [PATCH] [v4] media: s3c-camif: fix out-of-bounds array access
Sakari Ailus writes: On Tue, Jan 16, 2018 at 10:52:15PM +0100, Arnd Bergmann wrote: Signed-off-by: Arnd Bergmann
Acked-by: Sakari Ailus Acked-by: Sakari Ailus



Re: [PATCH 03/16] x86/entry/32: Leave the kernel via the trampolin ...
Andy Lutomirski writes: (Summary) On Tue, Jan 16, 2018 at 8:36 AM, Joerg Roedel We're not *supposed* to be able to observe an asynchronous descriptor table change, but if the LDT changes out from under you, this is going to blow up badly. It would be really nice if you could pull this off without percpu access or without needing to do this dance where you load user FS, then kernel FS, then user FS. If that's not doable, then you should at least add exception handling -- look at the other 'pop %fs' instructions in entry_32.S.
the other 'pop %fs' instructions in entry_32.S.
the other 'pop %fs' instructions in entry_32.S.



Re: [PATCH 04/16] x86/pti: Define X86_CR3_PTI_PCID_USER_BIT on x86_32
Andy Lutomirski writes: On Tue, Jan 16, 2018 at 8:36 AM, Joerg Roedel wrote: that its visible for 32bit too.
Hmm. This is okay, I guess, but any code that actually uses this definition is inherently wrong, since 32-bit implies !PCID. definition is inherently wrong, since 32-bit implies !PCID. definition is inherently wrong, since 32-bit implies !PCID.



KVM: Fix stack-out-of-bounds read in write_mmio
Your Real Name writes: (Summary) Commit: e39d200fa5bf5b94a0948db0dae44c1b73b84a56
Target Stable Tree Branch: 4.9.y
Why this patch is needed: Due to a request to handle CVE-2017-17741, we would need to backport this patch to our kernel. The patch is already in mainline:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e39d200fa5bf5b94a0948db0dae44c1b73b84a56 Could you please include this patch in 4.9.y stable tree branch?



Re: [PATCH 02/16] x86/entry/32: Enter the kernel via trampoline stack
Andy Lutomirski writes: (Summary) +
Why check_user?
Why check_user?
+ SWITCH_TO_KERNEL_STACK nr_regs=6 check_user=1 LGTM.
LGTM.
+ SWITCH_TO_KERNEL_STACK nr_regs=5 check_user=1 This is wrong, I think. IIRC we have some crazy code already to handle this (for nmi and #DB), and maybe that's already adequate or can be made adequate, but at the very least this needs a big comment explaining why it's okay.
needs a big comment explaining why it's okay.
offsetofend(struct cpu_entry_area, entry_stack_page.stack));



Re: [PATCH] Documentation/process: add Co-Developed-by: tag for pa ...
Kees Cook writes: (Summary) If patch v1 was written by author A, then heavily modified and sent by author B to produce patch v2, what should the resulting states of git-author, and tag order be? I'm assuming it should be:
git-author: B
...
Signed-off-by: A
Co-Developed-by: A
Signed-off-by: B
Signed-off-by: B
It's not clear to me if git-author should instead be A, and/or Co-Developed-by should be B...
Co-Developed-by should be B...
Thanks!
Thanks!
-Kees
-Kees



Re: [PATCH v2 21/22] mmc: tmio: move {tmio_}mmc_of_parse() to tmio ...
Wolfram Sang writes: On Sat, Nov 25, 2017 at 01:24:56AM +0900, Masahiro Yamada wrote: Signed-off-by: Masahiro Yamada Reviewed-by: Wolfram Sang Reviewed-by: Wolfram Sang Reviewed-by: Wolfram Sang [unhandled content-type:application/pgp-signature]



Re: [PATCH v2 22/22] mmc: tmio: remove dma_ops from tmio_mmc_host_ ...
Wolfram Sang writes: (Summary) On Sat, Nov 25, 2017 at 01:24:57AM +0900, Masahiro Yamada wrote: Signed-off-by: Masahiro Yamada Reviewed-by: Wolfram Sang Reviewed-by: Wolfram Sang I'll do some more regression testing tomorrow and then give Tested-by as well if everything works fine (but it looks like it so far).
fine (but it looks like it so far).
fine (but it looks like it so far).
[unhandled content-type:application/pgp-signature]



Re: [PATCH v2 20/22] mmc: tmio: move clk_enable/disable out of tmi ...
Wolfram Sang writes: On Sat, Nov 25, 2017 at 01:24:55AM +0900, Masahiro Yamada wrote: Signed-off-by: Masahiro Yamada Reviewed-by: Wolfram Sang Reviewed-by: Wolfram Sang Reviewed-by: Wolfram Sang [unhandled content-type:application/pgp-signature]



Re: [01/12] watchdog: sp5100_tco: Always use SP5100_IO_PM_{INDEX_R ...
Guenter Roeck writes: On 01/16/2018 12:17 PM, Lyude Paul wrote:
patchwork beforehand and it looked like it was still pending Depends on Wim what he wants to do with it. We'll see when the commit window opens.
opens.
Guenter
Guenter
Lyude Paul
Lyude Paul



Re: [PATCH 02/16] x86/entry/32: Enter the kernel via trampoline stack
Andy Lutomirski writes: (Summary) On Tue, Jan 16, 2018 at 12:30 PM, Thomas Gleixner wrote: offsetofend(struct cpu_entry_area, entry_stack_page.stack)); How about putting just the needed offsets in asm_offsets and putting the actual calculation in the asm code or a header.
the asm code or a header.
+ OFFSET(TSS_sp1, tss_struct, x86_tss.sp1);
This belongs in asm_offsets.c. Just move the asm_offsets_64.c version there and call it a day.
there and call it a day.
there and call it a day.



[PATCH 1/2] dt-bindings: Documentation for qcom,llcc
Channagoud Kadabi writes: (Summary) 93 ++++++++++++++++++++++ 1 file changed, 93 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/msm/qcom,llcc.txt diff --git a/Documentation/devicetree/bindings/arm/msm/qcom,llcc.txt b/Documentation/devicetree/bindings/arm/msm/qcom,llcc.txt new file mode 100644 index 0000000..d433b0c --- /dev/null +++ b/Documentation/devicetree/bindings/arm/msm/qcom,llcc.txt @@ -0,0 +1,93 @@ +* LLCC (Last Level Cache Controller) + +Properties: +- compatible: + Usage: required + Value type: + Definition: Number of cache cells, must be 1 + +- max-slices: + usage: required + Value Type: + +compatible devices: + qcom,sdm845-llcc + +Example: + + qcom,system-cache@1300000 { + compatible = "qcom,llcc-core", "syscon", "simple-mfd";



[PATCH 2/2] drivers: soc: Add LLCC driver
Channagoud Kadabi writes:



[PATCH 0/2] SDM845 System Cache Driver
Channagoud Kadabi writes: (Summary) This series implements system cache or LLCC(Last Level Cache Controller) driver for SDM845 SOC. Each cache slice is associated with size and SCID (System Cache ID) The driver also provides API for clients to query the cache slice details, activate and deactivate them.
activate and deactivate them.
System cache has other blocks for memory error detection and AMON (Activity Monitor) for lock up detection.
AMON (Activity Monitor) for lock up detection.
Since the hardware block has multiple functional units the driver is implemented to use syscon/regmap interface.



Re: [PATCH RFC tip/core/rcu] Make SRCU be once again optional
"Paul E. McKenney" writes: (Summary) ^~
These two I don't get given the definitions for !CONFIG_DEBUG_LOCK_ALLOC: These two I don't get given the definitions for !CONFIG_DEBUG_LOCK_ALLOC: # define rcu_lock_acquire(a) do { } while (0) # define rcu_lock_release(a) do { } while (0) Is your build somehow picking up a different definition? */ static inline int srcu_read_lock_held(struct srcu_struct *sp) { - if (!debug_lockdep_rcu_enabled()) - return 1;



Re: [PATCH v3] retpoline: Add retpoline tag to VERMAGIC
Andi Kleen writes: On Tue, Jan 16, 2018 at 10:24:53PM +0100, Thomas Gleixner wrote: Acked-by: Thomas Gleixner Thanks. Through which tree should this go?
Or Linus, could you take it directly?
Or Linus, could you take it directly?
-Andi
-Andi
-Andi



linux-next: manual merge of the arm64 tree with Linus' tree
Stephen Rothwell writes: (Summary) Hi Catalin,
Hi Catalin,
Today's linux-next merge of the arm64 tree got a conflict in: Today's linux-next merge of the arm64 tree got a conflict in: arch/arm64/kernel/fpsimd.c
arch/arm64/kernel/fpsimd.c
between commit:
between commit:
a45448313706 ("arm64: fpsimd: Fix copying of FP state from signal frame into task struct") a45448313706 ("arm64: fpsimd: Fix copying of FP state from signal frame into task struct") from Linus' tree and commit:
from Linus' tree and commit:
0abdeff598a6 ("arm64: fpsimd: Fix state leakage when migrating after sigreturn") 0abdeff598a6 ("arm64: fpsimd: Fix state leakage when migrating after sigreturn") from the arm64 tree.
from the arm64 tree.
I fixed it up (I just used the latter version) and can carry the fix as necessary.



Re: [PATCH] ARM: make memzero optimization smarter
Arnd Bergmann writes: (Summary) We might actually get even better results by dropping the __memzero path entirely, since gcc has can optimize trivial memset() operations and inline them.
operations and inline them.
If I read arch/arm/lib/memzero.S correctly, it saves exactly two 'orr' instructions compared to the memset.S implementation, but calling memset() rather than __memzero() from C code ends up saving a function call at least some of the time.
function call at least some of the time.
Building a defconfig kernel with gcc-7.2.1, I see 1919 calls to __memzero() and 636 calls to memset() in vmlinux.



Re: [PATCH 07/11] signal/arm64: Document conflicts with SI_USER an ...
(Eric W. Biederman) writes: (Summary) Given that it seems to match my experience we can almost certainly change the code to just warn when the 0 is passed in for the si_code for fault handlers.
passed in for the si_code for fault handlers.
I want to ensure that all of the fields are filled in before I do that or else I risk passing unitialized values to userspace. But I like that as the long term goal for this code.
as the long term goal for this code.
draft an RFC for discussion (hopefully sometime this week).



Re: [RFC PATCH 00/16] PTI support for x86-32
Andy Lutomirski writes: On Tue, Jan 16, 2018 at 8:36 AM, Joerg Roedel wrote: tested Wine and DosEMU yet, so this might also be broken. If you pass all the x86 selftests, then Wine and DOSEMU are pretty likely to work :)
likely to work :)
--Andy
--Andy
--Andy



linux-next: manual merge of the arm64 tree with Linus' tree
Stephen Rothwell writes: (Summary) Hi Catalin,
Hi Catalin,
Today's linux-next merge of the arm64 tree got a conflict in: Today's linux-next merge of the arm64 tree got a conflict in: arch/arm64/kernel/cpufeature.c
arch/arm64/kernel/cpufeature.c
between commit:
between commit:
3fab39997a98 ("arm64/sve: Report SVE to userspace via CPUID only if supported") 3fab39997a98 ("arm64/sve: Report SVE to userspace via CPUID only if supported") from Linus' tree and commit:
from Linus' tree and commit:
64c02720ea35 ("arm64: cpufeature: Detect CPU RAS Extentions") 64c02720ea35 ("arm64: cpufeature: Detect CPU RAS Extentions") from the arm64 tree.
from the arm64 tree.
I fixed it up (see below) and can carry the fix as necessary.



Re: [PATCH] drm/dsi: Fix improper use of mipi_dsi_device_transfer( ...
Sean Paul writes: On Mon, Jan 15, 2018 at 10:12:24AM +0100, Andrzej Hajda wrote: Reviewed-by: Andrzej Hajda Applied to drm-misc-next. Thanks for the patch and review Applied to drm-misc-next. Thanks for the patch and review Sean
Sean
EXPORT_SYMBOL(mipi_dsi_set_maximum_return_packet_size);



Re: [PATCH v3 8/9] x86: use __uaccess_begin_nospec and ASM_IFENCE ...
Dan Williams writes: (Summary) sbb' instead of 'lfence', and any future changes will be handled like any new cpu enabling.
new cpu enabling.
To your specific question of the relative costs, sbb is architecturally cheaper, so let's go with that approach. It seems worse case userspace can speculatively leak something that's already in its address space.
in its address space.
I'll respin this set along those lines, and drop the ifence bits.



Re: [PATCH 1/3] ARM: dts: at91: nattis: use up-to-date mtd partitions
Peter Rosin writes: On 2018-01-16 17:30, Alexandre Belloni wrote:
Shouldn't it be simply removed then?
Hmm, that's a thought! Less is more, and all that. However, I think I rather have it in the device tree anyway. Then I have the option to drop a lot of tedious cmdline args in the future.
drop a lot of tedious cmdline args in the future.
Cheers,
Peter
Peter
Peter



Re: [PATCH] [v4] media: s3c-camif: fix out-of-bounds array access
Laurent Pinchart writes: (Summary) Hi Arnd,
Hi Arnd,
Thank you for the patch.
Thank you for the patch.
On Tuesday, 16 January 2018 23:52:15 EET Arnd Bergmann wrote: camera interface") Signed-off-by: Arnd Bergmann Reviewed-by: Laurent Pinchart Reviewed-by: Laurent Pinchart v4l_bound_align_image(&mf->width, 8, CAMIF_MAX_PIX_WIDTH, v4l_bound_align_image(&mf->width, 8, CAMIF_MAX_PIX_WIDTH,



Re: [PATCH arm/aspeed/ast2500 v1] ipmi: add an Aspeed KCS IPMI BMC ...
Corey Minyard writes: On 01/16/2018 02:59 PM, Corey Minyard wrote:
+};
One more thing...  Why aren't the above values being set in the device tree? Passing in a channel (and address) seems inflexible.  Kind of goes against the
philosophy of device trees.
philosophy of device trees.
-corey
-corey
+#endif /* _UAPI_LINUX_KCS_BMC_H */
+#endif /* _UAPI_LINUX_KCS_BMC_H */



Re: [PATCH v13 0/7] cgroup-aware OOM killer
Michal Hocko writes: (Summary) On Tue 16-01-18 13:36:21, David Rientjes wrote:
next line states.
I disagree and will not repeat argument why.
I disagree and will not repeat argument why.
the whole system. The current one is a policy that addresses a reasonably large class of usecases out there based on containers without forcing everybody else to use the same policy.
forcing everybody else to use the same policy.
only for mem cgroup oom policies.
cgroup mount option sounds like a reasonable approach already used for the unified hierarchy in early stages.
the unified hierarchy in early stages.
one or two particular policies and being no-ops otherwise.



Re: [PATCH v7 10/14] MIPS: ingenic: Detect machtype from SoC compa ...
James Hogan writes: (Summary) On Tue, Jan 16, 2018 at 04:48:00PM +0100, Paul Cercueil wrote: + return MACH_INGENIC_JZ4770;
Based on the assumption that fdt will always be non-NULL since commit ffb1843d059c ("MIPS: JZ4740: require & include DT"): ffb1843d059c ("MIPS: JZ4740: require & include DT"): Reviewed-by: James Hogan
Reviewed-by: James Hogan
Cheers
James
James
2.11.0
[unhandled content-type:application/pgp-signature]



Re: [PATCH 3/6] gpio: Add GPIO driver for Nintendo Wii
Jonathan Neuschäfer writes: (Summary) On Tue, Jan 16, 2018 at 10:42:54AM +0100, Linus Walleij wrote: ioread32be() and iowrite32be() to do explicit BE access. I'll try this out.
This include should not be needed.
Okay.
Okay.
BGPIOF_BIG_ENDIAN_BYTE_ORDER.
Yes, I plan to add IRQ support in a later patch.
Yes, I plan to add IRQ support in a later patch.
See the other drivers.
Yep, gpio-mmio looks like a good option, thanks for the pointer!



Re: [PATCH] [RESEND] vmwgfx: use monotonic event timestamps
Arnd Bergmann writes: (Summary) On Tue, Jan 16, 2018 at 6:28 PM, Thomas Hellstrom My bad.
No worries.
No worries.
Dave, is it too late to pull this in for the next merge window? The patch isn't urgent, it's fine to wait until after the merge window, I just want to avoid having to send it once more as I make my way through the remaining 'timeval' and 'timespec' users.
the remaining 'timeval' and 'timespec' users.
Arnd
Arnd
Arnd



[PATCH] [v4] media: s3c-camif: fix out-of-bounds array access
Arnd Bergmann writes: (Summary) While experimenting with older compiler versions, I ran into a warning that no longer shows up on gcc-4.8 or newer: into a warning that no longer shows up on gcc-4.8 or newer: drivers/media/platform/s3c-camif/camif-capture.c: In function '__camif_subdev_try_format': drivers/media/platform/s3c-camif/camif-capture.c:1265:25: error: array subscript is below array bounds drivers/media/platform/s3c-camif/camif-capture.c:1265:25: error: array subscript is below array bounds This is an off-by-one bug, leading to an access before the start of the array, while newer compilers silently assume this undefined behavior cannot happen and leave the loop at index 0 if no other entry matches.



Re: [PATCH v2] arm64: Branch predictor hardening for Cavium ThunderX2
Jon Masters writes: On 01/09/2018 07:47 AM, Jayachandran C wrote:
On 01/09/2018 07:47 AM, Jayachandran C wrote:
invoke it.
What's the status of this patch currently? Previously you had suggested to hold while the SMC got standardized, but then you seemed happy with pulling in. What's the latest?
pulling in. What's the latest?
Jon.
Jon.
Jon.



Re: [PATCH v2] x86/microcode/intel: Extend BDW late-loading with L ...
Borislav Petkov writes: On Tue, Jan 16, 2018 at 01:30:19PM -0800, Luck, Tony wrote: model_name.
Yeah, we're not doing that again. :)
Yeah, we're not doing that again. :)
called out in the erratum.
Oh well.
Oh well.
Thx.
Thx.



Re: [PATCH v2] arm64: Branch predictor hardening for Cavium ThunderX2
Jon Masters writes: On 01/09/2018 07:47 AM, Jayachandran C wrote:
invoke it.
What's the status of this patch for TX2? Previously you were holding on the new SMC number, but I think the consensus was to pull this in now? the new SMC number, but I think the consensus was to pull this in now? Jon.
Jon.



Re: [PATCH] ACPI/PCI: pci_link: reduce verbosity when IRQ is enabled
Bjorn Helgaas writes: (Summary) On Tue, Jan 16, 2018 at 01:53:00PM -0500, Sinan Kaya wrote: Signed-off-by: Sinan Kaya Looks like this was a result of 4d9391557b68 ("ACPI: add missing KERN_* constants to printks"), which I think added the wrong level in this case. More majordomo info at http://vger.kernel.org/majordomo-info.html More majordomo info at http://vger.kernel.org/majordomo-info.html



[PATCH v6 0/9] Renesas Capture Engine Unit (CEU) V4L2 driver
Jacopo Mondi writes: (Summary) ------------------------------------------------------------------------------- v4l2-compliance SHA : 1d3c611dee82090d9456730e24af368b51dcb4a9 Driver Info: Driver name : renesas-ceu Card type : Renesas CEU e8210000.ceu Bus info : platform:renesas-ceu-e8210000.c Driver version: 4.14.0 Capabilities : 0x84201000 Video Capture Multiplanar Streaming Extended Pix Format Device Capabilities Device Caps : 0x04201000 Video Capture Multiplanar Streaming Extended Pix Format Compliance test for device /dev/video0 (not using libv4l2): Required ioctls: test VIDIOC_QUERYCAP: OK Allow for multiple opens: test second video open: OK test VIDIOC_QUERYCAP: OK test VIDIOC_G/S_PRIORITY: OK test for unlimited opens: OK Debug ioctls: test VIDIOC_DBG_G/S_REGISTER: OK test VIDIOC_LOG_STATUS: OK (Not Supported) Input ioctls: test VIDIOC_G/S_TUNER/ENUM_FREQ_BANDS: OK (Not Supported) test VIDIOC_G/S_FREQUENCY: OK (Not Supported) test VIDIOC_S_HW_FREQ_SEEK: OK (Not Supported) test VID



[PATCH v6 2/9] include: media: Add Renesas CEU driver interface
Jacopo Mondi writes: (Summary) 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 include/media/drv-intf/renesas-ceu.h diff --git a/include/media/drv-intf/renesas-ceu.h b/include/media/drv-intf/renesas-ceu.h new file mode 100644 index 0000000..52841d1 --- /dev/null +++ b/include/media/drv-intf/renesas-ceu.h @@ -0,0 +1,26 @@ +// SPDX-License-Identifier: GPL-2.0 +/* + * renesas-ceu.h - Renesas CEU driver interface + * + * Copyright 2017-2018 Jacopo Mondi + */ + +#ifndef __MEDIA_DRV_INTF_RENESAS_CEU_H__ +#define __MEDIA_DRV_INTF_RENESAS_CEU_H__ + +#define CEU_MAX_SUBDEVS 2 + +struct ceu_async_subdev { + unsigned long flags;



[PATCH v6 1/9] dt-bindings: media: Add Renesas CEU bindings
Jacopo Mondi writes: (Summary) 81 ++++++++++++++++++++++ 1 file changed, 81 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/renesas,ceu.txt diff --git a/Documentation/devicetree/bindings/media/renesas,ceu.txt b/Documentation/devicetree/bindings/media/renesas,ceu.txt new file mode 100644 index 0000000..590ee27 --- /dev/null +++ b/Documentation/devicetree/bindings/media/renesas,ceu.txt @@ -0,0 +1,81 @@ +Renesas Capture Engine Unit (CEU) +---------------------------------------------- + +The Capture Engine Unit is the image capture interface found in the Renesas +SH Mobile and RZ SoCs. + +Required properties: +- compatible: Shall be "renesas,r7s72100-ceu" for CEU units found in RZ/A1-H + and RZ/A1-M SoCs. + + port { + ceu_in: endpoint { + remote-endpoint = <&ov7670_out>; + + ov7670: camera@21 { + compatible = "ovti,ov7670"; + + port { + ov7670_out: endpoint { + remote-endpoint = <&ceu_in>;



[PATCH v6 4/9] ARM: dts: r7s72100: Add Capture Engine Unit (CEU)
Jacopo Mondi writes: (Summary) Add Capture Engine Unit (CEU) node to device tree.
Add Capture Engine Unit (CEU) node to device tree.
Signed-off-by: Jacopo Mondi 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/arch/arm/boot/dts/r7s72100.dtsi b/arch/arm/boot/dts/r7s72100.dtsi index ab9645a..5fe62f9 100644 --- a/arch/arm/boot/dts/r7s72100.dtsi +++ b/arch/arm/boot/dts/r7s72100.dtsi @@ -135,9 +135,9 @@ #clock-cells = <1>; + + ceu: ceu@e8210000 { + reg = <0xe8210000 0x3000>;



[PATCH v6 6/9] media: i2c: ov772x: Remove soc_camera dependencies
Jacopo Mondi writes: (Summary) @@ -409,7 +412,7 @@ struct ov772x_priv { static const struct ov772x_color_format ov772x_cfmts[] = { { .code = MEDIA_BUS_FMT_YUYV8_2X8, - .colorspace = V4L2_COLORSPACE_JPEG, + .colorspace = V4L2_COLORSPACE_SRGB, .dsp3 = 0x0, .dsp4 = DSP_OFMT_YUV, .com3 = SWAP_YUV, @@ -417,7 +420,7 @@ static const struct ov772x_color_format ov772x_cfmts[] = { }, { .code = MEDIA_BUS_FMT_YVYU8_2X8, - .colorspace = V4L2_COLORSPACE_JPEG, + .colorspace = V4L2_COLORSPACE_SRGB, .dsp3 = UV_ON, .dsp4 = DSP_OFMT_YUV, .com3 = SWAP_YUV, @@ -425,7 +428,7 @@ static const struct ov772x_color_format ov772x_cfmts[] = { }, { .code = MEDIA_BUS_FMT_UYVY8_2X8, - .colorspace = V4L2_COLORSPACE_JPEG, + .colorspace = V4L2_COLORSPACE_SRGB, .dsp3 = 0x0, .dsp4 = DSP_OFMT_YUV, .com3 = 0x0, @@ -550,7 +553,7 @@ static int ov772x_reset(struct i2c_client *client) } /* - * soc_camera_ops function + * subdev ops */ static int ov772x_s_stream(struct v4l2_subdev *sd, int enable) @@ -650,13



Re: [PATCH] [v3] media: s3c-camif: fix out-of-bounds array access
Arnd Bergmann writes: (Summary) wrote:
camif_mbus_formats[i] in the else branch ?
Ah, that must be what I was thinking back when I first discussed it with Sylvester in
https://patchwork.kernel.org/patch/9950041/
https://patchwork.kernel.org/patch/9950041/
Unfortunately, I hadn't given it as much thought today when I tried to reconstruct the result to send a new version I tried to reconstruct the result to send a new version How about simply
mf->code = camif_mbus_formats[0];
Yes, makes sense.



[REGRESSION] mux/gpio.c is not able to get any gpio pins
Peter Rosin writes: (Summary) Total pages: 16256 Kernel command line: console=ttyS0,115200 rw consoleblank=0 ip=none root=ubi0:rootfs ubi.mtd=6 rootfstype=ubifs noinitrd mtdparts=atmel_nand:256k(at91bootstrap),384k(barebox)ro,256k@768k(bareboxenv),256k(bareboxenv2),128k@1536k(oftree),5M@2M(kernel),-@8M(rootfs) Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Memory: 56252K/65536K available (5120K kernel code, 182K rwdata, 1052K rodata, 1024K init, 109K bss, 9284K reserved, 0K cma-reserved) Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0xc4800000 - 0xff800000 ( 944 MB) lowmem : 0xc0000000 - 0xc4000000 ( 64 MB) .text : 0xc0008000 - 0xc0600000 (6112 kB) .init : 0xc0800000 - 0xc0900000 (1024 kB) .data : 0xc0900000 - 0xc092da8c ( 183 kB) .bss : 0xc092da8c - 0xc0948f8c ( 110 kB) NR_IRQS: 16, nr_irqs: 16, preallocated irqs



[PATCH v6 8/9] media: i2c: tw9910: Remove soc_camera dependencies
Jacopo Mondi writes: (Summary) I2C diff --git a/drivers/media/i2c/Makefile b/drivers/media/i2c/Makefile index fb99293..e26544f 100644 --- a/drivers/media/i2c/Makefile +++ b/drivers/media/i2c/Makefile @@ -48,6 +48,7 @@ obj-$(CONFIG_VIDEO_TVP7002) += tvp7002.o obj-$(CONFIG_VIDEO_TW2804) += tw2804.o obj-$(CONFIG_VIDEO_TW9903) += tw9903.o obj-$(CONFIG_VIDEO_TW9906) += tw9906.o +obj-$(CONFIG_VIDEO_TW9910) += tw9910.o obj-$(CONFIG_VIDEO_CS3308) += cs3308.o obj-$(CONFIG_VIDEO_CS5345) += cs5345.o obj-$(CONFIG_VIDEO_CS53L32A) += cs53l32a.o diff --git a/drivers/media/i2c/tw9910.c b/drivers/media/i2c/tw9910.c index bdb5e0a..96792df 100644 --- a/drivers/media/i2c/tw9910.c +++ b/drivers/media/i2c/tw9910.c @@ -1,6 +1,9 @@ +// SPDX-License-Identifier: GPL-2.0 /* * tw9910 Video Driver * + * Copyright (C) 2017 Jacopo Mondi



[PATCH v6 5/9] v4l: i2c: Copy ov772x soc_camera sensor driver
Jacopo Mondi writes: (Summary) HFLIP_IMG) + +#define VFLIP_IMG 0x80 /* Vertical flip image ON/OFF selection */ +#define HFLIP_IMG 0x40 /* Horizontal mirror image ON/OFF selection */ +#define SWAP_RGB 0x20 /* Swap B/R output sequence in RGB mode */ +#define SWAP_YUV 0x10 /* Swap Y/UV output sequence in YUV mode */ +#define SWAP_ML 0x08 /* Swap output MSB/LSB */ + /* Tri-state option for output clock */ +#define NOTRI_CLOCK 0x04 /* 0: Tri-state at this period */ + /* 1: No tri-state at this period */ + /* Tri-state option for output data */ +#define NOTRI_DATA 0x02 /* 0: Tri-state at this period */ + /* 1: No tri-state at this period */ +#define SCOLOR_TEST 0x01 /* Sensor color bar test pattern */ + +/* COM4 */ + /* PLL frequency control */ +#define PLL_BYPASS 0x00 /* 00: Bypass PLL */ +#define PLL_4x 0x40 /* 01: PLL 4x */ +#define PLL_6x 0x80 /* 10: PLL 6x */ +#define PLL_8x 0xc0 /* 11: PLL 8x */ + /* AEC evaluate window */ +



[PATCH v6 7/9] v4l: i2c: Copy tw9910 soc_camera sensor driver
Jacopo Mondi writes: (Summary) + +static const struct tw9910_scale_ctrl tw9910_ntsc_scales[] = { + { + .name = "NTSC SQ", + .width = 640, + .height = 480, + .hscale = 0x0100, + .vscale = 0x0100, + }, + { + .name = "NTSC CCIR601", + .width = 720, + .height = 480, + .hscale = 0x0100, + .vscale = 0x0100, + }, + { + .name = "NTSC SQ (CIF)", + .width = 320, + .height = 240, + .hscale = 0x0200, + .vscale = 0x0200, + }, + { + .name = "NTSC CCIR601 (CIF)", + .width = 360, + .height = 240, + .hscale = 0x0200, + .vscale = 0x0200, + }, + { + .name = "NTSC SQ (QCIF)", + .width = 160, + .height = 120, + .hscale = 0x0400, + .vscale = 0x0400, + }, + { + .name = "NTSC CCIR601 (QCIF)", + .width = 180, + .height = 120, + .hscale = 0x0400, + .vscale = 0x0400, + }, +};



Re: [PATCH v16 00/10] Add backlight helper functions
Sean Paul writes: (Summary) On Tue, Jan 16, 2018 at 10:31:07AM +0000, Meghana Madhyastha wrote: > -Add a comment about setting brightness = max_brightness in of_find_backlight > video: backlight: Add helpers to enable and disable backlight > video: backlight: Add of_find_backlight helper in backlight.c > video: backlight: Add devres versions of of_find_backlight > drm/tinydrm: Call devres version of of_find_backlight > drm/panel: Use of_find_backlight helper > drm/omapdrm: Use of_find_backlight helper >



[PATCH v6 9/9] arch: sh: migor: Use new renesas-ceu camera driver
Jacopo Mondi writes: (Summary) - -static struct platform_device migor_camera[] = { - { - .name = "soc-camera-pdrv", - .id = 0, - .dev = { - .platform_data = &ov7725_link, - }, - }, { - .name = "soc-camera-pdrv", - .id = 1, - .dev = { - .platform_data = &tw9910_link, - }, + .platform_data = &tw9910_info, }, };



[PATCH v6 3/9] v4l: platform: Add Renesas CEU driver
Jacopo Mondi writes: (Summary) +} + +static const struct v4l2_ioctl_ops ceu_ioctl_ops = { + .vidioc_querycap = ceu_querycap, + + .vidioc_enum_fmt_vid_cap_mplane = ceu_enum_fmt_vid_cap, + .vidioc_try_fmt_vid_cap_mplane = ceu_try_fmt_vid_cap, + .vidioc_s_fmt_vid_cap_mplane = ceu_s_fmt_vid_cap, + .vidioc_g_fmt_vid_cap_mplane = ceu_g_fmt_vid_cap, + + .vidioc_enum_input = ceu_enum_input, + .vidioc_g_input = ceu_g_input, + .vidioc_s_input = ceu_s_input, + + .vidioc_reqbufs = vb2_ioctl_reqbufs, + .vidioc_querybuf = vb2_ioctl_querybuf, + .vidioc_qbuf = vb2_ioctl_qbuf, + .vidioc_expbuf = vb2_ioctl_expbuf, + .vidioc_dqbuf = vb2_ioctl_dqbuf, + .vidioc_create_bufs = vb2_ioctl_create_bufs, + .vidioc_prepare_buf = vb2_ioctl_prepare_buf, + .vidioc_streamon = vb2_ioctl_streamon, + .vidioc_streamoff = vb2_ioctl_streamoff, + + .vidioc_g_parm = ceu_g_parm, + .vidioc_s_parm = ceu_s_parm, + .vidioc_enum_framesizes = ceu_enum_framesizes, + .vidioc_enum_frameintervals = ceu_enum_frameintervals, +};



[PATCH 2/3] ARM: dts: exynos: Fix missing missing reg warning for ...
Krzysztof Kozlowski writes: (Summary) 3 ++- 9 files changed, 27 insertions(+), 26 deletions(-) diff --git a/Documentation/devicetree/bindings/arm/samsung/pmu.txt b/Documentation/devicetree/bindings/arm/samsung/pmu.txt index 779f5614bcee..405646655ec7 100644 --- a/Documentation/devicetree/bindings/arm/samsung/pmu.txt +++ b/Documentation/devicetree/bindings/arm/samsung/pmu.txt @@ -12,6 +12,8 @@ Properties: - "samsung,exynos5433-pmu" - for Exynos5433 SoC. */ -/ { - soc { - compatible = "simple-bus"; - - poweroff: syscon-poweroff { - compatible = "syscon-poweroff";



[RFT 3/3] arm64: dts: exynos: Fix missing missing reg warning for ...
Krzysztof Kozlowski writes: (Summary) 14 +++++++------- 2 files changed, 15 insertions(+), 15 deletions(-) diff --git a/arch/arm64/boot/dts/exynos/exynos5433.dtsi b/arch/arm64/boot/dts/exynos/exynos5433.dtsi index 62f276970174..34c3648182d9 100644 --- a/arch/arm64/boot/dts/exynos/exynos5433.dtsi +++ b/arch/arm64/boot/dts/exynos/exynos5433.dtsi @@ -231,13 +231,6 @@ cpu_on = <0xC4000003>; - reboot: syscon-reboot { - compatible = "syscon-reboot"; gic: interrupt-controller@11001000 { diff --git a/arch/arm64/boot/dts/exynos/exynos7.dtsi b/arch/arm64/boot/dts/exynos/exynos7.dtsi index ad9dce6894ce..aa99d49af356 100644 --- a/arch/arm64/boot/dts/exynos/exynos7.dtsi +++ b/arch/arm64/boot/dts/exynos/exynos7.dtsi @@ -492,15 +492,15 @@ }; - reboot: syscon-reboot { - compatible = "syscon-reboot";



[PATCH 1/3] ARM: dts: exynos: Remove duplicated inclusion of sysco ...
Krzysztof Kozlowski writes: (Summary) The exynos-syscon-restart.dtsi is already included by exynos5.dtsi (through exynos54xx.dtsi).
(through exynos54xx.dtsi).
Signed-off-by: Krzysztof Kozlowski 1 - 1 file changed, 1 deletion(-) diff --git a/arch/arm/boot/dts/exynos5410.dtsi b/arch/arm/boot/dts/exynos5410.dtsi index 1886aa00b2db..1e6b57d013c4 100644 --- a/arch/arm/boot/dts/exynos5410.dtsi +++ b/arch/arm/boot/dts/exynos5410.dtsi @@ -11,7 +11,6 @@ */ #include "exynos54xx.dtsi" -#include "exynos-syscon-restart.dtsi" #include



Re: [PATCH] [RESEND] vmwgfx: use monotonic event timestamps
Woody Suwalski writes: (Summary) Thomas Hellstrom wrote:
Thomas, the same way my DRM patch has disappeared:
Date
Date
Tue, 19 Dec 2017 11:50:57 -0800
From Sinclair Yeh <>
Subject Re: [PATCH v.2] 4.15 vmgfx boot warning
Subject Re: [PATCH v.2] 4.15 vmgfx boot warning
Subject Re: [PATCH v.2] 4.15 vmgfx boot warning
Subject Re: [PATCH v.2] 4.15 vmgfx boot warning
Subject Re: [PATCH v.2] 4.15 vmgfx boot warning
This looks okay to me.
This looks okay to me.
On Mon, Dec 18, 2017 at 07:26:03PM -0500, Woody Suwalski wrote: ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ÿ¿¿¿¿¿ }
=============================================== The 4.15 drm_atomic_helper driver shows a warning during boot.



Re: [PATCH RFC v1] arm64: Handle traps from accessing CNTVCT/CNTFR ...
Nicolin Chen writes: (Summary) On Tue, Jan 16, 2018 at 09:19:13PM +0000, Marc Zyngier wrote: > > I understand that it should take care of the condition field as > > Just for curiosity: If we confine > > the topic to read access of CNTVCT/CNTFRQ, what'd be the penalty > > by ignoring the condition field and executing it anyway? > > > What I see for a conditional CNTVCT read is more likely: if (condition) { // in this case, if (true) r1 = lower32(cntvct);



Re: [PATCH v13 0/7] cgroup-aware OOM killer
David Rientjes writes: (Summary) On Mon, 15 Jan 2018, Michal Hocko wrote:
On Mon, 15 Jan 2018, Michal Hocko wrote:
far from limited to a single workload or company.
The complaint about the user interface is that it is not extensible, as my next line states. My suggestion adds two new files to the mem cgroup v2 filesystem and no mount option, and allows any policy to be added later that only uses these two files. It would also render both the mount option and the additional file in the mem cgroup v2 filesystem added by this patchset to be no-ops.
filesystem added by this patchset to be no-ops.
filesystem added by this patchset to be no-ops.



Re: [PATCH v2] x86/microcode/intel: Extend BDW late-loading with L ...
"Luck, Tony" writes: On Tue, Jan 16, 2018 at 09:50:37PM +0100, Borislav Petkov wrote: Or perhaps some other bit somewhere instead of this cache size thing? I could get you a list of model numbers that you can check against model_name. But that seems way worse. Especially as the 2.5MB thing is what is called out in the erratum.
is what is called out in the erratum.
-Tony
-Tony
-Tony



Re: [PATCH v6 02/12] drivers: base: cacheinfo: setup DT cache prop ...
Jeremy Linton writes: (Summary) Hi,
Hi,
On 01/15/2018 10:07 AM, Palmer Dabbelt wrote:
uses device tree on all Linux systems.
If I'm understanding the context correctly:
If I'm understanding the context correctly:
The first part of this patch set just straightens out the DT setup order so it happens in a single pass (rather that doing one pass to find the DT nodes, then another later on to update the cacheinfo from DT). If that were changed, then it might be possible to drop most of the DT cache setup code from the riscv/arch tree.
riscv/arch tree.
riscv/arch tree.
patch if really needed.
patch if really needed.



Re: [PATCH] lightnvm/pblk-gc: Delete an error message for a failed ...
Matias_Bjørling writes: On 01/16/2018 10:10 PM, SF Markus Elfring wrote:
GFP_KERNEL);
Thanks Markus. I'll queue it up for 4.17.
Thanks Markus. I'll queue it up for 4.17.
Thanks Markus. I'll queue it up for 4.17.



Re: [PATCH v4 00/17] ASoC: fsl_ssi: Clean up - program flow level
Caleb Crome writes: On Mon, Jan 15, 2018 at 3:16 PM, Nicolin Chen wrote: 2.7.4
Tested v4 with 8 channel TDM at 48kHz. No problems found. Tested v4 with 8 channel TDM at 48kHz. No problems found. Tested-by: Caleb Crome
Tested-by: Caleb Crome
Tested-by: Caleb Crome



Re: [PATCH] mm: numa: Do not trap faults on shared data section pages.
Mel Gorman writes: (Summary) It would have been nice to see data on other realistic workloads as well.
data on other realistic workloads as well.
My main source of discomfort is the fact that this is permanent as two processes perfectly isolated but with a suitably shared COW mapping will never migrate the data. A potential improvement to get the reported bandwidth up in the test program would be to skip the rest of the VMA if page_mapcount != 1 in a COW mapping as it would be reasonable to assume the remaining pages in the VMA are also affected and the scan is wasteful.



Re: [PATCH v3] retpoline: Add retpoline tag to VERMAGIC
Thomas Gleixner writes: On Tue, 16 Jan 2018, Andi Kleen wrote:
On Tue, 16 Jan 2018, Andi Kleen wrote:
Signed-off-by: Andi Kleen Acked-by: Thomas Gleixner Acked-by: Thomas Gleixner 2.14.3
2.14.3



Re: [PATCH v2] retpoline/module: Warn for missing retpoline in module
Thomas Gleixner writes: On Tue, 16 Jan 2018, Andi Kleen wrote:
On Tue, 16 Jan 2018, Andi Kleen wrote:
We can either go with the v3, or rework this one into a v4? V3 is fine. Not loading is the right thing to do :) V3 is fine. Not loading is the right thing to do :) Thanks,
Thanks,
tglx
tglx
tglx



Re: [PATCH] reset: ti-rstctrl: use the reset-simple driver
Suman Anna writes: (Summary) +- compatible : "ti,rstctrl" > +- reg : Should contain 1 register ranges(address and length) > + prm_gfx: prm@1100 { > + gfx_rstctrl: rstctrl@4 { > @@ -123,6 +123,7 @@ static const struct of_device_id reset_simple_dt_ids[] = { > { .compatible = "st,stm32-rcc", }, > { .compatible = "allwinner,sun6i-a31-clock-reset", > .data = &reset_simple_active_low }, > + { .compatible = "ti,rstctrl", }, > { .compatible = "zte,zx296718-reset", > { /* sentinel */ }, >



Re: [PATCH v13 0/7] cgroup-aware OOM killer
David Rientjes writes: (Summary) If the root mem cgroup and leaf cgroups were truly comparable, it also prevents both problems regardless of which cgroup the processes attached to.
attached to.
There is no connecting tissue between what I wrote and what you wrote. It's also obviously untested in those 10+ revisions since it uses oom_badness() for the root mem cgroup and not leaf mem cgroups which is why it breaks any system where user processes are attached to the root mem cgroup.



Re: [RFC PATCH 00/16] PTI support for x86-32
Thomas Gleixner writes: (Summary) On Tue, 16 Jan 2018, Joerg Roedel wrote:
in its development :)
16 files changed, 333 insertions(+), 123 deletions(-) Impressively small and well done !
Impressively small and well done !
Can you please make that patch set against
Can you please make that patch set against
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-pti-for-linus git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-pti-for-linus so we immediately have it backportable for 4.14 stable? We can pick some of the simple patches which make defines and inlines available out of the pile right away and apply them to x86/pti to shrink the amount of stuff you have to worry about.
the amount of stuff you have to worry about.
Thanks,
Thanks,
tglx
tglx
tglx
tglx



Re: [PATCH RFC v1] arm64: Handle traps from accessing CNTVCT/CNTFR ...
Marc Zyngier writes: (Summary) On Tue, 16 Jan 2018 20:32:19 +0000, Nicolin Chen wrote: > On Thu, Jan 11, 2018 at 08:51:37AM +0000, Marc Zyngier wrote: > [ I also added cntfrq here for safety as theoretically it could > drop it in the next version if someone can confirm it's not > Thanks -- Nicolin ] > esr) == hook->esr_val) { > Also, this code is fairly broken in its handling of conditional > I understand that it should take care of the condition field as > the topic to read access of CNTVCT/CNTFRQ, what'd be the penalty >



Re: [PATCH 12/16] x86/mm/pae: Populate the user page-table with us ...
Dave Hansen writes: On 01/16/2018 01:10 PM, Thomas Gleixner wrote:
and get rid of the ifdeffery completely.
Heh, that's an entertaining way to do it. Joerg, if you go do it this way, it would be nice to add all the other gunk that we don't allow to be set in the PAE pgd.
be set in the PAE pgd.
be set in the PAE pgd.



Re: [PATCH 3/4] tty: Iterate only thread group leaders in __do_SAK()
Oleg Nesterov writes: (Summary) Anyway, we could use send_sig_info(SIGKILL, SEND_SIG_FORCED, p) instead of that > At the same time, I do not know if we actually want to kill sub-namespace inits > If yes, we can use SEND_SIG_FORCED (better than ugly force_sig()) but > "An operating system's Secure Attention Key is a security tool which is > is an undefeatable way of killing all programs which could be > It seems, since not privileged user is able to create pid_ns to start >



RE: [PATCH v2] retpoline/module: Warn for missing retpoline in module
"Van De Ven, Arjan" writes: (Summary) PiBJIGp1c3Qgc2VudCBhIHYzIHRoYXQgY2hhbmdlcyB0aGUgVkVSTUFHSUMgb25seSwgYmFzZWQg b24gR3JlZydzDQo+IGVhcmxpZXIgZmVlZGJhY2suDQo+IA0KPiBJdCBoYXMgdGhlIGRyYXdiYWNr cyB0aGF0IGl0Og0KPiAtIHJlZnVzZXMgbG9hZGluZyBpbnN0ZWFkIG9mIHdhcm5zDQo+IC0gZG9l c24ndCBzdG9wIHJlZnVzaW5nIHdoZW4gdGhlIGZlYXR1cmUgaXMgcnVudGltZSBkaXNhYmxlZA0K PiANCj4gQnV0IGl0J3MgbXVjaCBzaW1wbGVyLCBqdXN0IGEgZmV3IGxpbmVzIG9mIGlmZGVmLg0K DQpJIHRoaW5rIHNpbXBsZSBpcyBnb29kIGF0IHRoaXMgcG9pbnQNCg0K DQpJIHRoaW5rIHNpbXBsZSBpcyBnb29kIGF0IHRoaXMgcG9pbnQNCg0K DQpJIHRoaW5rIHNpbXBsZSBpcyBnb29kIGF0IHRoaXMgcG9pbnQNCg0K



Re: [PATCH 12/16] x86/mm/pae: Populate the user page-table with us ...
Thomas Gleixner writes: On Tue, 16 Jan 2018, Joerg Roedel wrote:
pgd.pgd |= _PAGE_NX;
I'd suggest to have:
I'd suggest to have:
static inline pteval_t supported_pgd_mask(void)
{ if (IS_ENABLED(CONFIG_X86_64)) return __supported_pte_mask; return __supported_pte_mask & ~_PAGE_NX); } and get rid of the ifdeffery completely. Thanks, tglx



Re: [PATCH RFC tip/core/rcu] Make SRCU be once again optional
Arnd Bergmann writes: On Tue, Jan 16, 2018 at 10:02 PM, Arnd Bergmann wrote: On Fri, 2 Jun 2017, Paul E. McKenney wrote:
in this build failure:
Sorry, wrong file, try this one instead:
Sorry, wrong file, try this one instead:
https://pastebin.com/Xc0exzfg
https://pastebin.com/Xc0exzfg
Arnd
Arnd
Arnd



[PATCH] lightnvm/pblk-gc: Delete an error message for a failed mem ...
SF Markus Elfring writes: (Summary) Date: Tue, 16 Jan 2018 22:00:15 +0100
Date: Tue, 16 Jan 2018 22:00:15 +0100
Omit an extra message for a memory allocation failure in this function. 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/lightnvm/pblk-gc.c b/drivers/lightnvm/pblk-gc.c index 9c8e114c8a54..54cdb4360366 100644 --- a/drivers/lightnvm/pblk-gc.c +++ b/drivers/lightnvm/pblk-gc.c @@ -147,10 +147,8 @@ static void pblk_gc_line_prepare_ws(struct work_struct *work) int ret; - if (!invalid_bitmap) { - pr_err("pblk: could not allocate GC invalid bitmap\n"); - } emeta_buf = pblk_malloc(lm->emeta_len[0], l_mg->emeta_alloc_type, GFP_KERNEL);



Re: [PATCH v6 02/12] drivers: base: cacheinfo: setup DT cache prop ...
Jeremy Linton writes: (Summary) Hi,
Hi,
On 01/15/2018 06:33 AM, Sudeep Holla wrote:
is added that may break riscv IIUC.
Well I think you have a bisection issue where the additional information will disappear between this patch and wherever we put this code back in. I spent some time looking at the other users of this code to assure that they weren't doing partial DT setups and then having the common code use the resulting DT nodes. (to work around problems like the one recently fixed for the NONE->UNIFIED node conversion).
the NONE->UNIFIED node conversion).
the NONE->UNIFIED node conversion).
Sudeep
Sudeep