<>
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:
Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
NOTE: nothing is known to be fixed by this change, but it does enforce
some delays that are documented to be necessary. Possibly this could
fix some corner cases.
The function tcphy_dp_aux_calibration(), like most of the functions in
the type C PHY, is mostly undocumented and filled with mysterio
On Fri, 22 Sep 2017 15:11:38 +0100
Colin King wrote:
> From: Colin Ian King
>
> Don't populate const array patterns on the stack, instead make it
> static. Makes the object code smaller by over 60 bytes:
>
> Before:
>text data bss dec hex filename
>1953 4
Kishon,
On Thu, Sep 21, 2017 at 3:36 AM, Kishon Vijay Abraham I wrote:
> Hi Douglas,
>
> On Wednesday 20 September 2017 01:26 AM, Douglas Anderson wrote:
>> When connecting to certain DP monitors it was observed that only one
>> of the two orientations of the type C to DP cable would work.
>> Deb
Commit-ID: 411bc316f3365363959c2c895af2618389534583
Gitweb: http://git.kernel.org/tip/411bc316f3365363959c2c895af2618389534583
Author: Andi Kleen
AuthorDate: Thu, 14 Sep 2017 13:57:35 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 21 Sep 2017 13:12:58 -0300
perf stat: Fix a
Calculate the calibration code as per the docs. The docs talk about
reading and averaging the pullup and pulldown calibration codes. They
also talk about adding in some adjustment codes. Let's do what the
docs say.
In practice this doesn't seem to matter a whole lot. On a device I
tested the p
Commit-ID: 333b566559019b146905c623bde7f455c1d5add3
Gitweb: http://git.kernel.org/tip/333b566559019b146905c623bde7f455c1d5add3
Author: Andi Kleen
AuthorDate: Wed, 13 Sep 2017 14:50:06 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 18 Sep 2017 09:40:20 -0300
perf pmu: Improv
Commit-ID: 91e467bc568f15da2eac688e131010601e889184
Gitweb: http://git.kernel.org/tip/91e467bc568f15da2eac688e131010601e889184
Author: Kan Liang
AuthorDate: Sun, 10 Sep 2017 19:23:14 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 18 Sep 2017 09:40:19 -0300
perf machine: Use
On 09/22/2017 05:47 AM, Charles Keepax wrote:
> On Wed, Sep 20, 2017 at 06:04:20PM -0700, Florian Fainelli wrote:
>> It may happen that a device needs to force applying a state, e.g:
>> because it only defines one state of pin states (default) but loses
>> power/register contents when entering low
On rk3399-gru-kevin there are some cases where we're seeing AUX CH
failures when trying to do DisplayPort over type C. Problems are
intermittent and don't reproduce all the time. Problems are often
bursty and failures persist for several seconds before going away.
The failure case I focused on is
When connecting to certain DP monitors it was observed that only one
of the two orientations of the type C to DP cable would work.
Debugging showed that the problem was that we needed to set the type C
"flip" state earlier. Once we did this, problems went away.
While trying to dig into this probl
Commit-ID: 75e45e432052c7b1a5da866cff88192db8be1445
Gitweb: http://git.kernel.org/tip/75e45e432052c7b1a5da866cff88192db8be1445
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 14 Sep 2017 16:16:34 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 18 Sep 2017 09:40:19 -0300
pe
On some DP monitors we found that setting the wrong flip state on the
AUX channel could cause the monitor to stop asserting HotPlug Detect
(HPD). Setting the right flip state caused these monitors to start
asserting HotPlug Detect again.
Here's what we believe was happening:
* We'd plug in the mo
Commit-ID: 5a54c2f5e1717264f6e24687f703937eaca5f55d
Gitweb: http://git.kernel.org/tip/5a54c2f5e1717264f6e24687f703937eaca5f55d
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 20 Sep 2017 12:30:36 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 21 Sep 2017 13:12:59 -0300
pe
Commit-ID: c896f85a7c15ab9d040ffac8b8003e47996602a2
Gitweb: http://git.kernel.org/tip/c896f85a7c15ab9d040ffac8b8003e47996602a2
Author: Martin Kepplinger
AuthorDate: Wed, 13 Sep 2017 21:14:19 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 18 Sep 2017 09:40:21 -0300
perf tool
Commit-ID: 492e05b0654126bd6a04473028ac4c8cfc22ccec
Gitweb: http://git.kernel.org/tip/492e05b0654126bd6a04473028ac4c8cfc22ccec
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 20 Sep 2017 12:41:57 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 21 Sep 2017 13:12:59 -0300
to
Commit-ID: 0e1eed80885fdb09993bffb16f5662f4b53c1a08
Gitweb: http://git.kernel.org/tip/0e1eed80885fdb09993bffb16f5662f4b53c1a08
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 20 Sep 2017 16:41:34 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 21 Sep 2017 13:13:00 -0300
pe
On Fri, Sep 22, 2017 at 04:00:19PM +1000, Balbir Singh wrote:
> On Fri, 15 Sep 2017 18:21:08 -0700
> Ram Pai wrote:
>
> > From: Thiago Jung Bauermann
> >
> > Expose useful information for programs using memory protection keys.
> > Provide implementation for powerpc and x86.
> >
> > On a powerp
Commit-ID: 6ae8eefc6c8fe050f057781b70a83262eb0a61ee
Gitweb: http://git.kernel.org/tip/6ae8eefc6c8fe050f057781b70a83262eb0a61ee
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 21 Sep 2017 12:12:17 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 21 Sep 2017 13:13:00 -0300
to
Dear Sir,
We recently visited your website and we are interested in your models, We will
like to make an order from your list of products. However, we would like to see
your company's latest catalogs with the; minimum order quantity, delivery
time/FOB, payment terms etc. Official order placemen
Commit-ID: 5c9295bfe6f5f59f3f2eee78f58b0523d117897e
Gitweb: http://git.kernel.org/tip/5c9295bfe6f5f59f3f2eee78f58b0523d117897e
Author: Xiaochen Shen
AuthorDate: Tue, 19 Sep 2017 12:57:37 +0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 21 Sep 2017 13:12:58 -0300
perf tests: R
DW ethernet controller on HSDK hangs sometimes after SW reset, so
add reset node to make possible to reset DW ethernet controller HW.
Signed-off-by: Eugeniy Paltsev
---
Changes v2 -> v3:
* Remove v1 suffix as we finaly got rid of v1 suffix in reset
driver and docs.
* Rename reset node to
Commit-ID: 0a7c74eae307894c6c95316c382f118aef8481e8
Gitweb: http://git.kernel.org/tip/0a7c74eae307894c6c95316c382f118aef8481e8
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 4 Apr 2017 13:15:04 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 21 Sep 2017 13:28:06 -0300
per
Tested patch series on ia64 successfully.
Tested-by: Tony Luck
After this goes upstream, you should submit a patch to get rid of
all uses of %pF (70 instances in 35 files) and %pf (63 in 34)
Perhaps break the patch by top-level directory (e.g. get all the %pF
and %pF in the 17 files under drive
On 22.09.2017 18:21, Tomasz Nowicki wrote:
Hi Robin,
On 21.09.2017 17:52, Robin Murphy wrote:
The cached node mechanism provides a significant performance benefit for
allocations using a 32-bit DMA mask, but in the case of non-PCI devices
or where the 32-bit space is full, the loss of this bene
Please use 'brcmsmac:' as prefix instead of 'brcm80211:'.
On 22-09-17 16:03, Colin King wrote:
From: Colin Ian King
Don't populate const array ucode_ofdm_rates on the stack, instead make it
static. Makes the object code smaller by 100 bytes:
Before:
text data bss dec
On 09/22/2017 09:17 AM, Vivien Didelot wrote:
> bcm_sf2 is currently the only driver using the phy argument passed to
> .port_enable. It resets the state machine if the phy has been hard
> reset. This check is generic and can be moved to DSA core.
This is completely specific to bcm_sf2 because it
Hi gengdongjiu,
On 21/09/17 08:55, gengdongjiu wrote:
> On 2017/9/14 21:00, James Morse wrote:
>> user-space can choose whether to use SEA or SEI, it doesn't have to choose
>> the
>> same notification type that firmware used, which in turn doesn't have to be
>> the
>> same as that used by the CP
Hi Eric,
[auto build test ERROR on tip/auto-latest]
[also build test ERROR on v4.14-rc1 next-20170922]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Eric-Biggers
On 09/22/2017 06:20 AM, Charles Keepax wrote:
> On Fri, Sep 22, 2017 at 01:55:22PM +0200, Linus Walleij wrote:
>> On Thu, Sep 21, 2017 at 3:04 AM, Florian Fainelli
>> wrote:
>>
>>> It may happen that a device needs to force applying a state, e.g:
>>> because it only defines one state of pin state
On 09/22/2017 09:32 AM, Andrew Lunn wrote:
> On Fri, Sep 22, 2017 at 12:17:50PM -0400, Vivien Didelot wrote:
>> bcm_sf2 is currently the only driver using the phy argument passed to
>> .port_enable. It resets the state machine if the phy has been hard
>> reset. This check is generic and can be move
Hi!
I've got the following report while fuzzing the kernel with syzkaller.
On commit 6e80ecdddf4ea6f3cd84e83720f3d852e6624a68 (Sep 21).
==
BUG: KASAN: use-after-free in __run_timers+0xc0e/0xd40
Write of size 8 at addr 880069f701
From: Markus Elfring
Date: Fri, 22 Sep 2017 18:45:07 +0200
Adjust a jump target so that a bit of exception handling can be better
reused at the end of this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/media/usb/gspca/spca500.c |
On Fri, Sep 22, 2017 at 04:52:38PM +0900, Andi Shyti wrote:
> instead of sysfs_create_group.
>
> Signed-off-by: Andi Shyti
Applied, thank you.
> ---
> drivers/input/touchscreen/stmfts.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/input/touchscreen/stmft
On Fri, Sep 22, 2017 at 01:50:36PM +0800, KT Liao wrote:
> Original 20ms delay is a margin timing after a block writing
> in FW update flow.
>
> Sometimes it will cause fail during FW-updating if I2C timing delay.
> We offten see this issue in rockchip's I2C host.
>
> Extend the delay timing is t
On Fri, Sep 22, 2017 at 07:33:14AM +0200, Ingo Molnar wrote:
>
> * Eric Biggers wrote:
>
> > From: Eric Biggers
> >
> > This series fixes the bug found by syzkaller where the ptrace syscall
> > can be used to set invalid bits in a task's FPU state. I also found
> > that an equivalent bug was
On 22.09.2017 18:50, tn wrote:
On 22.09.2017 18:21, Tomasz Nowicki wrote:
Hi Robin,
On 21.09.2017 17:52, Robin Murphy wrote:
The cached node mechanism provides a significant performance benefit for
allocations using a 32-bit DMA mask, but in the case of non-PCI devices
or where the 32-bit spac
On Fri, 22 Sep 2017, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 22 Sep 2017 18:45:07 +0200
>
> Adjust a jump target so that a bit of exception handling can be better
> reused at the end of this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-
From: Colin Ian King
Currently if the stat type is invalid then data[i] is being set
either by dereferencing a null pointer p, or it is reading from
an incorrect previous location if we had a valid stat type
previously. Fix this by skipping over the read of p on an invalid
stat type.
Detected b
Hi Andi,
On Fri, Sep 22, 2017 at 01:17:02PM +0900, Andi Shyti wrote:
> Hi Dmitry,
>
> thanks for your review!
>
> [...]
>
> > > +static void s6sy761_report_coordinates(struct s6sy761_data *sdata, u8
> > > *event)
> > > +{
> > > + u8 tid = ((event[0] & S6SY761_MASK_TID) >> 2) - 1;
> >
> > Shou
On 09/22/2017 09:17 AM, Vivien Didelot wrote:
> The DSA slave open function configures the unicast MAC addresses on the
> master device, enable the switch port, change its STP state, then start
> the PHY device.
>
> Make the close function symmetric, by first stopping the PHY device,
> then changi
On 09/22/2017 09:17 AM, Vivien Didelot wrote:
> The .port_enable and .port_disable functions are meant to deal with the
> switch ports only, and no driver is using the phy argument anyway.
> Remove it.
I don't think this makes sense, there are perfectly legit reasons why a
switch driver may have s
On 09/22/2017 09:17 AM, Vivien Didelot wrote:
> Provide dsa_port_enable and dsa_port_disable helpers to respectively
> enable and disable a switch port. This makes the dsa_port_set_state_now
> helper static.
>
> Signed-off-by: Vivien Didelot
Reviewed-by: Florian Fainelli
--
Florian
On Wed, 2017-09-13 at 19:49 +0300, Leon Romanovsky wrote:
> On Mon, Sep 11, 2017 at 05:03:13PM +0100, Colin King wrote:
> > From: Colin Ian King
> >
> > In the case where mbox_status is OCRDMA_MBX_STATUS_FAILED and
> > add_status is OCRDMA_MBX_STATUS_FAILED err_num is assigned -EAGAIN
> > however
On Mon, 2017-09-18 at 12:28 +0100, Sudip Mukherjee wrote:
> From: Sudip Mukherjee
>
> If delay_drop_debugfs_init() fails in any of the operations to create
> debugfs, it is calling delay_drop_debugfs_cleanup() as part of its
> cleanup. But delay_drop_debugfs_cleanup() checks for 'dbg' and since
>
On Fri, Sep 22, 2017 at 06:44:12PM +0300, Konstantin Khlebnikov wrote:
> On Thu, Sep 21, 2017 at 2:06 AM, Roman Gushchin wrote:
> > Right now there is no convenient way to check if a process is being
> > coredumped at the moment.
> >
> > It might be necessary to recognize such state to prevent kil
On Fri, 2017-09-22 at 09:48 +0200, Arnd Bergmann wrote:
> On Fri, Sep 22, 2017 at 1:11 AM, Colin Ian King
> wrote:
> > On 22/09/17 00:09, Christophe JAILLET wrote:
> > > Le 22/09/2017 à 00:19, Colin King a écrit :
> > > > From: Colin Ian King
> > > >
> > > > Don't populate the read-only arrays d
On 22/09/17 17:21, Tomasz Nowicki wrote:
> Hi Robin,
>
> On 21.09.2017 17:52, Robin Murphy wrote:
>> The cached node mechanism provides a significant performance benefit for
>> allocations using a 32-bit DMA mask, but in the case of non-PCI devices
>> or where the 32-bit space is full, the loss of
> On Sep 20, 2017, at 11:15 PM, Thomas Meyer wrote:
>
> Use *_pool_zalloc rather than *_pool_alloc followed by memset with 0.
> Found by coccinelle spatch "api/alloc/pool_zalloc-simple.cocci"
>
> Signed-off-by: Thomas Meyer
> ---
>
> diff -u -p a/drivers/scsi/qla2xxx/qla_bsg.c b/drivers/scsi/
On Fri, Sep 22, 2017 at 7:42 AM, Shuah Khan wrote:
> Hi John/Greg,
>
> On 09/21/2017 02:10 PM, Shuah Khan wrote:
>> do_timer_oneshot() uses select() as a timer with FD_SETSIZE and readfs
>> is cleared with FD_ZERO without FD_SET.
>>
>> When stdout and stderr are redirected, the test hangs in selec
When timer_create() fails on a bootime or realtime clock, setup_timer()
returns 0 as if timer has been set. Callers wait forever for the timer
to expire.
This hang is seen on a system that doesn't have support for:
CLOCK_REALTIME_ALARM ABSTIME missing CAP_WAKE_ALARM? : [UNSUPPORTED]
Test hangs
>> return 0;
>> -error:
>> +
>> +report_failure:
>> +PERR("Set packet size: set interface error");
>> return -EBUSY;
>> }
>
> Why change the label name?
I find the suggested variant a bi better.
> They are both equally uninformative.
Which identifier would you find appropriate t
On Fri, 22 Sep 2017, SF Markus Elfring wrote:
> >>return 0;
> >> -error:
> >> +
> >> +report_failure:
> >> + PERR("Set packet size: set interface error");
> >>return -EBUSY;
> >> }
> >
> > Why change the label name?
>
> I find the suggested variant a bi better.
>
>
> > They are both eq
HI Sudeep,
> -Original Message-
> From: Sudeep Holla [mailto:sudeep.ho...@arm.com]
> Sent: Friday, September 22, 2017 4:10 AM
> To: Jiaying Liang
> Cc: linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org; jassisinghb...@gmail.com; Cyril Chempar
From: Eric Biggers
This series fixes the bug found by syzkaller where the ptrace syscall
can be used to set invalid bits in a task's FPU state. I also found
that an equivalent bug was reachable using the sigreturn syscall, so the
first patch fixes the bug in both cases.
The other two patches st
From: Eric Biggers
On x86, userspace can use the ptrace() or rt_sigreturn() system calls to
set a task's extended state (xstate) or "FPU" registers. ptrace() can
set them for another task using the PTRACE_SETREGSET request with
NT_X86_XSTATE, while rt_sigreturn() can set them for the current tas
From: Eric Biggers
Userspace can change the FPU state of a task using the ptrace() or
rt_sigreturn() system calls. Because reserved bits in the FPU state can
cause the XRSTOR instruction to fail, the kernel has to carefully
validate that no reserved bits or other invalid values are being set.
U
From: Eric Biggers
Move validation of user-supplied xstate_headers into a helper function
and call it from both the ptrace and sigreturn syscall paths. The new
function also considers it to be an error if *any* reserved bits are
set, whereas before we were just clearing most of them.
This shoul
>>> They are both equally uninformative.
>>
>> Which identifier would you find appropriate there?
>
> error was fine.
How do the different views fit together?
Regards,
Markus
Thanks for the reply. Learned a lot. :)
GEM_BUG_ON is new to me since it wasn't there at the beginning of GVT-g
upstream. It showed up later. So I left a lot of WARN_ON in the code and some
of them should be GEM_BUG_ON now.
Now I can figure out those differences. We can discuss with our QA to s
Hey Bjorn,
On Fri, Sep 22, 2017 at 10:56:05AM -0500, Bjorn Helgaas wrote:
> Joerg, if you pick this up, would you mind capitalizing the subject
> line to match the PCI convention, e.g.,
>
> PCI: Add dummy pci_acs_enabled() for CONFIG_PCI=n build
>
> If it's too late for you to pick this up thi
On 19.09.2017 21:03, Krzysztof Kozlowski wrote:
> On Fri, Sep 15, 2017 at 07:50:06PM +0200, Kamil Konieczny wrote:
>> Add support for MD5, SHA1, SHA256 hash algorithms for Exynos HW.
>> It uses the crypto framework asynchronous hash api.
>> It is based on omap-sham.c driver.
>> S5P has some HW diff
Hi Marc-André,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.14-rc1 next-20170922]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/marcandre-lureau-redhat-com/fw_cfg-add
Improve the binding example by removing the '@di0' notation, which
fixes the following build warning:
Warning (unit_address_vs_reg): Node /display@di0 has a unit name, but
no reg property
Signed-off-by: Marco Franchi
---
Documentation/devicetree/bindings/display/imx/fsl-imx-drm.txt | 2 +-
1 f
Peter, ping?
Thanks.
--
tejun
On Fri, Sep 22, 2017 at 10:13 AM, Colin King wrote:
> From: Colin Ian King
>
> Currently if the stat type is invalid then data[i] is being set
> either by dereferencing a null pointer p, or it is reading from
> an incorrect previous location if we had a valid stat type
> previously. Fix this by
Hi Björn,
On Fri, Sep 22, 2017 at 5:56 PM, Bjorn Helgaas wrote:
> On Mon, Sep 11, 2017 at 02:29:15PM +0200, Geert Uytterhoeven wrote:
>> If CONFIG_PCI=n, and gcc (e.g. 4.1.2) decides not to inline
>> get_pci_function_alias_group(), the build fails with:
>>
>> drivers/iommu/iommu.o: In functio
Hi Randy,
On Fri, Sep 22, 2017 at 6:24 PM, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Having the CHARLCD Kconfig symbol between "menuconfig AUXDISPLAY"
> and "if AUXDISPLAY" breaks the AUXDISPLAY submenus, so move the
> CHARLCD Kconfig symbol above the "menuconfig" so that the menu
> display i
Hi Florian,
Florian Fainelli writes:
> On 09/22/2017 09:17 AM, Vivien Didelot wrote:
>> The .port_enable and .port_disable functions are meant to deal with the
>> switch ports only, and no driver is using the phy argument anyway.
>> Remove it.
>
> I don't think this makes sense, there are perfec
On 09/22/17 11:15, Geert Uytterhoeven wrote:
> Hi Randy,
>
> On Fri, Sep 22, 2017 at 6:24 PM, Randy Dunlap wrote:
>> From: Randy Dunlap
>>
>> Having the CHARLCD Kconfig symbol between "menuconfig AUXDISPLAY"
>> and "if AUXDISPLAY" breaks the AUXDISPLAY submenus, so move the
>> CHARLCD Kconfig sy
On 09/22/2017 11:12 AM, Vivien Didelot wrote:
> Hi Florian,
>
> Florian Fainelli writes:
>
>> On 09/22/2017 09:17 AM, Vivien Didelot wrote:
>>> The .port_enable and .port_disable functions are meant to deal with the
>>> switch ports only, and no driver is using the phy argument anyway.
>>> Remov
Fix small typos in the Instructions and Uploading sections. Fix a typo in
the start/stop effect example usage code.
Signed-off-by: Jean-François Têtu
---
Documentation/input/ff.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/input/ff.rst b/Documentatio
Hi Peter,
On Fri, Sep 22, 2017 at 2:02 AM, Peter Zijlstra wrote:
> On Thu, Sep 21, 2017 at 06:50:24PM -0700, Joel Fernandes wrote:
>> +DECLARE_EVENT_CLASS(preemptirq_template,
>> +
>> + TP_PROTO(unsigned long ip, unsigned long parent_ip),
>> +
>> + TP_ARGS(ip, parent_ip),
>> +
>> + TP
I'll re-submit with all the CHECK warnings fixed.
Thanks
Al
On Thu, Sep 21, 2017 at 5:39 AM, 'Kishon Vijay Abraham I' via
BCM-KERNEL-FEEDBACK-LIST,PDL
wrote:
> Hi Florian,
>
> On Thursday 21 September 2017 04:07 AM, Florian Fainelli wrote:
>> Hi Kishon,
>>
>> On 09/15/2017 04:49 PM, Florian Fain
Use a more typical kernel logging style.
The current macro hides the gspca_dev argument so add it to the
macro uses instead.
Miscellanea:
o Add missing '\n' terminations to formats
o Realign arguments to open parenthesis
Signed-off-by: Joe Perches
---
drivers/media/usb/gspca/benq.c
Hi,
This is a direct seccomp pull request (similar to SELinux's for the v4.14
window); it's the same series that I sent to James earlier (notes below).
Please pull these seccomp changes for v4.14-rc2.
Thanks!
-Kees
The following changes since commit 520eccdfe187591a51ea9ab4c1a024ae4d0f68d9:
On 9/22/17 11:46 AM, SF Markus Elfring wrote:
They are both equally uninformative.
>>>
>>> Which identifier would you find appropriate there?
>>
>> error was fine.
>
> How do the different views fit together?
You want to change something. Changing something requires to spend
energy. You ne
From: Andy Lowe
If a port has no dma channel defined in the device tree, then
don't attempt to allocate a dma channel for the port.
Also suppress the warning message concerning the failure to allocate
a dma channel. Continue to emit the warning message if a dma
channel is defined but cannot be a
On Fri, 2017-09-22 at 19:46 +0200, SF Markus Elfring wrote:
> > > > They are both equally uninformative.
> > >
> > > Which identifier would you find appropriate there?
> >
> > error was fine.
>
> How do the different views fit together?
Markus, please respect what others tell you because
your c
From: Mathias Nyman
Modify xhci_find_next_ext_cap(base, offset, id) to return the next
capability offset if 0 is passed for id. Otherwise it will behave as
previously and return the offset of the next capability with matching id
capability id 0 is not used by xhci (reserved)
This is useful when
Add MUX_USB_* and MUX_TYPEC_* state constant defines, which can be used by
USB device/host, resp. Type-C polarity/role/altmode mux drivers and
consumers to ensure that they agree on the meaning of the
mux_control_select() state argument.
Signed-off-by: Hans de Goede
---
Changes in v2:
-Start numb
From: Stephen Boyd
Sometimes drivers only use muxes under certain scenarios. For
example, the chipidea usb controller may be connected to a usb
switch on some platforms, and connected directly to a usb port on
others. The driver won't know one way or the other though, so add
a mux_control_get_opt
On non DT platforms we cannot get the mux_chip by pnode. Other subsystems
(regulator, clock, pwm) have the same problem and solve this by allowing
platform / board-setup code to add entries to a lookup table and then use
this table to look things up.
This commit adds support for getting a mux cont
From: Peter Rosin
A board may need a mux controller to stay as-is for a while longer, e.g.
if setting the normally preferred idle state destroys booting.
The mechanism provided here is not perfect in two ways.
1. As soon as the mux controller is registered, some mux consumer can
access it and
We need to add mappings for the mux subsys to be able to find the
muxes for the fusb302 driver to be able to control the PI3USB30532
Type-C mux and the device/host mux integrated in the CHT SoC.
Signed-off-by: Hans de Goede
Acked-by: Andy Shevchenko
---
drivers/platform/x86/Kconfig
Intel Cherrytrail SoCs have an internal USB mux for muxing the otg-port
USB data lines between the xHCI host controller and the dwc3 gadget
controller. On some Cherrytrail systems this mux is controlled through
AML code reacting on a GPIO IRQ connected to the USB OTG id pin (through
an _AIE ACPI me
Add mux support to the fusb302 driver, call devm_tcpc_gen_mux_create()
to let the generic tcpc_mux_dev code create a tcpc_mux_dev for us.
Also document the mux-names used by the generic tcpc_mux_dev code in
our devicetree bindings.
Cc: Rob Herring
Cc: Mark Rutland
Cc: devicet...@vger.kernel.org
Add a driver for the Pericom PI3USB30532 Type-C cross switch /
mux chip found on some devices with a Type-C port.
Signed-off-by: Hans de Goede
---
Changes in v2:
-Adjust for new MUX_TYPEC_foo state defines
-Add MAINTAINERS entry
-Various code-style fixes
Changes in v3:
-Use new init_as_is mux fl
Cherry Trail SoCs have a built-in USB-role mux for switching between
the host and device controllers, rather then using an external mux
controller by a GPIO.
There is a driver using the mux-subsys to control this mux, this
commit adds support to the intel-int3496 driver to get a mux_controller
han
Setting the mux to TYPEC_MUX_NONE, TCPC_USB_SWITCH_DISCONNECT when the
data-role is device is not correct. Plenty of devices support operating
as USB device through a (separate) USB device controller.
So this commit instead splits out TYPEC_MUX_USB into TYPEC_MUX_USB_HOST
and TYPEC_MUX_USB_DEVICE
The Intel cherrytrail xhci controller has an extended cap mmio-range
which contains registers to control the muxing to the xhci (host mode)
or the dwc3 (device mode) and vbus-detection for the otg usb-phy.
Having a mux driver included in the xhci code (or under drivers/usb/host)
is not desirable.
So far the mux functionality of the tcpm code has not been hooked up
in any tcpc drivers. This commit adds a generic TCPC mux driver using
the mux subsys, which tcpc drivers can use to provide mux functionality
in cases where an external my is used.
Signed-off-by: Hans de Goede
---
Changes in v3:
On Fri, Sep 22, 2017 at 6:02 AM, Jean-Philippe Brucker
wrote:
> On 22/09/17 10:02, Joerg Roedel wrote:
>> On Tue, Sep 19, 2017 at 10:23:43AM -0400, Rob Clark wrote:
>>> I would like to decide in the IRQ whether or not to queue work or not,
>>> because when we get a gpu fault, we tend to get 1000's
On Fri, Sep 22, 2017 at 05:28:04PM +0200, Sebastian Andrzej Siewior wrote:
> The current check via srcu_online is slightly racy because after looking
> at srcu_online there could be an interrupt that interrupted us long
> enough until the CPU we checked against went offline.
But in that case, woul
On Thu, Sep 21, 2017 at 12:14 PM, Ram Pai wrote:
> Here is a patch that accomplishes the job. tested to work with
> some simple use cases. check if this works for you. If it does
> than we will have to think through all the edge cases and make it
> acceptable.
>From your experiments, it looks ex
This patch fix the warning "xxx has a unit name, but no reg property" by
removing "@0" from such node.
Signed-off-by: Corentin Labbe
Acked-by: Maxime Ripard
---
arch/arm/boot/dts/sun8i-h3-orangepi-plus.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/sun
Currently the mux_control_get implementation only deals with getting
mux controllers on DT platforms. This commit renames the current
implementation to of_mux_control_get to reflect this and makes
mux_control_get a wrapper around of_mux_control_get.
This is a preparation patch for adding support f
Hello
The goal of this patch series is to have a clean DT build with W=1.
Regards
Changes since v1:
- moved i2c2 unit address change from patch #2 in patch #1
Corentin Labbe (12):
ARM: dts: sunxi: h3/h5: Fix simple-bus unit address format error
ARM: dts: sunxi: h3/h5: Fix i2c2 register addr
This patch remove leading 0 of unit address and so remove
lots of warning when building DT with W=1.
Signed-off-by: Corentin Labbe
Acked-by: Maxime Ripard
---
arch/arm/boot/dts/sun8i-a83t.dtsi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/sun8i-a83t
601 - 700 of 786 matches
Mail list logo
