Tegra210 and prior Tegra chips have deep sleep entry and wakeup related
timings which are platform specific that should be configured before
entering into deep sleep.
Below are the timing specific configurations for deep sleep entry and
wakeup.
- Core rail power-on stabilization timer
- OSC clock
This patch configures polarity of the core power request signal
in PMC control register based on the device tree property.
PMC asserts and de-asserts power request signal based on it polarity
when it need to power-up and power-down the core rail during SC7.
Reviewed-by: Dmitry Osipenko
Signed-of
This patch updates device tree for RTC and PMC to allow system wake
from deep sleep on RTC alarm.
Signed-off-by: Sowjanya Komatineni
---
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210.dtsi
b/ar
This patch has Jetson TX1 platform specific SC7 timing configuration
in device tree.
Signed-off-by: Sowjanya Komatineni
---
arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi
b/arch/arm64/boot/
This patch uses fence_udelay rather than udelay during PLLU
initialization to ensure writes to clock registers happens before
waiting for specified delay.
Acked-by: Thierry Reding
Signed-off-by: Sowjanya Komatineni
---
drivers/clk/tegra/clk-tegra210.c | 8
1 file changed, 4 insertions(
This patch implements DFLL suspend and resume operation.
During system suspend entry, CPU clock will switch CPU to safe
clock source of PLLP and disables DFLL clock output.
DFLL driver suspend confirms DFLL disable state and errors out on
being active.
DFLL is re-initialized during the DFLL driv
This patch implements save and restore of PLL context.
During system suspend, core power goes off and looses the settings
of the Tegra CAR controller registers.
So during resume, pll context is restored based on cached rate
and state.
Acked-by: Thierry Reding
Signed-off-by: Sowjanya Komatineni
Hi,
On 8/16/19 3:52 PM, Heikki Krogerus wrote:
On Fri, Aug 16, 2019 at 04:45:50PM +0300, Andy Shevchenko wrote:
On Fri, Aug 16, 2019 at 1:45 PM Heikki Krogerus
wrote:
The primary purpose for this node will be to allow linking
the users of the switch to it. The users will be for example
USB T
This patch series includes Tegra210 deepsleep (SC7) support with RTC alarm
wake event.
This series also includes save and restore of PLLs, clocks, OSC contexts
for deepsleep exit to normal operation.
This patch series doesn't support 100% suspend/resume to allow fully
functional state upon resume
This patch adds support for saving OSC clock frequency and the
drive-strength during OSC clock init and creates an API to restore
OSC control register value from the saved context.
This API is invoked by Tegra210 clock driver during system resume
to restore the OSC clock settings.
Acked-by: Thie
On Fri, Aug 16, 2019 at 2:44 AM Bhushan Shah wrote:
>
> Allwinner H6 have a mv64xxx i2c interface available to be used.
>
> Signed-off-by: Bhushan Shah
> ---
>
> Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml | 3 +++
> 1 file changed, 3 insertions(+)
Reviewed-by: Rob Herring
> -Original Message-
> From: Vitaly Kuznetsov
> Sent: Friday, August 16, 2019 12:16 PM
> To: Haiyang Zhang
> Cc: KY Srinivasan ; Stephen Hemminger
> ; linux-kernel@vger.kernel.org;
> sas...@kernel.org; da...@davemloft.net; sae...@mellanox.com;
> l...@kernel.org; era...@mellanox.com; lo
Hi arm-soc maintainers,
Please look into the following changes and merge them if they
look good.
Regards,
Leo
The following changes since commit 157eed91b374c42eb264157366daf3dabc8bc816:
Merge tag 'tee-optee-for-5.4' of
git://git.linaro.org/people/jens.wiklander/linux-tee into arm/drivers
(
On Fri, Aug 16, 2019 at 1:04 AM Laurentiu Tudor wrote:
>
> Hi Leo,
>
> > -Original Message-
> > From: Li Yang
> > Sent: Friday, August 16, 2019 2:13 AM
> > To: Ioana Ciornei
> > Cc: Laurentiu Tudor ; Roy Pledge
> > ; lkml
> > Subject: Re: [PATCH 1/3] bus: fsl-mc: remove explicit device_
From: Denis Efremov
Date: Wed, 14 Aug 2019 15:58:00 +0300
> Update MAINTAINERS to reflect that sysfs-bus-mdio was removed in
> commit a6cd0d2d493a ("Documentation: net-sysfs: Remove duplicate
> PHY device documentation") and sysfs-class-net-phydev was added in
> commit 86f22d04dfb5 ("net: sysfs:
(Found this mail in the offline draft folder of another laptop)
> So, then the current approach of using subsys_initcall() can't be
> changed easily, right now. But planned for the future (or at least
> not introducing new caes).
Yes.
> But: how does that conflict w/ just moving the existing re
On 8/7/2019 6:35 PM, Fuqian Huang wrote:
Remove the redundant initialization code.
Signed-off-by: Fuqian Huang
---
Looks good!
Reviewed-by: James Smart
-- james
From: Denis Efremov
Date: Wed, 14 Aug 2019 15:12:09 +0300
> Update MAINTAINERS record to reflect the filename change.
> The file was moved in commit 25e992a4603c ("r8169: rename
> r8169.c to r8169_main.c")
>
> Cc: Heiner Kallweit
> Cc: nic_s...@realtek.com
> Cc: David S. Miller
> Cc: net...@vg
On Sat, 2019-08-10 at 13:33 -0700, Joe Perches wrote:
> On Sat, 2019-08-10 at 13:18 -0700, Joe Perches wrote:
[]
> > There are classes of patches generated by scripts that have
> > no real mechanism to be applied today.
> >
> > For instance: global coccinelle scripted changes to use stracpy
> > ht
Hi Shuah,
Thanks for the patches.
On 8/15/19 4:42 PM, Shuah Khan wrote:
> vimc uses Component API to split the driver into functional components.
> The real hardware resembles a monolith structure than component and
> component structure added a level of complexity making it hard to
> maintain wi
On Fri, Aug 16, 2019 at 12:43:02PM -0700, mario.limoncie...@dell.com wrote:
> > We need to coordinate with Jens, don't think its a good idea if I'll
> > just randomly get stuff from linus' tree and send an rc pull request.
>
> The dependent commit is in Linus' tree now.
> 4eaefe8c621c6195c91044396
On Fri, 16 Aug 2019, Andy Lutomirski wrote:
> On 8/15/19 9:38 AM, Dmitry Safonov wrote:
> > As it has been discussed on timens RFC, adding a new conditional branch
> > `if (inside_time_ns)` on VDSO for all processes is undesirable.
> > It will add a penalty for everybody as branch predictor may mis
On Tue 2019-08-13 12:11:47, Matthias Kaehlcke wrote:
> Add a .config_led hook which is called by the PHY core when
> configuration data for a PHY LED is available. Each LED can be
> configured to be solid 'off, solid 'on' for certain (or all)
> link speeds or to blink on RX/TX activity.
>
> Signed
Hi!
Please Cc led mailing lists on led issues.
On Tue 2019-08-13 12:11:44, Matthias Kaehlcke wrote:
> The LED behavior of some Ethernet PHYs is configurable. Add an
> optional 'leds' subnode with a child node for each LED to be
> configured. The binding aims to be compatible with the common
> LE
One of the components in LiteON CL1 device has limitations that
can be encountered based upon boundary race conditions using the
nvme bus specific suspend to idle flow.
When this situation occurs the drive doesn't resume properly from
suspend-to-idle.
LiteON has confirmed this problem and fixed i
From: Arnaldo Carvalho de Melo
Sometime we want to only consider events after something happens, so
allow discarding events till such events is found, e.g.:
Record all scheduler tracepoints and the sys_enter_nanosleep syscall
event for the 'sleep 1' workload:
# perf record -e sched:*,syscalls
From: Haiyan Song
Add a Intel event file for perf.
Signed-off-by: Haiyan Song
Reviewed-by: Kan Liang
Cc: Alexander Shishkin
Cc: Andi Kleen
Cc: Jin Yao
Cc: Jiri Olsa
Cc: Peter Zijlstra
Link: http://lkml.kernel.org/r/20190815035942.30602-1-haiyanx.s...@intel.com
Signed-off-by: Arnaldo Carva
/scm/linux/kernel/git/acme/linux into perf/core
(2019-08-15 11:10:38 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-core-for-mingo-5.4-20190816
for you to fetch changes up to e2736219e6ca3117e10651e215b96d66775220da:
p
From: Arnaldo Carvalho de Melo
Now other tools that want switching can use an evswitch for that, just
set it up and add it to the PERF_RECORD_SAMPLE processing function.
Cc: Adrian Hunter
Cc: Florian Weimer
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: William Cohen
Link: https://lkml.kernel.org/n/tip
From: Arnaldo Carvalho de Melo
If the user specifies a on or off switch event and it isn't in the
perf.data file, provide a hint about how to see the events in the
perf.data evlist:
# perf script --switch-on=syscall:sys_enter_nanosleep
--switch-off=syscalls:sys_exit_nanosleep
ERROR: event_o
From: Arnaldo Carvalho de Melo
All tools will want those, so provide a convenient way to get them.
Cc: Adrian Hunter
Cc: Florian Weimer
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: William Cohen
Link: https://lkml.kernel.org/n/tip-v16pe3sbf3wjmn152u18f...@git.kernel.org
Signed-off-by: Arnaldo Carvalh
From: Arnaldo Carvalho de Melo
So that we can have macros for the OPT_ entries and also for finding
those in an evlist, this way other tools will use this very easily.
Cc: Adrian Hunter
Cc: Florian Weimer
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: William Cohen
Link: https://lkml.kernel.org/n/tip-q
From: Arnaldo Carvalho de Melo
Now that we see that the simple userspace-based "slicing" of events
using delimiter events ("markers") works, lets move it to a separate
header to make it available to other tools, next step will be having
the switch on/off check done at the PERF_RECORD_SAMPLE proce
From: Arnaldo Carvalho de Melo
One may want to see the --switch-on event as well, allow for that, using
the previous cset example:
# perf script --switch-on syscalls:sys_enter_nanosleep --show-on-off
sleep 13638 [001] 108237.582286: syscalls:sys_enter_nanosleep: rqtp:
0x7fff1948ac40,
From: Arnaldo Carvalho de Melo
Another step in having all the boilerplate in just one place to then use
in the other tools.
Cc: Adrian Hunter
Cc: Florian Weimer
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: William Cohen
Link: https://lkml.kernel.org/n/tip-snreb1wmwyjei3eefwotx...@git.kernel.org
Signe
From: Arnaldo Carvalho de Melo
Allows adding hints there, will be done in followup patch.
Cc: Adrian Hunter
Cc: Florian Weimer
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: William Cohen
Link: https://lkml.kernel.org/n/tip-1kvrdi7weuz3hxycwvarc...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
From: Arnaldo Carvalho de Melo
Counterpart of --switch-on:
# perf record -e sched:*,syscalls:sys_*_nanosleep sleep 1
[ perf record: Woken up 36 times to write data ]
[ perf record: Captured and wrote 0.032 MB perf.data (10 samples) ]
#
# perf script
:20918 20918 [002] 109866.1436
From: Arnaldo Carvalho de Melo
Just like 'perf trace' and 'perf script', should be useful for instance
to only consider samples after the initialization phase of some
workload.
The man page has some examples and considerations about its current
interface, that still doesn't handle the on/off eve
From: John Keeping
If dwarf_callchain_users is false, then unwind__prepare_access() will
not set unwind_libunwind_ops so the remaining test here is sufficient.
Signed-off-by: John Keeping
Reviewed-by: Jiri Olsa
Cc: Alexander Shishkin
Cc: Konstantin Khlebnikov
Cc: Namhyung Kim
Cc: Peter Zijl
From: Arnaldo Carvalho de Melo
Just like with 'perf script':
# perf trace -e sched:*,syscalls:*sleep* sleep 1
0.000 :28345/28345 sched:sched_waking:comm=perf pid=28346 prio=120
target_cpu=005
0.005 :28345/28345 sched:sched_wakeup:perf:28346 [120] success=1 CPU:005
0.383 s
From: John Keeping
Commit e5adfc3e7e77 ("perf map: Synthesize maps only for thread group
leader") changed the recording side so that we no longer get mmap events
for threads other than the thread group leader (when synthesising these
events for threads which exist before perf is started).
When a
From: Arnaldo Carvalho de Melo
Since 'perf top' shares the histogram browser with 'perf report', then
the same explanation in the previous cset applies.
An additional example uses a pair of SDT events available for systemtap:
# perf probe --exec=/usr/bin/stap '%*:*'
Added new events:
sd
From: John Keeping
In the next commit we will add new fields to map_groups and we need
these to be null if no value is assigned. The simplest way to achieve
this is to request zeroed memory from the allocator.
Signed-off-by: John Keeping
Reviewed-by: Jiri Olsa
Cc: Alexander Shishkin
Cc: Kons
Hi Thomas,
On Fri, Aug 16, 2019 at 02:28:42PM +0200, Thomas Gleixner wrote:
> On Tue, 13 Aug 2019, YueHaibing wrote:
>
> > While do COMPILE_TEST building, if GENERIC_IRQ_CHIP is
> > not selected, it fails:
> >
> > drivers/irqchip/irq-ingenic-tcu.o: In function `ingenic_tcu_intc_cascade':
> > irq
Hi Thomas,
On 8/15/19 8:21 PM, Thomas Gleixner wrote:
> On Thu, 15 Aug 2019, Dmitry Safonov wrote:
>> ---
>> arch/Kconfig | 5 +++
>> arch/x86/Kconfig | 1 +
>> arch/x86/entry/vdso/vdso-layout.lds.S | 9 -
>> arch/x86/entry/vdso/vdso2c.c
On 02.08.2019 12.33, Rafael J. Wysocki wrote:
Hi All,
On top of the "Simplify the suspend-to-idle control flow" patch series
posted previously:
https://lore.kernel.org/lkml/71085220.z6FKkvYQPX@kreacher/
sanitize the suspend-to-idle flow even further.
First off, decouple EC wakeup from the LP
Dan Williams writes:
> In the process of debugging a system with an NVDIMM that was failing to
> unlock it was found that the kernel is reporting 'locked' while the DIMM
> security interface is 'frozen'. Unfortunately the security state is
> tracked internally as an enum which prevents it from co
Hi Shuah,
Thanks for the patch, just some small comments below.
On 8/15/19 4:42 PM, Shuah Khan wrote:
> vimc uses Component API to split the driver into functional components.
> The real hardware resembles a monolith structure than component and
> component structure added a level of complexity m
On Fri, 16 Aug 2019, Paul Burton wrote:
> On Fri, Aug 16, 2019 at 02:28:42PM +0200, Thomas Gleixner wrote:
> > On Tue, 13 Aug 2019, YueHaibing wrote:
> >
> > > While do COMPILE_TEST building, if GENERIC_IRQ_CHIP is
> > > not selected, it fails:
> > >
> > > drivers/irqchip/irq-ingenic-tcu.o: In fu
On Fri, Aug 16, 2019 at 3:19 PM Alan Stern wrote:
>
> On Fri, 16 Aug 2019, Mathieu Desnoyers wrote:
>
> > If you choose not to use READ_ONCE(), then the "load tearing" issue can
> > cause similar spurious 1 -> 0 -> 1 transitions near 16-bit counter
> > overflow as described above. The "Invented lo
Dan Williams writes:
> The blanket blocking of all security operations while the DIMM is in
> active use in a region is too restrictive. The only security operations
> that need to be aware of the ->busy state are those that mutate the
> state of data, i.e. erase and overwrite.
>
> Refactor the -
On Fri, 16 Aug 2019, Joel Fernandes wrote:
> On Fri, Aug 16, 2019 at 3:19 PM Alan Stern wrote:
> > On Fri, 16 Aug 2019, Mathieu Desnoyers wrote:
> >
> > > If you choose not to use READ_ONCE(), then the "load tearing" issue can
> > > cause similar spurious 1 -> 0 -> 1 transitions near 16-bit counte
On Fri, 16 Aug 2019 16:44:10 -0400
Joel Fernandes wrote:
> I am also more on the side of using *_ONCE. To me, by principal, I
> would be willing to convert any concurrent plain access using _ONCE,
> just so we don't have to worry about it now or in the future and also
> documents the access.
>
Commit-ID: f90a24171a8179a29e5e1532fd5bb94e59b5380e
Gitweb: https://git.kernel.org/tip/f90a24171a8179a29e5e1532fd5bb94e59b5380e
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 14 Aug 2019 16:20:13 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 15 Aug 2019 12:23:58 -0300
p
Commit-ID: 11e54d35e6d5c3533b706753224ef38ea235684b
Gitweb: https://git.kernel.org/tip/11e54d35e6d5c3533b706753224ef38ea235684b
Author: Haiyan Song
AuthorDate: Thu, 15 Aug 2019 11:59:42 +0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 15 Aug 2019 12:04:04 -0300
perf vendor ev
Commit-ID: 6469eb6dffeb44edfa3d4ca496b044b4a9c643b9
Gitweb: https://git.kernel.org/tip/6469eb6dffeb44edfa3d4ca496b044b4a9c643b9
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 14 Aug 2019 16:40:58 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 15 Aug 2019 12:24:08 -0300
p
Dan Williams writes:
> The security operations are exported from libnvdimm/security.c to
> libnvdimm/dimm_devs.c, and libnvdimm/security.c is optionally compiled
> based on the CONFIG_NVDIMM_KEYS config symbol.
>
> Rather than export the operations across compile objects, just move the
> __securi
Commit-ID: dd41f660c03a6d8f2c2f3b2cccf50d8c4e06dd42
Gitweb: https://git.kernel.org/tip/dd41f660c03a6d8f2c2f3b2cccf50d8c4e06dd42
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 14 Aug 2019 16:51:28 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 15 Aug 2019 12:24:16 -0300
p
On Fri, 16 Aug 2019 10:35:24 +0800
Tina Zhang wrote:
> Introduce vGPU specific irq type VFIO_IRQ_TYPE_GFX, and
> VFIO_IRQ_SUBTYPE_GFX_DISPLAY_IRQ as the subtype for vGPU display.
>
> Introduce vfio_irq_info_cap_display_plane_events capability to notify
> user space with the vGPU's plane update e
On Fri, 16 Aug 2019 10:35:23 +0800
Tina Zhang wrote:
> Cap the number of irqs with fixed indexes and use capability chains
> to chain device specific irqs.
>
> Signed-off-by: Tina Zhang
> Signed-off-by: Eric Auger
> ---
> include/uapi/linux/vfio.h | 19 ++-
> 1 file changed, 1
Commit-ID: d2360442725fd29b3189887476c57059854a398c
Gitweb: https://git.kernel.org/tip/d2360442725fd29b3189887476c57059854a398c
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 15 Aug 2019 10:37:24 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 15 Aug 2019 12:24:24 -0300
p
On 8/16/19 8:23 AM, Greg Kroah-Hartman wrote:
> On Fri, Aug 16, 2019 at 07:05:06AM -0700, Frank Rowand wrote:
>> i Greg,
>>
>> On 8/16/19 2:10 AM, Greg Kroah-Hartman wrote:
>>> On Thu, Aug 15, 2019 at 08:09:19PM -0700, Frank Rowand wrote:
Hi Saravana,
On 8/15/19 6:50 PM, Saravana Kan
Commit-ID: 8829e56fa050998164e496d380cd69186ae9b8d0
Gitweb: https://git.kernel.org/tip/8829e56fa050998164e496d380cd69186ae9b8d0
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 15 Aug 2019 11:00:11 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 15 Aug 2019 12:24:31 -0300
p
Commit-ID: 0b495b121585a1b6ca120fe13f950e2f86ca8197
Gitweb: https://git.kernel.org/tip/0b495b121585a1b6ca120fe13f950e2f86ca8197
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 15 Aug 2019 11:11:14 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 15 Aug 2019 12:24:42 -0300
p
On 8/16/19 1:52 PM, Frank Rowand wrote:
> On 8/16/19 8:23 AM, Greg Kroah-Hartman wrote:
>> On Fri, Aug 16, 2019 at 07:05:06AM -0700, Frank Rowand wrote:
>>> i Greg,
>>>
>>> On 8/16/19 2:10 AM, Greg Kroah-Hartman wrote:
On Thu, Aug 15, 2019 at 08:09:19PM -0700, Frank Rowand wrote:
> Hi Sara
This series adds support for Tanix TX6 box:
- Allwinner H6 Quad-core 64-bit ARM Cortex-A53
- GPU Mali-T720
- 4GiB DDR3 RAM (3GiB useable)
- 100Mbps EMAC via AC200 EPHY
- Cdtech 47822BS Wifi/BT
- 2x USB 2.0 Host and 1x USB 3.0 Host
- HDMI port
- IR receiver
- 64GiB eMMC
- 5V/2A DC power supply
Patc
Add new Oranth Tanix TX6 board compatible string to the bindings
documentation.
Signed-off-by: Jernej Skrabec
---
Documentation/devicetree/bindings/arm/sunxi.yaml | 5 +
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/sunxi.yaml
b/Documentation/devicetree
Tanix TX6 is an Allwinner H6 based TV box, which supports:
- Allwinner H6 Quad-core 64-bit ARM Cortex-A53
- GPU Mali-T720
- 4GiB DDR3 RAM (3GiB useable)
- 100Mbps EMAC via AC200 EPHY
- Cdtech 47822BS Wifi/BT
- 2x USB 2.0 Host and 1x USB 3.0 Host
- HDMI port
- IR receiver
- 64GiB eMMC
- 5V/2A DC pow
Commit-ID: add3a719c95f0443d563889b4af255b78ba54521
Gitweb: https://git.kernel.org/tip/add3a719c95f0443d563889b4af255b78ba54521
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 15 Aug 2019 11:21:21 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 15 Aug 2019 12:25:47 -0300
p
Commit-ID: 124e02be72fdff05ab5d7f004a3c0d4061569380
Gitweb: https://git.kernel.org/tip/124e02be72fdff05ab5d7f004a3c0d4061569380
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 15 Aug 2019 11:31:29 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 15 Aug 2019 12:25:55 -0300
p
Commit-ID: c9a4269930dada68971a4a97f3abf079af8cde4e
Gitweb: https://git.kernel.org/tip/c9a4269930dada68971a4a97f3abf079af8cde4e
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 15 Aug 2019 11:35:56 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 15 Aug 2019 12:26:04 -0300
p
Commit-ID: 8b3c9ea7bf8f50ead6787c084cfc6d3a0b1e38aa
Gitweb: https://git.kernel.org/tip/8b3c9ea7bf8f50ead6787c084cfc6d3a0b1e38aa
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 15 Aug 2019 12:02:13 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 15 Aug 2019 12:26:13 -0300
p
Commit-ID: 22ac4318ad95847797de99dccaf059c76cd74efe
Gitweb: https://git.kernel.org/tip/22ac4318ad95847797de99dccaf059c76cd74efe
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 15 Aug 2019 12:15:39 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 15 Aug 2019 12:26:21 -0300
p
On Fri, Aug 16, 2019 at 10:49:04PM +0200, Thomas Gleixner wrote:
> On Fri, 16 Aug 2019, Joel Fernandes wrote:
> > On Fri, Aug 16, 2019 at 3:19 PM Alan Stern
> > wrote:
> > > On Fri, 16 Aug 2019, Mathieu Desnoyers wrote:
> > >
> > > > If you choose not to use READ_ONCE(), then the "load tearing" i
Commit-ID: 2f53ae347f597842683c4bde5b9ce76f5efae247
Gitweb: https://git.kernel.org/tip/2f53ae347f597842683c4bde5b9ce76f5efae247
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 15 Aug 2019 16:03:26 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 15 Aug 2019 16:03:26 -0300
p
Commit-ID: ef4b1a539f4b8776701752c5a09ee741a4232ae6
Gitweb: https://git.kernel.org/tip/ef4b1a539f4b8776701752c5a09ee741a4232ae6
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 15 Aug 2019 18:18:58 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 16 Aug 2019 12:14:33 -0300
p
On 15.08.2019 17:32, Christian Herber wrote:
> This patch adds basic support for BASE-T1 PHYs in the framework.
> BASE-T1 PHYs main area of application are automotive and industrial.
> BASE-T1 is standardized in IEEE 802.3, namely
> - IEEE 802.3bw: 100BASE-T1
> - IEEE 802.3bp 1000BASE-T1
> - IEEE 8
On Fri, Aug 16, 2019 at 04:49:12PM -0400, Steven Rostedt wrote:
> On Fri, 16 Aug 2019 16:44:10 -0400
> Joel Fernandes wrote:
>
>
> > I am also more on the side of using *_ONCE. To me, by principal, I
> > would be willing to convert any concurrent plain access using _ONCE,
> > just so we don't ha
Commit-ID: ab6cd0e5276e24403751e0b3b8ed807738a8571f
Gitweb: https://git.kernel.org/tip/ab6cd0e5276e24403751e0b3b8ed807738a8571f
Author: John Keeping
AuthorDate: Thu, 15 Aug 2019 11:01:44 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 16 Aug 2019 12:25:23 -0300
perf map: Use
Commit-ID: e8ba2906f6b9054102ad035ac9cafad9d4168589
Gitweb: https://git.kernel.org/tip/e8ba2906f6b9054102ad035ac9cafad9d4168589
Author: John Keeping
AuthorDate: Thu, 15 Aug 2019 11:01:45 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 16 Aug 2019 12:25:57 -0300
perf unwind:
On Fri, 16 Aug 2019 08:54:34 +0200 Christoph Hellwig wrote:
> The kvmppc ultravisor code wants a device private memory pool that is
> system wide and not attached to a device. Instead of faking up one
> provide a low-level memremap_pages for it. Note that this function is
> not exported, and do
The latest feature release Git v2.23.0 is now available at the
usual places. It is comprised of 505 non-merge commits since
v2.22.0, contributed by 77 people, 26 of which are new faces.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/
The following public repositories
Commit-ID: e2736219e6ca3117e10651e215b96d66775220da
Gitweb: https://git.kernel.org/tip/e2736219e6ca3117e10651e215b96d66775220da
Author: John Keeping
AuthorDate: Thu, 15 Aug 2019 11:01:46 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 16 Aug 2019 12:30:14 -0300
perf unwind:
On Fri, 16 Aug 2019 15:21:25 +0800, Sam Shih wrote:
> From: Ryder Lee
>
> This updates bindings for MT7629 pwm controller.
>
> Signed-off-by: Ryder Lee
> Signed-off-by: Sam Shih
> Reviewed-by: Matthias Brugger
> ---
> Documentation/devicetree/bindings/pwm/pwm-mediatek.txt | 1 +
> 1 file cha
On Fri, 16 Aug 2019 08:54:31 +0200 Christoph Hellwig wrote:
> Just add a simple macro that passes a NULL dev argument to
> dev_request_free_mem_region, and call request_mem_region in the
> function for that particular case.
Nit:
> +struct resource *request_free_mem_region(struct resource *base,
On Fri, Aug 16, 2019 at 1:49 PM Jeff Moyer wrote:
>
> Dan Williams writes:
>
> > The blanket blocking of all security operations while the DIMM is in
> > active use in a region is too restrictive. The only security operations
> > that need to be aware of the ->busy state are those that mutate the
On Fri, Aug 16, 2019 at 1:49 PM Thomas Gleixner wrote:
>
> Can we finally put a foot down and tell compiler and standard committee
> people to stop this insanity?
It's already effectively done.
Yes, values can be read from memory multiple times if they need
reloading. So "READ_ONCE()" when the v
On Fri, 16 Aug 2019 14:32:58 +0200 Christoph Hellwig wrote:
> On Fri, Aug 16, 2019 at 11:57:40AM +, Jason Gunthorpe wrote:
> > Are there conflicts with trees other than hmm?
> >
> > We can put it on a topic branch and merge to hmm to resolve. If hmm
> > has problems then send the topic on it
tree:
https://kernel.googlesource.com/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
from-joel.2019.08.16a
head: 01b0e4d3e0ac279b295bc06a3591f0b810b9908f
commit: bda80ba9decc7a32413e88d2f070de180c4b76ab [143/172] rcu/tree: Add basic
support for kfree_rcu() batching
config: riscv-defconfig (a
On 15.08.2019 17:32, Christian Herber wrote:
> BASE-T1 is a category of Ethernet PHYs.
> They use a single copper pair for transmission.
> This patch add basic support for this category of PHYs.
> It coveres the discovery of abilities and basic configuration.
> It includes setting fixed speed and e
On Thu, Jul 25, 2019 at 02:50:45PM +0800, Richard Tresidder wrote:
> Signed-off-by: Richard Tresidder
> ---
>
> Notes:
> Add device tree binding documentation for addition of force_load
> boolean value to allow loading a battery during boot even if not
> present at that time.
> Ac
On Thu, Aug 15, 2019 at 9:20 AM Sean Christopherson
wrote:
>
> Jump to the common error handling in x86_decode_insn() if
> __do_insn_fetch_bytes() fails so that its error code is converted to the
> appropriate return type. Although the various helpers used by
> x86_decode_insn() return X86EMUL_*
Arul,
On Fri, 16 Aug 2019, Arul Jeniston wrote:
> Adding few more data points...
Can you please trim your replies? It's annoying to have to search for the
meat of your mail by scrolling down several pages and paying attention to
not skip something useful inside of useless information.
> On Fri,
On Thu, Jul 25, 2019 at 11:26:46AM +0100, Jan Kotas wrote:
> This patch adds a DT bindings documentation for
> Cadence CSI2RX v2.1 controller.
And 1.3?
>
> Signed-off-by: Jan Kotas
> ---
> Documentation/devicetree/bindings/media/cdns,csi2rx.txt | 4 +++-
> 1 file changed, 3 insertions(+), 1 de
On Thu, 25 Jul 2019 12:41:34 +0200, Niklas Cassel wrote:
> Some Qualcomm SoCs have support for Core Power Reduction (CPR).
> On these platforms, we need to attach to the power domain provider
> providing the performance states, so that the leaky device (the CPU)
> can configure the performance stat
On Fri, Aug 16, 2019 at 7:56 AM Stephen Boyd wrote:
>
> The device_set_wakeup_enable() function can be called on a device that
> hasn't been registered with device_add() yet. This allows the device to
> be in a state where wakeup is enabled for it but the device isn't
> published to userspace in s
On Fri, Aug 16, 2019 at 10:13:42PM +0200, Pavel Machek wrote:
> On Tue 2019-08-13 12:11:47, Matthias Kaehlcke wrote:
> > Add a .config_led hook which is called by the PHY core when
> > configuration data for a PHY LED is available. Each LED can be
> > configured to be solid 'off, solid 'on' for cer
On Thu, Jul 25, 2019 at 03:59:55PM +0100, Piotr Sroka wrote:
> Document the bindings used by Cadence NAND controller driver
>
> Signed-off-by: Piotr Sroka
> ---
> Changes for v5:
> - replace "_" by "-" in all properties
> - change compatible name from cdns,hpnfc to cdns,hp-nfc
> Changes for v4:
>
On Thu, 25 Jul 2019 18:18:30 +0300, Dmitry Osipenko wrote:
> There is voltage coupling between three regulators on Tegra20 boards and
> between two on Tegra30. The voltage coupling is a SoC-level feature and
> thus it is mandatory and common for all of the Tegra boards.
>
> Signed-off-by: Dmitry O
emap_pages+0x894/0xc70:
devm_memremap_pages at mm/memremap.c:307
[ 32.074412][ T294] WARNING: CPU: 31 PID: 294 at mm/kasan/init.c:496
kasan_add_zero_shadow.cold.2+0xc/0x39
[ 32.077448][ T294] Modules linked in:
[ 32.078614][ T294] CPU: 31 PID: 294 Comm: kworker/u97:1 Not tainted 5.3.0-
rc4-nex
601 - 700 of 817 matches
Mail list logo
