On 16 October 2017 at 03:46, Chaotian Jing wrote:
> devicetree bindings has been updated to support multi-platforms,
> so that each platform has its owns compatible name.
> And, this compatible name may used in driver to distinguish with
> other platform.
>
> Signed-off-by: Chaotian Jing
On Wed, Oct 25, 2017 at 4:16 PM, Bjorn Helgaas wrote:
> On Wed, Oct 25, 2017 at 11:40:47AM -0700, Scott Branden wrote:
>> Hi Bjorn,
>>
>>
>> On 17-10-25 10:23 AM, Bjorn Helgaas wrote:
>> >[+cc Ray, Scott, Jon]
>> >
>> >On Wed, Oct 25, 2017 at 11:28:07AM -0400, Jim Quinlan wrote:
>> >>On Tue, Oct
On Tue, Oct 24, 2017 at 3:07 PM, Greg Kroah-Hartman
wrote:
> 4.13-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Arnd Bergmann
>
> commit 785545c8982604fe3ba79d16409e83993be77d5e upstream.
>
>
On Tue, Oct 24, 2017 at 3:07 PM, Greg Kroah-Hartman
wrote:
> 4.13-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Arnd Bergmann
>
> commit 785545c8982604fe3ba79d16409e83993be77d5e upstream.
>
> The last cleanup introduced two harmless
On rk3288-veyron devices on Chrome OS it was found that plugging in an
Arduino-based USB device could cause the system to lockup, especially
if the CPU Frequency was at one of the slower operating points (like
100 MHz / 200 MHz).
Upon tracing, I found that the following was happening:
* The USB
On rk3288-veyron devices on Chrome OS it was found that plugging in an
Arduino-based USB device could cause the system to lockup, especially
if the CPU Frequency was at one of the slower operating points (like
100 MHz / 200 MHz).
Upon tracing, I found that the following was happening:
* The USB
Hi Josh,
Here is one more warning:
[5.852094] WARNING: can't dereference iret registers at b6ce01b7ffe0
for ip entry_SYSCALL_64_fastpath+0xa/0xc2
[avagin@laptop linux]$ git describe tip/auto-latest
v4.14-rc6-471-g376214a8543d
On Fri, Oct 20, 2017 at 11:21:33AM -0500, Josh Poimboeuf
Hi Josh,
Here is one more warning:
[5.852094] WARNING: can't dereference iret registers at b6ce01b7ffe0
for ip entry_SYSCALL_64_fastpath+0xa/0xc2
[avagin@laptop linux]$ git describe tip/auto-latest
v4.14-rc6-471-g376214a8543d
On Fri, Oct 20, 2017 at 11:21:33AM -0500, Josh Poimboeuf
> On Oct 25, 2017, at 10:39, Dan Williams wrote:
>
> On Wed, 2017-10-25 at 17:12 +, Perez-Gonzalez, Inaky wrote:
>>> On Tue, 2017-10-24 at 21:00 +, Perez-Gonzalez, Inaky wrote:
> ping any comments on this?
None from me; I don't have access to this HW
> On Oct 25, 2017, at 10:39, Dan Williams wrote:
>
> On Wed, 2017-10-25 at 17:12 +, Perez-Gonzalez, Inaky wrote:
>>> On Tue, 2017-10-24 at 21:00 +, Perez-Gonzalez, Inaky wrote:
> ping any comments on this?
None from me; I don't have access to this HW anymore, so I can't
On Tue, Oct 24, 2017 at 9:46 PM, Matthias Kaehlcke wrote:
> El Mon, Oct 09, 2017 at 12:41:53PM -0700 Matthias Kaehlcke ha dit:
>> + u8 cmd_payload[];
>> } __packed *buf;
>> struct i2400m_bootrom_header ack;
>
> ping
>
> any comments on this?
What for?
On Tue, Oct 24, 2017 at 9:46 PM, Matthias Kaehlcke wrote:
> El Mon, Oct 09, 2017 at 12:41:53PM -0700 Matthias Kaehlcke ha dit:
>> + u8 cmd_payload[];
>> } __packed *buf;
>> struct i2400m_bootrom_header ack;
>
> ping
>
> any comments on this?
What for? The patch is
On Tue, Sep 12, 2017 at 1:49 AM, SZ Lin wrote:
> Add QSPI node support, and this function is disabled by default
> This setting could be overwritten in board-level definitions
Adding Shawn Guo.
>
> Signed-off-by: SZ Lin
Acked-by: Li Yang
On Tue, Sep 12, 2017 at 1:49 AM, SZ Lin wrote:
> Add QSPI node support, and this function is disabled by default
> This setting could be overwritten in board-level definitions
Adding Shawn Guo.
>
> Signed-off-by: SZ Lin
Acked-by: Li Yang
> ---
> arch/arm/boot/dts/ls1021a.dtsi | 14
On 10/23/2017 10:44 PM, Fengguang Wu wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> commit ce56a86e2ade45d052b3228cdfebe913a1ae7381
> Author: Craig Bergstrom
On 10/23/2017 10:44 PM, Fengguang Wu wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> commit ce56a86e2ade45d052b3228cdfebe913a1ae7381
> Author: Craig Bergstrom
>
Add a test that exercises DAX's new MAP_SYNC flag.
This test creates a file and writes to it via an mmap(), but never syncs
via fsync/msync. This process is tracked via dm-log-writes, then replayed.
If MAP_SYNC is working the dm-log-writes replay will show the test file
with 1MiB of on-media
Add a test that exercises DAX's new MAP_SYNC flag.
This test creates a file and writes to it via an mmap(), but never syncs
via fsync/msync. This process is tracked via dm-log-writes, then replayed.
If MAP_SYNC is working the dm-log-writes replay will show the test file
with 1MiB of on-media
Linus,
please pull sound fixes for v4.14-rc7 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-4.14-rc7
The topmost commit is f265788c336979090ac80b9ae173aa817c4fe40d
sound fixes for 4.14-rc7
Linus,
please pull sound fixes for v4.14-rc7 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-4.14-rc7
The topmost commit is f265788c336979090ac80b9ae173aa817c4fe40d
sound fixes for 4.14-rc7
Hi!
...hardware should be identical. 3.5.3-nemo kernel seems to work on
both. 4.13-rc2 with display and clock patches boots on phone "S", but
does not on phone "P"; nothing nothing is received on serial port.
There is some difference in the bootloaders: S's bootloader provides
lots of debug
Hi!
...hardware should be identical. 3.5.3-nemo kernel seems to work on
both. 4.13-rc2 with display and clock patches boots on phone "S", but
does not on phone "P"; nothing nothing is received on serial port.
There is some difference in the bootloaders: S's bootloader provides
lots of debug
On Wed, 25 Oct 2017 19:32:53 +0200,
Randy Dunlap wrote:
>
> On 10/25/17 05:45, Max Staudt wrote:
>
> > diff --git a/drivers/video/console/Kconfig b/drivers/video/console/Kconfig
> > index a6617c07229a..c3496c5ac2bb 100644
> > --- a/drivers/video/console/Kconfig
> > +++
On Wed, 25 Oct 2017 19:32:53 +0200,
Randy Dunlap wrote:
>
> On 10/25/17 05:45, Max Staudt wrote:
>
> > diff --git a/drivers/video/console/Kconfig b/drivers/video/console/Kconfig
> > index a6617c07229a..c3496c5ac2bb 100644
> > --- a/drivers/video/console/Kconfig
> > +++
On Wed Oct 25 17, Jarkko Sakkinen wrote:
On Wed, Oct 25, 2017 at 07:17:17AM -0700, Matthew Garrett wrote:
On Wed, Oct 25, 2017 at 6:44 AM, Jarkko Sakkinen
wrote:
> I'm implementing a fix for CVE-2017-15361 that simply blacklists
> vulnerable FW versions. I
On Wed Oct 25 17, Jarkko Sakkinen wrote:
On Wed, Oct 25, 2017 at 07:17:17AM -0700, Matthew Garrett wrote:
On Wed, Oct 25, 2017 at 6:44 AM, Jarkko Sakkinen
wrote:
> I'm implementing a fix for CVE-2017-15361 that simply blacklists
> vulnerable FW versions. I think this is the only responsible
On Wed, Oct 25, 2017 at 10:07:46PM +0200, Jarkko Sakkinen wrote:
> The id has a nice feature that it is unique for one boot cycle you can
> even try to get a chip that has been deleted. It has the most stable
> properties in the long run.
It isn't unique, we can re-use ids them via idr_alloc().
On Wed, Oct 25, 2017 at 10:07:46PM +0200, Jarkko Sakkinen wrote:
> The id has a nice feature that it is unique for one boot cycle you can
> even try to get a chip that has been deleted. It has the most stable
> properties in the long run.
It isn't unique, we can re-use ids them via idr_alloc().
From: Markus Elfring
Date: Wed, 25 Oct 2017 22:00:42 +0200
Adjust jump targets so that a call of the function "mutex_unlock" is stored
only once in a case branch of this function implementation.
Replace two calls by goto statements.
This issue was detected by
From: Markus Elfring
Date: Wed, 25 Oct 2017 22:00:42 +0200
Adjust jump targets so that a call of the function "mutex_unlock" is stored
only once in a case branch of this function implementation.
Replace two calls by goto statements.
This issue was detected by using the Coccinelle software.
From: Markus Elfring
Date: Wed, 25 Oct 2017 21:36:03 +0200
* Add a jump target so that a specific error message is stored only once
at the end of this function implementation.
* Replace two calls of the function "dev_err" by goto statements.
* Adjust condition
From: Markus Elfring
Date: Wed, 25 Oct 2017 21:36:03 +0200
* Add a jump target so that a specific error message is stored only once
at the end of this function implementation.
* Replace two calls of the function "dev_err" by goto statements.
* Adjust condition checks.
This issue was
On Wed, Oct 25, 2017 at 11:40:47AM -0700, Scott Branden wrote:
> Hi Bjorn,
>
>
> On 17-10-25 10:23 AM, Bjorn Helgaas wrote:
> >[+cc Ray, Scott, Jon]
> >
> >On Wed, Oct 25, 2017 at 11:28:07AM -0400, Jim Quinlan wrote:
> >>On Tue, Oct 24, 2017 at 2:57 PM, Florian Fainelli
>
On Wed, Oct 25, 2017 at 11:40:47AM -0700, Scott Branden wrote:
> Hi Bjorn,
>
>
> On 17-10-25 10:23 AM, Bjorn Helgaas wrote:
> >[+cc Ray, Scott, Jon]
> >
> >On Wed, Oct 25, 2017 at 11:28:07AM -0400, Jim Quinlan wrote:
> >>On Tue, Oct 24, 2017 at 2:57 PM, Florian Fainelli
> >>wrote:
> >>>Hi Jim,
From: Markus Elfring
Date: Wed, 25 Oct 2017 22:10:12 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Use common error handling code in stk8ba50_probe()
Improve unlocking of a mutex in
From: Markus Elfring
Date: Wed, 25 Oct 2017 22:10:12 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Use common error handling code in stk8ba50_probe()
Improve unlocking of a mutex in stk8ba50_read_raw()
On Mon, 23 Oct 2017, Michal Hocko wrote:
> On Sun 22-10-17 17:24:51, David Rientjes wrote:
> > On Thu, 19 Oct 2017, Johannes Weiner wrote:
> >
> > > David would have really liked for this patchset to include knobs to
> > > influence how the algorithm picks cgroup victims. The rest of us
> > >
On Mon, 23 Oct 2017, Michal Hocko wrote:
> On Sun 22-10-17 17:24:51, David Rientjes wrote:
> > On Thu, 19 Oct 2017, Johannes Weiner wrote:
> >
> > > David would have really liked for this patchset to include knobs to
> > > influence how the algorithm picks cgroup victims. The rest of us
> > >
On Tue, Oct 24, 2017 at 11:49 AM, Rafael J. Wysocki wrote:
> On Tuesday, October 24, 2017 7:54:09 AM CEST Ramesh Thomas wrote:
>> On 2017-10-20 at 13:27:34 +0200, Rafael J. Wysocki wrote:
>> > static ssize_t pm_qos_resume_latency_store(struct device *dev,
>> > @@ -228,11
On Wed, Oct 25, 2017 at 01:46:33PM -0600, Jason Gunthorpe wrote:
> > struct tpm_chip *tpm_chip_find_get(u64 id)
> > {
> > struct tpm_chup *chip;
> > struct tpm_chip *res = NULL;
> > int chip_num = 0;
> > int chip_prev;
> >
> > mutex_lock(_lock);
> >
> > do {
> >
On Tue, Oct 24, 2017 at 11:49 AM, Rafael J. Wysocki wrote:
> On Tuesday, October 24, 2017 7:54:09 AM CEST Ramesh Thomas wrote:
>> On 2017-10-20 at 13:27:34 +0200, Rafael J. Wysocki wrote:
>> > static ssize_t pm_qos_resume_latency_store(struct device *dev,
>> > @@ -228,11 +235,19 @@ static
On Wed, Oct 25, 2017 at 01:46:33PM -0600, Jason Gunthorpe wrote:
> > struct tpm_chip *tpm_chip_find_get(u64 id)
> > {
> > struct tpm_chup *chip;
> > struct tpm_chip *res = NULL;
> > int chip_num = 0;
> > int chip_prev;
> >
> > mutex_lock(_lock);
> >
> > do {
> >
On Wed, Oct 25, 2017 at 10:00:30PM +0200, Jarkko Sakkinen wrote:
> A minor tidbit: could the tpm_ prefix removed from those fields?
Yes, in v2
I will send v2 when you land your rework patch as this will depend on it.
Jason
On Wed, Oct 25, 2017 at 10:00:30PM +0200, Jarkko Sakkinen wrote:
> A minor tidbit: could the tpm_ prefix removed from those fields?
Yes, in v2
I will send v2 when you land your rework patch as this will depend on it.
Jason
On Wed, Oct 25, 2017 at 01:37:07PM -0600, Jason Gunthorpe wrote:
> On Wed, Oct 25, 2017 at 08:58:17PM +0200, Jarkko Sakkinen wrote:
> > On Wed, Oct 25, 2017 at 08:15:09PM +0530, PrasannaKumar Muralidharan wrote:
> > > > + if (!IS_ENABLED(CONFIG_HW_RANDOM_TPM))
> > > > + return
On Wed, Oct 25, 2017 at 01:37:07PM -0600, Jason Gunthorpe wrote:
> On Wed, Oct 25, 2017 at 08:58:17PM +0200, Jarkko Sakkinen wrote:
> > On Wed, Oct 25, 2017 at 08:15:09PM +0530, PrasannaKumar Muralidharan wrote:
> > > > + if (!IS_ENABLED(CONFIG_HW_RANDOM_TPM))
> > > > + return
On 10/23/2017 05:12 PM, Guenter Roeck wrote:
On Mon, Oct 23, 2017 at 10:23:02AM -0500, Eddie James wrote:
On 10/21/2017 11:10 AM, Guenter Roeck wrote:
On Thu, Oct 19, 2017 at 03:57:08PM -0500, eaja...@linux.vnet.ibm.com wrote:
From: "Edward A. James"
The MFR_ID and
On 10/23/2017 05:12 PM, Guenter Roeck wrote:
On Mon, Oct 23, 2017 at 10:23:02AM -0500, Eddie James wrote:
On 10/21/2017 11:10 AM, Guenter Roeck wrote:
On Thu, Oct 19, 2017 at 03:57:08PM -0500, eaja...@linux.vnet.ibm.com wrote:
From: "Edward A. James"
The MFR_ID and MFR_MODEL, which are
From: "Edward A. James"
For devices with word data registers, the pmbus core may call read/write
word data functions with a page value of -1, in order to perform the
operation without setting the page. However, the read/write word data
functions accept only unsigned 8-bit
From: "Edward A. James"
For devices with word data registers, the pmbus core may call read/write
word data functions with a page value of -1, in order to perform the
operation without setting the page. However, the read/write word data
functions accept only unsigned 8-bit page numbers, resulting
> struct tpm_chip *tpm_chip_find_get(u64 id)
> {
> struct tpm_chup *chip;
> struct tpm_chip *res = NULL;
> int chip_num = 0;
> int chip_prev;
>
> mutex_lock(_lock);
>
> do {
> chip_prev = chip_num;
>
> chip =
> struct tpm_chip *tpm_chip_find_get(u64 id)
> {
> struct tpm_chup *chip;
> struct tpm_chip *res = NULL;
> int chip_num = 0;
> int chip_prev;
>
> mutex_lock(_lock);
>
> do {
> chip_prev = chip_num;
>
> chip =
> Now, what I need in the kernel is to _selectively_ suspend devices
> that are not needed in the "backup/emergency" mode.
Which means you need to get the applications using them to die - or you
could rewrite the driver top to bottom to have locking sufficient to
ensure that your power management
> Now, what I need in the kernel is to _selectively_ suspend devices
> that are not needed in the "backup/emergency" mode.
Which means you need to get the applications using them to die - or you
could rewrite the driver top to bottom to have locking sufficient to
ensure that your power management
On Wed, Oct 25, 2017 at 08:58:17PM +0200, Jarkko Sakkinen wrote:
> On Wed, Oct 25, 2017 at 08:15:09PM +0530, PrasannaKumar Muralidharan wrote:
> > > + if (!IS_ENABLED(CONFIG_HW_RANDOM_TPM))
> > > + return 0;
> >
> > Can #ifndef CONFIG_HW_RANDOM_TPM be used instead? That way an
On Wed, Oct 25, 2017 at 08:58:17PM +0200, Jarkko Sakkinen wrote:
> On Wed, Oct 25, 2017 at 08:15:09PM +0530, PrasannaKumar Muralidharan wrote:
> > > + if (!IS_ENABLED(CONFIG_HW_RANDOM_TPM))
> > > + return 0;
> >
> > Can #ifndef CONFIG_HW_RANDOM_TPM be used instead? That way an
On Wed, Oct 25, 2017 at 08:40:26PM +0530, PrasannaKumar Muralidharan wrote:
> > -struct tpm_chip *tpm_chip_find_get(int chip_num)
> > +struct tpm_chip *tpm_chip_find_get(struct tpm_chip *chip)
> > {
> > - struct tpm_chip *chip, *res = NULL;
> > + struct tpm_chip *res = NULL;
> > +
On Wed, Oct 25, 2017 at 08:40:26PM +0530, PrasannaKumar Muralidharan wrote:
> > -struct tpm_chip *tpm_chip_find_get(int chip_num)
> > +struct tpm_chip *tpm_chip_find_get(struct tpm_chip *chip)
> > {
> > - struct tpm_chip *chip, *res = NULL;
> > + struct tpm_chip *res = NULL;
> > +
On 10/25/2017 07:04 AM, Jose Abreu wrote:
> This adds the documentation for TSN feature EST and FP.
>
> Signed-off-by: Jose Abreu
> Cc: David S. Miller
> Cc: Joao Pinto
> Cc: Giuseppe Cavallaro
> Cc:
On 10/25/2017 07:04 AM, Jose Abreu wrote:
> This adds the documentation for TSN feature EST and FP.
>
> Signed-off-by: Jose Abreu
> Cc: David S. Miller
> Cc: Joao Pinto
> Cc: Giuseppe Cavallaro
> Cc: Alexandre Torgue
> Cc: Rob Herring
> ---
>
On Tue, 2017-10-24 at 03:28 -0700, Kees Cook wrote:
> In preparation for unconditionally passing the struct timer_list
> pointer to
> all timer callbacks, switch to using the new timer_setup() and
> from_timer()
> to pass the timer pointer explicitly.
>
> Cc: Moni Shoua
> Cc:
On Tue, 2017-10-24 at 03:28 -0700, Kees Cook wrote:
> In preparation for unconditionally passing the struct timer_list
> pointer to
> all timer callbacks, switch to using the new timer_setup() and
> from_timer()
> to pass the timer pointer explicitly.
>
> Cc: Moni Shoua
> Cc: Doug Ledford
> Cc:
> When tty_open() is opening a serial tty at the first time, after
> alloc_tty_struct() is called, before tty->ops->open() is finished.
That's kind of unavoidable.
> Serial driever like pl011 on ARM is ready to setup kworker threads
> to receive data with flush_to_ldisc(). Serial input at this
> When tty_open() is opening a serial tty at the first time, after
> alloc_tty_struct() is called, before tty->ops->open() is finished.
That's kind of unavoidable.
> Serial driever like pl011 on ARM is ready to setup kworker threads
> to receive data with flush_to_ldisc(). Serial input at this
On Wed, Oct 25, 2017 at 08:21:16PM +0530, PrasannaKumar Muralidharan wrote:
> >> > 2. Moving struct tpm_rng to the TPM client is architecturally
> >> >uacceptable.
> >>
> >> As there was no response to the patch there is no way to know whether
> >> it is acceptable or not.
> >
> > I like the
On Wed, Oct 25, 2017 at 08:21:16PM +0530, PrasannaKumar Muralidharan wrote:
> >> > 2. Moving struct tpm_rng to the TPM client is architecturally
> >> >uacceptable.
> >>
> >> As there was no response to the patch there is no way to know whether
> >> it is acceptable or not.
> >
> > I like the
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/pci-quirks.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/pci-quirks.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/host/pci-quirks.c
Add a driver for RAVE Supervisory Processor, an MCU implementing
various bits of housekeeping functionality (watchdoging, backlight
control, LED control, etc) on RAVE family of products by Zodiac
Inflight Innovations.
This driver implementes core MFD/serdev device as well as
communication
Add a driver for RAVE Supervisory Processor, an MCU implementing
various bits of housekeeping functionality (watchdoging, backlight
control, LED control, etc) on RAVE family of products by Zodiac
Inflight Innovations.
This driver implementes core MFD/serdev device as well as
communication
Add Device Tree bindings for RAVE SP watchdog drvier - an MFD cell of
parent RAVE SP driver (documented in
Documentation/devicetree/bindings/mfd/zii,rave-sp.txt).
Cc: linux-kernel@vger.kernel.org
Cc: devicet...@vger.kernel.org
Cc: linux-watch...@vger.kernel.org
Cc: cphe...@gmail.com
Cc: Lucas
Add Device Tree bindings for RAVE SP watchdog drvier - an MFD cell of
parent RAVE SP driver (documented in
Documentation/devicetree/bindings/mfd/zii,rave-sp.txt).
Cc: linux-kernel@vger.kernel.org
Cc: devicet...@vger.kernel.org
Cc: linux-watch...@vger.kernel.org
Cc: cphe...@gmail.com
Cc: Lucas
Greg,
Quoting "Gustavo A. R. Silva" :
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/isp1362-hcd.c | 1 +
1 file changed, 1
Greg,
Quoting "Gustavo A. R. Silva" :
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/isp1362-hcd.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Using devres infrastructure it is possible to write a serdev driver
that doesn't have any code that needs to be called as a part of
.remove. Add code to make .remove optional.
Cc: linux-kernel@vger.kernel.org
Cc: linux-ser...@vger.kernel.org
Cc: Rob Herring
Cc: cphe...@gmail.com
Hi everyone,
This patch series is v9 of the driver for supervisory processor found
on RAVE series of devices from ZII. Supervisory processor is a PIC
microcontroller connected to various electrical subsystems on RAVE
devices whose firmware implements protocol to command/qery them.
NOTE:
* This
Using devres infrastructure it is possible to write a serdev driver
that doesn't have any code that needs to be called as a part of
.remove. Add code to make .remove optional.
Cc: linux-kernel@vger.kernel.org
Cc: linux-ser...@vger.kernel.org
Cc: Rob Herring
Cc: cphe...@gmail.com
Cc: Guenter
Hi everyone,
This patch series is v9 of the driver for supervisory processor found
on RAVE series of devices from ZII. Supervisory processor is a PIC
microcontroller connected to various electrical subsystems on RAVE
devices whose firmware implements protocol to command/qery them.
NOTE:
* This
Add code implementing managed version of serdev_device_open() for
serdev device drivers that "open" the device during driver's lifecycle
only once (e.g. opened in .probe() and closed in .remove()).
Cc: linux-kernel@vger.kernel.org
Cc: linux-ser...@vger.kernel.org
Cc: Rob Herring
Add code implementing managed version of serdev_device_open() for
serdev device drivers that "open" the device during driver's lifecycle
only once (e.g. opened in .probe() and closed in .remove()).
Cc: linux-kernel@vger.kernel.org
Cc: linux-ser...@vger.kernel.org
Cc: Rob Herring
Cc:
This driver provides access to RAVE SP watchdog functionality.
Cc: linux-kernel@vger.kernel.org
Cc: linux-watch...@vger.kernel.org
Cc: cphe...@gmail.com
Cc: Lucas Stach
Cc: Nikita Yushchenko
Cc: Lee Jones
Cc: Greg
This driver provides access to RAVE SP watchdog functionality.
Cc: linux-kernel@vger.kernel.org
Cc: linux-watch...@vger.kernel.org
Cc: cphe...@gmail.com
Cc: Lucas Stach
Cc: Nikita Yushchenko
Cc: Lee Jones
Cc: Greg Kroah-Hartman
Cc: Pavel Machek
Cc: Andy Shevchenko
Cc: Guenter Roeck
Cc: Rob
On 25 October 2017 at 01:57, Tobin C. Harding wrote:
> On Tue, Oct 24, 2017 at 09:25:20PM +0200, Rasmus Villemoes wrote:
>>
>> I haven't followed the discussion too closely, but has it been
>> considered to exempt NULL from hashing?
>
[snip]
>
> The code in question is;
>
> static
On 25 October 2017 at 01:57, Tobin C. Harding wrote:
> On Tue, Oct 24, 2017 at 09:25:20PM +0200, Rasmus Villemoes wrote:
>>
>> I haven't followed the discussion too closely, but has it been
>> considered to exempt NULL from hashing?
>
[snip]
>
> The code in question is;
>
> static
On Wed, Oct 25, 2017 at 11:49 AM, Willem de Bruijn
wrote:
> From skb->dev and netdev_priv, the tun device has flags 0x1002 ==
> IFF_TAP | IFF_NO_PI. This kernel precedes the recent support for
> IFF_NAPI and IFF_NAPI_FRAGS. The allocation most likely happened
>
On Wed, Oct 25, 2017 at 11:49 AM, Willem de Bruijn
wrote:
> From skb->dev and netdev_priv, the tun device has flags 0x1002 ==
> IFF_TAP | IFF_NO_PI. This kernel precedes the recent support for
> IFF_NAPI and IFF_NAPI_FRAGS. The allocation most likely happened
> in tun_build_skb from
Some of the PCIe services such as AER are being left enabled during
shutdown. This might cause spurious AER errors while SOC is being
powered down.
Let's clean up the PCIe services gracefully during shutdown to clear
these false positives.
Signed-off-by: Sinan Kaya
---
Some of the PCIe services such as AER are being left enabled during
shutdown. This might cause spurious AER errors while SOC is being
powered down.
Let's clean up the PCIe services gracefully during shutdown to clear
these false positives.
Signed-off-by: Sinan Kaya
---
On Wed 25-10-17 14:11:06, Johannes Weiner wrote:
> On Wed, Oct 25, 2017 at 07:29:24PM +0200, Michal Hocko wrote:
> > On Wed 25-10-17 12:44:02, Johannes Weiner wrote:
> > > On Wed, Oct 25, 2017 at 04:12:21PM +0200, Michal Hocko wrote:
> > > > So how about we start with a BIG FAT WARNING for the
On Wed 25-10-17 14:11:06, Johannes Weiner wrote:
> On Wed, Oct 25, 2017 at 07:29:24PM +0200, Michal Hocko wrote:
> > On Wed 25-10-17 12:44:02, Johannes Weiner wrote:
> > > On Wed, Oct 25, 2017 at 04:12:21PM +0200, Michal Hocko wrote:
> > > > So how about we start with a BIG FAT WARNING for the
The values are already configurable from ACPI.
This patch makes the high count (HCNT) and low count (LCNT)
register values configurable through device tree.
Cc: xe-linux-exter...@cisco.com
Signed-off-by: Shikhar Dogra
---
The values are already configurable from ACPI.
This patch makes the high count (HCNT) and low count (LCNT)
register values configurable through device tree.
Cc: xe-linux-exter...@cisco.com
Signed-off-by: Shikhar Dogra
---
Documentation/devicetree/bindings/i2c/i2c-designware.txt | 16
On Wed, Oct 25, 2017 at 08:15:09PM +0530, PrasannaKumar Muralidharan wrote:
> > + if (!IS_ENABLED(CONFIG_HW_RANDOM_TPM))
> > + return 0;
>
> Can #ifndef CONFIG_HW_RANDOM_TPM be used instead? That way an if
> condition can be avoided.
Nope. There is no reason to avoid the
On Wed, Oct 25, 2017 at 08:15:09PM +0530, PrasannaKumar Muralidharan wrote:
> > + if (!IS_ENABLED(CONFIG_HW_RANDOM_TPM))
> > + return 0;
>
> Can #ifndef CONFIG_HW_RANDOM_TPM be used instead? That way an if
> condition can be avoided.
Nope. There is no reason to avoid the
Improve the binding example by removing the leading 0 from '@08' notation,
which fixes the following build warnings:
Warning (unit_address_format): Node /pfuze100@08 unit name should not have
leading 0s
Warning (unit_address_format): Node /pfuze200@08 unit name should not have
leading 0s
Improve the binding example by removing the leading 0 from '@08' notation,
which fixes the following build warnings:
Warning (unit_address_format): Node /pfuze100@08 unit name should not have
leading 0s
Warning (unit_address_format): Node /pfuze200@08 unit name should not have
leading 0s
From: Markus Elfring
Date: Wed, 25 Oct 2017 20:46:18 +0200
* Adjust jump targets so that a call of the function "mutex_unlock"
is mostly stored at the end of these function implementations.
* Replace four calls by goto statements.
* Adjust condition checks.
From: Markus Elfring
Date: Wed, 25 Oct 2017 20:46:18 +0200
* Adjust jump targets so that a call of the function "mutex_unlock"
is mostly stored at the end of these function implementations.
* Replace four calls by goto statements.
* Adjust condition checks.
This issue was detected by using
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/fotg210-hcd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/host/fotg210-hcd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/host/fotg210-hcd.c
301 - 400 of 1506 matches
Mail list logo