On Thu, Jul 12, 2018 at 12:12 AM Doug Anderson wrote:
>
> Hi,
>
> On Mon, Jul 9, 2018 at 4:43 AM, Amit Kucheria
> wrote:
> > We want to create common code for v2 of the TSENS IP block that is used in
> > a large number of Qualcomm SoCs. "qcom,tsens-v2" should be able to handle
> > most of the
From: Jan Dakinevich
Date: Mon, 9 Jul 2018 16:51:19 +0300
> Size of csk_tbl is about 58K, which means 3rd order page allocation.
> kvzalloc provides a fallback if no high order memory is available.
>
> Signed-off-by: Jan Dakinevich
Applied, thanks.
On Thu, Jul 12, 2018 at 12:12 AM Doug Anderson wrote:
>
> Hi,
>
> On Mon, Jul 9, 2018 at 4:43 AM, Amit Kucheria
> wrote:
> > We want to create common code for v2 of the TSENS IP block that is used in
> > a large number of Qualcomm SoCs. "qcom,tsens-v2" should be able to handle
> > most of the
From: Jan Dakinevich
Date: Mon, 9 Jul 2018 16:51:19 +0300
> Size of csk_tbl is about 58K, which means 3rd order page allocation.
> kvzalloc provides a fallback if no high order memory is available.
>
> Signed-off-by: Jan Dakinevich
Applied, thanks.
On Thu, Jul 12, 2018 at 07:16:18AM +0200, Andreas Gruenbacher wrote:
> Hi Stephen,
>
> On 12 July 2018 at 06:41, Stephen Rothwell wrote:
> > Hi Andreas,
> >
> > On Thu, 12 Jul 2018 04:30:07 +0200 Andreas Gruenbacher
> > wrote:
> >>
> >> this is what I'm seeing (git log --pretty=oneline
On Thu, Jul 12, 2018 at 07:16:18AM +0200, Andreas Gruenbacher wrote:
> Hi Stephen,
>
> On 12 July 2018 at 06:41, Stephen Rothwell wrote:
> > Hi Andreas,
> >
> > On Thu, 12 Jul 2018 04:30:07 +0200 Andreas Gruenbacher
> > wrote:
> >>
> >> this is what I'm seeing (git log --pretty=oneline
Signed-off-by: Constantine Shulyupin
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index b40d702337f2..42c439b5cd6a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7303,6 +7303,7 @@ F:drivers/misc/mic/
F: drivers/dma/mic_x100_dma.c
F:
This patch add additional functions that converts some fields to string.
For example function usbssp_trb_comp_code_string take completion c
ode value and return string describing completion code.
Signed-off-by: Pawel Laszczak
---
drivers/usb/usbssp/gadget.h | 572
It is a first patch introduce Cadence USBSSP DRD
controller. This patch is related to device side.
Device part of USBSSP controller base on standard
XHCI specification.
File define macros used bye USBSSP controller,
structures holding and grouping registers, and other
object that are used by
This patch creates a set of event class. For each event class this patch
defines some trace events.
1. event class: usbssp_log_msg
- usbssp_dbg_address - debug message used in function handling
Address Device Command.
- usbssp_dbg_context_change - debug messages related to
Signed-off-by: Constantine Shulyupin
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index b40d702337f2..42c439b5cd6a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7303,6 +7303,7 @@ F:drivers/misc/mic/
F: drivers/dma/mic_x100_dma.c
F:
This patch add additional functions that converts some fields to string.
For example function usbssp_trb_comp_code_string take completion c
ode value and return string describing completion code.
Signed-off-by: Pawel Laszczak
---
drivers/usb/usbssp/gadget.h | 572
It is a first patch introduce Cadence USBSSP DRD
controller. This patch is related to device side.
Device part of USBSSP controller base on standard
XHCI specification.
File define macros used bye USBSSP controller,
structures holding and grouping registers, and other
object that are used by
This patch creates a set of event class. For each event class this patch
defines some trace events.
1. event class: usbssp_log_msg
- usbssp_dbg_address - debug message used in function handling
Address Device Command.
- usbssp_dbg_context_change - debug messages related to
Hi Baoquan,
At 07/11/2018 08:40 PM, Baoquan He wrote:
Please try this v3 patch:
>>From 9850d3de9c02e570dc7572069a9749a8add4c4c7 Mon Sep 17 00:00:00 2001
From: Baoquan He
Date: Wed, 11 Jul 2018 20:31:51 +0800
Subject: [PATCH v3] mm, page_alloc: find movable zone after kernel text
In
Patch add implementation of usbssp_mem_cleanup and
all other functions used during cleaning driver during
unloading module.
Signed-off-by: Pawel Laszczak
---
drivers/usb/usbssp/gadget-mem.c | 180 ++-
drivers/usb/usbssp/gadget-ring.c | 21
Hi Baoquan,
At 07/11/2018 08:40 PM, Baoquan He wrote:
Please try this v3 patch:
>>From 9850d3de9c02e570dc7572069a9749a8add4c4c7 Mon Sep 17 00:00:00 2001
From: Baoquan He
Date: Wed, 11 Jul 2018 20:31:51 +0800
Subject: [PATCH v3] mm, page_alloc: find movable zone after kernel text
In
Patch add implementation of usbssp_mem_cleanup and
all other functions used during cleaning driver during
unloading module.
Signed-off-by: Pawel Laszczak
---
drivers/usb/usbssp/gadget-mem.c | 180 ++-
drivers/usb/usbssp/gadget-ring.c | 21
From: Sean Wang
After the commit acf137951367 ("pinctrl: core: Return selector to the
pinctrl driver") and the commit 47f1242d19c3 ("pinctrl: pinmux: Return
selector to the pinctrl driver"), it's necessary to add the fixes
needed for the pin controller drivers to use the appropriate returned
From: Sean Wang
After the commit acf137951367 ("pinctrl: core: Return selector to the
pinctrl driver") and the commit 47f1242d19c3 ("pinctrl: pinmux: Return
selector to the pinctrl driver"), it's necessary to add the fixes
needed for the pin controller drivers to use the appropriate returned
Errors:
In file included from /usr/include/x86_64-linux-gnu/sys/types.h:194:0,
from /usr/include/stdlib.h:394,
from mpssd.c:23:
mpssd.c:93:10: error: initializer element is not constant
.num = htole16(MIC_VRING_ENTRIES),
mpssd.c:610:10: warning: implicit
Patch implements function responsible for disabling
USB endpoint. This function is called
from USB core gadget during handling SET_CONFIGURATION or
SET_INTERFACE request, or after such events as USB_RESET or detaching
device from host.
Signed-off-by: Pawel Laszczak
---
Errors:
In file included from /usr/include/x86_64-linux-gnu/sys/types.h:194:0,
from /usr/include/stdlib.h:394,
from mpssd.c:23:
mpssd.c:93:10: error: initializer element is not constant
.num = htole16(MIC_VRING_ENTRIES),
mpssd.c:610:10: warning: implicit
Patch implements function responsible for disabling
USB endpoint. This function is called
from USB core gadget during handling SET_CONFIGURATION or
SET_INTERFACE request, or after such events as USB_RESET or detaching
device from host.
Signed-off-by: Pawel Laszczak
---
On Thu, Jul 12, 2018 at 3:30 AM Doug Anderson wrote:
>
> Hi Matthias,
>
> On Wed, Jul 11, 2018 at 2:51 PM, Matthias Kaehlcke wrote:
> > On Wed, Jul 11, 2018 at 11:44:13AM -0700, Doug Anderson wrote:
> >> Hi,
> >>
> >> On Mon, Jul 9, 2018 at 4:43 AM, Amit Kucheria
> >> wrote:
> >> > SDM845 has
On Thu, Jul 12, 2018 at 3:30 AM Doug Anderson wrote:
>
> Hi Matthias,
>
> On Wed, Jul 11, 2018 at 2:51 PM, Matthias Kaehlcke wrote:
> > On Wed, Jul 11, 2018 at 11:44:13AM -0700, Doug Anderson wrote:
> >> Hi,
> >>
> >> On Mon, Jul 9, 2018 at 4:43 AM, Amit Kucheria
> >> wrote:
> >> > SDM845 has
Hi Stephen,
On 12 July 2018 at 06:41, Stephen Rothwell wrote:
> Hi Andreas,
>
> On Thu, 12 Jul 2018 04:30:07 +0200 Andreas Gruenbacher
> wrote:
>>
>> this is what I'm seeing (git log --pretty=oneline --abbrev-commit
>> --graph ^origin/master gfs2/for-next):
>>
>> * f79caf101801 (gfs2/for-next)
Hi Stephen,
On 12 July 2018 at 06:41, Stephen Rothwell wrote:
> Hi Andreas,
>
> On Thu, 12 Jul 2018 04:30:07 +0200 Andreas Gruenbacher
> wrote:
>>
>> this is what I'm seeing (git log --pretty=oneline --abbrev-commit
>> --graph ^origin/master gfs2/for-next):
>>
>> * f79caf101801 (gfs2/for-next)
On Thu, Jul 12, 2018 at 12:10 AM Doug Anderson wrote:
>
> Hi,
>
> On Mon, Jul 9, 2018 at 4:43 AM, Amit Kucheria
> wrote:
> > SDM845 uses v2 of the TSENS IP block but the get_temp() function
> > appears to be identical across v2.x.y in code seen so far. We use the
> > generic get_temp() function
On Thu, Jul 12, 2018 at 12:10 AM Doug Anderson wrote:
>
> Hi,
>
> On Mon, Jul 9, 2018 at 4:43 AM, Amit Kucheria
> wrote:
> > SDM845 uses v2 of the TSENS IP block but the get_temp() function
> > appears to be identical across v2.x.y in code seen so far. We use the
> > generic get_temp() function
Prepare rtc driver for rtc-only with DDR in self-refresh mode.
omap_rtc_power_off now should cater to two features:
1) RTC plus DDR in self-refresh is power a saving mode where in the
entire system including the different voltage rails from PMIC are
shutdown except the ones feeding on to RTC and
Prepare rtc driver for rtc-only with DDR in self-refresh mode.
omap_rtc_power_off now should cater to two features:
1) RTC plus DDR in self-refresh is power a saving mode where in the
entire system including the different voltage rails from PMIC are
shutdown except the ones feeding on to RTC and
Prepare rtc driver for rtc-only with DDR in self-refresh mode.
The patch series is based on top of Johan Hovald's series:
https://lkml.kernel.org/r/20180704090558.16647-1-jo...@kernel.org
Tested for suspend/resume and poweroff on am437x-gp-evm.
Keerthy (4):
rtc: omap: Cut down the shutdown
Add an interface function to set up the rtc for a power_off
mode.
Signed-off-by: Keerthy
---
drivers/rtc/interface.c | 12
drivers/rtc/rtc-omap.c | 1 +
include/linux/rtc.h | 2 ++
3 files changed, 15 insertions(+)
diff --git a/drivers/rtc/interface.c
Use of_device_is_system_power_controller instead of manually reading
the system-power-controller property from the device tree node.
Signed-off-by: Keerthy
---
drivers/rtc/rtc-omap.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-omap.c
Prepare rtc driver for rtc-only with DDR in self-refresh mode.
The patch series is based on top of Johan Hovald's series:
https://lkml.kernel.org/r/20180704090558.16647-1-jo...@kernel.org
Tested for suspend/resume and poweroff on am437x-gp-evm.
Keerthy (4):
rtc: omap: Cut down the shutdown
Add an interface function to set up the rtc for a power_off
mode.
Signed-off-by: Keerthy
---
drivers/rtc/interface.c | 12
drivers/rtc/rtc-omap.c | 1 +
include/linux/rtc.h | 2 ++
3 files changed, 15 insertions(+)
diff --git a/drivers/rtc/interface.c
Use of_device_is_system_power_controller instead of manually reading
the system-power-controller property from the device tree node.
Signed-off-by: Keerthy
---
drivers/rtc/rtc-omap.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-omap.c
Cut down the shutdown time from 2 seconds to 1 sec. In case of roll
over try again.
Signed-off-by: Keerthy
---
Changes in v4:
* Fixed a compilation issue.
* Extended the roll over check post interrupt programming.
drivers/rtc/rtc-omap.c | 13 +++--
1 file changed, 11
Cut down the shutdown time from 2 seconds to 1 sec. In case of roll
over try again.
Signed-off-by: Keerthy
---
Changes in v4:
* Fixed a compilation issue.
* Extended the roll over check post interrupt programming.
drivers/rtc/rtc-omap.c | 13 +++--
1 file changed, 11
On Thu, Jul 12, 2018 at 12:09 AM Doug Anderson wrote:
>
> Hi,
>
> On Mon, Jul 9, 2018 at 4:43 AM, Amit Kucheria
> wrote:
> > We also split up the regmap address space into two, one for the TM
> > registers, the other for the SROT registers. This was required to deal with
> > different address
On Thu, Jul 12, 2018 at 12:09 AM Doug Anderson wrote:
>
> Hi,
>
> On Mon, Jul 9, 2018 at 4:43 AM, Amit Kucheria
> wrote:
> > We also split up the regmap address space into two, one for the TM
> > registers, the other for the SROT registers. This was required to deal with
> > different address
This isn't per-se a real device, it's a pseudo-device that
represents the use of the Aspeed built-in ColdFire to
implement the FSI protocol by bitbanging the GPIOs instead
of doing it from the ARM core.
Thus it's a drop-in replacement for the existing
fsi-master-gpio pseudo-device for use on
The Aspeed AST2x00 can contain a ColdFire v1 coprocessor which
is currently unused on OpenPower systems.
This adds an alternative to the fsi-master-gpio driver that
uses that coprocessor instead of bit banging from the ARM
core itself. The end result is about 4 times faster.
The firmware for the
This isn't per-se a real device, it's a pseudo-device that
represents the use of the Aspeed built-in ColdFire to
implement the FSI protocol by bitbanging the GPIOs instead
of doing it from the ARM core.
Thus it's a drop-in replacement for the existing
fsi-master-gpio pseudo-device for use on
The Aspeed AST2x00 can contain a ColdFire v1 coprocessor which
is currently unused on OpenPower systems.
This adds an alternative to the fsi-master-gpio driver that
uses that coprocessor instead of bit banging from the ARM
core itself. The end result is about 4 times faster.
The firmware for the
There are still quite a few cases where a device might want
to get to a different node of the device-tree, obtain the
resources and map them.
We have of_iomap() and of_io_request_and_map() but they both
have shortcomings, such as not returning the size of the
resource found (which can be useful)
Signed-off-by: Benjamin Herrenschmidt
---
arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts
b/arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts
index 347938673c83..4f4e42e47e3f
Signed-off-by: Benjamin Herrenschmidt
---
arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts
b/arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts
index 347938673c83..4f4e42e47e3f
There are still quite a few cases where a device might want
to get to a different node of the device-tree, obtain the
resources and map them.
We have of_iomap() and of_io_request_and_map() but they both
have shortcomings, such as not returning the size of the
resource found (which can be useful)
This switches away from userspace bitbanging to kernel FSI
using the coprocessor.
Signed-off-by: Benjamin Herrenschmidt
---
arch/arm/boot/dts/aspeed-bmc-opp-palmetto.dts | 28 ++-
1 file changed, 21 insertions(+), 7 deletions(-)
diff --git
This switches away from userspace bitbanging to kernel FSI
using the coprocessor.
Signed-off-by: Benjamin Herrenschmidt
---
arch/arm/boot/dts/aspeed-bmc-opp-palmetto.dts | 28 ++-
1 file changed, 21 insertions(+), 7 deletions(-)
diff --git
On Wed, 2018-07-11 at 22:57 -0400, Steven Rostedt wrote:
> On Fri, 11 May 2018 14:39:18 -0700
> Joe Perches wrote:
>
> > With a possible change to pr_fmt coming, the logging output can
> > become unbalanced when an initial line has a prefix and subsequent
> > lines do not when a multiple line
On Wed, 2018-07-11 at 22:57 -0400, Steven Rostedt wrote:
> On Fri, 11 May 2018 14:39:18 -0700
> Joe Perches wrote:
>
> > With a possible change to pr_fmt coming, the logging output can
> > become unbalanced when an initial line has a prefix and subsequent
> > lines do not when a multiple line
Hi Andreas,
On Thu, 12 Jul 2018 04:30:07 +0200 Andreas Gruenbacher
wrote:
>
> this is what I'm seeing (git log --pretty=oneline --abbrev-commit
> --graph ^origin/master gfs2/for-next):
>
> * f79caf101801 (gfs2/for-next) gfs2: use iomap_readpage for blocksize
> == PAGE_SIZE
> * af58827ee500
Hi Andreas,
On Thu, 12 Jul 2018 04:30:07 +0200 Andreas Gruenbacher
wrote:
>
> this is what I'm seeing (git log --pretty=oneline --abbrev-commit
> --graph ^origin/master gfs2/for-next):
>
> * f79caf101801 (gfs2/for-next) gfs2: use iomap_readpage for blocksize
> == PAGE_SIZE
> * af58827ee500
On Thu, Jul 12, 2018 at 12:07 AM, Doug Anderson wrote:
> Hi,
>
> On Mon, Jul 9, 2018 at 4:43 AM, Amit Kucheria
> wrote:
>> There are two banks of registers for v2 TSENS IPs: SROT and TM. On older
>> SoCs these were contiguous, leading to DTs mapping them as one register
>> address space of size
On Thu, Jul 12, 2018 at 12:07 AM, Doug Anderson wrote:
> Hi,
>
> On Mon, Jul 9, 2018 at 4:43 AM, Amit Kucheria
> wrote:
>> There are two banks of registers for v2 TSENS IPs: SROT and TM. On older
>> SoCs these were contiguous, leading to DTs mapping them as one register
>> address space of size
Hi all,
On Wed, 11 Jul 2018 14:17:37 +1000 Stephen Rothwell
wrote:
>
> After merging the scsi-mkp tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from include/linux/spinlock_types.h:18:0,
> from include/linux/spinlock.h:82,
>
Hi all,
On Wed, 11 Jul 2018 14:17:37 +1000 Stephen Rothwell
wrote:
>
> After merging the scsi-mkp tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from include/linux/spinlock_types.h:18:0,
> from include/linux/spinlock.h:82,
>
Hi all,
On Wed, 11 Jul 2018 14:04:57 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the scsi-mkp tree got a conflict in:
>
> MAINTAINERS
>
> between commit:
>
> 54e45716a84a ("scsi: remove NCR_D700 driver")
>
> from Linus' tree and commit:
>
> 01a21986f8ed
Hi all,
On Wed, 11 Jul 2018 14:04:57 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the scsi-mkp tree got a conflict in:
>
> MAINTAINERS
>
> between commit:
>
> 54e45716a84a ("scsi: remove NCR_D700 driver")
>
> from Linus' tree and commit:
>
> 01a21986f8ed
On Wed, Jul 11, 2018 at 11:21:20PM -0400, Steven Rostedt wrote:
> On Wed, 11 Jul 2018 13:52:49 -0700
> Joel Fernandes wrote:
>
> > > #define __DECLARE_TRACE(name, proto, args, cond, data_proto, data_args) \
> > > extern struct tracepoint __tracepoint_##name; \
> > > static
On Wed, Jul 11, 2018 at 11:21:20PM -0400, Steven Rostedt wrote:
> On Wed, 11 Jul 2018 13:52:49 -0700
> Joel Fernandes wrote:
>
> > > #define __DECLARE_TRACE(name, proto, args, cond, data_proto, data_args) \
> > > extern struct tracepoint __tracepoint_##name; \
> > > static
On (07/11/18 23:09), Steven Rostedt wrote:
> > On (07/11/18 15:17), Steven Rostedt wrote:
> > > +bool ignore_console_lock_warning __read_mostly;
> > > +EXPORT_SYMBOL(ignore_console_lock_warning);
> >
> > OK. So, to recap,
> > We made is_console_locked() EXPORT_SYMBOL recently [it's still in
>
On (07/11/18 23:09), Steven Rostedt wrote:
> > On (07/11/18 15:17), Steven Rostedt wrote:
> > > +bool ignore_console_lock_warning __read_mostly;
> > > +EXPORT_SYMBOL(ignore_console_lock_warning);
> >
> > OK. So, to recap,
> > We made is_console_locked() EXPORT_SYMBOL recently [it's still in
>
The bindings were missing when the device-tree
files were added
Signed-off-by: Luis Araneda
---
.../devicetree/bindings/arm/xilinx.txt | 17 +
1 file changed, 17 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/xilinx.txt
Move the Adapteva Parallela board to Xilinx dt-bindings,
as it's based on a Zynq SoC from Xilinx
Signed-off-by: Luis Araneda
---
Documentation/devicetree/bindings/arm/adapteva.txt | 7 ---
Documentation/devicetree/bindings/arm/xilinx.txt | 3 +++
2 files changed, 3 insertions(+), 7
The bindings were missing when the device-tree
files were added
Signed-off-by: Luis Araneda
---
.../devicetree/bindings/arm/xilinx.txt | 17 +
1 file changed, 17 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/xilinx.txt
Move the Adapteva Parallela board to Xilinx dt-bindings,
as it's based on a Zynq SoC from Xilinx
Signed-off-by: Luis Araneda
---
Documentation/devicetree/bindings/arm/adapteva.txt | 7 ---
Documentation/devicetree/bindings/arm/xilinx.txt | 3 +++
2 files changed, 3 insertions(+), 7
This series attempts to standardize device naming and improve
its information for better identification
The values of the "compatible" and "model" device-tree properties
are corrected for some devices, adding complementary information
when necessary
Changes since v2:
- Split dt-bindings patch
Sort additional compatible strings (boards) alphabetically
by their manufacturer and model number
This will help when finding a board because they
will be grouped by their manufacturer
Signed-off-by: Luis Araneda
---
Documentation/devicetree/bindings/arm/xilinx.txt | 6 +++---
1 file changed,
This series attempts to standardize device naming and improve
its information for better identification
The values of the "compatible" and "model" device-tree properties
are corrected for some devices, adding complementary information
when necessary
Changes since v2:
- Split dt-bindings patch
Sort additional compatible strings (boards) alphabetically
by their manufacturer and model number
This will help when finding a board because they
will be grouped by their manufacturer
Signed-off-by: Luis Araneda
---
Documentation/devicetree/bindings/arm/xilinx.txt | 6 +++---
1 file changed,
Change the description of some boards to make it similar
to the value of the model property from their respective
device-tree, using the format " "
Signed-off-by: Luis Araneda
---
Documentation/devicetree/bindings/arm/xilinx.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
Both boards are made by Avnet, Inc. So add an additional
value to the compatible property
Signed-off-by: Luis Araneda
---
arch/arm/boot/dts/zynq-microzed.dts | 2 +-
arch/arm/boot/dts/zynq-zed.dts | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Replace the current value of the model property by a more accurate
description of each board (which includes the manufacturer), as some
of the boards had the same value ("Xilinx Zynq")
Signed-off-by: Luis Araneda
---
arch/arm/boot/dts/zynq-cc108.dts | 2 +-
Change the description of some boards to make it similar
to the value of the model property from their respective
device-tree, using the format " "
Signed-off-by: Luis Araneda
---
Documentation/devicetree/bindings/arm/xilinx.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
Both boards are made by Avnet, Inc. So add an additional
value to the compatible property
Signed-off-by: Luis Araneda
---
arch/arm/boot/dts/zynq-microzed.dts | 2 +-
arch/arm/boot/dts/zynq-zed.dts | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Replace the current value of the model property by a more accurate
description of each board (which includes the manufacturer), as some
of the boards had the same value ("Xilinx Zynq")
Signed-off-by: Luis Araneda
---
arch/arm/boot/dts/zynq-cc108.dts | 2 +-
Hi Jassi,
> -Original Message-
> From: Jassi Brar [mailto:jassisinghb...@gmail.com]
> Sent: Thursday, July 12, 2018 1:01 AM
> To: A.s. Dong
> Cc: Sascha Hauer ; linux-arm-
> ker...@lists.infradead.org; donga...@gmail.com; linux-
> ker...@vger.kernel.org; Oleksij Rempel ; dl-
> linux-imx
Hi Jassi,
> -Original Message-
> From: Jassi Brar [mailto:jassisinghb...@gmail.com]
> Sent: Thursday, July 12, 2018 1:01 AM
> To: A.s. Dong
> Cc: Sascha Hauer ; linux-arm-
> ker...@lists.infradead.org; donga...@gmail.com; linux-
> ker...@vger.kernel.org; Oleksij Rempel ; dl-
> linux-imx
This series implements support for offloading the FSI protocol bitbanging
to the ColdFire secondary core of the Aspeed SoCs. The result increases
FSI performance by a factor of 4, and on systems that don't support async
FSI clock, provide much more regular and continuous clocking which helps
This series implements support for offloading the FSI protocol bitbanging
to the ColdFire secondary core of the Aspeed SoCs. The result increases
FSI performance by a factor of 4, and on systems that don't support async
FSI clock, provide much more regular and continuous clocking which helps
From: Yandong Zhao
It does not matter if the caller of may_use_simd() migrates to
another cpu after the call, but it is still important that the
kernel_neon_busy percpu instance that is read matches the cpu the
task is running on at the time of the read.
This means that raw_cpu_read() is not
From: Yandong Zhao
It does not matter if the caller of may_use_simd() migrates to
another cpu after the call, but it is still important that the
kernel_neon_busy percpu instance that is read matches the cpu the
task is running on at the time of the read.
This means that raw_cpu_read() is not
On Wed, 11 Jul 2018 13:52:49 -0700
Joel Fernandes wrote:
> > #define __DECLARE_TRACE(name, proto, args, cond, data_proto, data_args) \
> > extern struct tracepoint __tracepoint_##name; \
> > static inline void trace_##name(proto) \
> > {
On Wed, 11 Jul 2018 13:52:49 -0700
Joel Fernandes wrote:
> > #define __DECLARE_TRACE(name, proto, args, cond, data_proto, data_args) \
> > extern struct tracepoint __tracepoint_##name; \
> > static inline void trace_##name(proto) \
> > {
> /* Aligned to page sizes to match whats mapped via vsyscalls to userspace */
> #define HV_CLOCK_SIZE (sizeof(struct pvclock_vsyscall_time_info) * NR_CPUS)
HV_CLOCK_SIZE is not used anywhere anymore, can be deleted.
> +#define HVC_BOOT_ARRAY_SIZE \
> + (PAGE_SIZE / sizeof(struct
> /* Aligned to page sizes to match whats mapped via vsyscalls to userspace */
> #define HV_CLOCK_SIZE (sizeof(struct pvclock_vsyscall_time_info) * NR_CPUS)
HV_CLOCK_SIZE is not used anywhere anymore, can be deleted.
> +#define HVC_BOOT_ARRAY_SIZE \
> + (PAGE_SIZE / sizeof(struct
On Thu, 12 Jul 2018 10:58:48 +0900
Sergey Senozhatsky wrote:
> On (07/11/18 15:17), Steven Rostedt wrote:
> > +bool ignore_console_lock_warning __read_mostly;
> > +EXPORT_SYMBOL(ignore_console_lock_warning);
>
> OK. So, to recap,
> We made is_console_locked() EXPORT_SYMBOL recently [it's
On Thu, 12 Jul 2018 10:58:48 +0900
Sergey Senozhatsky wrote:
> On (07/11/18 15:17), Steven Rostedt wrote:
> > +bool ignore_console_lock_warning __read_mostly;
> > +EXPORT_SYMBOL(ignore_console_lock_warning);
>
> OK. So, to recap,
> We made is_console_locked() EXPORT_SYMBOL recently [it's
On Wed, Jul 11, 2018 at 8:31 AM, Tony Lindgren wrote:
> * Koen Kooi [180711 07:36]:
>> +_opp_table {
>> + /*
>> + * All PG 2.0 silicon may not support 1GHz but some of the early
>> + * BeagleBone Blacks have PG 2.0 silicon which is guaranteed
>> + * to support 1GHz OPP so
On Wed, Jul 11, 2018 at 8:31 AM, Tony Lindgren wrote:
> * Koen Kooi [180711 07:36]:
>> +_opp_table {
>> + /*
>> + * All PG 2.0 silicon may not support 1GHz but some of the early
>> + * BeagleBone Blacks have PG 2.0 silicon which is guaranteed
>> + * to support 1GHz OPP so
Hi Greg !
This is the second round of updates of the FSI stack.
These comprise of:
- Some build fixes detected with COMPILE_TEST when
used on "other" archs
- Sparse warning fixes
- Some object lifetime fixes
- A new feature to control some of the protocol delays
- Overheaul of the
Hi Greg !
This is the second round of updates of the FSI stack.
These comprise of:
- Some build fixes detected with COMPILE_TEST when
used on "other" archs
- Sparse warning fixes
- Some object lifetime fixes
- A new feature to control some of the protocol delays
- Overheaul of the
On Fri, 11 May 2018 14:39:18 -0700
Joe Perches wrote:
> With a possible change to pr_fmt coming, the logging output can
> become unbalanced when an initial line has a prefix and subsequent
> lines do not when a multiple line pr_ is emitted.
>
> Fix it by emitting a single line.
>
>
On Fri, 11 May 2018 14:39:18 -0700
Joe Perches wrote:
> With a possible change to pr_fmt coming, the logging output can
> become unbalanced when an initial line has a prefix and subsequent
> lines do not when a multiple line pr_ is emitted.
>
> Fix it by emitting a single line.
>
>
+#include
Can be removed, because as Paolo, noticed X86_HYPER_KVM check is not needed.
> +static int __init kvm_setup_vsyscall_timeinfo(void)
> +{
> +#ifdef CONFIG_X86_64
> + u8 flags;
> +
> + if (!hv_clock || !kvmclock_vsyscall)
> + return 0;
> +
> + flags =
+#include
Can be removed, because as Paolo, noticed X86_HYPER_KVM check is not needed.
> +static int __init kvm_setup_vsyscall_timeinfo(void)
> +{
> +#ifdef CONFIG_X86_64
> + u8 flags;
> +
> + if (!hv_clock || !kvmclock_vsyscall)
> + return 0;
> +
> + flags =
1 - 100 of 1754 matches
Mail list logo
