From: Peter Xu
It's been missing for a while but no one is touching that up. Fix it.
Link: http://lkml.kernel.org/r/20180315060639.9578-1-pet...@redhat.com
CC: Ingo Molnar
Cc:sta...@vger.kernel.org
Fixes: 7b2c86250122d ("tracing: Add NMI tracing in hwlat
From: Peter Xu
It's been missing for a while but no one is touching that up. Fix it.
Link: http://lkml.kernel.org/r/20180315060639.9578-1-pet...@redhat.com
CC: Ingo Molnar
Cc:sta...@vger.kernel.org
Fixes: 7b2c86250122d ("tracing: Add NMI tracing in hwlat detector")
Signed-off-by: Peter Xu
From: Masami Hiramatsu
Previous testcase redirects echo-out into /dev/null
using "&>" as below
echo "trigger-command" >> trigger &> /dev/null
But this means redirecting both stdout and stderr into
/dev/null because it is same as below
echo "trigger-command" >> trigger >
From: Ravi Bangoria
Kernel is crashing when user tries to record 'ftrace:function' event
with empty filter:
# perf record -e ftrace:function --filter="" ls
# dmesg
BUG: unable to handle kernel NULL pointer dereference at 0008
Oops: [#1] SMP
From: Masami Hiramatsu
Previous testcase redirects echo-out into /dev/null
using "&>" as below
echo "trigger-command" >> trigger &> /dev/null
But this means redirecting both stdout and stderr into
/dev/null because it is same as below
echo "trigger-command" >> trigger > /dev/null 2>&1
So ">>
From: Ravi Bangoria
Kernel is crashing when user tries to record 'ftrace:function' event
with empty filter:
# perf record -e ftrace:function --filter="" ls
# dmesg
BUG: unable to handle kernel NULL pointer dereference at 0008
Oops: [#1] SMP PTI
...
RIP:
From: Thomas Richter
File /sys/kernel/debug/kprobes/blacklist displays random addresses:
[root@s8360046 linux]# cat /sys/kernel/debug/kprobes/blacklist
0x47149a90-0xbfcb099a print_type_x8
This breaks 'perf probe' which uses the blacklist file to
From: Thomas Richter
File /sys/kernel/debug/kprobes/blacklist displays random addresses:
[root@s8360046 linux]# cat /sys/kernel/debug/kprobes/blacklist
0x47149a90-0xbfcb099a print_type_x8
This breaks 'perf probe' which uses the blacklist file to prohibit
probes on
From: Ahbong Chang
Without this forward declaration compile may fail if this header is
included only for registering other probe event without struct
pool_workqueue.
Link: http://lkml.kernel.org/r/20180416023626.139915-1-cwahb...@google.com
Reviewed-by: Todd Poynor
From: "Steven Rostedt (VMware)"
Arnaldo noticed that the latest kernel is missing the syscall event system
directory in x86. I bisected it down to d5a00528b58c ("syscalls/core,
syscalls/x86: Rename struct pt_regs-based sys_*() to __x64_sys_*()").
The system call trace
From: Masami Hiramatsu
Add a testcase for multiple actions with different
parameters on an event trigger, which has been fixed
by commit 192c283e93bd ("tracing: Add action comparisons
when testing matching hist triggers").
Link:
From: Ahbong Chang
Without this forward declaration compile may fail if this header is
included only for registering other probe event without struct
pool_workqueue.
Link: http://lkml.kernel.org/r/20180416023626.139915-1-cwahb...@google.com
Reviewed-by: Todd Poynor
Signed-off-by: Ahbong Chang
From: "Steven Rostedt (VMware)"
Arnaldo noticed that the latest kernel is missing the syscall event system
directory in x86. I bisected it down to d5a00528b58c ("syscalls/core,
syscalls/x86: Rename struct pt_regs-based sys_*() to __x64_sys_*()").
The system call trace events are special, as
From: Masami Hiramatsu
Add a testcase for multiple actions with different
parameters on an event trigger, which has been fixed
by commit 192c283e93bd ("tracing: Add action comparisons
when testing matching hist triggers").
Link:
Linus,
Following tracing fixes:
- Add workqueue forward declaration (for new work, but a nice clean up)
- seftest fixes for the new histogram code
- Print output fix for hwlat tracer
- Fix missing system call events - due to change in x86 syscall naming
- Fix kprobe address being used
Linus,
Following tracing fixes:
- Add workqueue forward declaration (for new work, but a nice clean up)
- seftest fixes for the new histogram code
- Print output fix for hwlat tracer
- Fix missing system call events - due to change in x86 syscall naming
- Fix kprobe address being used
PCI fixes:
- fix Aardvark MRRS setting (Evan Wang)
- clarify "bandwidth available" link status message (Jakub Kicinski)
- update Kirin GPIO name to fix probe failure (Loic Poulain)
- fix Aardvark IRQ usage (Victor Gu)
- fix Aardvark config accessor issues (Victor Gu)
The following
PCI fixes:
- fix Aardvark MRRS setting (Evan Wang)
- clarify "bandwidth available" link status message (Jakub Kicinski)
- update Kirin GPIO name to fix probe failure (Loic Poulain)
- fix Aardvark IRQ usage (Victor Gu)
- fix Aardvark config accessor issues (Victor Gu)
The following
On Thu, Apr 26, 2018 at 03:53:58PM +0900, Tetsuo Handa wrote:
> Oh, pull request was already sent. Should be merged shortly.
>
> https://marc.info/?l=linux-kernel=152472466201090=2
More testing, either before or after merging, would be greatly
appreciated. One of the challenges is that there
On Thu, Apr 26, 2018 at 03:53:58PM +0900, Tetsuo Handa wrote:
> Oh, pull request was already sent. Should be merged shortly.
>
> https://marc.info/?l=linux-kernel=152472466201090=2
More testing, either before or after merging, would be greatly
appreciated. One of the challenges is that there
On Thu, Apr 26, 2018 at 3:57 AM, Anson Huang wrote:
> The 'phy-supply' is for enabling/disabling phy regulator, but here the
> MAX7322 IO0 is NOT for
> enabling/disabling PHY regulator, it is for IO voltage switch between 1.5V
> and 1.8V, our ENET
> IO can work with both
On Thu, Apr 26, 2018 at 3:57 AM, Anson Huang wrote:
> The 'phy-supply' is for enabling/disabling phy regulator, but here the
> MAX7322 IO0 is NOT for
> enabling/disabling PHY regulator, it is for IO voltage switch between 1.5V
> and 1.8V, our ENET
> IO can work with both 1.5V and 1.8V, so any
On 4/17/2018 1:09 PM, Alexandru Gagniuc wrote:
On errors reported from CPER, cper_print_bits() was used to log the
AER bits. This resulted in hard-to-understand messages, without a
prefix. Instead use __aer_print_error() for both native AER and CPER
to provide a more consistent log format.
On 4/17/2018 1:09 PM, Alexandru Gagniuc wrote:
On errors reported from CPER, cper_print_bits() was used to log the
AER bits. This resulted in hard-to-understand messages, without a
prefix. Instead use __aer_print_error() for both native AER and CPER
to provide a more consistent log format.
Hey Rui,
On Tue, Apr 24, 2018 at 09:25:45PM +0800, Zhang Rui wrote:
> Hi, Eduardo,
>
> On 五, 2018-04-20 at 09:18 -0700, Eduardo Valentin wrote:
> > Hello Linus,
> >
> > Here are a couple of fixes on thermal subsystem.
> > Please consider pulling from
> >
> >
Hey Rui,
On Tue, Apr 24, 2018 at 09:25:45PM +0800, Zhang Rui wrote:
> Hi, Eduardo,
>
> On 五, 2018-04-20 at 09:18 -0700, Eduardo Valentin wrote:
> > Hello Linus,
> >
> > Here are a couple of fixes on thermal subsystem.
> > Please consider pulling from
> >
> >
2018-04-20 18:51 GMT+02:00 Herbert Xu :
> On Mon, Apr 09, 2018 at 03:54:45PM +0200, Salvatore Mesoraca wrote:
>> v2:
>> As suggested by Herbert Xu, the blocksize and alignmask checks
>> have been moved to crypto_check_alg.
>> So, now, all the other
2018-04-20 18:51 GMT+02:00 Herbert Xu :
> On Mon, Apr 09, 2018 at 03:54:45PM +0200, Salvatore Mesoraca wrote:
>> v2:
>> As suggested by Herbert Xu, the blocksize and alignmask checks
>> have been moved to crypto_check_alg.
>> So, now, all the other separate checks are not
Pankaj Gupta writes:
>> Ideally, qemu (seabios?) would advertise a platform capabilities
>> sub-table that doesn't fill in the flush bits.
>
> Could you please elaborate on this, how its related to disabling
> MAP_SYNC? We are not doing entire nvdimm device emulation.
My
Pankaj Gupta writes:
>> Ideally, qemu (seabios?) would advertise a platform capabilities
>> sub-table that doesn't fill in the flush bits.
>
> Could you please elaborate on this, how its related to disabling
> MAP_SYNC? We are not doing entire nvdimm device emulation.
My mistake. If you're
On Thu, Apr 26, 2018 at 3:31 AM, Anson Huang wrote:
> I searched the mail I sent, I can NOT found where I said "MAX7310 controls
> the ethernet phy"
Initially you passed: pinctrl-assert-gpios = < 0
GPIO_ACTIVE_HIGH> inside the fec1 node.
Then I explained that
On Thu, Apr 26, 2018 at 3:31 AM, Anson Huang wrote:
> I searched the mail I sent, I can NOT found where I said "MAX7310 controls
> the ethernet phy"
Initially you passed: pinctrl-assert-gpios = < 0
GPIO_ACTIVE_HIGH> inside the fec1 node.
Then I explained that 'pinctrl-assert-gpios' is
On Thu, Apr 26, 2018 at 04:21:19PM +, Kani, Toshi wrote:
> All pages under the pmd had been unmapped and then lazy TLB purged with
> INVLPG before coming to this code path. Speculation is not allowed to
> pages without mapping.
CPUs have not only TLBs, but also page-walk caches which cache
On Thu, Apr 26, 2018 at 04:21:19PM +, Kani, Toshi wrote:
> All pages under the pmd had been unmapped and then lazy TLB purged with
> INVLPG before coming to this code path. Speculation is not allowed to
> pages without mapping.
CPUs have not only TLBs, but also page-walk caches which cache
This commit fixes incorrect setting of reset bits for PCI/VGA and
PECI modules.
1. Reset bit for PCI/VGA is 8.
2. PECI reset bit is missing so added bit 10 as its reset bit.
Signed-off-by: Jae Hyun Yoo
Fixes: 15ed8ce5f84e ("clk: aspeed: Register gated clocks")
Cc:
This commit fixes incorrect setting of reset bits for PCI/VGA and
PECI modules.
1. Reset bit for PCI/VGA is 8.
2. PECI reset bit is missing so added bit 10 as its reset bit.
Signed-off-by: Jae Hyun Yoo
Fixes: 15ed8ce5f84e ("clk: aspeed: Register gated clocks")
Cc: stable
---
>
> Dan Williams writes:
>
> > [ adding Jeff directly since he has also been looking at
> > infrastructure to track when MAP_SYNC should be disabled ]
> >
> > On Wed, Apr 25, 2018 at 7:21 AM, Dan Williams
> > wrote:
> >> On Wed, Apr 25, 2018
>
> Dan Williams writes:
>
> > [ adding Jeff directly since he has also been looking at
> > infrastructure to track when MAP_SYNC should be disabled ]
> >
> > On Wed, Apr 25, 2018 at 7:21 AM, Dan Williams
> > wrote:
> >> On Wed, Apr 25, 2018 at 4:24 AM, Pankaj Gupta wrote:
> >>> This patch
> >
> >>
> >> On Wed, Apr 25, 2018 at 04:54:14PM +0530, Pankaj Gupta wrote:
> >> > This patch adds functionality to perform
> >> > flush from guest to hosy over VIRTIO
> >> > when 'ND_REGION_VIRTIO'flag is set on
> >> > nd_negion. Flag is set by 'virtio-pmem'
> >> > driver.
> >> >
> >> >
> >
> >>
> >> On Wed, Apr 25, 2018 at 04:54:14PM +0530, Pankaj Gupta wrote:
> >> > This patch adds functionality to perform
> >> > flush from guest to hosy over VIRTIO
> >> > when 'ND_REGION_VIRTIO'flag is set on
> >> > nd_negion. Flag is set by 'virtio-pmem'
> >> > driver.
> >> >
> >> >
On 26/04/18 10:26, Ruslan Bilovol wrote:
On Tue, Apr 24, 2018 at 9:02 PM, Takashi Iwai wrote:
On Tue, 24 Apr 2018 19:24:41 +0200,
Jorge Sanjuan wrote:
v2 fixes:
- If/else statements braces style fixes.
- Add wrapping function to mixer unit code.
- Make connectors
On 26/04/18 10:26, Ruslan Bilovol wrote:
On Tue, Apr 24, 2018 at 9:02 PM, Takashi Iwai wrote:
On Tue, 24 Apr 2018 19:24:41 +0200,
Jorge Sanjuan wrote:
v2 fixes:
- If/else statements braces style fixes.
- Add wrapping function to mixer unit code.
- Make connectors control kctl struct
Christian Brauner writes:
> On Thu, Apr 26, 2018 at 11:47:19AM -0500, Eric W. Biederman wrote:
>> Christian Brauner writes:
>>
>> > On Tue, Apr 24, 2018 at 06:00:35PM -0500, Eric W. Biederman wrote:
>> >> Christian Brauner
Christian Brauner writes:
> On Thu, Apr 26, 2018 at 11:47:19AM -0500, Eric W. Biederman wrote:
>> Christian Brauner writes:
>>
>> > On Tue, Apr 24, 2018 at 06:00:35PM -0500, Eric W. Biederman wrote:
>> >> Christian Brauner writes:
>> >>
>> >> > On Wed, Apr 25, 2018, 00:41 Eric W. Biederman
On Thu, Apr 26, 2018 at 03:54:27PM +0200, Thomas Gleixner wrote:
> +#!/usr/bin/env python
> +# SPDX-License-Identifier: GPL2.0
You didn't run the tool on itself :)
Other than that, looks good, if you fix the above line feel free to add:
Reviewed-by: Greg Kroah-Hartman
On Thu, Apr 26, 2018 at 03:54:27PM +0200, Thomas Gleixner wrote:
> +#!/usr/bin/env python
> +# SPDX-License-Identifier: GPL2.0
You didn't run the tool on itself :)
Other than that, looks good, if you fix the above line feel free to add:
Reviewed-by: Greg Kroah-Hartman
On Thu, Apr 26, 2018 at 11:47:19AM -0500, Eric W. Biederman wrote:
> Christian Brauner writes:
>
> > On Tue, Apr 24, 2018 at 06:00:35PM -0500, Eric W. Biederman wrote:
> >> Christian Brauner writes:
> >>
> >> > On Wed, Apr 25,
On Thu, Apr 26, 2018 at 11:47:19AM -0500, Eric W. Biederman wrote:
> Christian Brauner writes:
>
> > On Tue, Apr 24, 2018 at 06:00:35PM -0500, Eric W. Biederman wrote:
> >> Christian Brauner writes:
> >>
> >> > On Wed, Apr 25, 2018, 00:41 Eric W. Biederman
> >> > wrote:
> >> >
> >> > Bah.
This patch adds pins, groups and functions for parallel RGB output
signals from DU. The HDMI and TCON pins are added to separate groups.
Based on a similar patch of the R8A7796 PFC driver by Niklas Söderlund
.
Signed-off-by: Takeshi Kihara
This patch adds pins, groups and functions for parallel RGB output
signals from DU. The HDMI and TCON pins are added to separate groups.
Based on a similar patch of the R8A7796 PFC driver by Niklas Söderlund
.
Signed-off-by: Takeshi Kihara
[Kieran: Rebase on top of tree]
Signed-off-by: Kieran
Signed-off-by: Kieran Bingham
---
Documentation/devicetree/bindings/display/renesas,du.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/renesas,du.txt
Signed-off-by: Kieran Bingham
---
Documentation/devicetree/bindings/display/renesas,du.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/renesas,du.txt
b/Documentation/devicetree/bindings/display/renesas,du.txt
index a36a6e7ee54f..7c6854bd0a04
The naming of the fields for the ODPM signals in the DU extensional
function control register 6 (DEFR6) is incorrect against the data sheets
for both R-Car Gen2 and R-Car Gen3.
Rename the fields to match the datasheet.
Signed-off-by: Kieran Bingham
---
The naming of the fields for the ODPM signals in the DU extensional
function control register 6 (DEFR6) is incorrect against the data sheets
for both R-Car Gen2 and R-Car Gen3.
Rename the fields to match the datasheet.
Signed-off-by: Kieran Bingham
---
drivers/gpu/drm/rcar-du/rcar_du_group.c |
The r8a77965 has 4 VSP instances.
Based on a similar patch of the R8A7796 device tree
by Laurent Pinchart .
Signed-off-by: Takeshi Kihara
[Kieran: Rebased to top of tree, fixed sort orders]
Signed-off-by: Kieran Bingham
The r8a77965 has 4 VSP instances.
Based on a similar patch of the R8A7796 device tree
by Laurent Pinchart .
Signed-off-by: Takeshi Kihara
[Kieran: Rebased to top of tree, fixed sort orders]
Signed-off-by: Kieran Bingham
---
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 44
Ahem - this one seems to have lost it's commit message.
Apologies :)
--
Kieran
On 26/04/18 17:53, Kieran Bingham wrote:
> Signed-off-by: Kieran Bingham
> ---
> Documentation/devicetree/bindings/display/renesas,du.txt | 2 ++
> 1 file changed, 2
Ahem - this one seems to have lost it's commit message.
Apologies :)
--
Kieran
On 26/04/18 17:53, Kieran Bingham wrote:
> Signed-off-by: Kieran Bingham
> ---
> Documentation/devicetree/bindings/display/renesas,du.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git
On Thu, Apr 26, 2018 at 9:40 AM, Pankaj Gupta wrote:
>
>>
>> On Wed, Apr 25, 2018 at 04:54:14PM +0530, Pankaj Gupta wrote:
>> > This patch adds functionality to perform
>> > flush from guest to hosy over VIRTIO
>> > when 'ND_REGION_VIRTIO'flag is set on
>> > nd_negion. Flag is
On Thu, Apr 26, 2018 at 9:40 AM, Pankaj Gupta wrote:
>
>>
>> On Wed, Apr 25, 2018 at 04:54:14PM +0530, Pankaj Gupta wrote:
>> > This patch adds functionality to perform
>> > flush from guest to hosy over VIRTIO
>> > when 'ND_REGION_VIRTIO'flag is set on
>> > nd_negion. Flag is set by
Add the HDMI encoder to the R8A77965 DT in disabled state.
Based on a similar patch of the R8A7796 device tree
by Laurent Pinchart .
Signed-off-by: Takeshi Kihara
[Kieran: Rebase to top of tree]
Signed-off-by: Kieran
Add the HDMI encoder to the R8A77965 DT in disabled state.
Based on a similar patch of the R8A7796 device tree
by Laurent Pinchart .
Signed-off-by: Takeshi Kihara
[Kieran: Rebase to top of tree]
Signed-off-by: Kieran Bingham
---
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 28
From: Takeshi Kihara
The DU1 external dot clock is provided by the fixed frequency clock
generator X21, while the DU0 and DU3 clocks are provided by the
programmable Versaclock5 clock generator.
Signed-off-by: Takeshi Kihara
From: Takeshi Kihara
This patch enables the HDMI encoder for the Salvator-X 2nd version board
on the R8A77965 SoC and hook it up to the HDMI connector.
Based on code of the Salvator-X 2nd version board
on the R8A7796 SoC device tree
by Geert Uytterhoeven
From: Takeshi Kihara
The DU1 external dot clock is provided by the fixed frequency clock
generator X21, while the DU0 and DU3 clocks are provided by the
programmable Versaclock5 clock generator.
Signed-off-by: Takeshi Kihara
Signed-off-by: Kieran Bingham
---
From: Takeshi Kihara
This patch enables the HDMI encoder for the Salvator-X 2nd version board
on the R8A77965 SoC and hook it up to the HDMI connector.
Based on code of the Salvator-X 2nd version board
on the R8A7796 SoC device tree
by Geert Uytterhoeven
Signed-off-by: Takeshi Kihara
The DU CRTC driver does not support distinguishing between a hardware
index, and a software (CRTC) index in the event that a DU channel might
not be populated by the hardware.
Support this by adapting the rcar_du_device_info structure to store a
bitmask of available channels rather than a count
The DU CRTC driver does not support distinguishing between a hardware
index, and a software (CRTC) index in the event that a DU channel might
not be populated by the hardware.
Support this by adapting the rcar_du_device_info structure to store a
bitmask of available channels rather than a count
The group objects assume linear indexing, and more so always assume that
channel 0 of any active group is used.
Now that the CRTC objects support non-linear indexing, adapt the groups
to remove assumptions that channel 0 is utilised in each group by using
the channel mask provided in the device
The group objects assume linear indexing, and more so always assume that
channel 0 of any active group is used.
Now that the CRTC objects support non-linear indexing, adapt the groups
to remove assumptions that channel 0 is utilised in each group by using
the channel mask provided in the device
On 25/04/18 23:35, Ruslan Bilovol wrote:
On Tue, Apr 24, 2018 at 8:24 PM, Jorge Sanjuan
wrote:
This adds support for the MIXER UNIT in UAC3. All the information
is obtained from the (HIGH CAPABILITY) Cluster's header. We don't
read the rest of the logical
On 25/04/18 23:35, Ruslan Bilovol wrote:
On Tue, Apr 24, 2018 at 8:24 PM, Jorge Sanjuan
wrote:
This adds support for the MIXER UNIT in UAC3. All the information
is obtained from the (HIGH CAPABILITY) Cluster's header. We don't
read the rest of the logical cluster to obtain the channel
On Tue, Apr 24, 2018 at 02:44:40PM +0100, Gustavo Pimentel wrote:
> Adds a seconds entry on the pci_epf_test_ids structure that disables the
"Add a second entry to..."
> linkup_notifier parameter on driver for the designware EP.
>
> This allows designware EPs that doesn't have linkup
On Tue, Apr 24, 2018 at 02:44:40PM +0100, Gustavo Pimentel wrote:
> Adds a seconds entry on the pci_epf_test_ids structure that disables the
"Add a second entry to..."
> linkup_notifier parameter on driver for the designware EP.
>
> This allows designware EPs that doesn't have linkup
SPARC M7 and newer processors utilize ADI to version and
protect memory. This driver is capable of reading/writing
ADI/MCD versions from privileged user space processes.
Addresses in the adi file are mapped linearly to physical
memory at a ratio of 1:adi_blksz. Thus, a read (or write)
of offset
SPARC M7 and newer processors utilize ADI to version and
protect memory. This driver is capable of reading/writing
ADI/MCD versions from privileged user space processes.
Addresses in the adi file are mapped linearly to physical
memory at a ratio of 1:adi_blksz. Thus, a read (or write)
of offset
ADI is a feature supported on SPARC M7 and newer processors to allow
hardware to catch rogue accesses to memory. ADI is supported for data
fetches only and not instruction fetches. An app can enable ADI on its
data pages, set version tags on them and use versioned addresses to
access the data
ADI is a feature supported on SPARC M7 and newer processors to allow
hardware to catch rogue accesses to memory. ADI is supported for data
fetches only and not instruction fetches. An app can enable ADI on its
data pages, set version tags on them and use versioned addresses to
access the data
Add a selftest for the sparc64 privileged ADI driver. These
tests verify the read(), pread(), write(), pwrite(), and seek()
functionality of the driver. The tests also report simple
performance statistics:
Syscall CallAvgTime AvgSize
Count (ticks) (bytes)
Add a selftest for the sparc64 privileged ADI driver. These
tests verify the read(), pread(), write(), pwrite(), and seek()
functionality of the driver. The tests also report simple
performance statistics:
Syscall CallAvgTime AvgSize
Count (ticks) (bytes)
Include the r8a77965-sysc header to provide power domain enumerations
and definitions.
Signed-off-by: Kieran Bingham
---
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git
Hi Peter,
On Thu, Apr 26, 2018 at 05:53:35PM +0200, Peter Zijlstra wrote:
> On Thu, Apr 26, 2018 at 11:34:19AM +0100, Will Deacon wrote:
> > @@ -290,58 +312,50 @@ void queued_spin_lock_slowpath(struct qspinlock
> > *lock, u32 val)
> > }
> >
> > /*
> > +* If we observe any
The SoC dtsi includes the generic renesas-cpg-mssr header, which does
not contain all of the relevant SoC specific definitions.
Adapt this to be the r8a77965 specific header.
Signed-off-by: Kieran Bingham
---
arch/arm64/boot/dts/renesas/r8a77965.dtsi |
Include the r8a77965-sysc header to provide power domain enumerations
and definitions.
Signed-off-by: Kieran Bingham
---
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a77965.dtsi
Hi Peter,
On Thu, Apr 26, 2018 at 05:53:35PM +0200, Peter Zijlstra wrote:
> On Thu, Apr 26, 2018 at 11:34:19AM +0100, Will Deacon wrote:
> > @@ -290,58 +312,50 @@ void queued_spin_lock_slowpath(struct qspinlock
> > *lock, u32 val)
> > }
> >
> > /*
> > +* If we observe any
The SoC dtsi includes the generic renesas-cpg-mssr header, which does
not contain all of the relevant SoC specific definitions.
Adapt this to be the r8a77965 specific header.
Signed-off-by: Kieran Bingham
---
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 2 +-
1 file changed, 1 insertion(+), 1
The DU entity node has been previously added but only as a placeholder.
Populate the node with the properties to use the device.
Signed-off-by: Kieran Bingham
---
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 14 +-
1 file changed, 13
The DU entity node has been previously added but only as a placeholder.
Populate the node with the properties to use the device.
Signed-off-by: Kieran Bingham
---
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git
From: Takeshi Kihara
The DU1 external dot clock is provided by the fixed frequency clock
generator X21, while the DU0 and DU3 clocks are provided by the
programmable Versaclock6 clock generator.
Signed-off-by: Takeshi Kihara
From: Takeshi Kihara
The DU1 external dot clock is provided by the fixed frequency clock
generator X21, while the DU0 and DU3 clocks are provided by the
programmable Versaclock6 clock generator.
Signed-off-by: Takeshi Kihara
Signed-off-by: Kieran Bingham
---
The R8A77965 (M3-N) SoC provides VGA, HDMI and LVDS output.
This platform is unusual in that the VGA is connected to DU3 leaving DU2
unpopulated. This is reflected by the channel_mask accordingly.
Signed-off-by: Kieran Bingham
---
The R8A77965 (M3-N) SoC provides VGA, HDMI and LVDS output.
This platform is unusual in that the VGA is connected to DU3 leaving DU2
unpopulated. This is reflected by the channel_mask accordingly.
Signed-off-by: Kieran Bingham
---
drivers/gpu/drm/rcar-du/rcar_du_drv.c | 29
From: Takeshi Kihara
Enable the HDMI encoder for the M3N Salvator-X board and hook it up to
the HDMI connector.
Based on a similar patches of the the Salvator-X board
on the R8A7796 SoC device tree
by Laurent Pinchart
From: Takeshi Kihara
Enable the HDMI encoder for the M3N Salvator-X board and hook it up to
the HDMI connector.
Based on a similar patches of the the Salvator-X board
on the R8A7796 SoC device tree
by Laurent Pinchart
Signed-off-by: Takeshi Kihara
Signed-off-by: Kieran Bingham
---
The FCPs handle the interface between various IP cores and memory. Add
the instances related to the FDPs and VSP2s.
Based on a similar patch of the R8A7796 device tree
by Laurent Pinchart .
Signed-off-by: Takeshi Kihara
The FCPs handle the interface between various IP cores and memory. Add
the instances related to the FDPs and VSP2s.
Based on a similar patch of the R8A7796 device tree
by Laurent Pinchart .
Signed-off-by: Takeshi Kihara
[Kieran: Rebase to top of tree]
Signed-off-by: Kieran Bingham
---
The DU output table lists the port combinations for each supported DU
type. Newer models of R-Car Gen3 platforms have an increased string
length.
Increase the table indentation in preparation for supporting new target
types.
Signed-off-by: Kieran Bingham
The DU output table lists the port combinations for each supported DU
type. Newer models of R-Car Gen3 platforms have an increased string
length.
Increase the table indentation in preparation for supporting new target
types.
Signed-off-by: Kieran Bingham
---
On 26 April 2018 at 14:06, Hans de Goede wrote:
> Hi All,
>
> Here is v4 of my patch-set to add support for EFI embedded fw to the kernel.
>
> Changes since v3:
> -Drop note in docs about EFI_FIRMWARE_VOLUME_PROTOCOL, it is not part of
> UEFI proper, so the EFI maintainers
On 26 April 2018 at 14:06, Hans de Goede wrote:
> Hi All,
>
> Here is v4 of my patch-set to add support for EFI embedded fw to the kernel.
>
> Changes since v3:
> -Drop note in docs about EFI_FIRMWARE_VOLUME_PROTOCOL, it is not part of
> UEFI proper, so the EFI maintainers don't want us
901 - 1000 of 2428 matches
Mail list logo