On Thu 03 Oct 22:38 PDT 2019, Stephen Boyd wrote:
> Quoting Murali Nalajala (2019-10-03 16:51:50)
> > @@ -151,14 +156,16 @@ struct soc_device *soc_device_register(struct
> > soc_device_attribute *soc_dev_attr
> >
> > ret = device_register(_dev->dev);
> > if (ret)
> > -
Specify 'i2c-mux-idle-disconnect' for both I2C switches present on the
board, since both are connected to the same parent bus and all of
their children have the same I2C address.
Fixes: ca4b4d373fcc ("ARM: dts: vf610: Add ZII SCU4 AIB board")
Signed-off-by: Andrey Smirnov
Cc: Shawn Guo
Cc:
Quoting Murali Nalajala (2019-10-03 16:51:50)
> @@ -151,14 +156,16 @@ struct soc_device *soc_device_register(struct
> soc_device_attribute *soc_dev_attr
>
> ret = device_register(_dev->dev);
> if (ret)
> - goto out3;
> + goto out4;
>
>
On Fri, Aug 09, 2019 at 04:33:11PM +0800, Xin Long wrote:
> On Thu, Aug 8, 2019 at 11:01 PM syzbot
> wrote:
> >
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:0eb0ce0a Merge tag 'spi-fix-v5.3-rc3' of git://git.kernel...
> > git tree: upstream
> > console
Hello,
To fix the 'ppp0: recursion detected' messages we see on our firewall I
found a solution at:
https://forum.openwrt.org/t/pptp-recursion-detected-system-reboot-itself/12585
Can we please implement this solution if deemed OK?
Kind regards,
Udo
Use real temporary working directory for generating kselftest
archive.
tools/testing/selftests/kselftest directory has been used for
the temporary working directory for making a tar archive from
gen_kselftest_tar.sh, and it removes the directory for cleanup.
However, since the kselftest
On 04-10-2019 06:57, Udo van den Heuvel wrote:
> To fix the 'ppp0: recursion detected' messages we see on our firewall I
> found a solution at:
>
> https://forum.openwrt.org/t/pptp-recursion-detected-system-reboot-itself/12585
>
> Can we please implement this solution if deemed OK?
Or perhaps
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-5.4-rc2-tag
xen: fixes and cleanups for 5.4-rc2
It contains the following patches:
- a fix in the Xen balloon driver avoiding hitting a BUG_ON() in some
cases, plus a follow-on
ok - so to sum up, it sounds like you are saying the 350 false
positives (see attached file) that happen on building cifs.ko .will be
fixed by a
future change to modpost? This is a typical module build ...
download and install current kernel package (in this case Ubuntu
5.4-rc1). which saves
Hi All:
drivers/regulator/ltc3589.c
Variable "irqstat" in function ltc3589_isr() could be uninitialized if
regmap_read() returns -EINVAL. But it's directly used later without
the return check, which is potentially unsafe.
Also, we cannot simply return -EINVAL in ltc3589_isr() because
the error
Hi All:
drivers/pwm/pwm-stm32-lp.c:
Variable "val" and "prd" in function stm32_pwm_lp_get_state() could be
uninitialized
if regmap_read() returns -EINVAL. But it's directly used later without
the return check,
which is potentially unsafe.
Also, we cannot simply return -EINVAL in
'curr_status' is declared as u32.
But this variable is not used after below statement.
curr_status = vptr->mii_status & (~VELOCITY_LINK_FAIL);
This variable could be dropped to mute below warning message:
drivers/net/ethernet/via/via-velocity.c:868:6:
warning: variable ‘curr_status’ set
Hi Steve,
On Fri, Oct 4, 2019 at 1:28 PM Steve French wrote:
>
> On Thu, Oct 3, 2019 at 10:41 PM Masahiro Yamada
> wrote:
> >
> > Hi Steve,
> >
> > On Fri, Oct 4, 2019 at 1:07 AM Steve French wrote:
> > >
> > > On Thu, Oct 3, 2019 at 10:24 AM Masahiro Yamada
> > > wrote:
> > > >
> > > > Hi
Inside function stm32_pwm_config(), variable "psc" and " arr"
could be uninitialized if regmap_read() returns -EINVALs.
However, they are used later in the if statement to decide
the return value which is potentially unsafe.
The same case happens in function stm32_pwm_detect_channels()
with
On Thu, 2019-10-03 at 16:53 +0200, Dmitry Vyukov wrote:
> On Thu, Oct 3, 2019 at 3:51 PM Walter Wu wrote:>
> > how about this?
> >
> > commit fd64691026e7ccb8d2946d0804b0621ac177df38
> > Author: Walter Wu
> > Date: Fri Sep 27 09:54:18 2019 +0800
> >
> > kasan: detect invalid size in memory
Hi all,
After merging the rtc tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/rtc/rtc-mc146818-lib.c: In function 'mc146818_set_time':
drivers/rtc/rtc-mc146818-lib.c:176:6: error: 'boot_cpu_data' undeclared (first
use in this function); did you mean
On 03.10.19 20:12, Boris Ostrovsky wrote:
Currently execution of panic() continues until Xen's panic notifier
(xen_panic_event()) is called at which point we make a hypercall that
never returns.
This means that any notifier that is supposed to be called later as
well as significant part of
Hi Kevin,
On Thu, 3 Oct 2019 at 23:14, Kevin Hilman wrote:
>
> Anand Moon writes:
>
> > Looks like this changes got lost so resend these changes again.
>
> Yeah, sorry about that. Your cover letter subjects were quite similar,
> and several versions of this series and the previoius series
On Thu, Oct 3, 2019 at 10:41 PM Masahiro Yamada
wrote:
>
> Hi Steve,
>
> On Fri, Oct 4, 2019 at 1:07 AM Steve French wrote:
> >
> > On Thu, Oct 3, 2019 at 10:24 AM Masahiro Yamada
> > wrote:
> > >
> > > Hi Steve,
> > >
> > > On Fri, Oct 4, 2019 at 12:15 AM Steve French wrote:
> > > >
> > > >
Platform implementation for free_initmem() should poison the memory while
freeing it up. Hence pass across POISON_FREE_INITMEM while calling into
free_reserved_area(). The same is being followed in the generic fallback
for free_initmem() and some other platforms overriding it.
Cc: Catalin Marinas
Hi:
drivers/power/supply/rt5033_battery.c:
In function rt5033_battery_get_present(), variable "val" could be
uninitialized if regmap_read() returns -EINVAL. However, "val" is
used to decide the return value, which is potentially unsafe.
Also, we cannot simply return -EINVAL in
The riscv has csr_read/write macro, see arch/riscv/include/asm/csr.h,
the same function naming will cause build error, using such generic names
in a driver is bad, rename csr_[read,write][l,] to mobiveil_csr_read/write
to fix it.
drivers/pci/controller/pcie-mobiveil.c:238:69: error: macro
On Thu, Oct 3, 2019 at 12:44 AM Jeffrey Hugo wrote:
>
> The retention idle state does not appear to be supported by the firmware
> present on the msm8998 laptops since the state is advertised as disabled
> in ACPI, and attempting to enable the state in DT is observed to result
> in boot hangs.
Hi Steve,
On Fri, Oct 4, 2019 at 1:07 AM Steve French wrote:
>
> On Thu, Oct 3, 2019 at 10:24 AM Masahiro Yamada
> wrote:
> >
> > Hi Steve,
> >
> > On Fri, Oct 4, 2019 at 12:15 AM Steve French wrote:
> > >
> > > On Thu, Oct 3, 2019 at 5:43 AM Matthias Maennich
> > > wrote:
> > > >
> > > > Hi
On 04.10.19 04:13, Shawn Lin wrote:
> On 2019/10/4 8:53, Soeren Moch wrote:
>>
>>
>> On 04.10.19 02:01, Robin Murphy wrote:
>>> On 2019-10-03 10:50 pm, Soeren Moch wrote:
According to the RockPro64 schematic [1] the rk3399 sdmmc
controller is
connected to a microSD (TF card)
Hi All:
drivers/net/ethernet/hisilicon/hip04_eth.c:
In function hip04_reset_ppe(), variable "val" could be uninitialized
if regmap_read() returns -EINVAL. However, "val" is used to decide
the control flow, which is potentially unsafe.
Also, we cannot simply return -EINVAL in hip04_reset_ppe()
On Thu, 2019-10-03 at 20:05 +0200, Rafael J. Wysocki wrote:
> On Wednesday, October 2, 2019 2:29:26 PM CEST Giovanni Gherdovich
> wrote:
> > From: Srinivas Pandruvada
> >
> > intel_pstate has two operating modes: active and passive. In
> > "active"
> > mode, the in-built scaling governor is used
Hi Chris,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on gpio/for-next]
[cannot apply to v5.4-rc1 next-20191003]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option
On Thu, Oct 3, 2019 at 7:36 PM Amit Kucheria wrote:
>
> On Wed, Oct 2, 2019 at 11:48 PM Jeffrey Hugo wrote:
> >
> > On Wed, Oct 2, 2019 at 3:27 AM Niklas Cassel
> > wrote:
> > >
> > > On Wed, Oct 02, 2019 at 11:19:50AM +0200, Niklas Cassel wrote:
> > > > On Mon, Sep 30, 2019 at 04:20:15PM
Hi Chris,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on gpio/for-next]
[cannot apply to v5.4-rc1 next-20191003]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify
From: Roman Kagan Sent: Thursday, October 3, 2019 5:53 AM
> >
> > AFAIU you're trying to mirror native_x2apic_icr_write() here but this is
> > different from what hv_apic_icr_write() does
> > (SET_APIC_DEST_FIELD(id)).
>
> Right. In xapic mode the ICR2 aka the high 4 bytes of ICR is programmed
On 1/10/19 6:29 pm, Mika Westerberg wrote:
When we discover existing DP tunnels the code checks whether DP IN
adapter port is enabled by calling tb_dp_port_is_enabled() before it
continues the discovery process. On Light Ridge (gen 1) controller
reading only the first dword of the DP IN config
Hello,
Let us repair your phone or gadget right on the spot
visit us today
https://www.justrepair.net
or come into our location
https://goo.gl/maps/k5iRbeJyggiXnZSG6
Give us a nice review and we`ll make you a big discount
Thank you,
Ameer
This patch adds support for multiple debug options separated by ',' and
non-int values.
--debug verbose=2,stderr
Signed-off-by: Changbin Du
---
tools/perf/Documentation/perf.txt | 10 ++--
tools/perf/util/debug.c | 86 ---
2 files changed, 50
When in TUI mode, it is impossible to show all the debug messages to
console. This make it hard to debug perf issues using debug messages.
This patch adds support for logging debug messages to file to resolve
this problem.
The usage is:
perf -debug verbose=2,file=~/perf.log COMMAND
When in TUI mode, it is impossible to show all the debug messages to
console. This make it hard to debug perf issues using debug messages.
This patch adds support for logging debug messages to file to resolve
this problem.
v3:
o fix a segfault issue.
v2:
o specific all debug options one time.
On Sun, Sep 29, 2019 at 09:44:07AM +0200, Jiri Olsa wrote:
> On Sun, Sep 22, 2019 at 10:38:21AM +0800, Changbin Du wrote:
> > When in TUI mode, it is impossible to show all the debug messages to
> > console. This make it hard to debug perf issues using debug messages.
> > This patch adds support
On 2019/10/4 8:53, Soeren Moch wrote:
On 04.10.19 02:01, Robin Murphy wrote:
On 2019-10-03 10:50 pm, Soeren Moch wrote:
According to the RockPro64 schematic [1] the rk3399 sdmmc controller is
connected to a microSD (TF card) slot, which cannot be switched to 1.8V.
Really? AFAICS the SDMMC0
Hi Martin,
On Fri, Oct 4, 2019 at 10:59 AM Martin K. Petersen
wrote:
>
>
> Masahiro,
>
> >> Add a header include guard just in case.
>
> Fine with me. Is it going through your tree or should I pick it up?
Could you please apply it to your tree?
Thanks.
--
Best Regards
Masahiro Yamada
Paul,
No objections from me.
> + vpd_pg80 = rcu_replace(sdev->vpd_pg80, vpd_pg80,
> +lockdep_is_held(>inquiry_mutex));
> + vpd_pg83 = rcu_replace(sdev->vpd_pg83, vpd_pg83,
> +lockdep_is_held(>inquiry_mutex));
Just a heads-up that
+cc neeln...@google.com and hao...@google.com, they helped a lot
for this issue. Sorry I forgot to include them when sending out the patch.
On Thu, Oct 3, 2019 at 5:55 PM Phil Auld wrote:
>
> Hi,
>
> On Thu, Oct 03, 2019 at 05:12:43PM -0700 Xuewei Zhang wrote:
> > quota/period ratio is used to
Masahiro,
>> Add a header include guard just in case.
Fine with me. Is it going through your tree or should I pick it up?
--
Martin K. Petersen Oracle Linux Engineering
> alloc_workqueue is not checked for errors and as a result,
> a potential NULL dereference could occur.
Himanshu: Please review!
--
Martin K. Petersen Oracle Linux Engineering
On Tue, Oct 1, 2019 at 10:43 AM Nicolas Saenz Julienne
wrote:
>
> On Mon, 2019-09-30 at 16:24 -0500, Rob Herring wrote:
> > On Mon, Sep 30, 2019 at 8:32 AM Nicolas Saenz Julienne
> > wrote:
> > > On Mon, 2019-09-30 at 05:57 -0700, Christoph Hellwig wrote:
> > > > On Thu, Sep 26, 2019 at
According to
Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.txt,
i2c-mux-idle-disconnect is a property of a parent node since it
pertains to the mux/switch as a whole, so move it there and drop all
of the concurrences in child nodes.
Fixes: d031773169df ("ARM: dts: Adds device tree file
Sure. We will re-submit the patches with the revision suggested.
Thanks.
Regards,
Chiawei
* Email Confidentiality Notice
DISCLAIMER:
This message (and any attachments) may contain legally privileged and/or other
confidential information. If you have received it
On Wed, Oct 2, 2019 at 11:48 PM Jeffrey Hugo wrote:
>
> On Wed, Oct 2, 2019 at 3:27 AM Niklas Cassel wrote:
> >
> > On Wed, Oct 02, 2019 at 11:19:50AM +0200, Niklas Cassel wrote:
> > > On Mon, Sep 30, 2019 at 04:20:15PM -0600, Jeffrey Hugo wrote:
> > > > Amit, the merged version of the below
This is ported this from Broadcom's XLDK. There seem to be 3 different
IP blocks for 3 separate banks of GPIOs in the iProc chips.
I've dropped everything except support for the Chip Common A GPIO
controller because the other blocks actually seem to be supportable with
other drivers. The driver
This GPIO controller is present on a number of Broadcom switch ASICs
with integrated SoCs. It is similar to the nsp-gpio and iproc-gpio
blocks but different enough to require a separate driver.
Signed-off-by: Chris Packham
---
.../bindings/gpio/brcm,xgs-iproc.txt | 41
This driver supports the Chip Common A GPIO controller present on a
number of Broadcom switch ASICs with integrated SoCs. The controller is
similar to the pinctrl-nsp-gpio and pinctrl-iproc-gpio blocks but
different enough that a separate driver is required.
This has been ported from Broadcom's
DEBUG_FS does not belong to 'Compile-time checks and compiler options'.
Signed-off-by: Changbin Du
Acked-by: Randy Dunlap
Tested-by: Randy Dunlap
---
lib/Kconfig.debug | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/lib/Kconfig.debug
Create a submenu 'Scheduler Debugging' for scheduler debugging options.
Signed-off-by: Changbin Du
Acked-by: Randy Dunlap
Tested-by: Randy Dunlap
---
lib/Kconfig.debug | 4
1 file changed, 4 insertions(+)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index
Group generic kernel debugging instruments sysrq/kgdb/ubsan together into
a new submenu.
Signed-off-by: Changbin Du
Acked-by: Randy Dunlap
Tested-by: Randy Dunlap
---
lib/Kconfig.debug | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/lib/Kconfig.debug
This series is a trivial improvment for the layout of 'kernel hacking'
configuration menu. Now we have many items in it which makes takes
a little time to look up them since they are not well structurized yet.
Early discussion is here:
https://lkml.org/lkml/2019/9/1/39
This is a preview:
│
They are both memory debug options to debug kernel stack issues.
Signed-off-by: Changbin Du
Acked-by: Randy Dunlap
Tested-by: Randy Dunlap
---
lib/Kconfig.debug | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
Group these similar runtime data structures verification options together.
Signed-off-by: Changbin Du
Acked-by: Randy Dunlap
Tested-by: Randy Dunlap
---
lib/Kconfig.debug | 24 ++--
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git a/lib/Kconfig.debug
The arch special options are a little long, so create a submenu for them.
Signed-off-by: Changbin Du
Acked-by: Randy Dunlap
Tested-by: Randy Dunlap
---
lib/Kconfig.debug | 4
1 file changed, 4 insertions(+)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index
I think DEBUG_BUGVERBOSE is a dmesg option which gives more debug info
to dmesg.
Signed-off-by: Changbin Du
Acked-by: Randy Dunlap
Tested-by: Randy Dunlap
---
lib/Kconfig.debug | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/lib/Kconfig.debug
Move error injection, coverage, testing, kunit options to a new submenu
'Kernel Testing and Coverage'. They are all for test purpose.
Signed-off-by: Changbin Du
Acked-by: Randy Dunlap
Tested-by: Randy Dunlap
---
lib/Kconfig.debug | 499 +++---
1 file
They are similar options so place them together.
Signed-off-by: Changbin Du
Acked-by: Randy Dunlap
Tested-by: Randy Dunlap
---
lib/Kconfig.debug | 58 +++
1 file changed, 29 insertions(+), 29 deletions(-)
diff --git a/lib/Kconfig.debug
This is a cleanup series addressing issues around isa string accesses
and prints. Patch 1 is actually a revised patch as a result of discussion
in the following thread.
http://lists.infradead.org/pipermail/linux-riscv/2019-September/006702.html
Patch 2 is an additional cleanup that tries to
Currently, isa string is read and checked for correctness at multiple
places.
Consolidate them into one function and use it only during early bootup.
In case of a incorrect isa string, the cpu shouldn't boot at all.
Signed-off-by: Atish Patra
---
arch/riscv/include/asm/processor.h | 1 +
/proc/cpuinfo should just print all the isa string as an information
instead of determining what is supported or not. ELF hwcap can be
used by the userspace to figure out that.
Simplify the isa string printing by removing the unsupported isa string
print and all related code.
The relevant
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This automated bisection report was sent to you on the basis *
* that you may be involved with the breaking commit it has *
* found. No manual investigation has been done to verify it, *
* and the root cause of the
Hi,
On Thu, Oct 03, 2019 at 05:12:43PM -0700 Xuewei Zhang wrote:
> quota/period ratio is used to ensure a child task group won't get more
> bandwidth than the parent task group, and is calculated as:
> normalized_cfs_quota() = [(quota_us << 20) / period_us]
>
> If the quota/period ratio was
On 04.10.19 02:01, Robin Murphy wrote:
> On 2019-10-03 10:50 pm, Soeren Moch wrote:
>> According to the RockPro64 schematic [1] the rk3399 sdmmc controller is
>> connected to a microSD (TF card) slot, which cannot be switched to 1.8V.
>
> Really? AFAICS the SDMMC0 wiring looks pretty much
reference to
`.devm_led_classdev_register_ext'
Caused by commit
3a0275384c27 ("HID: Add driver for Logitech gaming keyboards (G15, G15 v2)")
For this build, CONFIG_HID_LOGITECH=y and CONFIG_LEDS_CLASS=m.
I have used the hid tree from next-20191003 for today.
--
Cheers,
Stephe
On Thu, 2019-10-03 at 21:51 +0300, Jarkko Sakkinen wrote:
> Switch from GFP_HIGHUSER to GFP_KERNEL. On 32-bit platforms kmap()
> space
> could be unnecessarily wasted because of using GFP_HIGHUSER by taking
> a
> page of from the highmem.
>
> Suggested-by: James Bottomley
> Signed-off-by: Jarkko
I'll tackle this tomorrow. I've been working on the feature control MSR
series and will get that sent out tomorrow as well. I should also be able
to get you the multi-page EADD patch.
quota/period ratio is used to ensure a child task group won't get more
bandwidth than the parent task group, and is calculated as:
normalized_cfs_quota() = [(quota_us << 20) / period_us]
If the quota/period ratio was changed during this scaling due to
precision loss, it will cause inconsistency
Some HCI devices which have the HCI_QUIRK_NON_PERSISTENT_SETUP [1]
require a call to setup() to be ran after every open().
During the setup() stage, these devices expect the chip to acknowledge
its setup() completion via vendor specific frames.
If userspace opens() such HCI device in
On Wed, Oct 02, 2019 at 05:59:36PM -0400, Bruce Ashfield wrote:
> On Wed, Oct 2, 2019 at 2:19 PM Roman Gushchin wrote:
> >
> > On Wed, Oct 02, 2019 at 12:18:54AM -0400, Bruce Ashfield wrote:
> > > On Tue, Oct 1, 2019 at 10:01 PM Roman Gushchin wrote:
> > > >
> > > > On Tue, Oct 01, 2019 at
> From: Stefano Garzarella
> Sent: Friday, September 27, 2019 4:27 AM
> ...
> Patch 9 changes the hvs_remote_addr_init(). setting the
> VMADDR_CID_HOST as remote CID instead of VMADDR_CID_ANY to make
> the choice of transport to be used work properly.
> @Dexuan Could this change break anything?
On Thu, Oct 03, 2019 at 02:18:04AM +0300, Jarkko Sakkinen wrote:
> Also there is two space bars after *every* sentence. Your text editor is
> totally broken somehow.
I completely misunderstood your earlier comment, I thought you were saying
there were random spaces at the end of lines.
It's not
On Thu, 2019-10-03 at 13:39 -0700, Alexander Duyck wrote:
> On Thu, Oct 3, 2019 at 11:51 AM David Z. Dai wrote:
> >
> > On Thu, 2019-10-03 at 10:39 -0700, Alexander Duyck wrote:
> > > On Thu, Oct 3, 2019 at 9:59 AM David Dai wrote:
> > > >
> > > > We see the behavior when EEH e1000e adapter
On 2019-10-03 10:50 pm, Soeren Moch wrote:
According to the RockPro64 schematic [1] the rk3399 sdmmc controller is
connected to a microSD (TF card) slot, which cannot be switched to 1.8V.
Really? AFAICS the SDMMC0 wiring looks pretty much identical to the
NanoPC-T4 schematic (it's the same
On 10/3/19 9:52 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.195 release.
There are 99 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
On 10/3/19 9:51 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.77 release.
There are 211 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 10/3/19 9:51 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.147 release.
There are 185 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 10/3/19 9:52 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.195 release.
There are 129 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
Soc framework exposed sysfs entries are not sufficient for some
of the h/w platforms. Currently there is no interface where soc
drivers can expose further information about their SoCs via soc
framework. This change address this limitation where clients can
pass their custom entries as attribute
"kernelci.org bot" writes:
> stable-rc/linux-5.2.y boot: 136 boots: 1 failed, 126 passed with 9 offline
> (v5.2.18-314-g2c8369f13ff8)
>
> Full Boot Summary:
> https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.2.y/kernel/v5.2.18-314-g2c8369f13ff8/
> Full Build Summary:
>
On 10/3/19 9:49 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.2.19 release.
There are 313 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
On 10/3/19 9:49 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.3.4 release.
There are 344 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
On 10/3/19 12:39 PM, Nicolas Saenz Julienne wrote:
> On Thu, 2019-10-03 at 11:08 -0700, Florian Fainelli wrote:
>> On 10/2/19 4:45 AM, Nicolas Saenz Julienne wrote:
>>> Currently, in arm_dt_init_cpu_maps(), the hwid of the boot CPU is read
>>> from MPIDR on SMP devices and set to 0 for non SMP.
On 2019-10-03 16:22, Stephen Boyd wrote:
Quoting Murali Nalajala (2019-10-02 17:06:14)
@@ -121,6 +118,7 @@ static void soc_release(struct device *dev)
struct soc_device *soc_device_register(struct soc_device_attribute
*soc_dev_attr)
{
struct soc_device *soc_dev;
+ const struct
From: Kuppuswamy Sathyanarayanan
As per PCI firmware specification r3.2 Downstream Port Containment
Related Enhancements ECN, sec 4.5.1, OS must implement following steps
to enable/use EDR feature.
1. OS can use bit 7 of _OSC Control Field to negotiate control over
Downstream Port Containment
From: Kuppuswamy Sathyanarayanan
As per ACPI specification v6.3, sec 5.6.6, Error Disconnect Recover
(EDR) notification used by firmware to let OS know about the DPC event
and permit OS to perform error recovery when processing the EDR
notification. Also, as per PCI firmware specification r3.2
From: Kuppuswamy Sathyanarayanan
As per PCI firmware specification r3.2 Downstream Port Containment
Related Enhancements ECN, OS is responsible for clearing the AER
registers in EDR mode. So clear AER registers in dpc_process_error()
function.
Signed-off-by: Kuppuswamy Sathyanarayanan
From: Kuppuswamy Sathyanarayanan
Commit bdb5ac85777d ("PCI/ERR: Handle fatal error recovery") uses
reset_link() to recover from fatal errors. But, if the reset is
successful there is no need to continue the rest of the error recovery
checks. Also, during fatal error recovery, if the initial
From: Kuppuswamy Sathyanarayanan
Currently, in native mode, DPC driver is configured to trigger DPC only
for FATAL errors and hence it only supports port recovery for FATAL
errors. But with Error Disconnect Recover (EDR) support, DPC
configuration is done by firmware, and hence we should expect
From: Kuppuswamy Sathyanarayanan
With Error Disconnect Recover (EDR) support, we need to support
processing DPC event either from DPC IRQ or ACPI EDR event. So create
a wrapper function dpc_process_error() and move common error handling
code in to it. It will be used to process the DPC event in
From: Kuppuswamy Sathyanarayanan
As per PCI firmware specification r3.2 Downstream Port Containment
Related Enhancements ECN, sec 4.5.1, table 4-6, Error Disconnect
Recover (EDR) support allows OS to handle error recovery and
clearing Error Registers even in FF mode. So remove FF mode checks in
From: Kuppuswamy Sathyanarayanan
As per ACPI specification r6.3, sec 5.6.6, when firmware owns Downstream
Port Containment (DPC), its expected to use the "Error Disconnect
Recover" (EDR) notification to alert OSPM of a DPC event and if OS
supports EDR, its expected to handle the software state
From: Kuppuswamy Sathyanarayanan
This patchset adds support for following features:
1. Error Disconnect Recover (EDR) support.
2. _OSC based negotiation support for DPC.
You can find EDR spec in the following link.
https://members.pcisig.com/wg/PCI-SIG/document/12614
Changes since v8:
*
On 03/10/2019 09:48, Argus Lin wrote:
> MT6359 is a new power management IC and it is used for
> MT6779 SoCs. To define mt6359_regs for pmic register mapping
> and pmic_mt6359 for accessing register.
>
> Signed-off-by: Argus Lin
> ---
> drivers/soc/mediatek/mtk-pmic-wrap.c | 72
>
On 03/10/2019 09:48, Argus Lin wrote:
> MT6779 is a highly integrated SoCs, it uses MT6359 for power
> management. This patch adds pwrap driver to access MT6359.
> Pwrap of MT6779 support dynamic priority meichanism, sequence
mechanism
> monitor and starvation mechanism to make transaction
Quoting Murali Nalajala (2019-10-02 17:06:14)
> @@ -121,6 +118,7 @@ static void soc_release(struct device *dev)
> struct soc_device *soc_device_register(struct soc_device_attribute
> *soc_dev_attr)
> {
> struct soc_device *soc_dev;
> + const struct attribute_group
From: Andrea Parri Sent: Thursday, October 3, 2019
8:52 AM
>
> If the hardware supports TSC scaling, Hyper-V will set bit 15 of the
> HV_PARTITION_PRIVILEGE_MASK in guest VMs with a compatible Hyper-V
> configuration version. Bit 15 corresponds to the
> AccessTscInvariantControls privilege.
From: Branden Bonaby Sent: Thursday, October 3,
2019 2:02 PM
>
> Introduce user specified latency in the packet reception path
> By exposing the test parameters as part of the debugfs channel
> attributes. We will control the testing state via these attributes.
>
> Signed-off-by: Branden
1 - 100 of 2124 matches
Mail list logo
