Add syscon-reboot-mode driver DT node for rk3368 platform
Tested-by: Caesar Wang
Signed-off-by: Andy Yan
---
Changes in v5: None
Changes in v4: None
Changes in v3:
- descirbe all reboot mode as properity instead of subnode
Changes in v2:
-
ARC Timers have historically been probed directly.
As precursor to start probing Timers thru DT introduce these bindings
Note that to keep series bisectable, these bindings are not yet used in
code.
Cc: Daniel Lezcano
Cc: Rob Herring
Cc:
From: Alexey Brodkin
UARTs usually have fixed clock so we're switching to use of
constant values instead of something derived from core clock
frequency.
Among other things this will allow us to get rid of
arc_{get|set}_core_freq() and switch to generic clock
framework
- timer frequency is derived from DT (no longer rely on top level
DT "clock-frequency" probed early and exported by asm/clk.h)
- TIMER0_IRQ need not be exported across arch code, confided to intc as
it is property of same
Cc: Noam Camus
Cc: Daniel Lezcano
From: Noam Camus
ARC Timers so far have been handled as "legacy" w/o explicit description
in DT. This poses challenge for newer platforms wanting to use them.
This series will eventually help move timers over to DT.
This patch does a small change of using a CPU notifier to set
From: Alexey Brodkin
There are no more users of this - so RIP!
Signed-off-by: Alexey Brodkin
[vgupta: update changelog]
Signed-off-by: Vineet Gupta
Signed-off-by: Vineet Gupta
---
This allows us to introduce timers in DT in next commit
Cc: Daniel Lezcano
Cc: Rob Herring
Cc: devicet...@vger.kernel.org
Signed-off-by: Vineet Gupta
---
arch/arc/boot/dts/axc001.dtsi | 6 ++
When control reaches to Linux UFS driver during UFS boot mode, UFS host
controller interrupt status/enable registers may have left over
settings.
In order to avoid any spurious interrupts due to these left overs,
it's important to clear these interrupt status/enable registers before
enabling UFS
Sometimes due to hw issues it takes some time to the
host controller register to update. In order to verify the register
has updated, a polling is done until its value is set.
In addition the functions ufshcd_hba_stop() and
ufshcd_wait_for_register() was updated with an additional input
Some vendor's UFS device sends back to back NACs for the DL data frames
causing the host controller to raise the DFES error status. Sometimes
such UFS devices send back to back NAC without waiting for new
retransmitted DL frame from the host and in such cases it might be
possible the Host UniPro
This adds the binding documentation for the MediaTek Ethernet
controller.
Signed-off-by: John Crispin
Acked-by: Rob Herring
Cc: devicet...@vger.kernel.org
---
.../devicetree/bindings/net/mediatek-net.txt | 77
1 file changed, 77
This series adds support for the Mediatek ethernet core found on current ARM
based SoCs. The driver works on MT2701 and MT7623 SoCs
Instead of trying to upstream everything at once I decided to concentrate on
the important parts required to make current generation silicon work. The V3
series only
Copy a few structs and commands from the EC firmware headers so we can
communicate with the EC regarding PD functionality.
Signed-off-by: Tomeu Vizoso
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
include/linux/mfd/cros_ec_commands.h | 324
在 2016年03月03日 16:03, Elaine Zhang 写道:
According to a description from TRM, add all the power domains
Signed-off-by: Elaine Zhang
---
include/dt-bindings/power/rk3399-power.h | 53
1 file changed, 53 insertions(+)
create mode
On 02/26/2016 10:27 PM, Sören Brinkmann wrote:
> On Fri, 2016-02-26 at 15:03:19 +0200, Grygorii Strashko wrote:
>> On 02/05/2016 01:39 AM, Sören Brinkmann wrote:
>>> On Thu, 2016-02-04 at 15:14:47 -0800, Moritz Fischer wrote:
Hi Soeren,
On Thu, Feb 4, 2016 at 2:41 PM, Sören
Some of platforms like Nvidia's Tegra210 Jetson-TX1 platform has
multiple PMW based regulators. Add support to have multiple instances
of the driver by not changing any global data of pwm regulator and
if required, making instance specific copy and then making changes.
Signed-off-by: Laxman
bvec has provided one iterator already, so not necessary
to invent a new wheel for this job.
Signed-off-by: Ming Lei
---
lib/iov_iter.c | 31 +++
1 file changed, 11 insertions(+), 20 deletions(-)
diff --git a/lib/iov_iter.c b/lib/iov_iter.c
The firmware table is currently parsed by the virtual timer code in
order to retrieve the virtual timer interrupt. However, this is already
done by the arch timer driver.
To avoid code duplication, use the newly function arch_timer_get_kvm_info()
which return all the information required by the
So that we can use bvec iterator to implement iterate_bvec(): lib/iov_iter.c.
Signed-off-by: Ming Lei
---
include/linux/blk_types.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/blk_types.h b/include/linux/blk_types.h
index
bvec_iter_advance() only writes to the parameter of 'iter',
so address of 'bvec' can be marked as const safely.
Without the change, we can trigger compiling warning in the
following patch for implementing iterate_bvec(): lib/iov_iter.c
with bvec iterator.
Signed-off-by: Ming Lei
David Miller wrote:
> >> I know you put a lot of time and effort into this, but I want to strongly
> >> recommend against a garbage collected hash table for anything whatsoever.
> >>
> >> Especially if the given objects are in some way created/destroyed/etc. by
> >>
Intel's new PKU extension introduces a bit of the page fault error code
that must be dynamically computed after the PTE lookup (unlike I/D, U/S
and W/R). To ease this, these two patches make permission_fault return
the page fault error code.
Right now it only adds the P bit to the input
Yes, all of these are needed. :) This is admittedly a bit odd, but
kvm-unit-tests access.flat tests this if you run it with "-cpu host"
and of course ept=0.
KVM handles supervisor writes of a pte.u=0/pte.w=0/CR0.WP=0 page by
setting U=0 and W=1 in the shadow PTE. This will cause a user write
to
On Mon, Mar 07, 2016 at 04:02:25PM -0800, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.5 release.
> There are 74 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.
It is now equal to use_eager_fpu(), which simply tests a cpufeature bit.
Signed-off-by: Paolo Bonzini
---
arch/x86/include/asm/kvm_host.h | 1 -
arch/x86/kvm/cpuid.c| 3 +--
arch/x86/kvm/x86.c | 2 +-
3 files changed, 2 insertions(+), 4 deletions(-)
For the next patch, we will want to filter PFERR_FETCH_MASK away early,
and not pass it to permission_fault if neither NX nor SMEP are enabled.
Prepare for the change.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/mmu.c | 2 +-
arch/x86/kvm/paging_tmpl.h | 26
add device tree bindings document for reboot-mode driver
Signed-off-by: Andy Yan
---
Changes in v5:
- delete a unnecessary blank line in syscon-reboot-mode.txt
- rename macro BOOT_LOADER to BOOT_BL_DOWNLOAD, which gives a more clear mean
Changes in v4:
- remove
This driver parse the reboot commands like "reboot loader"
and "reboot recovery" to get a boot mode described in the
device tree , then call the write interfae to store the boot
mode in some place like special register or sram , which can
be read by the bootloader after system reboot, then the
A race condition exists between request requeueing and scsi layer
error handling:
When UFS driver queuecommand returns a busy status for a request,
it will be requeued and its tag will be freed and set to -1.
At the same time it is possible that the request will timeout and
scsi layer will start
On Wed, Feb 24, 2016 at 05:12:55PM -0500, Tejun Heo wrote:
> perf_event is a utility controller whose primary role is identifying
> cgroup membership to filter perf events; however, because it also
> tracks some per-css state, it can't be replaced by pure cgroup
> membership test. Mark the
Am 08.03.2016 um 10:41 schrieb Julien Chauveau:
> Le 8 mars 2016 à 09:54, Geert Uytterhoeven a écrit :
>> On Mon, Mar 7, 2016 at 7:24 PM, Andreas Färber wrote:
>>> Drop #address-cells and #size-cells, which are not required by the
>>> gpio-keys binding
* Andy Lutomirski wrote:
> > > ENTRY(entry_INT80_32)
> >
> > entry_INT80_32() is only used on pure 32-bit kernels, 64-bit kernels use
> > entry_INT80_compat(). So the above text should not talk about 64-bit
> > programs, as
> > they can never trigger this specific entry
On Tue, Mar 08, 2016 at 09:18:33AM +, Chrzaniuk, Hubert wrote:
> Yes, that’s right:
> 1. d0cdf9003140 is the patch I am referring to
> 2. EDAC for KNL platform on 4.5 will not cause any problems but will not be
> functional for DIMMs (only for MCDRAM)
Ok, thanks for confirming.
> Thanks,
Commit-ID: 1b2dbbf41a0f4cf7a5662bccb9a18128d16e5ffb
Gitweb: http://git.kernel.org/tip/1b2dbbf41a0f4cf7a5662bccb9a18128d16e5ffb
Author: Namhyung Kim
AuthorDate: Mon, 7 Mar 2016 16:44:46 -0300
Committer: Ingo Molnar
CommitDate: Tue, 8 Mar 2016
Commit-ID: 58ecd33be90647724a78ce5e0b42f5bc482771fd
Gitweb: http://git.kernel.org/tip/58ecd33be90647724a78ce5e0b42f5bc482771fd
Author: Namhyung Kim
AuthorDate: Mon, 7 Mar 2016 16:44:51 -0300
Committer: Ingo Molnar
CommitDate: Tue, 8 Mar 2016
* Josh Poimboeuf wrote:
> This is v19 of the compile-time stack metadata validation patch set.
>
> It's based on tip:core/objtool.
So I've upgraded my main build box to Fedora 23, to:
gcc version 5.3.1 20151207 (Red Hat 5.3.1-2) (GCC)
GNU assembler version 2.25
Commit-ID: a61a22f6845f9e86e0ca60d1d256a35ca12312ef
Gitweb: http://git.kernel.org/tip/a61a22f6845f9e86e0ca60d1d256a35ca12312ef
Author: Namhyung Kim
AuthorDate: Mon, 7 Mar 2016 16:44:50 -0300
Committer: Ingo Molnar
CommitDate: Tue, 8 Mar 2016
Hi,
Krzysztof Opasiak writes:
> [ text/plain ]
>
>
> On 03/08/2016 08:43 AM, Felipe Balbi wrote:
> (...)
>
> This is necessary because this driver is actually wrong in which is
> asking for the host to power itself. This is not specified on USB-MIDI
>
This function returns the code for the host event that triggered the
interrupt that is being currently handled.
Is to be used by observers of the event_notifier in the EC device.
Signed-off-by: Tomeu Vizoso
---
Changes in v4: None
Changes in v3: None
Changes in v2:
So that callers of cros_ec_cmd_xfer don't have to repeat boilerplate
code when checking for errors from the EC side.
Signed-off-by: Tomeu Vizoso
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/platform/chrome/cros_ec_proto.c | 14
* H. Peter Anvin wrote:
> On March 7, 2016 12:22:28 AM PST, Ingo Molnar wrote:
> >
> >* Andy Lutomirski wrote:
> >
> >> Ingo suggested that the comments should explain when the various
> >> entries are used. This adds these explanations and
Commit-ID: 2dbbe9f26c082be5aa0e8ba5480e7bac43b2c4f0
Gitweb: http://git.kernel.org/tip/2dbbe9f26c082be5aa0e8ba5480e7bac43b2c4f0
Author: Namhyung Kim
AuthorDate: Mon, 7 Mar 2016 16:44:48 -0300
Committer: Ingo Molnar
CommitDate: Tue, 8 Mar 2016
From: Sameer Nanda
This driver exposes the charger functionality in the PD EC to userspace.
Signed-off-by: Tomeu Vizoso
Cc: Sameer Nanda
Cc: Benson Leung
Cc: Shawn Nematbakhsh
---
Commit-ID: f58c95e344c26223c6503e6ecb0c1e11806d91e0
Gitweb: http://git.kernel.org/tip/f58c95e344c26223c6503e6ecb0c1e11806d91e0
Author: Namhyung Kim
AuthorDate: Mon, 7 Mar 2016 16:44:49 -0300
Committer: Ingo Molnar
CommitDate: Tue, 8 Mar 2016
Currently PWM regulator support the multiple voltage by
two different mechanism: Voltage table based and continuous
steps which divides duty cycle into 100 parts.
There is a use cases where entire voltage ranges from minimum
to maximum is divided into n equal steps and just providing the
steps
With following equation for calculating
voltage_to_duty_cycle_percentage
100 - (((req_uV * 100) - (min_uV * 100)) / diff);
we get 0% for max_uV and 100% for min_uV.
Correcting this to
((req_uV * 100) - (min_uV * 100)) / diff;
to get proper duty cycle.
Signed-off-by: Laxman
This series fix the equation for calculating the ducty cycle for PWM,
add supports for multiple instances, prints the error numbers if it fails,
and add Linear Equal Step mode for voltage setting.
For the context: NVIDIA's Tegra210 platform Jetson-TX1 uses the two
Open Voltage Regulators (OVR
Add support for Linear Equal Step mode in pwm regulators on which
specified regulator's minimum and maximum voltages are divided into
specified equal steps. The number of steps must divided the range of
minimum to maximum as well as PWM periods in equal parts.
Add DT property to specify number
* Alexandre Belloni | 2016-03-05 12:35:53 [+0100]:
>Hi Sebastian,
Hi Alexandre,
>The series landed in arm-soc and is making its way to v4.6. I guess you
>can pull the original pull request. It is based on v4.5-rc1 but should
>apply cleanly on v4.4:
I sucked this in. It seems to work. What
Prints the error number along with error message when any
error occurs. This helps on getting the reason of failure
quickly from log without any code instrument.
Signed-off-by: Laxman Dewangan
Cc: Lee Jones
---
drivers/regulator/pwm-regulator.c | 12
On Fri, Mar 04, 2016 at 08:22:22PM +0100, Torsten Duwe wrote:
> On Fri, Mar 04, 2016 at 07:16:57PM +0100, Torsten Duwe wrote:
> > On Fri, Mar 04, 2016 at 02:01:37PM +0100, Petr Mladek wrote:
> > >
> > > Do I understand it correctly that we could not patch functions that
> > > pass arguments on
The sunxi NAND controller is able to pipeline ECC operations only when
operated in DMA mode, which improves a lot NAND throughput while keeping
CPU usage low.
Signed-off-by: Boris Brezillon
---
drivers/mtd/nand/sunxi_nand.c | 301
On (Fri) 04 Mar 2016 [15:02:47], Jitendra Kolhe wrote:
> > >
> > > * Liang Li (liang.z...@intel.com) wrote:
> > > > The current QEMU live migration implementation mark the all the
> > > > guest's RAM pages as dirtied in the ram bulk stage, all these pages
> > > > will be processed and that takes
Some NAND controller drivers are making use of DMA to transfer data from
the controller to the buffer passed by the MTD user.
Provide a generic mtd_map/unmap_buf() implementation to avoid open coded
(and sometime erroneous) implementations.
Signed-off-by: Boris Brezillon
On 03/08/2016 11:10 AM, Michal Hocko wrote:
> On Tue 08-03-16 10:52:15, Vlastimil Babka wrote:
>> On 03/08/2016 10:46 AM, Michal Hocko wrote:
> [...]
> @@ -3294,6 +3289,18 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned
> int order,
>did_some_progress >
Document dmas and dma-names properties.
Signed-off-by: Boris Brezillon
---
Documentation/devicetree/bindings/mtd/sunxi-nand.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/mtd/sunxi-nand.txt
On (Thu) 03 Mar 2016 [18:44:24], Liang Li wrote:
> The current QEMU live migration implementation mark the all the
> guest's RAM pages as dirtied in the ram bulk stage, all these pages
> will be processed and that takes quit a lot of CPU cycles.
>
> From guest's point of view, it doesn't care
Hello,
This patch series aims at adding support for DMA assisted operations to
the sunxi_nand driver.
The first 3 patches are just reworks in the existing driver preparing
things for DMA ->read/write_page() operations. Those ones are mainly
re-arranging existing functions, and moving some code
In order to support DMA operations in a clean way we need to extract some
of the logic coded in sunxi_nfc_hw_ecc_read/write_page() into their own
function.
Signed-off-by: Boris Brezillon
---
drivers/mtd/nand/sunxi_nand.c | 163
Fill up the recently introduced gic_kvm_info with the virtual GIC
information.
Signed-off-by: Julien Grall
Cc: Thomas Gleixner
Cc: Jason Cooper
Cc: Marc Zyngier
---
Changes in v3:
- Add ACPI
For now, there is only one member. More member will be added later.
Signed-off-by: Julien Grall
---
Cc: Thomas Gleixner
Cc: Jason Cooper
Cc: Marc Zyngier
Changes in v2:
- Patch added
---
Even though all the variables aren't marked with __initdata, they are
only used during initialization. So the structure is marked with
__initdata.
Signed-off-by: Julien Grall
---
Cc: Thomas Gleixner
Cc: Jason Cooper
Cc: Marc
On Tue, Mar 08, 2016 at 09:51:05AM +0100, Christian Borntraeger wrote:
> On 03/08/2016 01:41 AM, Kees Cook wrote:
>
> >> --- a/arch/s390/kernel/vmlinux.lds.S
> >> +++ b/arch/s390/kernel/vmlinux.lds.S
> >> @@ -52,6 +52,12 @@ SECTIONS
> >>
> >> RW_DATA_SECTION(0x100, PAGE_SIZE, THREAD_SIZE)
Hello, Hannes,
Re-sending
thanks,
Yaniv
>> On 03/03/2016 05:10 PM, yga...@codeaurora.org wrote:
On 03/01/2016 09:25 PM, yga...@codeaurora.org wrote:
>> On 02/28/2016 09:32 PM, Yaniv Gardi wrote:
>>> A race condition exists between request requeueing and scsi layer
>>> error
Hello, Hannes,
Re-sending
thanks,
Yaniv
>> On 03/03/2016 05:10 PM, yga...@codeaurora.org wrote:
On 03/01/2016 09:25 PM, yga...@codeaurora.org wrote:
>> On 02/28/2016 09:32 PM, Yaniv Gardi wrote:
>>> A race condition exists between request requeueing and scsi layer
>>> error
Use queue_delayed_work only when debounce time is
required to read gpio state properly, read the gpio
state and set the extcon cable state in IRQ handler
context if gpio settling time is not needed.
Signed-off-by: Venkat Reddy Talla
---
drivers/extcon/extcon-gpio.c | 6
Intel's new PKU extension introduces a bit of the page fault error code
that must be dynamically computed after the PTE lookup (unlike I/D, U/S
and W/R). To ease this, these two patches make permission_fault return
the page fault error code.
Right now it only adds the P bit to the input
Hi Stephen,
[CC''ing linux-security-module]
On Tue, 2016-03-08 at 16:22 +0700, Stephen Boyd wrote:
> Some systems are memory constrained but they need to load very
> large firmwares. The firmware subsystem allows drivers to request
> this firmware be loaded from the filesystem, but this requires
This should be an IS_ERR() check. mount_pseudo() returns error pointers
and this function should return the error pointer to its caller as well.
Fixes: 3684aa7099e0 ('block-dev: enable writeback cgroup support')
Signed-off-by: Dan Carpenter
diff --git a/fs/block_dev.c
We accidentally return success instead of a negative error code.
Signed-off-by: Dan Carpenter
diff --git a/drivers/net/wireless/marvell/libertas/main.c
b/drivers/net/wireless/marvell/libertas/main.c
index b35b8bc..8541cbe 100644
---
On Monday, March 07, 2016 07:50:57 PM Len Brown wrote:
> > But with Broadwell-EP processor (E5-2687W v4) the CPU will not enter turbo
> > modes if this value is not set to performance
>
> BDX-EP supports HWP.
> Are these failing machines running in HWP mode?
>
> (On BDX-EP, and only on BDX-EP,
On Tue, Mar 08, 2016 at 11:37:16AM +0100, Ingo Molnar wrote:
>
> * Josh Poimboeuf wrote:
>
> > This is v19 of the compile-time stack metadata validation patch set.
> >
> > It's based on tip:core/objtool.
>
> So I've upgraded my main build box to Fedora 23, to:
>
> gcc
This change adds printouts of testbus and debug registers.
Reviewed-by: Gilad Broner
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/ufs-qcom.c | 77 +
drivers/scsi/ufs/ufs-qcom.h | 9 ++
2 files
From: Alexey Brodkin
For AXS103, certain bitfile configurations may not work with stock
"clock-frequency" specified in DT. Instead of duplicating the DT files, we
fixup the DT in-place.
This used to be done differently - as in top level "clock-frequency" was
read very
Some UFS devices (and may be host) have issues if LCC is
enabled. So we are setting PA_Local_TX_LCC_Enable to 0
before link startup which will make sure that both host
and device TX LCC are disabled once link startup is
completed.
Reviewed-by: Gilad Broner
Signed-off-by:
Query commands have 100ms timeout and it may timeout if they are
issued in parallel to ongoing read/write SCSI commands, this change
adds the retry (max: 10) in case command timeouts.
Reviewed-by: Hannes Reinecke
Signed-off-by: Subhash Jadavani
We are seeing that some devices are raising the urgent bkops exception
events even when BKOPS status doesn't indicate performace impacted or
critical. Handle these device by determining their urgent bkops status
at runtime.
Reviewed-by: Hannes Reinecke
Signed-off-by: Subhash
We put the UFS device in sleep state & UFS link in hibern8 state during
runtime suspaned. After this we put all the UFS rails in low power
modes immediately but it seems some devices may still draw more than
sleep current from UFS rails (especially from VCCQ rail) atleast for
500us.
To avoid this
This change enables the device ref clock before changing to HS mode
and disables it if entered to PWM mode.
Reviewed-by: Gilad Broner
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/ufs-qcom.c | 12
drivers/scsi/ufs/ufshcd.h | 9
Hello Tejun,
On (03/07/16 10:49), Tejun Heo wrote:
> On Tue, Mar 08, 2016 at 12:10:47AM +0900, Sergey Senozhatsky wrote:
> > A new version. Switched to [printk] kthread.
>
> There are some benefits to using a percpu workqueue with CPU_INTENSIVE
> set or an unbound workqueue. It'd need
On 2016/3/8 15:48, Joonsoo Kim wrote:
> On Mon, Mar 07, 2016 at 01:59:12PM +0100, Vlastimil Babka wrote:
>> On 03/07/2016 05:34 AM, Joonsoo Kim wrote:
>>> On Fri, Mar 04, 2016 at 03:35:26PM +0800, Hanjun Guo wrote:
> Sad to hear that.
>
> Could you tell me your system's MAX_ORDER and
On Tue, Mar 08, 2016 at 06:33:57PM +1100, Balbir Singh wrote:
> Changelog v5:
> 1. Removed the mini-stack frame created for klp_return_helper.
> As a result of the mini-stack frame, function with > 8
> arguments could not be patched
Did you get my previous mails? Those
On Mon, Mar 7, 2016 at 10:07 PM, Kees Cook wrote:
> On Sun, Mar 6, 2016 at 3:07 PM, Emese Revfy wrote:
>> The sancov gcc plugin inserts a __sanitizer_cov_trace_pc() call
>> at the start of basic blocks.
>>
>> This plugin is a helper plugin for the kcov
On Mon, Mar 07, 2016 at 10:26:42AM +0800, Huang Rui wrote:
> Introduce an AMD accumlated power reporting mechanism for the Family
> 15h, Model 60h processor that can be used to calculate the average
> power consumed by a processor during a measurement interval. The
> feature support is indicated
Em Tue, 08 Mar 2016 11:49:35 +0200
Jani Nikula escreveu:
> On Tue, 08 Mar 2016, Dan Allen wrote:
> > One of the key goals of the Asciidoctor project is to be able to directly
> > produce a wide variety of outputs from the same source (without DocBook).
KVM handles supervisor writes of a pte.u=0/pte.w=0/CR0.WP=0 page by
setting U=0 and W=1 in the shadow PTE. This will cause a user write
to fault and a supervisor write to succeed (which is correct because
CR0.WP=0). A user read instead will flip U=0 to 1 and W=1 back to 0.
This enables user
When eager FPU is disabled, KVM will still see the MPX bit in CPUID and
presumably the MPX vmentry and vmexit controls. However, it will not
be able to expose the MPX XSAVE features to the guest, because the guest's
accessible XSAVE features are always a subset of host_xcr0.
In this case, we
On Mon, Mar 07, 2016 at 03:45:43PM -0800, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.64 release.
> There are 36 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
Patch 1 ensures that all aspects of MPX are disabled when eager FPU
is disabled on the host. Patch 2 is just a cleanup.
Paolo Bonzini (2):
KVM: x86: disable MPX if host did not enable MPX XSAVE features
KVM: x86: remove eager_fpu field of struct kvm_vcpu_arch
From: Noam Camus
- call clocksource_probe()
- This in turns needs of_clk_init() to be called earlier
Cc: Daniel Lezcano
Signed-off-by: Noam Camus
[vgupta: broken off from a bigger patch]
Signed-off-by: Vineet Gupta
- Remove explicit clocksource setup and let it be done by OF framework
by defining CLOCKSOURCE_OF_DECLARE() for various timers
- This allows multiple clocksources to be potentially registered
simultaneouly: previously we could only do one - as all of them had
same arc_counter_setup()
The function __spi_pump_messages() is called by spi_pump_messages() and
__spi_sync(). The function __spi_sync() has an argument 'bus_locked'
that indicates if it is called with the SPI bus mutex held or not. If
'bus_locked' is false then __spi_sync() will acquire the mutex itself.
Commit
Hi,
This mini-series came out as a result of discussions during EZChip platform
code review.
This switches ARC timers to DT based probe and removes the homebrew clk API
we had before.
@Rob could you please take a look at the DT bindings.
@Daniel any comments would be appreciated !
Thx,
-Vineet
On 08.03.2016 14:02, Laxman Dewangan wrote:
> Print the error number of GPIO hog failed during
> its configurations. This helps in identifying the
> failure without instrumenting the code.
>
> Signed-off-by: Laxman Dewangan
> ---
> drivers/gpio/gpiolib.c | 9 +
> 1
On 2016-02-18 18:26, Josh Cartwright wrote:
The use of IRQF_ONESHOT when registering an interrupt handler with
request_irq() is non-sensical.
Not only that, it also prevents the handler from being threaded when it
otherwise should be w/ IRQ_FORCED_THREADING is enabled. This causes the
On Tue, Mar 8, 2016 at 1:56 PM, Jacek Anaszewski
wrote:
> Hi Amitoj,
>
> Thanks for the patches.
>
> Applied only the 7/7 one. In the remaining ones, please remove
> also all occurrences of platform_set_drvdata() in the probe()
> and pdev_to_gpio() definition from
Add ethernet support for MediaTek SoCs from the MT7623 family. These have
dual GMAC. Depending on the exact version, there might be a built-in
Gigabit switch (MT7530). The core does not have the typical DMA ring setup.
Instead there is a linked list that we add descriptors to. There is only
one
Hi all,
while trying to understand the meaning of the net_device flag NETIF_F_HIGHDMA
I came across the function illegal_highdma() which seems to perform two tasks:
1. Check if a network interface is able to handle high memory pages
2. Check if a network interface is able to handle the
> The cw1200 uses #ifdef to check for CONFIG_PM, but then
> uses SIMPLE_DEV_PM_OPS, which leaves the references out when
> CONFIG_PM_SLEEP is not defined, so we get a warning with
> PM=y && PM_SLEEP=n:
>
> drivers/net/wireless/st/cw1200/cw1200_spi.c:450:12: error:
> 'cw1200_spi_suspend' defined
Commit-ID: a23f37e864609f0887c1cb77c4d5b62586484a61
Gitweb: http://git.kernel.org/tip/a23f37e864609f0887c1cb77c4d5b62586484a61
Author: Namhyung Kim
AuthorDate: Mon, 7 Mar 2016 16:44:47 -0300
Committer: Ingo Molnar
CommitDate: Tue, 8 Mar 2016
501 - 600 of 2412 matches
Mail list logo