This patch adds the required dtsi node to support the Camera
Adaptation Layer (CAL) for the DRA72 family of devices.
- Added CAL entry in dra72x.dtsi.
Signed-off-by: Benoit Parrot
---
arch/arm/boot/dts/dra72x.dtsi | 31 +++
1 file changed, 31 insertions(+)
diff --gi
Add the necessary node and configuration data for the VPE (Video
Processing Engine) hardware block on DRA7x.
The corresponding driver for this entry is in
drivers/media/platform/ti-vpe/vpe.c.
Signed-off-by: Benoit Parrot
---
arch/arm/boot/dts/dra7.dtsi | 26 ++
1 file ch
HWSUP on this domain is only working when VIP1 probes.
If only VIP2 on DRA74x or CAL on DRA72x probes the domain does
not get enabled. This might indicates an issue in the HW Auto
state-machine for this domain.
Work around is to set the CAM domain to use SWSUP only.
Signed-off-by: Benoit Parrot
From: Guenter Roeck
Commit f2ed6b07645e ("ASoC: Make aux_dev more like a generic component")
caused a regression on this driver, since now a kernel oops is seen
when the driver is loaded, or more specifically when
ts3a227e_enable_jack_detect() is called.
That commit changed the probing of aux_de
Device Tree bindings for the Video Processing Engine (VPE) driver.
Signed-off-by: Benoit Parrot
---
Documentation/devicetree/bindings/media/ti-vpe.txt | 41 ++
1 file changed, 41 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/ti-vpe.txt
diff --git
diff --git a/Makefile b/Makefile
index 2a995675d6bf..feab5f5a507c 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 9
-SUBLEVEL = 55
+SUBLEVEL = 56
EXTRAVERSION =
NAME = Roaring Lionus
diff --git a/net/core/filter.c b/net/core/filter.c
index bfeedbbde214..4eb4ce0ae
I'm announcing the release of the 4.9.56 kernel. It fixes a networking
bug in 4.9.55. Don't use 4.9.55, it's busted, sorry about that, I
should have held off and gotten more testing on it, my fault :(
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
On 12/10/17 20:11, Boris Ostrovsky wrote:
> On 10/06/2017 10:32 AM, Josh Poimboeuf wrote:
>> On Thu, Oct 05, 2017 at 04:35:03PM -0400, Boris Ostrovsky wrote:
#ifdef CONFIG_PARAVIRT
+/*
+ * Paravirt alternatives are applied much earlier than normal
alternatives.
+ * They a
On 10/12/17 2:28 PM, Guenter Roeck wrote:
From: Guenter Roeck
Commit f2ed6b07645e ("ASoC: Make aux_dev more like a generic component")
caused a regression on this driver, since now a kernel oops is seen
when the driver is loaded, or more specifically when
ts3a227e_enable_jack_detect() is called
On Thu, Oct 12, 2017 at 08:41:17PM +0200, Daniel Vetter wrote:
> Hi Keith,
>
> On Tue, Oct 10, 2017 at 05:48:27PM -0700, Keith Packard wrote:
> > This allows an application to discover what display resources are
> > available before requesting a lease from the X server.
> >
> > Signed-off-by: Kei
On Thu, Oct 12, 2017 at 10:30:58AM +0100, Mel Gorman wrote:
> During truncate each entry in a pagevec is checked to see if it is an
> exceptional entry and if so, the shadow entry is cleaned up. This is
> potentially expensive as multiple entries for a mapping locks/unlocks the
> tree lock. This
ACPI 6.2 adds the Processor Properties Topology Table (PPTT), which is
used to describe the processor and cache topology. Ideally it is
used to extend/override information provided by the hardware, but
right now ARM64 is entirely dependent on firmware provided tables.
This patch parses the table f
Many modern machines have cluster on die (COD) non-uniformity
as well as the traditional multi-socket architectures. Reusing
the multi-socket or NUMA on die concepts for these (as arm64 does)
breaks down when presented with actual multi-socket/COD machines.
Similar, problems are also visible on som
ACPI 6.2 adds a new table, which describes how processing units
are related to each other in tree like fashion. Caches are
also sprinkled throughout the tree and describe the properties
of the caches in relation to other caches and processing units.
Add the code to parse the cache hierarchy and re
The /sys cache entries should support ACPI/PPTT generated cache
topology information. Lets detect ACPI systems and call
an arch specific cache_setup_acpi() routine to update the hardware
probed cache topology.
For arm64, if ACPI is enabled, determine the max number of cache
levels and populate the
There are a few arm64 specific users (cpufreq, psci, etc) which really
want the cluster rather than the topology_physical_package_id(). Lets
convert those users to topology_cod_id(). That way when we start
differentiating the socket/cluster they will continue to behave correctly.
Signed-off-by: Je
Add ACPI_SIG_PPTT to the table so initrd's can override the
system topology.
Suggested-by: Geoffrey Blake
Signed-off-by: Jeremy Linton
---
drivers/acpi/tables.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/acpi/tables.c b/drivers/acpi/tables.c
index 80ce2a7d224b
Propagate the topology information from the PPTT tree to the
cpu_topology array. We can get the thread id, core_id and
cluster_id by assuming certain levels of the PPTT tree correspond
to those concepts. The package_id is flagged in the tree and can be
found by passing an arbitrary large level to s
Now that we have a PPTT parser, in preparation for its use
on arm64, lets build it.
Signed-off-by: Jeremy Linton
---
arch/arm64/Kconfig | 1 +
drivers/acpi/Makefile | 1 +
drivers/acpi/arm64/Kconfig | 3 +++
3 files changed, 5 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/ar
The kexec/kdump tools need to know where the .bss is so it can be
included in the core dump. This allows vmcore-dmesg to have access to
the dmesg buffers of the crashed kernel as well as allowing the
debugger to examine variables in the bss section.
Add a request for the bss resource in addition
On Thu, Oct 12, 2017 at 02:40:58PM -0500, Pierre-Louis Bossart wrote:
> On 10/12/17 2:28 PM, Guenter Roeck wrote:
> >From: Guenter Roeck
> >
> >Commit f2ed6b07645e ("ASoC: Make aux_dev more like a generic component")
> >caused a regression on this driver, since now a kernel oops is seen
> >when th
hi Arnaldo:
On 9/29/17 2:26 PM, David Ahern wrote:
> Update rbtree files to 4.14.
Haven't seen this one in your perf/core branch. You added the existing
version, so assuming an update goes through you as well.
>
> Changes made after copy:
> - update guards in header files
> - remove rcu referen
On Fri, Oct 06, 2017 at 08:06:05PM -0500, Brijesh Singh wrote:
> The SEV_PEK_CSR command can be used to generate a PEK certificate
> signing request. The command is defined in SEV spec section 5.7.
>
> Cc: Paolo Bonzini
> Cc: "Radim Krčmář"
> Cc: Borislav Petkov
> Cc: Herbert Xu
> Cc: Gary Hoo
On 10/12/2017 03:27 PM, Andrew Cooper wrote:
> On 12/10/17 20:11, Boris Ostrovsky wrote:
>> On 10/06/2017 10:32 AM, Josh Poimboeuf wrote:
>>> On Thu, Oct 05, 2017 at 04:35:03PM -0400, Boris Ostrovsky wrote:
> #ifdef CONFIG_PARAVIRT
> +/*
> + * Paravirt alternatives are applied much ear
On Thu, Oct 12, 2017 at 07:15:59PM +0100, Radu Rendec wrote:
> On Wed, 2017-10-11 at 11:46 -0700, Guenter Roeck wrote:
> > On Wed, Oct 11, 2017 at 06:46:31PM +0100, Radu Rendec wrote:
> > > In a project I'm working on we have a valid use case where we activate
> > > both the i6300esb and softdog wa
(Cc'ing netdev and the author Eric)
On Thu, Oct 12, 2017 at 10:57 AM, Shuah Khan wrote:
> On Thu, Oct 12, 2017 at 11:52 AM, Eric Valette wrote:
>> Hi,
>>
>> Just compiled a fresh 4.9.55, with same .config, same user space than 4.9.54
>> and discovered I had no network because ifup fails because
Hi,
I have a reproducible scenario wherein removing a USB device while
reading /sys/kernel/debug/usb/devices causes a deadlock. This should
not be specific to any USB device. Any USB device removal that causes
a call to debugfs_remove() has inverted lock ordering with respect to
the read() of debu
Currently, when booting a kernel with DMI support on a platform that has
no DMI tables, the following output is emitted into the kernel log:
[0.128818] DMI not present or invalid.
...
[1.306659] dmi: Firmware registration failed.
...
[2.908681] dmi-sysfs: dmi entry is absent.
On 10/12/17 1:21 PM, Borislav Petkov wrote:
.
> Btw, that function returns 0 unconditionally. So you can make it return
> void and...
Will do
>> +if (ret)
>> +goto unlock;
> ... remove this check and initialize ret to 0 at the beginning.
>
Will do
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
In cases where a "drop through" comment was already in place, I replaced
it with a proper "fall through" comment, which is what GCC is expecting
to find.
Signed-off-by: Gustavo A. R. Silv
Hello,
Since linux kernel 4.14-rc1 almost any I/O has a chance to freeze kernel
(no log in /dev/tty0 nor /dev/ttyS0 not netconsole, no ARP answer over
network) on one of my machines. Compiling linux kernel reproduces the
issue reliably so far.
Bisecting between v4.13 and v4.14-rc1 led me to commi
> When a driver supports both dcb and hardware offloaded mqprio, and
> user is running mqprio and dcb tool concurrently, the configuration
> set by each tool may be conflicted with each other because the dcb
(for second 'each') s/each/the
> and mqprio may be using the same hardwere offload compone
In the commit 03de19212ea3 ("mmc: dw_mmc: introduce timer for broken
command transfer over scheme") we tried to calculate the expected
hardware command timeout value. Unfortunately that calculation isn't
quite correct in all cases. It used "bus_hz" but, as far as I can
tell, it's supposed to use
Just like the CTO timeout calculation introduced recently, the DTO
timeout calculation was incorrect. It used "bus_hz" but, as far as I
can tell, it's supposed to use the card clock. Let's account for the
div value, which is documented as 2x the value stored in the register,
or 1 if the register
On 10/12/17 1:28 PM, Borislav Petkov wrote:
> On Fri, Oct 06, 2017 at 08:06:03PM -0500, Brijesh Singh wrote:
>> The SEV_PEK_GEN command is used to generate a new Platform Endorsement
>> Key (PEK). The command is defined in SEV spec section 5.6.
>>
>> Cc: Paolo Bonzini
>> Cc: "Radim Krčmář"
>> C
The recent CTO timer introduced in commit 03de19212ea3 ("mmc: dw_mmc:
introduce timer for broken command transfer over scheme") was causing
observable problems due to race conditions. Previous patches have
fixed those race conditions.
It can be observed that these same race conditions ought to be
On Thu, Oct 12, 2017 at 12:56:57PM -0700, Cong Wang wrote:
> (Cc'ing netdev and the author Eric)
Already fixed, try 4.9.56 :)
thanks,
greg k-h
On 13/10/17 03:17, Gregory CLEMENT wrote:
> Hi Chris,
>
> On mer., oct. 11 2017, Chris Packham
> wrote:
>
>> The watchdog timer interrupt is available internally on the Armada-38x
>> SoCs. Connect it so that we can have the orion_wdt_irq generate debug
>> information when a watchdog timeout
This attempts to instill a bit of paranoia to the code dealing with
the CTO timer. It's believed that this will make the CTO timer more
robust in the case that we're having very long interrupt latencies.
Note that I originally thought that perhaps this patch was being
overly paranoid and wasn't r
Recently we landed 03de19212ea3 ("mmc: dw_mmc: introduce timer for
broken command transfer over scheme"). I found a bunch of problems
with that patch, so this series attempts to solve some of them.
This also fixes the DTO timer in some of the same ways even though I
haven't personally seen proble
When running with the commit 03de19212ea3 ("mmc: dw_mmc: introduce
timer for broken command transfer over scheme") I found this message
in the log:
Unexpected command timeout, state 7
It turns out that we weren't properly cancelling the new CTO timer in
the case that a voltage switch was done.
Hi Eric,
Are you okay with my changes/substitution of your key instantiation-state
patches?
David
---
Here's a collection of fixes for Linux keyrings, mostly thanks to Eric
Biggers, including:
(1) Fix a bunch of places where kernel drivers may access revoked user-type
keys and don't do it
From: Eric Biggers
When the file /proc/fs/fscache/objects (available with
CONFIG_FSCACHE_OBJECT_LIST=y) is opened, we request a user key with
description "fscache:objlist", then access its payload. However, a
revoked key has a NULL payload, and we failed to check for this.
request_key() *does* s
From: Eric Biggers
A key of type "encrypted" references a "master key" which is used to
encrypt and decrypt the encrypted key's payload. However, when we
accessed the master key's payload, we failed to handle the case where
the master key has been revoked, which sets the payload pointer to NULL.
From: Eric Biggers
digsig_verify() requests a user key, then accesses its payload.
However, a revoked key has a NULL payload, and we failed to check for
this. request_key() *does* skip revoked keys, but there is still a
window where the key can be revoked before we acquire its semaphore.
Fix it
From: Eric Biggers
In eCryptfs, we failed to verify that the authentication token keys are
not revoked before dereferencing their payloads, which is problematic
because the payload of a revoked key is NULL. request_key() *does* skip
revoked keys, but there is still a window where the key can be
From: Arnd Bergmann
The recent rework introduced a possible randconfig build failure
when CONFIG_CRYPTO configured to only allow modules:
security/keys/big_key.o: In function `big_key_crypt':
big_key.c:(.text+0x29f): undefined reference to `crypto_aead_setkey'
security/keys/big_key.o: In functio
From: Eric Biggers
As experience has shown, accessing the 'struct key' payload is very
error-prone, since we need to hold the key semaphore and properly
validate everything. Fortunately eCryptfs only does it from one place,
in ecryptfs_verify_auth_tok_from_key() in keystore.c. Therefore, move
t
From: Eric Biggers
When an fscrypt-encrypted file is opened, we request the file's master
key from the keyrings service as a logon key, then access its payload.
However, a revoked key has a NULL payload, and we failed to check for
this. request_key() *does* skip revoked keys, but there is still
From: Eric Biggers
eCryptfs blindly casts the user-supplied key payload to a
'struct ecryptfs_auth_tok' without validating that the payload does, in
fact, have the size of a 'struct ecryptfs_auth_tok'. Fix it.
Fixes: 237fead61998 ("[PATCH] ecryptfs: fs/Makefile and fs/Kconfig")
Reviewed-by: Jam
On Thu, Oct 12, 2017 at 11:01:24PM +0300, Dmitrii Tcvetkov wrote:
> Hello,
>
> Since linux kernel 4.14-rc1 almost any I/O has a chance to freeze kernel
> (no log in /dev/tty0 nor /dev/ttyS0 not netconsole, no ARP answer over
> network) on one of my machines. Compiling linux kernel reproduces the
>
Currently, when passed a key that already exists, add_key() will call the
key's ->update() method if such exists. But this is heavily broken in the
case where the key is uninstantiated because it doesn't call
__key_instantiate_and_link(). Consequently, it doesn't do most of the
things that are su
From: Eric Biggers
Similar to the case for key_validate(), we should load the key ->flags
and ->expiry once atomically in keyring_search_iterator(), since they
can be changed concurrently whenever the key semaphore isn't held.
Signed-off-by: Eric Biggers
Signed-off-by: David Howells
---
secu
From: Lee, Chun-Yi
Fix the wrong index number when checking the existence of second
id in function of finding asymmetric key. The id_1 is the second
id that the index in array must be 1 but not 0.
Fix: 9eb029893(KEYS: Generalise x509_request_asymmetric_key())
Cc: David Howells
Cc: Herbert Xu
From: Lee, Chun-Yi
For finding asymmetric key, the input id_0 and id_1 parameters can
not be NULL at the same time. This patch adds the BUG_ON checking
for id_0 and id_1.
Cc: David Howells
Cc: Herbert Xu
Cc: "David S. Miller"
Signed-off-by: "Lee, Chun-Yi"
Signed-off-by: David Howells
---
From: Eric Biggers
In proc_keys_show(), the key semaphore is not held, so the key ->flags
and ->expiry can be changed concurrently. We therefore should read them
atomically just once. Otherwise /proc/keys may show an inconsistent
state, such a key that is negative ('N') but not instantiated ('I
Consolidate KEY_FLAG_INSTANTIATED, KEY_FLAG_NEGATIVE and the rejection
error into one field such that:
(1) The instantiation state can be modified/read atomically.
(2) The error can be accessed atomically with the state.
(3) The error isn't stored unioned with the payload pointers.
Possibly
From: Eric Biggers
In key_validate(), load the flags and expiry time once atomically, since
these can change concurrently if key_validate() is called without the
key semaphore held. And we don't want to get inconsistent results if a
variable is referenced multiple times. For example, key->expir
> This patchset adds a new hardware offload type in mqprio before adding
> mqprio hardware offload support in hns3 driver.
I think one of the biggest issues in tying this to DCB configuration is the
non-immediate [and possibly non persistent] configuration.
Scenario #1:
User is configuring mqprio
On 10/12/17 1:48 PM, Borislav Petkov wrote:
...
> On Fri, Oct 06, 2017 at 08:06:04PM -0500, Brijesh Singh wrote:
>> The SEV_PDH_GEN command is used to re-generate the Platform
>> Diffie-Hellman (PDH) key. The command is defined in SEV spec section
>> 5.9.
>>
>> Cc: Paolo Bonzini
>> Cc: "Radim Kr
On Thu, Oct 12, 2017 at 03:11:07PM -0500, Brijesh Singh wrote:
> Lets consider this scenario
> 1- platform is in uninit state, we transition it to INIT
> 2- PEK_GEN command failed
> 3- since we have transitioned the platform in INIT state hence we must
> call the shutdown otherwise we will leave t
On Thu, Oct 12, 2017 at 03:21:04PM -0500, Brijesh Singh wrote:
> We need to follow the platform state machine logic defined in SEV spec
> section 5.1.2. The PEK_GEN can not be issued when platform is in WORKING
> state because the command actually re-generate the identity of the
> platform itself (
Batch (2) set of simple document ref fixes.
Tom Saeger (8):
Documentation: fix locking rt-mutex doc refs
Documentation: fix ref to sphinx/kerneldoc.py
Documentation: fix ref to workqueue content
Documentation: fix ref to coccinelle content
Documentation: fix ref to trace stm content
D
Signed-off-by: Tom Saeger
---
Documentation/process/4.Coding.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/process/4.Coding.rst
b/Documentation/process/4.Coding.rst
index 6df19943dd4d..26b106071364 100644
--- a/Documentation/process/4.Coding.rst
+++ b/Docu
Signed-off-by: Tom Saeger
---
.../RCU/Design/Expedited-Grace-Periods/Expedited-Grace-Periods.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/Documentation/RCU/Design/Expedited-Grace-Periods/Expedited-Grace-Periods.html
b/Documentation/RCU/Design/Expedited-Grace-Peri
Signed-off-by: Tom Saeger
---
Documentation/trace/intel_th.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/trace/intel_th.txt b/Documentation/trace/intel_th.txt
index f92070e7dde0..7a57165c2492 100644
--- a/Documentation/trace/intel_th.txt
+++ b/Documentation
Signed-off-by: Tom Saeger
---
Documentation/doc-guide/kernel-doc.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/doc-guide/kernel-doc.rst
b/Documentation/doc-guide/kernel-doc.rst
index b24854b5d6be..0268335414ce 100644
--- a/Documentation/doc-guide/kernel-do
Signed-off-by: Tom Saeger
---
Documentation/power/interface.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/power/interface.txt
b/Documentation/power/interface.txt
index 7dc75f48e8bd..27df7f98668a 100644
--- a/Documentation/power/interface.txt
+++ b/Document
Signed-off-by: Tom Saeger
---
Documentation/ABI/obsolete/sysfs-gpio | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/ABI/obsolete/sysfs-gpio
b/Documentation/ABI/obsolete/sysfs-gpio
index 867c1fab20e2..32513dc2eec9 100644
--- a/Documentation/ABI/obsolete/sysfs-gpi
Signed-off-by: Tom Saeger
---
Documentation/locking/rt-mutex-design.txt | 2 +-
Documentation/pi-futex.txt| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/locking/rt-mutex-design.txt
b/Documentation/locking/rt-mutex-design.txt
index 6c6e8c2410d
Make refs to selftests files valid including:
- watchdog-test.c
- dnotify_test.c
Signed-off-by: Tom Saeger
---
Documentation/filesystems/dnotify.txt| 2 +-
Documentation/watchdog/hpwdt.txt | 2 +-
Documentation/watchdog/pcwd-watchdog.txt | 2 +-
3 files changed, 3 insertions(+),
Looked at all the patches. Looks good to me.
Reviewed-by: Babu Moger
On 10/11/2017 1:50 PM, Vijay Kumar wrote:
SPARC provides lzcnt instruction (with VIS3) which can be used to
optimize fls, __fls and fls64 functions. For the systems that supports
lzcnt instruction, we now do boot time patchin
> On Oct 12, 2017, at 7:44 AM, Khalid Aziz wrote:
>
> Hi Anthony,
>
> Please quote only the relevant parts of the patch with comments. That makes
> it much easier to find the comments.
Okay.
>
> On 10/06/2017 04:12 PM, Anthony Yznaga wrote:
>>> On Sep 25, 2017, at 9:49 AM, Khalid Aziz wrot
On 10/12/17 3:21 PM, Borislav Petkov wrote:
> On Thu, Oct 12, 2017 at 03:11:07PM -0500, Brijesh Singh wrote:
>> Lets consider this scenario
>> 1- platform is in uninit state, we transition it to INIT
>> 2- PEK_GEN command failed
>> 3- since we have transitioned the platform in INIT state hence w
+Cc: Hans
On Wed, Oct 11, 2017 at 12:30 PM, Colin King wrote:
> From: Colin Ian King
>
> The functions cht_int33fe_check_for_max17047 and cht_int33fe_find_max17047
> are local to the source and do not need to be in global scope, so make
> them static.
>
> Cleans up sparse warnings:
> symbol 'cht
[ Adding LKML on CC so that others can find this. ]
On Wed, Oct 11, 2017 at 12:21:39PM +0800, Wang YanQing wrote:
> Hi, Paul McKenney.
>
> I have received many machine-stopped-respone reports, after reboot and
> inspect message, all of them show RCU stalled, but I can't figure out
> how to fix it
On Thu, Oct 12, 2017 at 8:50 AM, Pankaj Gupta wrote:
> This patch moves common code to base header files
> so that it can be used for both ACPI pmem and VIRTIO pmem
> drivers. More common code needs to be moved out in future
> based on functionality required for virtio_pmem driver and
> coupl
Latest llvm update excludes assembly instructions.
As a result __ASM_SYSREGS_H define is not required.
-target switch includes appropriate target specific files.
Tested on x86 and arm64 with llvm with git revision
commit df6ca162269f9d756f8742bf4b658dcf690e3eb5
Author: Yonghong Song
Date: Thu S
On Thu, Oct 12, 2017 at 10:24 PM, Tom Saeger wrote:
> Signed-off-by: Tom Saeger
> ---
> Documentation/power/interface.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/power/interface.txt
> b/Documentation/power/interface.txt
> index 7dc75f48e8bd..27df7f
On Thursday 12 October 2017 12:13:11 Karel Zak wrote:
> On Thu, Oct 12, 2017 at 11:21:13AM +0200, Pali Rohár wrote:
> > > The best for me is to keep blkid output backwardly compatible as much
> > > as possible :-)
> >
> > Backward compatibility is a good reason. But what with situation when
> > in
On Thu, Oct 12, 2017 at 8:50 AM, Pankaj Gupta wrote:
> This patch adds virtio-pmem driver for KVM guest.
> Guest reads the persistent memory range information
> over virtio bus from Qemu and reserves the range
> as persistent memory. Guest also allocates a block
> device corresponding to
On Mon, Oct 9, 2017 at 3:26 PM, wrote:
> From: Martin Blumenstingl
>
> The current Amlogic Meson eFuse driver only supports the 64-bit SoCs
> (GXBB and newer). Older SoCs cannot be supported by the same driver
> because they do not use the meson secure monitor firmware to access the
> hardware.
On Mon, Oct 9, 2017 at 3:26 PM, wrote:
> From: Martin Blumenstingl
>
> Amlogic Meson6, Meson8 and Meson8b SoCs have an efuse which contains
> calibration data from the factory (for the internal temperature sensor
> and some CVBS connector settings). Some manufacturers also store the MAC
> addres
On Thu, 12 Oct 2017, Thomas Gleixner wrote:
On Thu, 12 Oct 2017, Daniel Lezcano wrote:
On 11/10/2017 22:48, David Kozub wrote:
[ ... ]
+ disable_timer(timer);
+ cs5535_mfgpt_write(timer, MFGPT_REG_COUNTER, 0);
+
/* Set up the IRQ on the MFGPT side */
if (cs5535_mf
Hi,
This patch series should mostly be self-descriptive, but it's motivated by the
fact that I've found differing requirements from PCIe endpoint makers regarding
the state of PERST# when in system suspend (S3). Additionally, some existing
boards are not especially well suited for holding PERST# l
The patch is self-descriptive. I've found that we may need
platform-specific behavior for the PERST# signal in system suspend,
depending on the type of PCIe endpoints are attached.
Signed-off-by: Brian Norris
---
Documentation/devicetree/bindings/pci/pci.txt | 11 +++
1 file changed, 11
This helper can be used by drivers to determine the expected PERST#
behavior when in low-power system suspend (e.g., S3). I've found the
expected behavior to vary across a few different endpoint
implementations.
Signed-off-by: Brian Norris
---
drivers/of/of_pci.c| 25
I've found that different endpoints and board configurations have
required different behavior from the PCIe Reset (PERST#) signal when in
low-power system suspend (e.g., S3). Use the new of_pci helper to
request this state and assert (active low) PERST# before suspending.
Note that we reinitialize
Daniel Vetter writes:
> So given the huge possibilities of abuse, do we really, really need all
> this, and is there not any way to create a bit of protocol to pass the
> relevant data from X to clients? From your presentation is sounded like
> current xrandr is (almost) there ...
Yeah, it's the
On Fri, Oct 6, 2017 at 6:51 AM, Sudeep Holla wrote:
>
>
> On 06/10/17 14:47, Jassi Brar wrote:
>> On Fri, Oct 6, 2017 at 7:02 PM, Sudeep Holla wrote:
[..]
>>> Again that's not the point, doorbell is more common feature and that can
>>> be supported. As SCMI expects doorbell feature in the specifi
On Thu, Oct 12, 2017 at 04:01:48PM -0400, Tyler Hall wrote:
> Hi,
>
> I have a reproducible scenario wherein removing a USB device while
> reading /sys/kernel/debug/usb/devices causes a deadlock. This should
> not be specific to any USB device. Any USB device removal that causes
> a call to debugf
Daniel Vetter writes:
> One more that came up on irc after discussion why this is needed: The
> userspace side using this won't work on split gpus where the render node
> has 0 displays, and hence where you really need to query the compositor
> anyway.
Agreed -- using the X connection to get the
On 10/12/17 9:08 AM, Borislav Petkov wrote:
...
> Well, if you're going to have a global var, why not pull up the misc
> device instead?
>
> And mind you, I've moved out this assignments:
>
> + psp->sev_misc = psp_misc_dev;
> + init_waitqueue_head(&psp->sev_int_queue);
> + dev_
Hi,
While using livepatch, I found that when doing cumulative patches, if a patched
function is completed reverted by a subsequent patch (back to its original
state)
livepatch does not revert the funtion to its original state. Specifically, if
patch A introduces a change to function 1, and patch
In preparation for __klp_enable_patch() to call a number of 'static'
functions, in a subsequent patch, move them earlier in core.c. This patch
should be a nop from a functional pov.
Signed-off-by: Jason Baron
Cc: Josh Poimboeuf
Cc: Jessica Yu
Cc: Jiri Kosina
Cc: Miroslav Benes
Cc: Petr Mladek
Sometimes we would like to revert a particular fix. This is currently
This is not easy because we want to keep all other fixes active and we
could revert only the last applied patch.
One solution would be to apply new patch that implemented all
the reverted functions like in the original code. It
Currently klp_patch contains a pointer to a statically allocated array of
struct klp_object and struct klp_objects contains a pointer to a statically
allocated array of klp_func. In order to allow for the dynamic allocation
of objects and functions, link klp_patch, klp_object, and klp_func together
On 2017-10-12 16:42, Guenter Roeck wrote:
> On 10/12/2017 07:32 AM, Peter Rosin wrote:
>> On 2017-10-12 13:35, Peter Rosin wrote:
>>> Hi!
>>>
>>> I have encountered an "interesting" bug. It silently corrupts data
>>> and is generally nasty...
>>>
>>> On an I2C bus, driven by the at91 driver and DMA
On Wed, Oct 4, 2017 at 4:32 AM, Sudeep Holla wrote:
>
>
> On 04/10/17 12:24, Arnd Bergmann wrote:
>> On Thu, Sep 28, 2017 at 3:11 PM, Sudeep Holla wrote:
>>> Some of the mailbox controller expects controller specific data in order
>>> to implement simple doorbell mechanism as expected by SCMI spe
Hi,
On 22/09/2017 at 11:33:15 +0800, sean.w...@mediatek.com wrote:
> diff --git a/drivers/rtc/rtc-mediatek.c b/drivers/rtc/rtc-mediatek.c
I'm pretty sure this should be named rtc-mt7622.c instead of
rtc-mediatek.c, exactly for the same reason you have patch 3/4.
> +static void mtk_w32(struct mtk
601 - 700 of 970 matches
Mail list logo
