[PATCH 2/2] Input: pm8941-pwrkey: Introduce reboot mode support

In some Qualcomm platforms the magic for informing LK which mode to reboot into is stored in the PON_SOFT_RB_SPARE register. Register with the reboot mode helpers to expose this to the user. Signed-off-by: Bjorn Andersson --- drivers/input/misc/Kconfig | 1 +

[PATCH 1/2] power: reset: reboot-mode: Make include file global

Move the reboot-mode.h include file into include/linux to allow drivers outside drivers/power/reset to implement reboot-mode. Signed-off-by: Bjorn Andersson --- drivers/power/reset/reboot-mode.c| 2 +- drivers/power/reset/syscon-reboot-mode.c

Odp: Re: Dzial Kredytowy

Witam, Czy potrzebujesz zatwierdzony biznes i prywatnego kredytu / Finansowanie w maksymalnej wysokosci 3% w skali roku? Skontaktuj sie z nami po wiecej szczególów w razie zainteresowania. Dziekuje. BSN Capital Partners Ltd (London) Zarzadzanie. -- Angielska wersja

[PATCH v2 1/3] firmware: qcom: scm: Expose secure IO service

The secure IO service provides operations for reading and writing secure memory from non-secure mode, expose this API through SCM. Signed-off-by: Bjorn Andersson --- Changes since v1: - Correct scm-call return value handling - Make scm_io_readl() return data by

[PATCH v2 2/3] firmware: qcom: scm: Expose download-mode control

In order to aid post-mortem debugging the Qualcomm platforms provides a "memory download mode", where the boot loader will provide an interface for custom tools to "download" the content of RAM to a host machine. The mode is triggered by writing a magic value somehwere in RAM, that is read in the

[PATCH v2 3/3] arm64: dts: qcom: Specify dload address for msm8916 and msm8996

On msm8916 and msm8996 boards a secure io-write is used to write the magic for selecting "download mode", specify this address in the DeviceTree. Note that qcom_scm.download_mode=1 must be specified on the kernel command line for the kernel to attempt selecting download mode. Signed-off-by:

Re: [PATCH] JFS: do not ignore return code from write_one_page()

On Fri, 26 May 2017 15:48:51 -0500 Dave Kleikamp wrote: > Andrew, > > Do you want to pick this up into akpm-current? I could push it through > the jfs tree, but without the change to write_one_page(), my version of > the patch would need a manual merge. It'd be a

Re: [PATCH v1 1/1] intel_telemetry_debugfs: fix oops found while load/unload module test

Hi! > On Sat, May 27, 2017 at 08:17:39AM -0700, priyalee.kushw...@intel.com wrote: > > From: Priyalee Kushwaha > > > > This fix oops found while testing load/unload test of > > intel_telemetry_debugfs module. Module_init uses register_pm_notifier > > for PM

[GIT PULL] Please pull powerpc/linux.git powerpc-4.12-4 tag

Hi Linus, Please pull some more powerpc fixes for 4.12: The following changes since commit e41e53cd4fe331d0d1f06f8e4ed7e2cc63ee2c34: powerpc/mm: Fix virt_addr_valid() etc. on 64-bit hash (2017-05-19 13:04:35 +1000) are available in the git repository at:

[PATCH v3 09/10] ARM: dts: sun8i: Add basic dtsi file for Allwinner R40

From: Chen-Yu Tsai The Allwinner R40 SoC is marketed as the successor to the A20 SoC. The R40 is a smaller chip than the A20, but features the same set of programmable pins, with a couple extra pins and some new pin functions. The chip features 4 Cortex-A7 cores and a Mali-400 MP2

[PATCH v3 04/10] pinctrl: sunxi: drop dedicated A20 driver

As we added A20 support to A10 pinctrl driver, now we can delete the dedicated A20 pinctrl driver, which is duplicated code. Signed-off-by: Icenowy Zheng --- Changes in v3: - Only remove the A20 driver(A10 driver for A20 is enabled in the previous commit now).

[tip:timers/core] posix-timers: Remove mmtimer leftovers

Commit-ID: f822798e3ced63427d57d128ee8d118126455f84 Gitweb: http://git.kernel.org/tip/f822798e3ced63427d57d128ee8d118126455f84 Author: Dimitri Sivanich AuthorDate: Fri, 26 May 2017 23:30:52 +0200 Committer: Thomas Gleixner CommitDate: Sat, 27 May

Re: [PATCH] scripts/gdb: make lx-dmesg command work (reliably)

On Fri, May 26, 2017 at 2:12 PM, Jan Kiszka wrote: > On 2017-05-26 13:04, André Draszik wrote: >> +log_buf_addr = >> int(str(gdb.parse_and_eval("'printk.c'::log_buf")).split()[0], 16) > > Overlong line. Please stay pep8 compliant. What I heard from colleague of

Re: [Q] What about PCI mmio access alignment?

On Thu, May 25, 2017 at 1:12 PM, Du, Changbin wrote: > I have a basic quesion about the alignment when access PCI bar mmio space. Is > the address accessed must be DW aligned and count must be DW aligned? I guess the best answer is PCI architecture specification. Book I

Re: [PATCH v2 13/27] thunderbolt: Read vendor and device name from DROM

On Sat, May 27, 2017 at 6:57 PM, Andy Shevchenko wrote: > On Fri, May 26, 2017 at 7:09 PM, Mika Westerberg > wrote: >> The device DROM contains name of the vendor and device among other >> things. Extract this information and expose it

Re: [PATCH v2 13/27] thunderbolt: Read vendor and device name from DROM

On Fri, May 26, 2017 at 7:09 PM, Mika Westerberg wrote: > The device DROM contains name of the vendor and device among other > things. Extract this information and expose it to the userspace via two > new attributes. > +static const char *parse_name(const u8

Re: [RFC][PATCH 0/4] Fixes for two recently found timekeeping bugs

On Sat, May 27, 2017 at 12:38 AM, Ingo Molnar wrote: > > * John Stultz wrote: > >> As part of the Linaro Linux Kernel Functional Test (LKFT) >> effort, test failures from kselftest/timer's >> inconsistency-check were reported connected to >>

Re: [PATCH 16/16] platform/x86: dell-wmi: Convert to the WMI bus infrastructure

On May 27, 2017 9:04:38 AM PDT, Andy Lutomirski wrote: >On Sat, May 27, 2017 at 3:50 AM, Pali Rohár >wrote: >> On Saturday 27 May 2017 07:31:30 Darren Hart wrote: >>> - dell_wmi_input_dev->name = "Dell WMI hotkeys"; >>> - dell_wmi_input_dev->phys =

Re: [PATCH 06/10] gpio: mockup: refuse to accept an odd number of GPIO ranges

On Sat, May 27, 2017 at 8:29 PM, Andy Shevchenko wrote: > On Thu, May 25, 2017 at 11:33 AM, Bartosz Golaszewski wrote: >> Currently we ignore the last odd range value, since each chip is >> described by two values. Be more strict and require the user to

Re: [ANNOUNCE] v4.9.30-rt20

Yes, meanwhile I have looked it up and found that it belongs to 7B96E8162A8CF5D1 Sorry. All good! On 27/05/17 19:33, Sebastian Andrzej Siewior wrote: On 2017-05-27 19:19:51 [+0200], Bernhard Landauer wrote: Thanks a lot as always! I have a question regarding packager keys: It seems this time

Re: [PATCH v4 05/10] hyper-v: use fast hypercall for HVCALL_SIGNAL_EVENT

On Wed, May 24, 2017 at 3:04 PM, Vitaly Kuznetsov wrote: > We need to pass only 8 bytes of input for HvSignalEvent which makes it a > perfect fit for fast hypercall. hv_input_signal_event_buffer is not needed > any more and hv_input_signal_event is converted to union for

[PATCH 6/7] clocksource: Rename CLKSRC_OF to TIMER_OF

The config option name is now renamed to 'TIMER_OF' for consistency with the CLOCKSOURCE_OF_DECLARE => TIMER_OF_DECLARE change. Signed-off-by: Daniel Lezcano --- arch/arm/Kconfig| 10 +++--- arch/arm/mach-bcm/Kconfig | 2 +-

[PATCH 5/7] clocksource: Rename clksrc

The table name is now renamed to 'timer' for consistency with the CLOCKSOURCE_OF_DECLARE => TIMER_OF_DECLARE change. Signed-off-by: Daniel Lezcano --- drivers/clocksource/clksrc-probe.c | 18 +- include/asm-generic/vmlinux.lds.h | 6 +++---

[PATCH 7/7] clocksource: Rename CLKSRC_ACPI

The config option name is now renamed to 'CLKSRC_ACPI' for consistency with the CLOCKSOURCE_OF_DECLARE => TIMER_OF_DECLARE change. Signed-off-by: Daniel Lezcano --- drivers/clocksource/Kconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 4/7] clocksource: Rename CLOCKSOURCE_ACPI_DECLARE

The macro name is now renamed to 'TIMER_ACPI_DECLARE' for consistency with the CLOCKSOURCE_OF_DECLARE => TIMER_OF_DECLARE change. Signed-off-by: Daniel Lezcano --- drivers/clocksource/arm_arch_timer.c | 2 +- include/linux/clocksource.h | 2 +- 2 files

[PATCH 1/7] Revert "clockevents: Add a clkevt-of mechanism like clksrc-of"

After discussing it, this feature is dropped as it is not considered adequate: https://patchwork.kernel.org/patch/9639317/ There is no user of this macro yet, so there is no impact on the drivers. This reverts commit 376bc27150f180d9f5eddec6a14117780177589d. Cc: Mark Rutland

[PATCH v3 03/10] pinctrl: sunxi: add A20 support to A10 driver

As A20 is designed as a pin-compatible upgrade of A10, their pin controller are very similar, and can share one driver. Add A20 support to the A10 driver. Signed-off-by: Icenowy Zheng --- Changes in v3: - Enable A10 driver for A20 and disable A20 driver in this commit, in

[PATCH v3 01/10] arm: sunxi: add support for R40 SoC

Allwinner R40 is a new SoC, with Quad Core Cortex-A7 and peripherals like A20. Add support for it. Signed-off-by: Icenowy Zheng --- Changes in v3: - Use V1.0 documents. Documentation/arm/sunxi/README | 6 ++ Documentation/devicetree/bindings/arm/sunxi.txt

[PATCH v3 06/10] pinctrl: sunxi: add support of R40 to A10 pinctrl driver

R40 is said to be an upgrade of A20, and its pin configuration is also similar to A20 (and thus similar to A10). Add support for R40 to the A10 pinctrl driver. Signed-off-by: Icenowy Zheng --- drivers/pinctrl/sunxi/Kconfig | 2 +-

[PATCH v3 05/10] dt-bindings: add compatible string for Allwinner R40 pinctrl

Allwinner R40 has a pin controller like the ones in older Allwinner SoCs (especially A20), and can use modified version of the A10/A20 pinctrl driver. Add a compatible string for it. Signed-off-by: Icenowy Zheng Acked-by: Rob Herring --- Changes in v3: - Added

[PATCH v3 02/10] pinctrl: sunxi: Add SoC ID definitions for A10, A20 and R40 SoCs

Allwinner A10, A20 and R40 SoCs have similar GPIO layout. Add SoC definitions in pinctrl-sunxi.h, in order to merge A20 support into A10 driver, and add R40 support into it. Signed-off-by: Icenowy Zheng --- Changes in v3: - Commit message change.

[PATCH v3 00/10] Initial Allwinner R40 support

This is the first non-RFC version of this patchset, which added basical support including I2C, UART and MMC to the mainline Linux. The pinctrl driver of A20 is also merged into the one of A10 before R40 support is added into the A10 driver. Chen-Yu Tsai (2): ARM: dts: sun8i: Add basic dtsi

hi dear

Good day dear, i hope this mail meets you well? my name is Jack, from the U.S. I know this may seem inappropriate so i ask for your forgiveness but i wish to get to know you better, if I may be so bold. I consider myself an easy-going man, adventurous, honest and fun loving person but I am

Re: [PATCH] pid_ns: Allow to get pid_for_children ns before child_reaper is created

Kirill Tkhai writes: > This patch prohibits pid allocation till child_reaper > of pid namespace is set, and it makes possible and safe > to get just unshared pid_ns from "/proc/[pid]/ns/pid_for_children" > file. This may be useful to determine user_ns of such a created >

Re: [PATCH] misc: ad525x_dpot_spi: Add device tree support

Hi, Thanks for the patch. On 05/26/2017 08:17 PM, Roshni Shah wrote: > --- /dev/null > +++ b/Documentation/devicetree/bindings/misc/ad525x_dpot-spi.txt > @@ -0,0 +1,44 @@ > +Digital Potentiometers (SPI) compatible with Analog Devices family > + > +Required properties: > +- compatible: Should be

Re: [PATCH v2 2/6] stmmac: pci: Use stmmac_pci_info for all devices

On Fri, May 26, 2017 at 7:07 PM, Jan Kiszka wrote: > Make stmmac_default_data compatible with stmmac_pci_info.setup and use > an info structure for all devices. This allows to make the probing more > regular. > +#define STMMAC_DEVICE(vendor_id, dev_id, info) { \ >

[PATCH v6 2/6] iommu: of: Ignore all errors except EPROBE_DEFER

While deferring the probe of IOMMU masters, xlate and add_device callbacks called from of_iommu_configure can pass back error values like -ENODEV, which means the IOMMU cannot be connected with that master for real reasons. Before the IOMMU probe deferral, all such errors were ignored. Now all

Re: [PATCH v3 09/10] gpio-exar/8250-exar: Make set of exported GPIOs configurable

On Fri, May 26, 2017 at 7:02 PM, Jan Kiszka wrote: > On the SIMATIC, IOT2040 only a single pin is exportable as GPIO, the > rest is required to operate the UART. To allow modeling this case, > expand the platform device data structure to specify a (consecutive) pin >

[PATCH v6 3/6] ACPI/IORT: Ignore all errors except EPROBE_DEFER

While deferring the probe of IOMMU masters, xlate and add_device callbacks called from iort_iommu_configure can pass back error values like -ENODEV, which means the IOMMU cannot be connected with that master for real reasons. Before the IOMMU probe deferral, all such errors were ignored. Now all

[PATCH v6 6/6] arm: dma-mapping: Reset the device's dma_ops

arch_teardown_dma_ops() being the inverse of arch_setup_dma_ops() ,dma_ops should be cleared in the teardown path. Currently, only the device's iommu mapping structures are cleared in arch_teardown_dma_ops, but not the dma_ops. So on the next reprobe, dma_ops left in place is stale from the first

[PATCH v6 5/6] ACPI/IORT: Move the check to get iommu_ops from translated fwspec

From: Lorenzo Pieralisi With IOMMU probe deferral, iort_iommu_configure can be called multiple times for the same device. Hence we have a check to see if the device's fwspec is already translated and return the iommu_ops from that directly. But the check is wrongly

[PATCH v6 4/6] ARM: dma-mapping: Don't tear down third-party mappings

From: Laurent Pinchart arch_setup_dma_ops() is used in device probe code paths to create an IOMMU mapping and attach it to the device. The function assumes that the device is attached to a device-specific IOMMU instance (or at least a device-specific

Re: [PATCH] dsa: mv88e6xxx: fix returnvar.cocci warnings

On Sat, May 27, 2017 at 06:38:14AM +0200, Julia Lawall wrote: > Remove unneeded variable used to store return value. > > Generated by: scripts/coccinelle/misc/returnvar.cocci Hi Julia Thanks for the patch. However, Vivien already submitted a patch. Andrew

[PATCH] ALSA: declare snd_kcontrol_new structures as const

Declare snd_kcontrol_new structures as const as they are only passed an argument to the function snd_ctl_new1. This argument is of type const, so snd_kcontrol_new structures having this property can be made const. Done using Coccinelle: @r disable optional_qualifier@ identifier x; position p; @@

Re: [PATCH 2/2] reset: Add basic single-register reset driver

On Fri, May 26, 2017 at 6:32 AM, Joel Stanley wrote: > This driver is a basic single-register reset controller driver that > supports clearing a single bit in a register. > While this makes sense, I'm wondering if there can be generic interface for this from which we can derive

[PATCH v4 00/11] drm: sun4i: Add support for the HDMI controller

Hi, Here is an attempt at getting the HDMI controller running. This HDMI controller is found on a number of old Allwinner SoCs (A10, A10s, A20, A31). This driver only supports for now the A10s because it was an easy target, being very close to the A13 that is already supported by our DRM

[PATCH v4 05/11] drm/sun4i: tcon: Change vertical total size computation inconsistency

Both TCON channels need to have the resolution doubled, since the size the hardware is going to use is whatever we put in the register divided by two. However, we handle it differently for the two channels: in the channel 0, our register access macro does the multiplication of the value passed as

[PATCH v4 09/11] dt-bindings: display: sun4i: Add allwinner,tcon-channel property

The Allwinner Timings Controller has two, mutually exclusive, channels. When the binding has been introduced, it was assumed that there would be only a single user per channel in the system. While this is likely for the channel 0 which only connects to LCD displays, it turns out that the channel

[PATCH v4 07/11] drm/sun4i: Ignore the generic connectors for components

The generic connectors such as hdmi-connector doesn't have any driver in, so if they are added to the component list, we will be waiting forever for a non-existing driver to probe. Add a list of the connectors we want to ignore when building our component list. Reviewed-by: Chen-Yu Tsai

[PATCH v4 03/11] drm/sun4i: tcon: Switch mux on only for composite

Even though that mux is undocumented, it seems like it needs to be set to 1 when using composite, and 0 when using HDMI. Signed-off-by: Maxime Ripard Acked-by: Chen-Yu Tsai --- drivers/gpu/drm/sun4i/sun4i_tcon.c | 9 - 1 file changed, 8

[PATCH v4 04/11] drm/sun4i: tcon: Fix tcon channel 1 backporch calculation

It seems like what's called a backporch in the datasheet is actually the backporch plus the sync period. Fix that in our driver. Acked-by: Chen-Yu Tsai Signed-off-by: Maxime Ripard --- drivers/gpu/drm/sun4i/sun4i_tcon.c | 4 ++-- 1 file changed,

Re: [PATCH 05/10] gpio: mockup: improve the debugfs input sanitization

On Sat, May 27, 2017 at 7:45 PM, Andy Shevchenko wrote: > On Thu, May 25, 2017 at 11:33 AM, Bartosz Golaszewski wrote: >> We're currently only checking the first character of the input to the >> debugfs event files, so a string like '0sdfdsf' is valid

Re: [RFC][PATCH 0/9] Make containers kernel objects

On Mon, 2017-05-22 at 14:04 -0500, Eric W. Biederman wrote: > David Howells writes: > > > Here are a set of patches to define a container object for the > > kernel and > > to provide some methods to create and manipulate them. > > > > The reason I think this is necessary is

Re: [PATCH v4 03/10] x86/hyper-v: make hv_do_hypercall() inline

On Wed, May 24, 2017 at 3:03 PM, Vitaly Kuznetsov wrote: > We have only three call sites for hv_do_hypercall() and we're going to > change HVCALL_SIGNAL_EVENT to doing fast hypercall so we can inline this > function for optimization. > > Hyper-V top level functional

Re: [PATCH v2] um: add dummy ioremap and iounmap functions

Hi Logan, On Thu, May 25, 2017 at 5:53 PM, Logan Gunthorpe wrote: > On 25/05/17 09:48 AM, Richard Weinberger wrote: >> Which ones are failing? >> I thought we killed the problem by making CONFIG_COMPILE_TEST depend on !UML. > > None, at the moment. My work is trying to add

Re: [PATCH 4/6] regulator: hi6421v530: add driver for hi6421v530 voltage regulator

On Fri, May 26, 2017 at 7:38 PM, Mark Brown wrote: > On Fri, May 26, 2017 at 02:35:16PM +0800, Guodong Xu wrote: > > Overall this driver needs quite a lot of modernization, it's at least a > couple of years out of date in how it's using the framework - there's > barely any use

[GIT PULL] TTY/Serial fixes for 4.12-rc3

The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6: Linux 4.12-rc1 (2017-05-13 13:19:49 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/ tags/tty-4.12-rc3 for you to fetch changes up to

Re: [PATCH v3] genirq: Check irq disabled & masked states in irq_shutdown

On Sat, 27 May 2017, Jeffy Chen wrote: > If a irq is already disabled, irq_shutdown may try to disable it again, > for example: > devm_request_irq->irq_startup->irq_enable > disable_irq <-- disabled > devm_free_irq->irq_shutdown <-- disable it

[PATCH] drm/rockchip: Correct vop out_mode configure

Force vop output mode on encoder driver seem not a good idea, EDP, HDMI, DisplayPort all have 10bit input on rk3399, On non-10bit vop, vop 8bit output bit[0-7] connect to the encoder high 8bit [2-9]. So force RGB10 to RGB888 on vop driver would be better. And another problem, EDP check crtc id

Re: [PATCH] platform/x86: wmi: Fix printing info about WDG structure

On Sat, May 27, 2017 at 2:51 PM, Pali Rohár wrote: > object_id and notify_id are in one union structure and their meaning is > defined by flags. Therefore do not print notify_id for non-event block and > do not print object_id for event block. Remove also reserved member as

Re: [PATCH v2 5/6] stmmac: pci: Use dmi_system_id table for retrieving PHY addresses

On Fri, May 26, 2017 at 7:07 PM, Jan Kiszka wrote: > Avoids reimplementation of DMI matching in stmmac_pci_find_phy_addr. > struct stmmac_pci_dmi_data { > - const char *name; > - const char *asset_tag; > - unsigned int func; > + int func; >

Re: [PATCH v3 02/10] gpio-exar/8250-exar: Do not even instantiate a GPIO device for Commtech cards

On Fri, May 26, 2017 at 7:02 PM, Jan Kiszka wrote: > Commtech adapters need the MPIOs for internal purposes, and the > gpio-exar driver already refused to pick them up. But there is actually > no point in even creating the underlying platform device. FWIW: Reviewed-by:

ATTENZIONE

ATTENZIONE; La cassetta postale ha superato il limite di archiviazione, che è 5 GB come definiti dall'amministratore, che è attualmente in esecuzione su 10.9GB, non si può essere in grado di inviare o ricevere nuovi messaggi fino a ri-convalidare la tua mailbox. Per rinnovare la vostra casella

Re: [PATCH v1 1/1] intel_telemetry_debugfs: fix oops found while load/unload module test

On Sat, May 27, 2017 at 9:54 AM, Pavel Machek wrote: >> On Sat, May 27, 2017 at 08:17:39AM -0700, priyalee.kushw...@intel.com wrote: >> +Rafael, Len, Pavel, linux-pm: Is there a preferred approach for dealing with >>CONFIG_PM_SLEEP? > > Yeah, empty

Re: [PATCH 15/16] platform/x86: wmi-mof: New driver to expose embedded WMI MOF metadata

Hi! Note that in WMI is stored binary MOF (BMOF; .bmf file; compiled MOF), not ordinary MOF data which are plain text. So maybe it could make sense to include "B" into name of sysfs entry? Or not? (Just suggestion) On Saturday 27 May 2017 07:31:29 Darren Hart wrote: > From: Andy Lutomirski

[PATCH] platform/x86: wmi: Fix printing info about WDG structure

object_id and notify_id are in one union structure and their meaning is defined by flags. Therefore do not print notify_id for non-event block and do not print object_id for event block. Remove also reserved member as it does not have any defined meaning or type yet. As object_id and notify_id

[PATCH] x86/kernel: Add generic handler for NMI events

The kernel allows drivers to register NMI handlers, or to use sysctls like unknown_nmi_panic to control the behavior of the system when an NMI is received by the kernel. This patch adds a generic handler where sysadmins can specify the behaviour to adopt for each NMI event code. List of events is

Re: [PATCH 0/8] i2c: refactor core and break out blocks

> If you don't mind sending the whole series to the intel-gfx list (Cc'd), > our CI will run a bunch of tests on it, exercising our use of the I2C > adapter interfaces for display data channel and I2C over Display Port > native aux. Cool, that sounds very helpful! Thanks for the offer, I'll

[ANNOUNCE] v4.9.30-rt20

Dear RT folks! I'm pleased to announce the v4.9.30-rt20 patch set. Changes since v4.9.30-rt19: - The patch "timers: Don't wake ktimersoftd on every tick" has been reverted because this optimisation can lead to timers not getting expired. Reported by Klaus Gusenleitner, debugged by

Re: [ANNOUNCE] v4.9.30-rt20

On 2017-05-27 19:19:51 [+0200], Bernhard Landauer wrote: > Thanks a lot as always! > I have a question regarding packager keys: > It seems this time the patch has been signed with a different key than > usual: > > unknown public key 4FE5E3262872E4CC > > Could you please let me know where you

Re: [ANNOUNCE] v4.9.30-rt20

Thanks a lot as always! I have a question regarding packager keys: It seems this time the patch has been signed with a different key than usual: unknown public key 4FE5E3262872E4CC Could you please let me know where you packager keys can be looked up? Thanks regards Bernhard On 27/05/17

Re: [PATCH v4 09/10] x86/hyper-v: support extended CPU ranges for TLB flush hypercalls

On Wed, May 24, 2017 at 3:04 PM, Vitaly Kuznetsov wrote: > Hyper-V hosts may support more than 64 vCPUs, we need to use > HVCALL_FLUSH_VIRTUAL_ADDRESS_SPACE_EX/LIST_EX hypercalls in this > case. > +{ > + /* > +* We can't be sure that translated vcpu numbers

Re: [PATCH] Revert "firmware: vpd: remove platform driver"

On Fri, May 26, 2017 at 01:57:49PM -0700, Dmitry Torokhov wrote: > This reverts commit 7975bd4cca05a99aa14964cfa22366ee64da50ad, because > VPD relies on driver core to handle deferrals returned by > coreboot_table_find(). > > Signed-off-by: Dmitry Torokhov >

drivers/hwmon/aspeed-pwm-tacho.c:337:35: error: storage size of 'aspeed_pwm_tacho_regmap_config' isn't known

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: c86daad2c25bfd4a33d48b7691afaa96d9c5ab46 commit: 2d7a548a3eff382da5cd743670693b7657327714 drivers: hwmon: Support for ASPEED PWM/Fan tach date: 7 weeks ago config: x86_64-randconfig-s3-05271727 (attached

[PATCH v2]: perf/core: addressing 4x slowdown during per-process, profiling of STREAM benchmark on Intel Xeon Phi

Motivation: The issue manifests like 4x slowdown when profiling single thread STREAM benchmark on Intel Xeon Phi running RHEL7.2 (Intel MPSS distribution). Perf profiling is done in per-process mode and involves about 30 core events. In case the benchmark is OpenMP based and runs under profiling

TCP get SND_CWND change on loss event

I want to store the value of snd_cwnd when a congestion event occurs (value before snd_cwnd is reduced), and the new value of snd_cwnd (the value it has been reduced to). In other words: the congestion window before and after a congestion event occurs. I'm uncertain where (and how) it would be

Re: TCP get SND_CWND change on loss event

On Sat, May 27, 2017 at 02:08:01PM +0200, Lars Erik Storbukås wrote: > I want to store the value of snd_cwnd when a congestion event occurs > (value before snd_cwnd is reduced), and the new value of snd_cwnd (the > value it has been reduced to). In other words: the congestion window > before and

Re: [PATCH] platform/x86: wmi: Fix printing info about WDG structure

On Saturday 27 May 2017 15:07:09 Andy Shevchenko wrote: > On Sat, May 27, 2017 at 2:51 PM, Pali Rohár > wrote: > > object_id and notify_id are in one union structure and their > > meaning is defined by flags. Therefore do not print notify_id for > > non-event block and do

Re: [PATCHv1, RFC 5/8] x86/mm: Fold p4d page table layer at runtime

On Thu, May 25, 2017 at 4:33 PM, Kirill A. Shutemov wrote: > This patch changes page table helpers to fold p4d at runtime. > The logic is the same as in . > > Signed-off-by: Kirill A. Shutemov > --- >

Re: [PATCH v2 21/27] thunderbolt: Store Thunderbolt generation in the switch structure

On Fri, May 26, 2017 at 7:09 PM, Mika Westerberg wrote: > In some cases it is useful to know what is the Thunderbolt generation > the switch supports. This introduces a new field to struct switch that > stores the generation of the switch based on the device ID.

Re: [PATCH] platform/x86: dell-rbtn: Improve explanation about DELLABC6

On Sat, May 27, 2017 at 8:16 AM, Darren Hart wrote: > From: Andy Lutomirski > > According to Mario at Dell, the DELLABC6 device should not be used on a > Linux system. It also conflicts with Intel-HID and its interactions with > Network Manager. Document

Re: [PATCH] platform/x86: dell-rbtn: Improve explanation about DELLABC6

On Saturday 27 May 2017 18:07:14 Andy Lutomirski wrote: > On Sat, May 27, 2017 at 4:01 AM, Pali Rohár > wrote: > > On Saturday 27 May 2017 07:16:19 Darren Hart wrote: > >> From: Andy Lutomirski > >> > >> According to Mario at Dell, the DELLABC6 device

Re: [PATCH 06/10] gpio: mockup: refuse to accept an odd number of GPIO ranges

On Thu, May 25, 2017 at 11:33 AM, Bartosz Golaszewski wrote: > Currently we ignore the last odd range value, since each chip is > described by two values. Be more strict and require the user to > pass an even number of ranges. > - if (gpio_mockup_params_nr < 2) > + if

[PATCH] moduleparam: fix doc: hwparam_irq configures an IRQ

Signed-off-by: Sylvain 'ythier' Hitier --- include/linux/moduleparam.h |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/moduleparam.h b/include/linux/moduleparam.h index 6be1949..1ee7b30 100644 --- a/include/linux/moduleparam.h +++

Re: [PATCH v7 02/26] x86/mm: Relocate page fault error codes to traps.h

On Fri, May 26, 2017 at 08:40:26PM -0700, Ricardo Neri wrote: > This change was initially intended to only rename the error codes, > without functional changes. Would making change be considered a change > in functionality? How? The before-and-after asm should be the identical. --

Re: [PATCH] platform/x86: dell-wmi: Add a better description for "stealth mode"

On Sat, May 27, 2017 at 8:16 AM, Darren Hart wrote: > From: Andy Lutomirski > > This is based on Mario's explanation and observation of my laptop. > Reviewed-by: Andy Shevchenko > Suggested-by: "Pali Rohár"

Re: [PATCH] platform/x86: dell-rbtn: Improve explanation about DELLABC6

On Saturday 27 May 2017 07:16:19 Darren Hart wrote: > From: Andy Lutomirski > > According to Mario at Dell, the DELLABC6 device should not be used on > a Linux system. It also conflicts with Intel-HID and its > interactions with Network Manager. Document that we are aware of the

[PATCH] RFC: platform/x86: wmi: Fix check for method instance number

instance_count defines number of instances of data block and instance itself is indexed from zero, which means first instance has number 0. Therefore check for invalid instance should be non-strict inequality. Signed-off-by: Pali Rohár --- I'm marking this patch as RFC

Re: [PATCH] platform/x86: wmi: Fix printing info about WDG structure

On Saturday 27 May 2017 15:17:29 Pali Rohár wrote: > On Saturday 27 May 2017 15:07:09 Andy Shevchenko wrote: > > On Sat, May 27, 2017 at 2:51 PM, Pali Rohár > > > > wrote: > > > object_id and notify_id are in one union structure and their > > > meaning is defined by flags.

Problem with new X.509 is_hash_blacklisted() interface

Added by commit 436529562df2748fd9918f578205b22cf8ced277 Author: David Howells Date: Mon Apr 3 16:07:25 2017 +0100 X.509: Allow X.509 certs to be blacklisted Ironically it duplicates a UEFI bug we've been struggling with for a while in the pkcs11 handlers: namely

Re: [PATCH v2 07/27] thunderbolt: Allow passing NULL to tb_ctl_free()

On Fri, May 26, 2017 at 7:09 PM, Mika Westerberg wrote: > Following the usual pattern used in many places, we allow passing NULL > pointer to tb_ctl_free(). Then the user can call the function regardless > if it has allocated control channel or not making the code

Re: [x86/mm] e2a7dcce31: kernel_BUG_at_arch/x86/mm/tlb.c

On Sat, May 27, 2017 at 6:31 AM, kernel test robot wrote: > > FYI, we noticed the following commit: > > commit: e2a7dcce31f10bd7471b4245a6d1f2de344e7adf ("x86/mm: Rework lazy TLB to > track the actual loaded mm") >

[PATCH v4 10/11] drm/sun4i: Add HDMI support

The earlier Allwinner SoCs (A10, A10s, A20, A31) have an embedded HDMI controller. That HDMI controller is able to do audio and CEC, but those have been left out for now. Reviewed-by: Chen-Yu Tsai Signed-off-by: Maxime Ripard ---

[PATCH v4 08/11] dt-bindings: display: sun4i: Add HDMI display bindings

One of the possible output of the display pipeline, on the SoCs that have it, is the HDMI controller. Add a binding for it. Acked-by: Chen-Yu Tsai Acked-by: Rob Herring Signed-off-by: Maxime Ripard ---

[PATCH v4 11/11] drm/sun4i: Add compatible for the A10s pipeline

The A10s has a slightly different display pipeline than the A13, with an HDMI controller. Add a compatible for it. Reviewed-by: Chen-Yu Tsai Acked-by: Rob Herring Signed-off-by: Maxime Ripard ---

[PATCH v4 02/11] drm/sun4i: tcon: Move the muxing out of the mode set function

The muxing can actually happen on both channels on some SoCs, so it makes more sense to just move it out of the sun4i_tcon1_mode_set function and create a separate function that needs to be called by the encoders. Let's do that and convert the existing drivers. Signed-off-by: Maxime Ripard

[PATCH v4 01/11] drm/sun4i: tcon: Add channel debug

While all functions have debug logs, the channel enable and disable are not logged. Make sure this is the case. Acked-by: Chen-Yu Tsai Signed-off-by: Maxime Ripard --- drivers/gpu/drm/sun4i/sun4i_tcon.c | 4 1 file changed, 4 insertions(+)

[PATCH v4 06/11] drm/sun4i: tcon: multiply the vtotal when not in interlace

It appears that the total vertical resolution needs to be doubled when we're not in interlaced. Make sure that is the case. Signed-off-by: Maxime Ripard --- drivers/gpu/drm/sun4i/sun4i_tcon.c | 26 ++ 1 file changed, 22 insertions(+), 4

Re: [RFC PATCH] ASoC: Intel: sst: Delete sst_save_shim64(); saved regs are never used

On Fri, May 26, 2017 at 7:34 PM, Douglas Anderson wrote: > In commit 9a075265c6dc ("ASoC: Intel: sst: Remove unused function > sst_restore_shim64()"), we deleted the sst_restore_shim64() since it > was never used. ...but a quick look at the code shows that we should > also

Re: [x86/mm] e2a7dcce31: kernel_BUG_at_arch/x86/mm/tlb.c

On Sat, May 27, 2017 at 9:00 AM, Andy Lutomirski wrote: > On Sat, May 27, 2017 at 6:31 AM, kernel test robot > wrote: >> >> FYI, we noticed the following commit: >> >> commit: e2a7dcce31f10bd7471b4245a6d1f2de344e7adf ("x86/mm: Rework lazy TLB >> to track

  1   2   3   4   5   6   >