On Tue, Aug 27, 2019 at 09:10:13PM +0800, Peter Xu wrote:
> Since we've just removed the dependency of vm type in previous patch,
> now we can create the vm much earlier. Note that to move it earlier
> we used an approximation of number of extra pages but it should be
> fine.
>
> This prepares fo
On Wed 2019-08-28 18:49:29, Sergey Senozhatsky wrote:
> On (08/28/19 02:31), Brendan Higgins wrote:
> [..]
> > Previously KUnit assumed that printk would always be present, which is
> > not a valid assumption to make. Fix that by removing call to
> > vprintk_emit, and calling printk directly.
> >
On Tue, Aug 27, 2019 at 09:10:11PM +0800, Peter Xu wrote:
> The work is based on Thomas's s390 port for dirty_log_test.
>
> This series originates from "[PATCH] KVM: selftests: Detect max PA
> width from cpuid" [1] and one of Drew's comments - instead of keeping
> the hackish line to overwrite gue
On Wed, Aug 28, 2019 at 01:51:06PM +0200, Andrew Jones wrote:
> On Tue, Aug 27, 2019 at 09:10:11PM +0800, Peter Xu wrote:
> > The work is based on Thomas's s390 port for dirty_log_test.
> >
> > This series originates from "[PATCH] KVM: selftests: Detect max PA
> > width from cpuid" [1] and one of
Hi Rob,
Thank you for the review comments.
On 28/8/2019 7:39 PM, Rob Herring wrote:
On Tue, Aug 27, 2019 at 10:47 PM Ramuthevar, Vadivel MuruganX
wrote:
Hi Rob,
On 27/8/2019 8:39 PM, Rob Herring wrote:
On Tue, Aug 27, 2019 at 3:27 AM Ramuthevar,Vadivel MuruganX
wrote:
From: Ramuthevar Va
On Wed, Aug 28, 2019 at 12:10 PM Enric Balletbo i Serra
wrote:
> On 27/8/19 18:12, Arnd Bergmann wrote:
> > On Tue, Aug 27, 2019 at 6:08 PM Bjorn Andersson
> > wrote:
> >>
> >> On Tue 27 Aug 08:48 PDT 2019, Enric Balletbo i Serra wrote:
> >>
> >>> Recently we refactored the CrOS EC drivers moving
This reverts commit a0085f2510e8976614ad8f766b209448b385492f.
After this commit systems wake up at random, most commonly when
- put to sleep while bluetooth audio stream is running
- connected bluetooth audio device is powered off while system is
asleep
This is broken since the commit was mer
On 8/28/19 1:02 PM, Srinivas Neeli wrote:
> Case 1:
> can_put_echo_skb(); -> skb = can_create_echo_skb(skb); -> return skb;
>
> In can_create_echo_skb() not using the shared_skb, so we are returning the
> old skb.
> Storing the return value in "skb". But it's a pointer, for storing that need
> d
śr., 28 sie 2019 o 13:13 David Jander napisał(a):
>
> On Wed, 28 Aug 2019 12:56:28 +0200
> Bartosz Golaszewski wrote:
>
> > śr., 28 sie 2019 o 10:38 Bartosz Golaszewski
> > napisał(a):
> > >
> > > wt., 27 sie 2019 o 08:46 David Jander napisał(a):
> > > >
> > > > The type of reg_direction needs
On Wed, Aug 28, 2019 at 01:47:23PM +0200, Jiri Slaby wrote:
> Let's start with this one: do you really want me to get rid of (local)
> symbols like this? It would make backtraces completely misleading as the
> unwinder would put a name of the previous function (or some garbage,
> depending on unwin
On Wed, Aug 28, 2019 at 09:45:28AM +0200, Miklos Szeredi wrote:
> On Wed, Aug 21, 2019 at 7:38 PM Vivek Goyal wrote:
> >
> > From: Miklos Szeredi
>
> Nice patch, except I have no idea why I did this. Splice with
> FOPEN_DIRECT_IO seems to work fine without it.
I don't know either. I took it b
The patchsets add support for MediaTek hardware module named DVFSRC
(dynamic voltage and frequency scaling resource collector). The DVFSRC is
a HW module which is used to collect all the requests from both software
and hardware and turn into the decision of minimum operating voltage and
minimum DRA
Support power domain performance state, add header file for scp event.
Signed-off-by: Henry Chen
---
drivers/soc/mediatek/mtk-scpsys.c | 58 +++
drivers/soc/mediatek/mtk-scpsys.h | 22 +++
2 files changed, 80 insertions(+)
create mode 100644 drive
Add dvfsrc driver for MT8183
Signed-off-by: Henry Chen
---
drivers/soc/mediatek/Kconfig | 15 ++
drivers/soc/mediatek/Makefile | 1 +
drivers/soc/mediatek/mtk-dvfsrc.c | 374 ++
include/soc/mediatek/mtk_dvfsrc.h | 22 +++
4 files changed, 412 inse
Document the binding for enabling dvfsrc on MediaTek SoC.
Signed-off-by: Henry Chen
---
.../devicetree/bindings/soc/mediatek/dvfsrc.txt| 23 ++
include/dt-bindings/soc/mtk,dvfsrc.h | 14 +
2 files changed, 37 insertions(+)
create mode 100644 Doc
Add support for performance state of scpsys on mt8183 platform.
Signed-off-by: Henry Chen
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
i
Add a header to collect SIPs and add one SIP call to initialize power
management hardware for the SIP interface defined to access the SPM
handling vcore voltage and ddr rate changes on mt8183 (and most likely
later socs).
Signed-off-by: Henry Chen
---
include/soc/mediatek/mtk_sip.h | 17
Add DDR EMI provider dictating dram interconnect bus performance
found on MT8183-based platforms
Signed-off-by: Henry Chen
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
b/arch/arm64/boot/dts/mediate
Introduce Mediatek MT8183 specific provider driver using the
interconnect framework.
Signed-off-by: Henry Chen
---
drivers/interconnect/Kconfig| 1 +
drivers/interconnect/Makefile | 1 +
drivers/interconnect/mediatek/Kconfig | 13 ++
drivers/interconnect/mediatek/Mak
Enable dvfsrc on mt8183 platform.
Signed-off-by: Henry Chen
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
index a58999f..7512f84 100644
--- a/arch/arm64/
Add opp table on scpsys dt-bindings for Mediatek SoC.
Signed-off-by: Henry Chen
---
.../devicetree/bindings/soc/mediatek/scpsys.txt| 42 ++
1 file changed, 42 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/mediatek/scpsys.txt
b/Documentation/devicetree
On Wed 2019-08-28 14:16:28, Borislav Petkov wrote:
> On Wed, Aug 28, 2019 at 02:09:36PM +0200, Pavel Machek wrote:
> > Yes, and now AMD has patch to break it on *all* machines.
>
> It doesn't break all machines - you need to look at that patch again.
This is not a way to have an inteligent conver
Add interconnect provider dt-bindings for MT8183.
Signed-off-by: Henry Chen
---
.../devicetree/bindings/soc/mediatek/dvfsrc.txt| 9 +
include/dt-bindings/interconnect/mtk,mt8183-emi.h | 18 ++
2 files changed, 27 insertions(+)
create mode 100644 include/dt-
On Wed, Aug 28, 2019 at 11:57 AM Sakari Ailus
wrote:
>
> Hi Rafael,
>
> On Wed, Aug 28, 2019 at 10:55:42AM +0200, Rafael J. Wysocki wrote:
> > On Mon, Aug 26, 2019 at 3:34 PM Greg Kroah-Hartman
> > wrote:
> > >
> > > On Mon, Aug 26, 2019 at 01:32:00PM +0300, Sakari Ailus wrote:
> > > > Hi Greg,
>
On Wed, Aug 28, 2019 at 11:22:37AM +0200, Greg Kroah-Hartman wrote:
> On Tue, Aug 27, 2019 at 01:41:49PM -0700, Hridya Valsaraju wrote:
> > Currently, all binder state and statistics live in debugfs.
> > We need this information even when debugfs is not mounted.
> > This patch adds the mount option
Detect and allow appended signatures.
Signed-off-by: Mimi Zohar
---
.../selftests/kexec/test_kexec_file_load.sh| 38 +++---
1 file changed, 34 insertions(+), 4 deletions(-)
diff --git a/tools/testing/selftests/kexec/test_kexec_file_load.sh
b/tools/testing/selftests/kexe
On Sat, 2019-08-10 at 05:28 +, Yangtao Li wrote:
> To unify code style.
>
> Signed-off-by: Yangtao Li
the later patches in this series does not change Makefile.
So this seems to be a cleanup patch independent of this patch set.
It's better to remove this patch from this patch series.
thanks
From: Ramuthevar Vadivel Murugan
Add a YAML schema to use the host controller driver with the
SDXC PHY on Intel's Lightning Mountain SoC.
Signed-off-by: Ramuthevar Vadivel Murugan
---
.../bindings/phy/intel,lgm-sdxc-phy.yaml | 52 ++
.../devicetree/bindings/phy/i
Add support for SDXC PHY on Intel's Lightning Mountain SoC.
Signed-off-by: Ramuthevar Vadivel Murugan
---
Ramuthevar Vadivel Murugan (2):
dt-bindings: phy: intel-sdxc-phy: Add YAML schema for LGM SDXC PHY
changes in v2:
- As per Rob's review comments added syscon properties.
phy: int
From: Ramuthevar Vadivel Murugan
Add support for SDXC PHY on Intel's Lightning Mountain SoC.
Signed-off-by: Ramuthevar Vadivel Murugan
---
drivers/phy/intel/Kconfig | 6 ++
drivers/phy/intel/Makefile | 1 +
drivers/phy/intel/phy-intel-sdxc.c | 144
On Sat, 2019-08-10 at 05:28 +, Yangtao Li wrote:
> Here, we do something to prepare for the subsequent
> support of multiple platforms.
>
> 1) rename sun50i_ths_calibrate to sun8i_ths_calibrate, because
>this function should be suitable for all platforms now.
>
> 2) introduce calibrate ca
Neil,
On Thu, 22 Aug 2019, Neil Horman wrote:
Just a few nits.
> On Intel hardware, cpus are limited in the number of irqs they can
> have affined to them (currently 240), based on section 10.5.2 of:
> https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-so
On Mon, Aug 26, 2019 at 02:59:15PM -0500, Kim Phillips wrote:
> The core AMD PMU has a 4-bit wide per-cycle increment for each
> performance monitor counter. That works for most counters, but
> now with AMD Family 17h and above processors, for some, more than 15
> events can occur in a cycle. Tho
Le 28/08/2019 à 12:30, Michal Suchanek a écrit :
There are numerous references to 32bit functions in generic and 64bit
code so ifdef them out.
As far as possible, avoid opting things out with ifdefs. Ref
https://www.kernel.org/doc/html/latest/process/coding-style.html#conditional-compilatio
The following commit has been merged into the x86/apic branch of tip:
Commit-ID: 743dac494d61d991967ebcfab92e4f80dc7583b3
Gitweb:
https://git.kernel.org/tip/743dac494d61d991967ebcfab92e4f80dc7583b3
Author:Neil Horman
AuthorDate:Thu, 22 Aug 2019 10:34:21 -04:00
Committer:
On Wed, 2019-08-28 at 09:11 +0200, Pavel Machek wrote:
> On Tue 2019-08-27 09:50:14, Greg Kroah-Hartman wrote:
> > [ Upstream commit dea1bb35c5f35e0577cfc61f79261d80b8715221 ]
> >
> > People are reporing seeing fscache errors being reported concerning
> > duplicate cookies even in cases where they
On Sun, Aug 25, 2019 at 5:06 PM Alejandro González
wrote:
> Jernej Skrabec compared the BSP driver with this
> driver, and found that the BSP driver configures pinctrl to operate at
> 1.8 V when entering DDR mode (although 3.3 V operation is supported), while
> the mainline kernel lacks any mecha
After commit 0688e64bc600 ("NFS: Allow signal interruption of NFS4ERR_DELAYed
operations") my NFS client dumps lockdep warnings:
WARNING: dir_create.sh/1911 still has locks held!
5.3.0-rc6.47364e5cdc #1 Not tainted
--
On Wed, Aug 28, 2019 at 11:27:39AM +0200, Sebastian Andrzej Siewior wrote:
> On 2019-08-27 08:53:06 [-0700], Paul E. McKenney wrote:
> > > > On the other hand, within a PREEMPT=n kernel, the call to schedule()
> > > > would split even an rcu_read_lock() critical section. Which is why I
> > > > ask
v4:
Add Fixes tag for both patch #1 and #2.
v3:
Update the commit message for patch #1.
v2:
Replace patch #2 with "r8152: remove calling netif_napi_del".
v1:
The commit 0ee1f4734967 ("r8152: napi hangup fix after disconnect")
add a check to avoid using napi_disable after netif_napi_del. However,
Remove unnecessary use of netif_napi_del. This also avoids to call
napi_disable() after netif_napi_del().
Fixes: ffa9fec30ca0 ("r8152: set RTL8152_UNPLUG only for real disconnection")
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drive
This reverts commit 0ee1f4734967af8321ecebaf9c74221ace34f2d5.
The commit 0ee1f4734967 ("r8152: napi hangup fix after
disconnect") adds a check about RTL8152_UNPLUG to determine
if calling napi_disable() is invalid in rtl8152_close(),
when rtl8152_disconnect() is called. This avoids to use
napi_dis
On Wed, Aug 28, 2019 at 11:23:33AM +0300, Felipe Balbi wrote:
> Originally I had memset only on the three cases where they were
> needed. Richard, which do you prefer? I don't mind changing it back.
Go ahead and change it back.
Thanks,
Richard
On Tue, Aug 27, 2019 at 01:41:50PM -0700, Hridya Valsaraju wrote:
> The following binder stat files currently live in debugfs.
>
> /sys/kernel/debug/binder/state
> /sys/kernel/debug/binder/stats
> /sys/kernel/debug/binder/transactions
>
> This patch makes these files available in a binderfs insta
On Mon, 2019-08-12 at 09:42 +0100, Quentin Perret wrote:
> The newly introduced Energy Model framework manages power cost tables
> in
> a generic way. Moreover, it supports several types of models since
> the
> tables can come from DT or firmware (through SCMI) for example. On
> the
> other hand, t
On Wed, Aug 28, 2019 at 11:33:01AM +0200, Peter Zijlstra wrote:
> On Tue, Aug 27, 2019 at 11:51:35PM +0200, Peter Zijlstra wrote:
> > On Tue, Aug 27, 2019 at 08:44:23PM +, Luck, Tony wrote:
> > > > I'm reposting because the version Ingo applied and partially fixed up
> > > > still
> > > > gene
On Tue, Aug 27, 2019 at 01:41:51PM -0700, Hridya Valsaraju wrote:
> Currently, the binder transaction log files 'transaction_log'
> and 'failed_transaction_log' live in debugfs at the following locations:
>
> /sys/kernel/debug/binder/failed_transaction_log
> /sys/kernel/debug/binder/transaction_lo
On Thu, Aug 01, 2019 at 04:25:29PM -0500, Bjorn Helgaas wrote:
> Hi,
>
> I got the following dmesg log from Fawad [1]:
>
> imx6q-pcie 1ffc000.pcie: host bridge /soc/pcie@1ffc000 ranges:
> imx6q-pcie 1ffc000.pcie:IO 0x01f8..0x01f8 -> 0x
> imx6q-pcie 1ffc000.pcie: MEM 0x
Hi Mimi,
> Detect and allow appended signatures.
> Signed-off-by: Mimi Zohar
Reviewed-by: Petr Vorel
Kind regards,
Petr
Scott Wood writes:
> On Tue, 2019-08-27 at 11:33 +1000, Michael Ellerman wrote:
>> Jason Yan writes:
>> > A polite ping :)
>> >
>> > What else should I do now?
>>
>> That's a good question.
>>
>> Scott, are you still maintaining FSL bits,
>
> Sort of... now that it's become very low volume, i
On 28/08/19 2:14 PM, Masahiro Yamada wrote:
> Currently, the DMA addresses are casted to (u64) for the upper 32bits
> to avoid "right shift count >= width of type" warning.
>
> provides macros to address this, and the macro names
> are self-documenting.
>
> Signed-off-by: Masahiro Yamada
> ---
On Tue, Aug 27, 2019 at 9:05 PM Aaro Koskinen wrote:
> On Tue, Aug 27, 2019 at 06:33:01PM +0200, Arnd Bergmann wrote:
> > On Fri, Aug 16, 2019 at 10:34 AM Aaro Koskinen wrote:
> > > However with earlyprintk it seems to hang as soon as kernel tries to print
> > > something. So something goes wrong
On Tue, Aug 27, 2019 at 05:37:16PM -0500, Rob Herring wrote:
> On Sat, Aug 24, 2019 at 10:26:55PM +0200, Michał Mirosław wrote:
> > Add single-pin LRCLK source options for Atmel SSC module.
> >
> > Signed-off-by: Michał Mirosław
> >
> > ---
> > v2: split from implementation patch
> >
> > ---
The following commit has been merged into the x86/cpu branch of tip:
Commit-ID: 5ebb34edbefa8ea6a7e109179d5fc7b3529dbeba
Gitweb:
https://git.kernel.org/tip/5ebb34edbefa8ea6a7e109179d5fc7b3529dbeba
Author:Peter Zijlstra
AuthorDate:Tue, 27 Aug 2019 21:48:24 +02:00
Committer:
On Wednesday 28 Aug 2019 at 20:58:47 (+0800), Zhang Rui wrote:
> this patch has coding style problems, please check the checkpatch.pl
> output.
> total: 5 errors, 17 warnings, 413 lines checked
Argh ! And that's what happens when I forget checkpatch ...
I'll fix this shortly. Sorry about that.
Qu
The following commit has been merged into the x86/cpu branch of tip:
Commit-ID: af239c44e3f976762e9bc052f0d5796b90ea530b
Gitweb:
https://git.kernel.org/tip/af239c44e3f976762e9bc052f0d5796b90ea530b
Author:Peter Zijlstra
AuthorDate:Tue, 27 Aug 2019 21:48:22 +02:00
Committer:
The following commit has been merged into the x86/cpu branch of tip:
Commit-ID: c66f78a6de4de6cb520b15cf6a1b586617b9add5
Gitweb:
https://git.kernel.org/tip/c66f78a6de4de6cb520b15cf6a1b586617b9add5
Author:Peter Zijlstra
AuthorDate:Tue, 27 Aug 2019 21:48:21 +02:00
Committer:
The following commit has been merged into the x86/cpu branch of tip:
Commit-ID: a3d8c0d13bdedf84fe74259f6949b2cdffd80e55
Gitweb:
https://git.kernel.org/tip/a3d8c0d13bdedf84fe74259f6949b2cdffd80e55
Author:Peter Zijlstra
AuthorDate:Tue, 27 Aug 2019 21:48:25 +02:00
Committer:
The following commit has been merged into the x86/cpu branch of tip:
Commit-ID: 5e741407eab7c602ee5a2b06afb0070a02f4412f
Gitweb:
https://git.kernel.org/tip/5e741407eab7c602ee5a2b06afb0070a02f4412f
Author:Peter Zijlstra
AuthorDate:Tue, 27 Aug 2019 21:48:23 +02:00
Committer:
On 28/08/2019 14.33, Denis Efremov wrote:
> On 8/28/19 2:33 PM, Rasmus Villemoes wrote:
>> On 25/08/2019 21.19, Julia Lawall wrote:
>>>
>>>
On 26 Aug 2019, at 02:59, Denis Efremov wrote:
> On 25.08.2019 19:37, Joe Perches wrote:
>> On Sun, 2019-08-25 at 16:05 +0300, Den
On Wed, Aug 28, 2019 at 09:07:17AM +0200, Ricard Wanderlof wrote:
> On Wed, 28 Aug 2019, Sasha Levin wrote:
> > On Tue, Aug 27, 2019 at 12:00:14PM +0100, Mark Brown wrote:
> > > If anyone ran into this on the older kernel and fixed or worked
> > > around it locally there's a reasonable chance this
On Fri, 2019-08-23 at 17:29 +0530, Amit Kucheria wrote:
> On Fri, Aug 23, 2019 at 3:08 PM Srinivas Kandagatla
> wrote:
> >
> > memory returned as part of nvmem_read via qfprom_read should be
> > freed by the consumer once done.
> > Existing code is not doing it so fix it.
> >
> > Below memory le
On Tue, Aug 27, 2019 at 01:41:52PM -0700, Hridya Valsaraju wrote:
> Currently /sys/kernel/debug/binder/proc contains
> the debug data for every binder_proc instance.
> This patch makes this information also available
> in a binderfs instance mounted with a mount option
> "stats=global" in addition
On Tue, Aug 27, 2019 at 09:01:42AM -0400, Kamal Dasu wrote:
Please don't top post, reply in line with needed context. This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is being addressed
Hi Michal, Thank you for spending your time on this.
On Tue, Aug 27, 2019 at 08:16:06AM +0200, Michal Hocko wrote:
> On Tue 27-08-19 02:14:20, Bharath Vedartham wrote:
> > Hi Michal,
> >
> > Here are some of my thoughts,
> > On Wed, Aug 21, 2019 at 04:06:32PM +0200, Michal Hocko wrote:
> > > On Th
On 08/28/2019 10:30 AM, Michal Suchanek wrote:
With endian switch disabled by default the ppc64le compat supports
ppc32le only which is something next to nobody has binaries for.
Less code means less bugs so drop the compat stuff.
I am not particularly sure about the best way to resolve the
Em Wed, Aug 28, 2019 at 08:15:54AM +0900, Namhyung Kim escreveu:
> Currently perf top only decays entries in a selected evsel. I don't
> know whether it's intended (maybe due to performance reason?) but
> anyway it might show incorrect output when event group is used since
> users will see leader
The patch
ALSA: pcm: add support for 352.8KHz and 384KHz sample rate
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.4
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 2
The patch
regulator: mt6358: Add support for MT6358 regulator
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.4
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
The patch
regulator: Add document for MT6358 regulator
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.4
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hou
Em Wed, Aug 28, 2019 at 11:44:59AM +0200, Peter Zijlstra escreveu:
> On Wed, Aug 28, 2019 at 04:31:22PM +0900, Namhyung Kim wrote:
> > To support cgroup tracking, add CGROUP event to save a link between
> > cgroup path and inode number. The attr.cgroup bit was also added to
> > enable cgroup track
The patch
ASoC: wcd9335: Fix primary interpolator max rate
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.4
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) a
On 27/08/19 3:33 AM, Ben Chuang wrote:
> From: Ben Chuang
>
> Add support for the GL9750 and GL9755 chipsets.
>
> Enable v4 mode and wait 5ms after set 1.8V signal enable for GL9750/
> GL9755. Fix the value of SDHCI_MAX_CURRENT register and use the vendor
> tuning flow for GL9750.
Looks good, o
On 8/28/19 4:05 PM, Rasmus Villemoes wrote:
> On 28/08/2019 14.33, Denis Efremov wrote:
>> On 8/28/19 2:33 PM, Rasmus Villemoes wrote:
>>> On 25/08/2019 21.19, Julia Lawall wrote:
> On 26 Aug 2019, at 02:59, Denis Efremov wrote:
>
>
>
>> On 25.08.2019 19:37, Joe Perch
On 2019-08-28 05:54:26 [-0700], Paul E. McKenney wrote:
> On Wed, Aug 28, 2019 at 11:27:39AM +0200, Sebastian Andrzej Siewior wrote:
> > On 2019-08-27 08:53:06 [-0700], Paul E. McKenney wrote:
> > > Am I understanding this correctly?
> >
> > Everything perfect except that it is not lockdep complai
This patch series enables Tegra194's C5 controller which owns x16 slot in
p2972- platform. C5 controller's PERST# and CLKREQ# are not configured as
output and bi-directional signals by default and hence they need to be
configured explicitly. Also, x16 slot's 3.3V and 12V supplies are controlled
Add optional bindings "pinctrl-names" and "pinctrl-0" to describe pin
configuration information of a particular PCIe controller.
Signed-off-by: Vidya Sagar
---
V2:
* None
.../devicetree/bindings/pci/nvidia,tegra194-pcie.txt | 8
1 file changed, 8 insertions(+)
diff --git a/Docume
On Wed, 2019-08-28 at 09:51 +0200, Dietmar Eggemann wrote:
> On 22/08/2019 04:17, Rik van Riel wrote:
> > Now that enqueue_task_fair and dequeue_task_fair no longer iterate
> > up
> > the hierarchy all the time, a method to lazily propagate
> > sum_exec_runtime
> > up the hierarchy is necessary.
>
On Wed 28-08-19 18:39:22, Bharath Vedartham wrote:
[...]
> > Therefore I would like to shift the discussion towards existing APIs and
> > whether they are suitable for such an advance auto-tuning. I haven't
> > heard any arguments about missing pieces.
> I understand your concern here. Just confirm
Add optional bindings "vpcie3v3-supply" and "vpcie12v-supply" to describe
regulators of a PCIe slot's supplies 3.3V and 12V provided the platform
is designed to have regulator controlled slot supplies.
Signed-off-by: Vidya Sagar
---
V2:
* None
.../devicetree/bindings/pci/nvidia,tegra194-pcie.tx
Add support to configure sideband signal pins when information is present
in respective controller's device-tree node.
Signed-off-by: Vidya Sagar
---
V2:
* Addressed review comment from Andrew Murray
* Handled failure case of pinctrl_pm_select_default_state() cleanly
drivers/pci/controller/dwc/
Add support to get regulator information of 3.3V and 12V supplies of a PCIe
slot from the respective controller's device-tree node and enable those
supplies. This is required in platforms like p2972- where the supplies
to x16 slot owned by C5 controller need to be enabled before attempting to
e
Add 3.3V and 12V supplies regulators information of x16 PCIe slot in
p2972- platform which is owned by C5 controller and also enable C5
controller.
Signed-off-by: Vidya Sagar
---
V2:
* None
.../arm64/boot/dts/nvidia/tegra194-p2888.dtsi | 24 +++
.../boot/dts/nvidia/tegra194-
Add support to configure PCIe C5's sideband signals PERST# and CLKREQ#
as output and bi-directional signals respectively which unlike other
PCIe controllers sideband signals are not configured by default.
Signed-off-by: Vidya Sagar
---
V2:
* None
arch/arm64/boot/dts/nvidia/tegra194.dtsi | 38 ++
Move the static keyword to the front of declarations of
pci_regs_behavior and pcie_cap_regs_behavior, and resolve
the following compiler warning that can be seen when
building with warnings enabled (W=1):
drivers/pci/pci-bridge-emul.c:41:1: warning: ‘static’ is not at beginning of
declaration [-W
On Wed, Aug 28, 2019 at 06:43:35PM +0800, Brad Campbell wrote:
> On 28/8/19 6:23 pm, Mika Westerberg wrote:
>
> > On Wed, Aug 28, 2019 at 05:12:00PM +0800, Brad Campbell wrote:
> >
> > Apart from the warning in the log (which is not fatal, I'll look into
> > it) to me the second path setup looks
For testing, it is useful to be able to specify a clock rate manually.
As this is a dangerous feature, it is not enabled by default.
Users need to modify the source directly and #define
CLOCK_ALLOW_WRITE_DEBUGFS.
This follows the spirit of commit 09c6ecd394105c48 ("regmap: Add support
for writing
On 28/08/2019 00:36, Jason Gunthorpe wrote:
> On Tue, Aug 27, 2019 at 04:34:31PM -0700, Andrew Morton wrote:
>> On Tue, 27 Aug 2019 01:34:13 + Jason Gunthorpe wrote:
>>
>>> On Sat, Aug 24, 2019 at 03:26:55PM -0700, Christoph Hellwig wrote:
On Fri, Aug 23, 2019 at 01:43:12PM +, Jason G
KH,
Just make sure I understand details.
> Commit "HID: i2c-hid: Don't reset device upon system resume
If you revert this it's fixed on this system?
In that commit you had mentioned if this causes problems it might be worth
quirking just Raydium but commit afbb1169ed5b58cfca017e368b53e019cf2858
Uacce (Unified/User-space-access-intended Accelerator Framework) targets to
provide Shared Virtual Addressing (SVA) between accelerators and processes.
So accelerator can access any data structure of the main cpu.
This differs from the data sharing between cpu and io device, which share
data conten
From: Kenneth Lee
Uacce (Unified/User-space-access-intended Accelerator Framework) targets to
provide Shared Virtual Addressing (SVA) between accelerators and processes.
So accelerator can access any data structure of the main cpu.
This differs from the data sharing between cpu and io device, whi
From: Kenneth Lee
Uacce (Unified/User-space-access-intended Accelerator Framework) is
a kernel module targets to provide Shared Virtual Addressing (SVA)
between the accelerator and process.
This patch add document to explain how it works.
Signed-off-by: Kenneth Lee
Signed-off-by: Zaibo Xu
Sig
On Wed, Aug 28, 2019 at 8:52 PM Linus Walleij wrote:
>
> On Sun, Aug 25, 2019 at 5:06 PM Alejandro González
> wrote:
>
> > Jernej Skrabec compared the BSP driver with this
> > driver, and found that the BSP driver configures pinctrl to operate at
> > 1.8 V when entering DDR mode (although 3.3 V o
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 42880f726c66f13ae1d9ac9ce4c43abe64ecac84
Gitweb:
https://git.kernel.org/tip/42880f726c66f13ae1d9ac9ce4c43abe64ecac84
Author:Alexander Shishkin
AuthorDate:Tue, 06 Aug 2019 11:46:01 +03:00
Comm
The following commit has been merged into the perf/core branch of tip:
Commit-ID: ab43762ef010967e4ccd53627f70a2eecbeafefb
Gitweb:
https://git.kernel.org/tip/ab43762ef010967e4ccd53627f70a2eecbeafefb
Author:Alexander Shishkin
AuthorDate:Tue, 06 Aug 2019 11:46:00 +03:00
Comm
The following commit has been merged into the x86/vmware branch of tip:
Commit-ID: f7b15c74cffd760ec9959078982d8268a38456c4
Gitweb:
https://git.kernel.org/tip/f7b15c74cffd760ec9959078982d8268a38456c4
Author:Thomas Hellstrom
AuthorDate:Wed, 28 Aug 2019 10:03:53 +02:00
Commi
The following commit has been merged into the x86/vmware branch of tip:
Commit-ID: bac7b4e843232a3a49a042410cf743341eb0887e
Gitweb:
https://git.kernel.org/tip/bac7b4e843232a3a49a042410cf743341eb0887e
Author:Thomas Hellstrom
AuthorDate:Wed, 28 Aug 2019 10:03:50 +02:00
Commi
The following commit has been merged into the x86/vmware branch of tip:
Commit-ID: 6abe3778cf5abd59b23b9037796f3eab8b7f1d98
Gitweb:
https://git.kernel.org/tip/6abe3778cf5abd59b23b9037796f3eab8b7f1d98
Author:Thomas Hellstrom
AuthorDate:Wed, 28 Aug 2019 10:03:52 +02:00
Commi
On Tue, Aug 27, 2019 at 11:56:20AM +0200, Krzysztof Wilczynski wrote:
> Merge PCI Express ASPM function prototypes and definitions
> from include/linux/pci-aspm.h into include/linux/pci.h.
>
> Function prototypes to move are pci_disable_link_state(),
> pci_disable_link_state_locked(), pcie_no_aspm
The following commit has been merged into the x86/vmware branch of tip:
Commit-ID: b4dd4f6e3648dfd66576515fd885a9a765c0
Gitweb:
https://git.kernel.org/tip/b4dd4f6e3648dfd66576515fd885a9a765c0
Author:Thomas Hellstrom
AuthorDate:Wed, 28 Aug 2019 10:03:51 +02:00
Commi
501 - 600 of 1154 matches
Mail list logo
