On Wed, 08 Feb 2017, changbin...@intel.com wrote:
> From: Changbin Du
>
> Prompt user how to quickly jump to the item he/she is interested in.
>
> Signed-off-by: Changbin Du
> Reviewed-by: Jani Nikula
This is assuming too much... but I looked at it now, and it looks good
to me.
Thanks,
Jani.
On Tue, 7 Feb 2017, John Stultz wrote:
> On Tue, Feb 7, 2017 at 3:40 PM, Kees Cook wrote:
> > Currently CONFIG_TIMER_STATS exposes process information across namespaces:
> >
> > kernel/time/timer_list.c print_timer():
> >
> > SEQ_printf(m, ", %s/%d", tmp, timer->start_pid);
> >
> > /proc/t
On Tue, 7 Feb 2017 14:23:23 -0700
Jonathan Corbet wrote:
> On Tue, 7 Feb 2017 21:51:49 +0100
> Jesper Dangaard Brouer wrote:
>
> > I sounds like Daniel (see other email) have bigger plans for what
> > Documentation/BPF/ should contain. E.g. consolidating
> > Documentation/networking/filter.txt
On 08/02/17 00:57, Christopher Covington wrote:
> The Qualcomm Datacenter Technologies QDF2400 family of SoCs contains a
> custom (non-PrimeCell) implementation of the SBSA UART. Occasionally the
> BUSY bit in the Flag Register gets stuck as 1, erratum 44 for both 2432v1
> and 2400v1 SoCs. Checking
Robin Murphy wrote:
Is there a reason anyone would ever want to turn this off? AFAICS you
save a few dozen bytes in return for a kernel image which you know won't
work properly on some hardware. That doesn't seem particularly
worthwhile, and it's not like the PL011 driver isn't already ripe with
On Wed, Feb 08, 2017 at 07:27:29AM -0600, Timur Tabi wrote:
> Robin Murphy wrote:
> >Are we to take it that every SoC now and always with any Kryo or Falkor
> >core which also has an SBSA UART will require this workaround?
>
> No, only Kryo and Falkor V1 based SOCs have this problem. Falkor V2
>
Mark Rutland wrote:
No, only Kryo and Falkor V1 based SOCs have this problem. Falkor V2
will have this fixed. We intend to revert these fixes after Falkor
V1 SOCs are no longer supported.
Supported by whom?
Qualcomm.
Generally, once something's upstreamed we expect it to remain supported
Hi!
v8 -> v9 changes
- dropped the suffix from the compatible string of the i2c-mux-simple
binding (was ,mux-locked or ,parent-locked) and add an optional
mux-locked property instead to change the desired locking behavior
from the default parent-locked
- add description of the difference bet
Everything else is indented with two spaces, so fix the odd one out.
Acked-by: Jonathan Cameron
Signed-off-by: Peter Rosin
---
Documentation/driver-model/devres.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/driver-model/devres.txt
b/Documentation/driver-
Add a new minimalistic subsystem that handles multiplexer controllers.
When multiplexers are used in various places in the kernel, and the
same multiplexer controller can be used for several independent things,
there should be one place to implement support for said multiplexer
controller.
A singl
Allow specifying that a single multiplexer controller can be used to
control several parallel multiplexers, thus enabling sharing of the
multiplexer controller by different consumers.
Add a binding for a first mux controller in the form of a GPIO based mux
controller.
Acked-by: Jonathan Cameron
On Wed, Feb 08 2017 at 2:09:12 pm GMT, Timur Tabi wrote:
> Mark Rutland wrote:
>
>>> No, only Kryo and Falkor V1 based SOCs have this problem. Falkor V2
>>> will have this fixed. We intend to revert these fixes after Falkor
>>> V1 SOCs are no longer supported.
>>
>> Supported by whom?
>
> Qualc
When a multiplexer changes how an iio device behaves (for example
by feeding different signals to an ADC), this driver can be used
to create one virtual iio channel for each multiplexer state.
Depends on the generic multiplexer subsystem.
Cache any ext_info values from the parent iio channel, cre
This is a general purpose i2c mux that uses a multiplexer controlled by
the multiplexer subsystem to do the muxing.
The user can select if the mux is to be mux-locked and parent-locked
as described in Documentation/i2c/i2c-topology.
Acked-by: Jonathan Cameron
Acked-by: Wolfram Sang
Signed-off-b
Describe how a multiplexer can be used to select which signal is fed to
an io-channel.
Acked-by: Jonathan Cameron
Acked-by: Rob Herring
Signed-off-by: Peter Rosin
---
.../bindings/iio/multiplexer/io-channel-mux.txt| 39 ++
MAINTAINERS
Describe how a general purpose multiplexer controller is used to mux an
i2c bus.
Acked-by: Jonathan Cameron
Signed-off-by: Peter Rosin
---
.../devicetree/bindings/i2c/i2c-mux-gpmux.txt | 99 ++
1 file changed, 99 insertions(+)
create mode 100644 Documentation/devicetre
Analog Devices ADG792A/G is a triple 4:1 mux.
Reviewed-by: Jonathan Cameron
Signed-off-by: Peter Rosin
---
drivers/mux/Kconfig | 12
drivers/mux/Makefile | 1 +
drivers/mux/mux-adg792a.c | 140 ++
3 files changed, 153 insertions(+)
On 02/08/2017 09:35 AM, Marc Zyngier wrote:
Interesting. How will you guarantee that nobody will ever want to run a
mainline kernel on this box after a certain date? Self-destruct timer?
;-)
As someone who runs mainline on HW that exceeded its "sell-by" date by a
few decades, I'm genuinely inter
Extend the inkern api with functions for reading and writing ext_info
of iio channels.
Acked-by: Jonathan Cameron
Signed-off-by: Peter Rosin
---
drivers/iio/inkern.c | 60
include/linux/iio/consumer.h | 37 +++
2 files
Analog Devices ADG792A/G is a triple 4:1 mux.
Acked-by: Jonathan Cameron
Signed-off-by: Peter Rosin
---
.../devicetree/bindings/mux/adi,adg792a.txt| 75 ++
1 file changed, 75 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mux/adi,adg792a.txt
dif
On Tue, Feb 07, 2017 at 07:35:16PM -0500, Christopher Covington wrote:
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -480,6 +480,18 @@ config CAVIUM_ERRATUM_27456
>
> If unsure, say Y.
>
> +config QCOM_FALKOR_ERRATUM_1003
> + bool "Falkor E1003: Incorrect translation du
On Tue, Feb 07, 2017 at 08:01:37PM +0100, Daniel Vetter wrote:
> On Tue, Feb 07, 2017 at 06:51:13PM +0100, Thierry Reding wrote:
> > From: Thierry Reding
> >
> > This commit adds a TODO list to the GPU driver developer's guide. The
> > content was taken from the DRMJanitors page on the X.Org wiki
On Wed, Feb 8, 2017 at 2:24 AM, Thomas Gleixner wrote:
> On Tue, 7 Feb 2017, John Stultz wrote:
>> On Tue, Feb 7, 2017 at 3:40 PM, Kees Cook wrote:
>> > Currently CONFIG_TIMER_STATS exposes process information across namespaces:
>> >
>> > kernel/time/timer_list.c print_timer():
>> >
>> >
Currently CONFIG_TIMER_STATS exposes process information across namespaces:
kernel/time/timer_list.c print_timer():
SEQ_printf(m, ", %s/%d", tmp, timer->start_pid);
/proc/timer_list:
#11: <>, hrtimer_wakeup, S:01, do_nanosleep, cron/2570
Given that the tracer can give
On Wed, Feb 8, 2017 at 11:26 AM, Kees Cook wrote:
>
> Given that the tracer can give the same information, this patch entirely
> removes CONFIG_TIMER_STATS.
>
> Suggested-by: Thomas Gleixner
> Signed-off-by: Kees Cook
> Acked-by: John Stultz
Looks good to me. Let's wait for the 4.11 merge wind
The Qualcomm Datacenter Technologies Falkor v1 CPU may allocate TLB entries
using an incorrect ASID when TTBRx_EL1 is being updated. When the erratum
is triggered, page table entries using the new translation table base
address (BADDR) will be allocated into the TLB using the old ASID. All
circumst
On 02/08/2017 11:34 AM, Catalin Marinas wrote:
> On Tue, Feb 07, 2017 at 07:35:16PM -0500, Christopher Covington wrote:
>> --- a/arch/arm64/Kconfig
>> +++ b/arch/arm64/Kconfig
>> @@ -480,6 +480,18 @@ config CAVIUM_ERRATUM_27456
>>
>>If unsure, say Y.
>>
>> +config QCOM_FALKOR_ERRATUM_10
Hi all,
when I `make pdfdocs`, I encountered one error in the following:
---
$ make pdfdocs
HOSTCC scripts/basic/fixdep
HOSTCC scripts/docproc
HOSTCC sc
On Wed, Feb 08, 2017 at 11:54:30AM -0800, Linus Torvalds wrote:
> On Wed, Feb 8, 2017 at 11:26 AM, Kees Cook wrote:
> >
> > Given that the tracer can give the same information, this patch entirely
> > removes CONFIG_TIMER_STATS.
> >
> > Suggested-by: Thomas Gleixner
> > Signed-off-by: Kees
Hi,
On 02/08/2017 08:27 AM, Timur Tabi wrote:
> Robin Murphy wrote:
>> Is there a reason anyone would ever want to turn this off? AFAICS you
>> save a few dozen bytes in return for a kernel image which you know won't
>> work properly on some hardware. That doesn't seem particularly
>> worthwhile,
On 02/07/2017 11:05 PM, Timur Tabi wrote:
> Christopher Covington wrote:
>> The Qualcomm Datacenter Technologies QDF2400 family of SoCs contains a
>> custom (non-PrimeCell) implementation of the SBSA UART. Occasionally the
>> BUSY bit in the Flag Register gets stuck as 1, erratum 44 for both 2432v1
On 02/08/2017 04:22 PM, Christopher Covington wrote:
>> -while (pl011_read(uap, REG_FR) & uap->vendor->fr_busy)
>> +while ((pl011_read(uap, REG_FR) ^ uap->vendor->inv_fr)
>> +& uap->vendor->fr_busy)
>
> I really think the XOR logic needs to be documented wherever
From: Ding Tianhong
Having a command line option to flip the errata handling for a
particular erratum is a little bit unusual, and it's vastly superior to
pass this in the DT. By common consensus, it's best to kill off the
command line parameter.
Signed-off-by: Ding Tianhong
[Mark: split patch,
Signed-off-by: Martin Kepplinger
---
Documentation/input/input.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/input/input.txt b/Documentation/input/input.txt
index 0acfddb..7ebce10 100644
--- a/Documentation/input/input.txt
+++ b/Documentation/input/inpu
Am 08.02.2017 um 22:17 schrieb 慕冬亮 :
> Hi all,
>
> when I `make pdfdocs`, I encountered one error in the following:
>
> ---
> $ make pdfdocs
> HOSTCC scripts/
35 matches
Mail list logo
