[PATCH 01/10] staging: iio: tsl2583: add of_match table for device tree support

Add device tree support for the tsl2583 IIO driver with no custom properties. Signed-off-by: Brian Masney --- .../devicetree/bindings/iio/light/tsl2583.txt | 26 ++ drivers/staging/iio/light/tsl2583.c| 13 +++ 2 files

[PATCH 09/10] staging: iio: tsl2583: add error code to sysfs store functions

in_illuminance_input_target_store() and in_illuminance_calibrate_store() validated the data from userspace, however it would not return an error code to userspace if an invalid value was passed in. This patch changes these functions so that they return -EINVAL if invalid data is passed in.

[PATCH 06/10] staging: iio: tsl2583: convert to use iio_chan_spec and {read,write}_raw

The tsl2583 driver directly creates sysfs attributes that should instead be created by the IIO core on behalf of the driver. This patch adds the iio_chan_spec array, the relevant info_mask elements and the read_raw() and write_raw() functions to take advantage of features provided by the IIO core.

[PATCH 07/10] staging: iio: tsl2583: convert illuminance0_calibscale sysfs attr to use iio_chan_spec

The illuminance0_calibscale sysfs attribute is not currently created by the IIO core. This patch adds the appropriate mask to iio_chan_spec, along with the appropriate data handling in the read_raw() and write_raw() functions, so that the sysfs attribute is created by the IIO core. With this

[PATCH 10/10] staging: iio: tsl2583: add locking to sysfs attributes

in_illuminance_input_target_show(), in_illuminance_input_target_store(), in_illuminance_calibrate_store(), and in_illuminance_lux_table_store() accesses data from the tsl2583_chip struct. Some of these fields can be modified by other parts of the driver concurrently. This patch adds the mutex

[PATCH 08/10] staging: iio: tsl2583: use IIO_*_ATTR* macros to create sysfs entries

Use the IIO_CONST_ATTR, IIO_DEVICE_ATTR_RW, and IIO_DEVICE_ATTR_WO macros for creating the in_illuminance_calibscale_available, in_illuminance_integration_time_available, in_illuminance_input_target, in_illuminance_calibrate, and in_illuminance_lux_table sysfs entries. Previously these sysfs

[PATCH 05/10] staging: iio: tsl2583: check return values from taos_chip_{on,off}

The return value from taos_chip_on() and taos_chip_off() was not checked in taos_luxtable_store() and taos_probe(). This patch adds proper error checking to these function calls. Signed-off-by: Brian Masney --- drivers/staging/iio/light/tsl2583.c | 26

[PATCH 03/10] staging: iio: tsl2583: return proper error code instead of -1

taos_als_calibrate() has a code path where -1 is returned. This patch changes the code so that a proper error code is returned. Signed-off-by: Brian Masney --- drivers/staging/iio/light/tsl2583.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[tip:perf/urgent] perf/core: Protect PMU device removal with a 'pmu_bus_running' check, to fix CONFIG_DEBUG_TEST_DRIVER_REMOVE=y kernel panic

Commit-ID: 0933840acf7b65d6d30a5b6089d882afea57aca3 Gitweb: http://git.kernel.org/tip/0933840acf7b65d6d30a5b6089d882afea57aca3 Author: Jiri Olsa AuthorDate: Thu, 20 Oct 2016 13:10:11 +0200 Committer: Ingo Molnar CommitDate: Fri, 28 Oct 2016 11:06:25

Re: [PATCH v2 0/3] usb: musb: da8xx: Fix few issues

On 10/28/2016 11:31 AM, Alexandre Bailon wrote: > On 10/27/2016 08:44 PM, David Lechner wrote: >> On 10/27/2016 12:16 PM, David Lechner wrote: >>> On 10/26/2016 05:58 AM, Alexandre Bailon wrote: Currently, the USB OTG of the da8xx doesn't work. This series intend to fix them.

Re: [PATCH] x86/cpuid: expose AVX512_4VNNIW and AVX512_4FMAPS features to kvm guest

On 28/10/2016 12:13, Luc, Piotr wrote: > On Fri, 2016-10-28 at 17:12 +0800, He Chen wrote: >> The spec can be found in Intel Software Developer Manual or in >> Instruction Set Extensions Programming Reference. >> >> Signed-off-by: Luwei Kang >> Signed-off-by: He Chen

Re: [RFC 1/2] mmc: sdhci: dt: Add device tree properties sdhci-caps and sdhci-caps-mask

On 25 October 2016 at 21:58, Zach Brown wrote: > On some systems the sdhci capabilty registers are incorrect for one > reason or another. > > The sdhci-caps-mask property specifies which bits in the registers > are incorrect and should be turned off before using sdhci-caps to

[PATCH v2] ASoC: hdmi-codec: Fix hdmi_of_xlate_dai_name when #sound-dai-cells = <0>

If a DAI specifies "#sound-dai-cells = <0>" in device-tree then hdmi_of_xlate_dai_name() will be called with zero args, which it isn't implemented to cope with. The resulting use of an uninitialised variable for the id will usually result in an error like: asoc-simple-card sound: parse error

[PATCH] pinctrl: max77620: add OF dependency

Drivers using pinconf_generic_params tables cannot be built with CONFIG_OF disabled: drivers/pinctrl/pinctrl-max77620.c:53:44: error: array type has incomplete element type ‘struct pinconf_generic_params’ drivers/pinctrl/pinctrl-max77620.c:55:3: error: field name not in record or union

[GIT PULL] objtool fix

Linus, Please pull the latest core-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-urgent-for-linus # HEAD: 56fb2d6eb63acd48b50437b415b6f7d2fcffe75d objtool: Fix rare switch jump table pattern detection One more objtool fixlet for GCC6

[PATCH 00/10] scripts/basic: Fine-tuning for seven function implementations

From: Markus Elfring Date: Fri, 28 Oct 2016 10:18:10 +0200 Some update suggestions were taken into account from static source code analysis. Markus Elfring (10): bin2c: Complete error handling in main() fixdep: Complete error handling in print_deps() fixdep:

[GIT PULL] timer fixes

Linus, Please pull the latest timers-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-for-linus # HEAD: 6bad6bccf2d717f652d37e63cf261eaa23466009 timers: Prevent base clock corruption when forwarding Fix four timer locking races:

Re: [RFC PATCH 0/3] sched: Introduce Window Assisted Load Tracking

On Fri, Oct 28, 2016 at 12:57:05AM -0700, Vikram Mulukutla wrote: > On 2016-10-28 00:49, Peter Zijlstra wrote: > >On Fri, Oct 28, 2016 at 12:10:39AM -0700, Vikram Mulukutla wrote: > >>This RFC patch has been tested on live X86 machines with the following > >>sanity > >>and benchmark results

Re: rowhammer protection [was Re: Getting interrupt every million cache misses]

On Fri 2016-10-28 09:07:01, Ingo Molnar wrote: > > * Pavel Machek wrote: > > > +static void rh_overflow(struct perf_event *event, struct perf_sample_data > > *data, struct pt_regs *regs) > > +{ > > + u64 *ts = this_cpu_ptr(_timestamp); /* this is NMI context */ > > + u64 now

Re: [PATCH] drm/rockchip: analogix_dp: add supports for regulators in edp IP

On 2016/10/23 3:18, Randy Li wrote: I found if eDP_AVDD_1V0 and eDP_AVDD_1V8 are not been power at RK3288, once trying to enable the pclk clock, the kernel would dead. This patch would try to enable them first. The eDP_AVDD_1V8 more likely to be applied to eDP phy, but I have no time to

Re: [PATCH v6 6/6] drm/fence: add out-fences support

Hi Gustavo, On Thu, Oct 27, 2016 at 05:37:11PM -0200, Gustavo Padovan wrote: From: Gustavo Padovan Support DRM out-fences by creating a sync_file with a fence for each CRTC that sets the OUT_FENCE_PTR property. We use the out_fence pointer received in the

Re: [PATCH] MAINTAINERS: add more people to the MTD maintainer team

Hi Brian, On Thu, 27 Oct 2016 13:57:32 -0700 Brian Norris wrote: > On Mon, Oct 24, 2016 at 02:35:26PM +0200, Boris Brezillon wrote: > > Brian has been maintaining the MTD subsystem alone for several years > > now, and maintaining such a subsystem can really be time

Re: Fwd: Fujitsu PrimePower 450 with SPARC64 V & Linux support

On 10/27/2016 08:50 PM, Allan Tsakuhhin wrote: > I am trying to build Linux system on Fujitsu PrimePower 450 running by > SPARC64 V CPUs. Does anyone have supportive materials (manuals, > overviews, specs) about Fujitsu PP450 and SPARC64 V CPUs. Every kind > of source material may be useful! > >

Re: [PATCH v2 0/3] usb: musb: da8xx: Fix few issues

On 10/27/2016 08:44 PM, David Lechner wrote: > On 10/27/2016 12:16 PM, David Lechner wrote: >> On 10/26/2016 05:58 AM, Alexandre Bailon wrote: >>> Currently, the USB OTG of the da8xx doesn't work. >>> This series intend to fix them. >>> >>> Change in v2: >>> * Fix the error path da8xx_musb_init()

Re: [PATCH] x86/cpuid: expose AVX512_4VNNIW and AVX512_4FMAPS features to kvm guest

On 28/10/2016 11:12, He Chen wrote: > The spec can be found in Intel Software Developer Manual or in > Instruction Set Extensions Programming Reference. > > Signed-off-by: Luwei Kang > Signed-off-by: He Chen > --- > arch/x86/kvm/cpuid.c | 7

Re: [PATCH] netfilter: ip_vs_sync: fix bogus maybe-uninitialized warning

On Mon, Oct 24, 2016 at 10:47:54PM +0300, Julian Anastasov wrote: > > Hello, > > On Mon, 24 Oct 2016, Arnd Bergmann wrote: > > > Building the ip_vs_sync code with CONFIG_OPTIMIZE_INLINING on x86 > > confuses the compiler to the point where it produces a rather > > dubious warning message:

Re: [PATCH] kvm/x86: Show WRMSR data is in hex

On 27/10/2016 20:14, Borislav Petkov wrote: > From: Borislav Petkov > > Add the "0x" prefix to the error messages format to make it unambiguous > about what kind of value we're talking about. > > Signed-off-by: Borislav Petkov > Cc: Paolo Bonzini

Re: [PATCH] x86/cpuid: expose AVX512_4VNNIW and AVX512_4FMAPS features to kvm guest

On 28/10/2016 11:46, He Chen wrote: > On Fri, Oct 28, 2016 at 11:31:05AM +0200, Paolo Bonzini wrote: >> >> >> On 28/10/2016 11:12, He Chen wrote: >>> The spec can be found in Intel Software Developer Manual or in >>> Instruction Set Extensions Programming Reference. >>> >>> Signed-off-by: Luwei

[GIT PULL] sound fixes for 4.9-rc3

Linus, please pull sound fixes for v4.9-rc3 from: git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git tags/sound-4.9-rc3 The topmost commit is bdc3478f90cd4d2928197f36629d5cf93b64dbe9 sound fixes for 4.9-rc3 Here

Re: [kernel-hardening] rowhammer protection [was Re: Getting interrupt every million cache misses]

Hi, I missed the original, so I've lost some context. Has this been tested on a system vulnerable to rowhammer, and if so, was it reliable in mitigating the issue? Which particular attack codebase was it tested against? On Thu, Oct 27, 2016 at 11:27:47PM +0200, Pavel Machek wrote: > ---

Re: [kernel-hardening] Re: rowhammer protection [was Re: Getting interrupt every million cache misses]

On Fri, Oct 28, 2016 at 11:35:47AM +0200, Ingo Molnar wrote: > > * Vegard Nossum wrote: > > > Would it make sense to sample the counter on context switch, do some > > accounting on a per-task cache miss counter, and slow down just the > > single task(s) with a too high

Re: [PATCH v7 0/4] da8xx USB PHY platform devices and clocks

On Thursday 27 October 2016 05:48 AM, David Lechner wrote: > This series depends on [v3] ARM: davinci: da8xx: Fix some redefined symbol > warnings being applied first. > > v7 changes: > * Dropped patches that have been accepted into linux-davinci

[PATCH 02/10] staging: iio: tsl2583: check for error code from i2c_smbus_read_byte()

taos_i2c_read() and taos_als_calibrate() does not check to see if the value returned by i2c_smbus_read_byte() was an error code. This patch adds the appropriate error handling. Signed-off-by: Brian Masney --- drivers/staging/iio/light/tsl2583.c | 22 +-

Re: [PATCH] ARM: DTS: da850: Add DMA to SPI0

On Wednesday 26 October 2016 05:02 AM, David Lechner wrote: > Add the bindings for DMA on SPI0 > > Signed-off-by: David Lechner Applied to v4.10/dt. small-case'd "DTS" in subject line while applying. Thanks, Sekhar

Re: [PATCH 2/2] serial: 8250_dw: Add support for IrDA SIR mode

Hi Andy, On Thu, Oct 27, 2016 at 07:56:10PM +0300, Andy Shevchenko wrote: > On Thu, 2016-10-27 at 17:38 +0100, Ed Blake wrote: > > Add a set_ldisc function to enable/disable IrDA SIR mode according to > > the new line discipline. > > Thanks for the patch. > > Consider that not all

[PATCH v3] staging: iio: cdc: ad7746: add additional config defines

Introduce defines for shifting and mask under the config register for better readability. Also, introduce helper variables for index calculation. Signed-off-by: Eva Rachel Retuya --- This patch might cause a conflict with this patch: staging: iio: cdc/ad7746: fix missing

[PATCH 01/10] scripts/basic/bin2c: Complete error handling in main()

From: Markus Elfring Date: Thu, 27 Oct 2016 16:15:04 +0200 Return values were not checked from five calls of the function "printf". This issue was detected also by using the Coccinelle software. * Add a bit of exception handling there. * Optimise this function

[PATCH 06/10] scripts/basic/fixdep: Complete error handling in do_config_file()

From: Markus Elfring Date: Thu, 27 Oct 2016 22:02:42 +0200 Return values were not checked from four calls of the function "close". This issue was detected also by using the Coccinelle software. Add a bit of exception handling there. Signed-off-by: Markus

[PATCH 05/10] scripts/basic/fixdep: Complete error handling in parse_dep_file()

From: Markus Elfring Date: Thu, 27 Oct 2016 19:43:43 +0200 Return values were not checked from five calls of the function "printf". This issue was detected also by using the Coccinelle software. * Add a bit of exception handling there. * Combine these calls

[GIT PULL] x86 fixes

Linus, Please pull the latest x86-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus # HEAD: 1c27f646b18fb56308dff82784ca61951bad0b48 x86/microcode/AMD: Fix more fallout from CONFIG_RANDOMIZE_MEMORY=y Misc fixes: three build

[PATCH] ARC: Enable PERF_EVENTS in nSIM driven platforms

Now when we have properly working performance counters in nSIM even with interrupt support (fix should be a part of upcoming nSIM engineering build 2016.12-005) we may enable perf support by default for all platforms that use nSIM for ARC cores simulation. Note all defconfigs were regenerated

[PATCH 10/10] scripts/basic/fixdep: Combine two fprintf() calls into one fputs() call in usage()

From: Markus Elfring Date: Fri, 28 Oct 2016 09:45:30 +0200 Some data were printed by two separate function calls. Print the same data by a single call of the function "fputs" instead. This issue was detected also by using the Coccinelle software. Signed-off-by:

[PATCH 2/4] drivers: base: cacheinfo: fix boot error message when acpi is enabled

ARM64 enables both CONFIG_OF and CONFIG_ACPI and the firmware can pass both ACPI tables and the device tree. Based on the kernel parameter, one of the two will be chosen. If acpi is enabled, then device tree is not unflattened. Currently ARM64 platforms report: " Failed to find cpu0

[PATCH 4/4] drivers: base: cacheinfo: support DT overrides for cache properties

Few architectures like x86, ia64 and s390 derive the cache topology and all the properties using a specific architected mechanism while some other architectures like powerpc all those information id derived from the device tree. On ARM, both the mechanism is used. While all the cache properties

[PATCH 1/4] drivers: base: cacheinfo: fix x86 with CONFIG_OF enabled

With CONFIG_OF enabled on x86, we get the following error on boot: " Failed to find cpu0 device node Unable to detect cache hierarchy from DT for CPU 0 " and the cacheinfo fails to get populated in the corresponding sysfs entries. This is because cache_setup_of_node looks for

Re: [PATCH v6 5/6] drm/fence: add fence timeline to drm_crtc

On Fri, Oct 28, 2016 at 09:42:12AM +0200, Daniel Vetter wrote: On Thu, Oct 27, 2016 at 05:37:10PM -0200, Gustavo Padovan wrote: From: Gustavo Padovan Create one timeline context for each CRTC to be able to handle out-fences and signal them. It adds a few

[PATCH] UBI: fastmap: Fix add_vol() return value test in ubi_attach_fastmap()

Commit e96a8a3bb671 ("UBI: Fastmap: Do not add vol if it already exists") introduced a bug by changing the possible error codes returned by add_vol(): - this functions no longer returns NULL in case of allocation failure but return ERR_PTR(-ENOMEM) - when a duplicate entry in the volume RB tree

Re: [PATCH] UBI: fastmap: Fix add_vol() return value test in ubi_attach_fastmap()

On 28.10.2016 11:12, Boris Brezillon wrote: > On Fri, 28 Oct 2016 11:08:44 +0200 > Boris Brezillon wrote: > >> Commit e96a8a3bb671 ("UBI: Fastmap: Do not add vol if it already >> exists") introduced a bug by changing the possible error codes returned >> by

[PATCH] x86/cpuid: expose AVX512_4VNNIW and AVX512_4FMAPS features to kvm guest

The spec can be found in Intel Software Developer Manual or in Instruction Set Extensions Programming Reference. Signed-off-by: Luwei Kang Signed-off-by: He Chen --- arch/x86/kvm/cpuid.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-)

Re: [PATCH] drm/rockchip: analogix_dp: add supports for regulators in edp IP

On 10/28/2016 05:11 PM, Shawn Lin wrote: On 2016/10/23 3:18, Randy Li wrote: I found if eDP_AVDD_1V0 and eDP_AVDD_1V8 are not been power at RK3288, once trying to enable the pclk clock, the kernel would dead. This patch would try to enable them first. The eDP_AVDD_1V8 more likely to be

Re: [PATCH v6 0/3] LSM: security module information improvements

On Thu, 27 Oct 2016, Casey Schaufler wrote: > The 3/3 patch is forward looking, I'll admit. Userspace > can start getting ready for the combined format in > advance of multiple major modules. When complete module > stacking patches are available I don't want to be addressing > "no userspace is

Re: [PATCH] arm64: mm: Fix memmap to be initialized for the entire section

On 27.10.16 17:01:36, Will Deacon wrote: > Hi Robert, > > On Mon, Oct 17, 2016 at 08:58:01PM +0200, Robert Richter wrote: > > Mark, Will, any opinion here? > > Having looking at this, I'm inclined to agree with you; pfn_valid() is > all about whether the underlying mem_map (struct page *) entry

Re: rowhammer protection [was Re: Getting interrupt every million cache misses]

* Vegard Nossum wrote: > Would it make sense to sample the counter on context switch, do some > accounting on a per-task cache miss counter, and slow down just the > single task(s) with a too high cache miss rate? That way there's no > global slowdown (which I assume

Re: [PATCH 1/5] KVM: x86: avoid atomic operations on APICv vmentry

On 27/10/2016 19:06, Radim Krčmář wrote: > 2016-10-27 19:51+0300, Michael S. Tsirkin: >> On Thu, Oct 27, 2016 at 06:44:00PM +0200, Radim Krčmář wrote: >>> 2016-10-27 00:42+0300, Michael S. Tsirkin: On Wed, Oct 26, 2016 at 09:53:45PM +0200, Radim Krčmář wrote: > 2016-10-14 20:21+0200,

[PATCH] net: phy: dp83848: add dp83822 PHY support

This PHY has a compatible register set with DP83848x so add support for it. Acked-by: Andrew F. Davis Signed-off-by: Roger Quadros --- drivers/net/phy/dp83848.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/net/phy/dp83848.c

Re: [PATCH v6] tty/serial: at91: fix hardware handshake on Atmel platforms

Le 27/10/2016 à 18:04, Richard Genoud a écrit : > After commit 1cf6e8fc8341 ("tty/serial: at91: fix RTS line management > when hardware handshake is enabled"), the hardware handshake wasn't > functional anymore on Atmel platforms (beside SAMA5D2). > > To understand why, one has to understand the

Re: rowhammer protection [was Re: Getting interrupt every million cache misses]

On 28 October 2016 at 11:35, Ingo Molnar wrote: > > * Vegard Nossum wrote: > >> Would it make sense to sample the counter on context switch, do some >> accounting on a per-task cache miss counter, and slow down just the >> single task(s) with a too high

Re: [PATCH v6 00/11] implement vcpu preempted check

On 28/10/2016 10:11, Pan Xinhui wrote: > change from v5: > spilt x86/kvm patch into guest/host part. > introduce kvm_write_guest_offset_cached. > fix some typos. > rebase patch onto 4.9.2 Acked-by: Paolo Bonzini Thanks, Paolo > change from v4: >

Re: [PATCH] x86/cpuid: expose AVX512_4VNNIW and AVX512_4FMAPS features to kvm guest

On Fri, Oct 28, 2016 at 11:54:13AM +0200, Paolo Bonzini wrote: > > > On 28/10/2016 11:46, He Chen wrote: > > On Fri, Oct 28, 2016 at 11:31:05AM +0200, Paolo Bonzini wrote: > >> > >> > >> On 28/10/2016 11:12, He Chen wrote: > >>> The spec can be found in Intel Software Developer Manual or in >

Re: [PATCH v5 2/5] driver core: Functional dependencies tracking support

On Thu, Oct 27, 2016 at 05:25:51PM +0200, Greg Kroah-Hartman wrote: > On Wed, Oct 26, 2016 at 01:19:02PM +0200, Lukas Wunner wrote: > > On Mon, Oct 10, 2016 at 02:51:04PM +0200, Rafael J. Wysocki wrote: > > > - Modify device_links_check_suppliers(), device_links_driver_bound(), > > >

[PATCH 04/10] staging: iio: tsl2583: remove redundant power_state sysfs attribute

IIO devices have a /sys/bus/iio/devices/iio:deviceX/power/ directory that allows viewing and controling various power parameters. The tsl2583 driver also has an additional custom sysfs attribute named power_state that is not needed. This patch removes the redundant power_state sysfs attribute.

[tip:perf/urgent] perf/powerpc: Don't call perf_event_disable() from atomic context

Commit-ID: 5aab90ce1ec449912a2ebc4d45e0c85dac29e9dd Gitweb: http://git.kernel.org/tip/5aab90ce1ec449912a2ebc4d45e0c85dac29e9dd Author: Jiri Olsa AuthorDate: Wed, 26 Oct 2016 11:48:24 +0200 Committer: Ingo Molnar CommitDate: Fri, 28 Oct 2016 11:06:25

[PATCH 3/3] ARM: dts: sun9i: cubieboard4: Enable AP6330 WiFi

The board has a Ampak AP6330 WiFi/BT/FM module. Inside it is a Broadcom BCM4330 WiFi/BT/FM combo IC. The WiFi portion is connected to mmc1, with the enabling pin connected to PL2. The AC100 RTC provides a low power clock signal. Signed-off-by: Chen-Yu Tsai ---

[PATCH 2/3] ARM: dts: sun9i: a80-optimus: Enable AP6330 WiFi

The board has a Ampak AP6330 WiFi/BT/FM module. Inside it is a Broadcom BCM4330 WiFi/BT/FM combo IC. The WiFi portion is connected to mmc1, with the enabling pin connected to PL2. The AC100 RTC provides a low power clock signal. Signed-off-by: Chen-Yu Tsai ---

[PATCH 0/3] ARM: dts: sun9i: Enable SDIO-based WiFi

Hi Maxime, Now that we have support for both PMICs, we can turn on the regulators needed for the onboard WiFi chips. This is a fairly simple series. The WiFi chips themselves are supported by the brcmfmac driver, but the user needs to get an nvram.txt file and put it in their firmware directory,

[PATCH 1/3] ARM: dts: sun9i: Add mmc1 pinmux setting

On the A80, mmc1 is available on pingroup G. Designs mostly use this to connect to an SDIO WiFi chip. Signed-off-by: Chen-Yu Tsai --- arch/arm/boot/dts/sun9i-a80.dtsi | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm/boot/dts/sun9i-a80.dtsi

Re: [PATCH 1/2] of, numa: Add function to disable of_node_to_nid().

On Tue, Oct 25, 2016 at 02:31:00PM -0700, David Daney wrote: > From: David Daney > > On arm64 NUMA kernels we can pass "numa=off" on the command line to > disable NUMA. A side effect of this is that kmalloc_node() calls to > non-zero nodes will crash the system with an

Re: [PATCH v2 3/3] reset: Add the TI SCI reset driver

On Fri, Oct 28, 2016 at 4:36 AM, Philipp Zabel wrote: > Hi Andrew, > > is there (going to be) as stable branch I can base these on, or should I > just wait until the prerequisite patches appear in arm-soc/for-next? > TISCI is still to be merged.

Re: [RFC v1 08/14] bus1: implement peer management context

On Fri, Oct 28, 2016 at 3:05 PM, Richard Weinberger wrote: > On Wed, Oct 26, 2016 at 9:18 PM, David Herrmann wrote: >> + /* initialize constant fields */ >> + peer->id = atomic64_inc_return(_ids); >> + peer->flags = 0; >> +

Re: [PATCH v2 1/2] backlight: pwm_bl: Move the checks for initial power state to a separate function

Hi Peter, Am Donnerstag, den 27.10.2016, 13:01 +0300 schrieb Peter Ujfalusi: > Move the checks to select the initial state for the backlight to a new > function and document the checks we are doing. > > At the same time correct the handling of the case when the GPIO is > initially configured as

Re: [Intel-gfx] [PATCH] scripts/checkpatch: Check for Reviewed-by under --strict

On Fri, 28 Oct 2016, Chris Wilson wrote: > Some subsystem polices have a strict requirement that every patch must > have at least one reviewer before being approved for upstream. Since > encouraging review is good policy (great review is even better policy!) > enforce

Re: [PATCH 0/5] drm/i915/skl: Backport watermark fixes for 4.8.y

On Wed, Oct 26, 2016 at 03:36:32PM -0400, Lyude wrote: > Now that these have finally made it into 4.9, it's time to finally backport > these fixes. Skylake has been a mess in multi-monitor setups for a while now > because up until recently we've been updating the watermarks on Skylake just > like

Re: [RFC v1 06/14] bus1: util - queue utility library

On Fri, Oct 28, 2016 at 3:33 PM, Peter Zijlstra wrote: > On Fri, Oct 28, 2016 at 01:33:25PM +0200, Tom Gundersen wrote: >> On Thu, Oct 27, 2016 at 6:43 PM, Peter Zijlstra wrote: >> > On Wed, Oct 26, 2016 at 09:18:02PM +0200, David Herrmann wrote: >> >

[PATCH v7 1/4] x86/msr: Add MSR(140H) and PHIR3MWAIT bit to msr-info.h

Intel Xeon Phi x200 (codenamed Knights Landing) has MSR MISC_FEATURE_ENABLES 0x140. Setting 2nd bit of this register makes MONITOR and MWAIT instructions do not cause invalid-opcode exception when called from ring different than 0. Hex Dec NameScope 140H 320

Re: [Intel-gfx] [PATCH] scripts/checkpatch: Check for Reviewed-by under --strict

On Fri, Oct 28, 2016 at 04:33:10PM +0300, Jani Nikula wrote: > On Fri, 28 Oct 2016, Chris Wilson wrote: > > Some subsystem polices have a strict requirement that every patch must > > have at least one reviewer before being approved for upstream. Since > > encouraging

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.9 has two fixes in it: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.9 My patch fixes the btrfs list_head abuse that we tracked down during Dave Jones' memory corruption investigation. With both Jens and my patches in place, I'm no

Re: [RFC v1 08/14] bus1: implement peer management context

On Fri, Oct 28, 2016 at 2:06 PM, Richard Weinberger wrote: > David, Tom, > > On Wed, Oct 26, 2016 at 9:18 PM, David Herrmann wrote: >> +struct bus1_peer *bus1_peer_new(void) >> +{ >> + static atomic64_t peer_ids = ATOMIC64_INIT(0); >> +

Re: [RFC v1 08/14] bus1: implement peer management context

On 28.10.2016 15:18, Tom Gundersen wrote: > On Fri, Oct 28, 2016 at 2:06 PM, Richard Weinberger > wrote: >> David, Tom, >> >> On Wed, Oct 26, 2016 at 9:18 PM, David Herrmann >> wrote: >>> +struct bus1_peer *bus1_peer_new(void) >>> +{ >>> +

Re: common android definition bug in 3.18 kernel

On 28-Oct 09:27, Peter Zijlstra wrote: > On Fri, Oct 28, 2016 at 11:00:21AM +0530, Rajesh P8 wrote: > > Hi all, > >   I am currently working on porting eas features using 3.18 common > > android kernel. In file  kernel/sched/fair.c there is no definition > > for the function

Re: [PATCH 08/15] perf tools: Introduce timestamp_in_usec()

Em Fri, Oct 28, 2016 at 10:53:38AM -0200, Arnaldo Carvalho de Melo escreveu: > Em Thu, Oct 27, 2016 at 04:14:55PM -0700, Joonwoo Park escreveu: > > > > > > On 10/27/2016 01:40 PM, Arnaldo Carvalho de Melo wrote: > > > From: Namhyung Kim > > > > > > Joonwoo reported that

Re: [RFC v1 06/14] bus1: util - queue utility library

On Fri, Oct 28, 2016 at 01:33:25PM +0200, Tom Gundersen wrote: > On Thu, Oct 27, 2016 at 6:43 PM, Peter Zijlstra wrote: > > On Wed, Oct 26, 2016 at 09:18:02PM +0200, David Herrmann wrote: > > > >> A bus1 message queue is a FIFO, i.e., messages are linearly ordered by > >>

Re: [PATCH 1/3] ARM: dts: exynos: Document eMMC/SD/SDIO devices in Exynos5250 Snow board

On Thu, Oct 27, 2016 at 02:11:41PM -0300, Javier Martinez Canillas wrote: > There's a cognitive load to figure out which mmc device node corresponds > to the eMMC flash, uSD card and WiFI SDIO module on the Snow boards. > > So it's better to have comments in the DTS to make this more clear. > >

Re: [PATCH 1/3] ARM: dts: exynos: Document eMMC/SD/SDIO devices in Exynos5250 Snow board

Hello Krzysztof, On 10/28/2016 10:34 AM, Krzysztof Kozlowski wrote: > On Thu, Oct 27, 2016 at 02:11:41PM -0300, Javier Martinez Canillas wrote: >> There's a cognitive load to figure out which mmc device node corresponds >> to the eMMC flash, uSD card and WiFI SDIO module on the Snow boards. >> >>

Re: Implement complete_all() with swait

On Fri, 28 Oct 2016 09:17:04 +0200 Daniel Wagner wrote: > > So I went through the list of users and tried to identify which of them > is going to make troubles. I found 4 users which are using > complete_all() while IRQs are disabled. The rest looks like it just > would work

Re: [RFC v1 00/14] Bus1 Kernel Message Bus

On Fri, Oct 28, 2016 at 3:11 PM, Richard Weinberger wrote: > On Wed, Oct 26, 2016 at 9:17 PM, David Herrmann wrote: >> Hi >> >> This proposal introduces bus1.ko, a kernel messaging bus. This is not a >> request >> for inclusion, yet. It is

[PATCH v7 3/4] x86/cpufeature: Add PHIR3MWAIT to CPU features

Add Intel Xeon Phi x200 (KnightsLanding) cpu feature - ring 3 monitor/mwait Signed-off-by: Grzegorz Andrejczuk --- arch/x86/include/asm/cpufeatures.h | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/x86/include/asm/cpufeatures.h

[PATCH v7 4/4] x86: Add enabling of the R3MWAIT during boot

If processor is Intel Xeon Phi x200 we enable user-level mwait feature. Enabling this feature suppresses invalid-opcode error, when MONITOR/MWAIT is called from ring 3. Signed-off-by: Grzegorz Andrejczuk --- Documentation/kernel-parameters.txt | 5 +

[PATCH v7 2/4] x86: Use HWCAP2 to expose Xeon Phi ring 3 MWAIT

Add HWCAP2 for x86 and reserve its 1st bit to expose Xeon Phi ring 3 monitor/mwait to userspace apps. Signed-off-by: Grzegorz Andrejczuk --- arch/x86/include/asm/elf.h | 9 + arch/x86/include/uapi/asm/hwcap2.h | 7 +++

[PATCH v7 0/4] Enabling Ring 3 MONITOR/MWAIT feature for Knights Landing

These patches enable Intel Xeon Phi x200 feature to use MONITOR/MWAIT instruction in ring 3 (userspace) Patches set MSR 0x140 for all logical CPUs. Then expose it as CPU feature and introduces elf HWCAP capability for x86. Reference:

Re: [PATCH v2 02/16] scsi: don't use fc_bsg_job::request and fc_bsg_job::reply directly

On 10/28/2016 01:31 PM, Hannes Reinecke wrote: On 10/28/2016 11:53 AM, Steffen Maier wrote: On 10/13/2016 06:24 PM, Johannes Thumshirn wrote: On Thu, Oct 13, 2016 at 05:15:25PM +0200, Steffen Maier wrote: I'm puzzled. $ git bisect start fc_bsg master

Re: [PATCH 00/14] introduce the BFQ-v0 I/O scheduler as an extra scheduler

On 10/27/2016 04:27 PM, Linus Walleij wrote: On Thu, Oct 27, 2016 at 11:08 PM, Jens Axboe wrote: blk-mq has evolved to support a variety of devices, there's nothing special about mmc that can't work well within that framework. There is. Read mmc_queue_thread() in

Re: [PATCH 1/2] ARM: dts: exynos: Use macro for PWM signal polarity in Exynos4 boards

On Thu, Oct 27, 2016 at 02:47:17PM -0300, Javier Martinez Canillas wrote: > Using the PWM_POLARITY_INVERTED macro instead of the hardcoded number > 0 makes the DTS easier to read. Eeee PWM_POLARITY_INVERTED = 1 << 0 = 1. And you are replacing 0 with 1. Hm? This is not described at all in

Re: [PATCH 1/2] ARM: dts: exynos: Use macro for PWM signal polarity in Exynos4 boards

Hello Krzysztof, On 10/28/2016 10:41 AM, Krzysztof Kozlowski wrote: > On Thu, Oct 27, 2016 at 02:47:17PM -0300, Javier Martinez Canillas wrote: >> Using the PWM_POLARITY_INVERTED macro instead of the hardcoded number >> 0 makes the DTS easier to read. > > > Eeee PWM_POLARITY_INVERTED = 1 <<

Re: [RFC v1 08/14] bus1: implement peer management context

On 28.10.2016 15:23, Tom Gundersen wrote: > On Fri, Oct 28, 2016 at 3:05 PM, Richard Weinberger > wrote: >> On Wed, Oct 26, 2016 at 9:18 PM, David Herrmann >> wrote: >>> + /* initialize constant fields */ >>> + peer->id =

Re: [RFC v1 06/14] bus1: util - queue utility library

On Fri, Oct 28, 2016 at 03:47:58PM +0200, Tom Gundersen wrote: > On Fri, Oct 28, 2016 at 3:33 PM, Peter Zijlstra wrote: > > On Fri, Oct 28, 2016 at 01:33:25PM +0200, Tom Gundersen wrote: > > And this, precisely, is what generates all the complexity found in this > > patch.

[PATCH v12 RESEND 4/4] Documentation: tee subsystem and op-tee driver

Signed-off-by: Jens Wiklander --- Documentation/00-INDEX | 2 + Documentation/tee.txt | 118 + MAINTAINERS| 1 + 3 files changed, 121 insertions(+) create mode 100644 Documentation/tee.txt diff --git

[PATCH v12 RESEND 0/4] generic TEE subsystem

Hi, This patch set introduces a generic TEE subsystem. The TEE subsystem will contain drivers for various TEE implementations. A TEE (Trusted Execution Environment) is a trusted OS running in some secure environment, for example, TrustZone on ARM CPUs, or a separate secure co-processor etc.

[PATCH v12 RESEND 1/4] dt/bindings: add bindings for optee

Introduces linaro prefix and adds bindings for ARM TrustZone based OP-TEE implementation. Acked-by: Rob Herring Signed-off-by: Jens Wiklander --- .../bindings/arm/firmware/linaro,optee-tz.txt | 31 ++

[PATCH v12 RESEND 2/4] tee: generic TEE subsystem

Initial patch for generic TEE subsystem. This subsystem provides: * Registration/un-registration of TEE drivers. * Shared memory between normal world and secure world. * Ioctl interface for interaction with user space. * Sysfs implementation_id of TEE driver A TEE (Trusted Execution Environment)

Re: [PATCH v3 1/3] powerpc/reloc32: fix corrupted modversion CRCs

On 27/10/16 17:27, Ard Biesheuvel wrote: Commit 0e0ed6406e61 ("powerpc/modules: Module CRC relocation fix causes perf issues") fixed an issue with relocatable PIE kernels in a way that essentially reintroduced the issue again for 32-bit builds. Since the chosen approach does is not applicable

<    1   2   3   4   5   6   7   8   9   10   >