On 11/08/2015 10:29 PM, Hugh Dickins wrote:
Would it be possible to move that line into migrate_page_copy()?
I don't think it's wrong where you placed it, but that block is really
about resetting the old page ready for freeing, and I'd prefer to keep
all the transference of properties from old
On Thu, 19 Nov 2015, Måns Rullgård wrote:
> Nicolas Pitre writes:
>
> > +static inline uint64_t __arch_xprod_64(uint64_t m, uint64_t n, bool bias)
> > +{
> > + unsigned long long res;
> > + unsigned int tmp = 0;
> > +
> > + if (!bias) {
> > + asm ( "umull %Q0, %R0, %Q1,
On Wed, Nov 18, 2015 at 04:21:17PM +0100, Arnd Bergmann wrote:
> resource_size_t may be defined as 32 or 64 bit depending on configuration,
> so it cannot be printed using the normal format strings, as gcc correctly
> warns:
>
> pinctrl-at91-pio4.c: In function 'atmel_pinctrl_probe':
>
On Tue, 2015-10-27 at 16:56 -0700, Paul Turner wrote:
>
> + * flags is currently unused.
> + */
> +SYSCALL_DEFINE3(restartable_sequences,
> +>> > int, flags, long, event_and_cpu, long, post_commit_instr_addr)
> +{
> + return rseq_configure_current((__user u64
Hi,
On Wed, Nov 18, 2015 at 5:43 PM, John Youn wrote:
> On 11/16/2015 9:22 AM, Doug Anderson wrote:
>> Felipe,
>>
>> On Mon, Nov 16, 2015 at 8:28 AM, Felipe Balbi wrote:
>>>
>>> Hi,
>>>
>>> Douglas Anderson writes:
In general it is wise to clear interrupts before processing them. If
Nicolas Pitre writes:
> +static inline uint64_t __arch_xprod_64(uint64_t m, uint64_t n, bool bias)
> +{
> + unsigned long long res;
> + unsigned int tmp = 0;
> +
> + if (!bias) {
> + asm ( "umull %Q0, %R0, %Q1, %Q2\n\t"
> + "mov%Q0, #0"
> +
On Thursday 19 November 2015 16:18:43 Russell King - ARM Linux wrote:
> On Thu, Nov 19, 2015 at 12:25:45PM +0100, Arnd Bergmann wrote:
> > On Thursday 19 November 2015 03:40:25 Chen Gang wrote:
> > > diff --git a/include/asm-generic/page.h b/include/asm-generic/page.h
> > > index 37d1fe2..67cfb7d
Hi Ulf,
On Thu, Nov 19, 2015 at 7:20 PM, Ulf Hansson wrote:
> On 10 November 2015 at 10:43, Haibo Chen wrote:
>> Here we use '|=' to set the tuning-step, but before that, we should
>> clear the tuning-step, otherwise we could got the wrong setting.
>>
>> Signed-off-by: Haibo Chen
>> ---
>>
On Thu, 19 Nov 2015 10:10:19 +0100 (CET)
Jiri Kosina wrote:
> On Thu, 19 Nov 2015, Ioan-Adrian Ratiu wrote:
>
> > First part of lockdep report:
> > http://imgur.com/clLsCWe
> >
> > Second part:
> > http://imgur.com/Wa2PzRl
> >
> > Here are some printk's of mine while reproducing + debugging
On Thu, Nov 19, 2015 at 06:19:10PM +0200, Octavian Purdila wrote:
> On Thu, Nov 19, 2015 at 5:23 PM, Seth Forshee
> wrote:
> > On Wed, Nov 18, 2015 at 12:00:17AM +0200, Octavian Purdila wrote:
> >> On Tue, Nov 17, 2015 at 10:12 PM, Richard Weinberger
> >> wrote:
> >> > Am 17.11.2015 um 20:25
Guenter Roeck writes:
>> +writel(WD_CONFIG_XTAL_IN, dev->base + WD_CONFIG);
>
> What happens if the DISABLE bit was previously set (assuming
> that DISABLE means that the watchdog is disabled) ?
>
> Concern I guess would be the combination of DISABLE being set
> and WD_COUNTER at a value !=
On Thu, Nov 19, 2015 at 7:17 PM, Ulf Hansson wrote:
> On 10 November 2015 at 10:43, Haibo Chen wrote:
>> Currently, we config the watermark_level register only in probe.
>> This will cause the mmc write operation timeout issue after system
>> resume back in LPSR mode. Because in LPSR mode, after
On Monday 16 November 2015 20:20:38 Nicolas Pitre wrote:
> Arnd,
>
> Please pull the following branch:
>
> git://git.linaro.org/people/nicolas.pitre/linux div64
>
> This contains those patches I've initially posted here:
>
> https://lkml.org/lkml/2015/11/2/715
>
> Only changes to
Felipe,
On Thu, Nov 19, 2015 at 7:34 AM, Felipe Balbi wrote:
>
> Hi,
>
> Douglas Anderson writes:
>> Until we have logic to determine which devices share the same TT let's
>> add logic to assume that all devices on a given dwc2 controller are on
>> one single_tt hub. This is better than the
On 11/18/2015 09:55 AM, Mans Rullgard wrote:
This adds support for the Sigma Designs SMP86xx/SMP87xx family built-in
watchdog.
Signed-off-by: Mans Rullgard
---
Changes:
- combine start and ping functions
- use watchdog_init_timeout()
- calculate max timeout from clock rate
- add get_timeleft
On 11/19/2015 7:48 AM, Jon Mason wrote:
On Wed, Nov 18, 2015 at 03:57:36PM -0800, Ray Jui wrote:
Would this patch merge properly with the other NSP DT clean up patch
+ I2C DT patch that you worked out internally but have not sent out?
I thought it's going to make the maintainers' life easier
There is already helper functions to do 64-bit I/O on 32-bit machines or buses,
thus we don't need to reinvent the wheel.
Signed-off-by: Andy Shevchenko
---
Cahngelog v2:
- rebase on top of recent linux-next
include/linux/intel-iommu.h | 18 ++
1 file changed, 2 insertions(+),
While going through the nohz code I got stumped by some of it.
This patch adds a few comments clarifying the code; based on discussion
with Thomas.
Signed-off-by: Peter Zijlstra (Intel)
---
diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
index 7c7ec4515983..cba9f3479fab 100644
On Thu, Nov 19, 2015 at 12:25:45PM +0100, Arnd Bergmann wrote:
> On Thursday 19 November 2015 03:40:25 Chen Gang wrote:
> > diff --git a/include/asm-generic/page.h b/include/asm-generic/page.h
> > index 37d1fe2..67cfb7d 100644
> > --- a/include/asm-generic/page.h
> > +++
On Thu, Nov 19, 2015 at 5:23 PM, Seth Forshee
wrote:
> On Wed, Nov 18, 2015 at 12:00:17AM +0200, Octavian Purdila wrote:
>> On Tue, Nov 17, 2015 at 10:12 PM, Richard Weinberger wrote:
>> > Am 17.11.2015 um 20:25 schrieb Octavian Purdila:
>> >> On Tue, Nov 17, 2015 at 9:21 PM, Seth Forshee
>> >>
On Wed, Nov 11, 2015 at 02:01:51PM -0800, Tony Luck wrote:
> We used to have a special ring buffer for deferred errors that
> was used to mark problem pages. We replaced that with a genpool.
> Then later converted mce_log() to also use the same genpool. As
> a result we end up adding all deferred
On Thu, Nov 19, 2015 at 04:49:41PM +0100, Jiri Kosina wrote:
> On Thu, 5 Nov 2015, Evgeniy Polyakov wrote:
>
> > > I fail to see why this kthread should be freezable at all. There is no way
> > > for w1 device to generate new I/O requests that should be written out to
> > > filesystem, is it?
> >
Hi Andrew,
On 19.11.2015 16:00, Andrew F. Davis wrote:
> On 11/18/2015 11:50 PM, Vladimir Zapolskiy wrote:
>> Hi Cory,
>>
>> On 19.11.2015 05:29, Cory Tusar wrote:
>>> This commit implements bindings in the eeprom_93xx46 driver allowing
>>> device word size and read-only attributes to be
On 11/19/2015 01:56 AM, Denis Turischev wrote:
AMD Mullins watchdog is fully compatible to the previous Hudson chipset,
reuse the existent sp5100_tco driver.
Signed-off-by: Denis Turischev
diff -Nru linux-4.3.orig/drivers/watchdog/sp5100_tco.c
linux-4.3/drivers/watchdog/sp5100_tco.c
---
On Thu, 19 Nov 2015, Paolo Bonzini wrote:
> On 19/11/2015 16:32, Stefano Stabellini wrote:
> > > In addition to Kevin's replies, I have a high-level question: can VFIO
> > > be used by QEMU for both KVM and Xen?
> >
> > No. VFIO cannot be used with Xen today. When running on Xen, the IOMMU
> > is
Hello, Lukas.
On Thu, Nov 19, 2015 at 04:31:11PM +0100, Lukas Wunner wrote:
> Hi Tejun,
>
> when you introduced current_is_async() with 84b233adcca3, was it a
> deliberate decision not to export it? All other non-static functions
> in async.c are exported as well.
>
> I'm asking because I would
On 11/19/2015 04:23 PM, Wenwei Tao wrote:
The return value should be non-zero under error conditions.
Remove nvme_free(dev) to avoid free dev more than once.
Signed-off-by: Wenwei Tao
---
drivers/lightnvm/core.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git
Add a simple boolean binding to turn on and off the use of ADC
microphone detection mode to determine 3/4 pole jack.
Signed-off-by: Charles Keepax
Acked-by: Chanwoo Choi
---
drivers/extcon/extcon-arizona.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git
This patch chain adds device bindings for the jack and
microphone detection system specific settings.
Changes since v2:
- Now moved things over to the new extcon binding document
Thanks,
Charles
Charles Keepax (6):
extcon: arizona: Add device binding to enable ADC mode micdet
extcon:
The switch is generally used in conjunction with the MICDET clamp to
suppress pops and clicks associated with jack insertion. This patch adds
a binding that allows the user to select the mode of operation for this
switch.
Signed-off-by: Charles Keepax
Acked-by: Chanwoo Choi
---
Add additional bindings to allow configuration of the system specific
microphone detection settings.
Signed-off-by: Charles Keepax
---
.../devicetree/bindings/extcon/extcon-arizona.txt | 20
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git
Some Arizona devices have the option to use the GPIO5 pin as a second
jack detection pin. This patch adds device bindings to specify to the
driver that it should use this pin. Note that the second jack detection
pin is hard wired in the chip so can only be enabled through the
binding, rather than
By default the driver expects the jackdet pin to be pulled low when a
jack is inserted. This patch adds a device binding that allows the user
to specify that the jackdet pin will be pulled high when a jack is
inserted.
Signed-off-by: Charles Keepax
Acked-by: Chanwoo Choi
---
Add additional bindings for both inverting the polarity of the jack
detection pins and allowing the use of a second jack detection pin. Note
that the second jack detection pin is hard wired in the chip so can only
be enabled through the binding, rather than a pin being specified.
Signed-off-by:
On Wed, Nov 18, 2015 at 12:46:21AM +0200, Octavian Purdila wrote:
> Naive implementation for non-mmu architectures: allocate physically
> contiguous xfs buffers with alloc_pages. Terribly inefficient with
> memory and fragmentation on high I/O loads but it may be good enough
> for basic usage
On Wed, Nov 18, 2015 at 03:57:36PM -0800, Ray Jui wrote:
> Would this patch merge properly with the other NSP DT clean up patch
> + I2C DT patch that you worked out internally but have not sent out?
>
> I thought it's going to make the maintainers' life easier if you can
> group DT changes per
Readers need to know if vtime runs at all on some CPU somewhere, this
is a fast-path check to determine if we need to check further the need
to add up any tickless cputime delta.
This fast path check uses context tracking state because vtime is tied
to context tracking as of now. This check
On Wed, Nov 18, 2015 at 8:06 PM, Stephen Rothwell wrote:
> Hi Paul,
>
> Today's linux-next merge of the audit tree got a conflict in:
>
> kernel/audit.c
>
> between commit:
>
> d0164adc89f6 ("mm, page_alloc: distinguish between being unable to sleep,
> unwilling to sleep and avoiding waking
Hi all,
the Allwinner A10/A20 SPI module supports an option to configure a number of
clock periods to wait between each word ("SPI Wait Clock Register" in the A20
manual). This is a very useful option if talking to devices which specify a
minimum amount of inter-word wait time.
I initially tried
Adds support and documentation for a new slave device property
"sun4i,spi-wdelay" that allows to set the SPI Wait Clock Register per
device / transfer. The SPI hardware will wait the specified amount of
SPI clock periods (plus a constant 3 clock periods) before transmitting
the next word.
The
On Fri, 6 Nov 2015, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 6 Nov 2015 17:55:23 +0100
>
> The kobject_put() function tests whether its argument is NULL and then
> returns immediately. Thus the test around the call is not needed.
>
> This issue was detected by using the
On Thu, 2015-11-19 at 15:32 +, Stefano Stabellini wrote:
> On Thu, 19 Nov 2015, Jike Song wrote:
> > Hi Alex, thanks for the discussion.
> >
> > In addition to Kevin's replies, I have a high-level question: can VFIO
> > be used by QEMU for both KVM and Xen?
>
> No. VFIO cannot be used with
Toshiba laptops with WWAN devices installed cannot use the device unless
it is attached and powered, similar to how Toshiba Bluetooth devices
work.
This patch adds support to WWAN devices, introducing three functions,
one to query the overall status of the wireless devices (RFKill, WLAN,
BT,
From: Hiroshi Shimamoto
There is an extra cost in task_cputime() and task_cputime_scaled() when
nohz_full is not activated. When vtime accounting is not enabled, we
don't need to get deltas of utime and stime under vtime seqlock.
This patch removes that cost with adding a shortcut route if
The first two patches from Hiroshi Shimamoto are fixes to be backported.
Although it's debatable whether the 2nd patch needs backport.
The patches that follow are further fixes and cleanups and the last
one is an optimization.
On Thu, 5 Nov 2015, Evgeniy Polyakov wrote:
> > I fail to see why this kthread should be freezable at all. There is no way
> > for w1 device to generate new I/O requests that should be written out to
> > filesystem, is it?
>
> w1 doesn't generate such requests, but it was more to make this
On 19/11/2015 16:32, Stefano Stabellini wrote:
> > In addition to Kevin's replies, I have a high-level question: can VFIO
> > be used by QEMU for both KVM and Xen?
>
> No. VFIO cannot be used with Xen today. When running on Xen, the IOMMU
> is owned by Xen.
I don't think QEMU command line
When a task runs on a housekeeper (a CPU running with the periodic tick
with neighbours running tickless), it doesn't account cputime using vtime
but relies on the tick. Such a task has its vtime_snap_whence value set
to VTIME_INACTIVE.
Readers won't handle that correctly though. As long as vtime
These two patches add WWAN support to the driver, the first adds the actual
support functions and the second adds RFKill handler functions to set the
device status according to the killswitch.
Changes since v1:
- Added missing calls to rfkill_unregister and rfkill_destroy functions
Azael Avalos
VTIME_SLEEPING state happens either when:
1) The task is sleeping and no tickless delta is to be added on the task
cputime stats.
2) The CPU isn't running vtime at all, so the same properties of 1) applies.
Lets rename the vtime symbol to reflect both states.
Cc: Christoph Lameter
Cc: Chris
A previuos patch added WWAN support to the driver, allowing to query
and set the device status.
This patch adds RFKill support for the recently introduced WWAN device,
making use of the WWAN and *wireless_status functions to query the
killswitch and (de)activate the device accordingly to its
The cputime can only be updated by the current task itself, even in
vtime case. So we can safely use seqcount instead of seqlock as there
is no writer concurrency involved.
Cc: Christoph Lameter
Cc: Chris Metcalf
Cc: Ingo Molnar
Cc: Luiz Capitulino
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc:
From: Hiroshi Shimamoto
/proc/stats shows invalid gtime when the thread is running in guest.
When vtime accounting is not enabled, we cannot get a valid delta.
The delta is calculated with now - tsk->vtime_snap, but tsk->vtime_snap
is only updated when vtime accounting is runtime enabled.
This
vtime_accounting_enabled() checks if vtime is running on the current CPU
and is as such a misnomer. Lets rename it to a function that reflect its
locality. We are going to need the current name for a function that tells
if vtime runs at all on some CPU.
Cc: Christoph Lameter
Cc: Chris Metcalf
On Wed, 18 Nov 2015, David Airlie wrote:
> I'm assuming I'll get a pull request from Jani by the end of the week,
> and I'll pass it on to you as per normal, but it might be good if he
> could accelerate that.
Done. http://mid.gmane.org/87vb8yt4a2@intel.com
BR,
Jani.
--
Jani Nikula,
On Fri, Nov 13, 2015 at 04:08:53PM +0800, Chen-Yu Tsai wrote:
> On Mon, Nov 9, 2015 at 12:18 PM, Chen-Yu Tsai wrote:
> > On Fri, Oct 30, 2015 at 10:20 PM, Maxime Ripard
> > wrote:
> >> The Allwinner SoCs have a gate controller to gate the access to the DRAM
> >> clock to the some devices that
On Thu, Nov 12, 2015 at 12:31:54PM -0800, Stephen Boyd wrote:
> On 11/06, Maxime Ripard wrote:
> > Hi Stephen,
> >
> > Thanks for your feedback!
> >
> > On Fri, Oct 30, 2015 at 02:29:02PM -0700, Stephen Boyd wrote:
> > > > +
> > > > + mux = kzalloc(sizeof(*mux), GFP_KERNEL);
> > > > +
Hi Tejun,
when you introduced current_is_async() with 84b233adcca3, was it a
deliberate decision not to export it? All other non-static functions
in async.c are exported as well.
I'm asking because I would like to use it in i915.ko.
Thanks,
Lukas
Lukas Wunner (1):
async: export
Introduced by 84b233adcca3 ("workqueue: implement current_is_async()").
Cc: Tejun Heo
Signed-off-by: Lukas Wunner
---
kernel/async.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/async.c b/kernel/async.c
index 4c3773c..d2edd6e 100644
--- a/kernel/async.c
+++ b/kernel/async.c
@@
On Thu, 19 Nov 2015, Krzysztof Kozlowski wrote:
> i2c_driver does not need to set an owner because i2c_register_driver()
> will set it.
>
> Signed-off-by: Krzysztof Kozlowski
> Acked-by: Benjamin Tissoires
Applied to for-4.5/i2c-hid. Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from
On 2015-11-18 18:39, Andrey Utkin wrote:
Me and my friend have once talked about careful application development,
which includes awareness about all possible error conditions.
So we have collected ideas about making kernel (or, in some cases, libc)
"hostile" to careless application, and we
> -Original Message-
> From: Bastien Nocera [mailto:had...@hadess.net]
> Sent: 19 November, 2015 17:25
> To: Tirdea, Irina; Dmitry Torokhov; Aleksei Mamlin; Karsten Merker;
> linux-in...@vger.kernel.org
> Cc: Mark Rutland; Rob Herring; Purdila, Octavian;
> linux-kernel@vger.kernel.org;
On Thu, 19 Nov 2015 14:39:35 +
Javi Merino wrote:
> > +
>
> One minor nit: can you use key=value (i.e. "throttled=%d") instead for
> consistency with the rest of this file?
>
will do.
> Other than that, I know that Peter suggested an enum for the action,
> but wouldn't it be better to
On 11/19/2015 09:23 AM, Christoph Hellwig wrote:
> It's pretty much guaranteed a block layer bug, most likely in the
> merge bios to request infrastucture where we don't obey the merging
> limits properly.
>
> Does either of you have a known good and first known bad kernel?
Well, I have been
On Mon, Nov 09, 2015 at 11:36:15AM +0800, Chen-Yu Tsai wrote:
> >> > + sclk1_parents[0] = sclk2_name;
> >> > + sclk1_parents[1] = sclk2d2_name;
> >>
> >> Is there any need to expose these 2 clocks via DT using
> >> of_clk_add_provider?
> >
> > No, as far as I'm aware, there's no user
Hi,
Douglas Anderson writes:
> Until we have logic to determine which devices share the same TT let's
> add logic to assume that all devices on a given dwc2 controller are on
> one single_tt hub. This is better than the previous code that assumed
> that all devices were on one multi_tt hub,
On Thu, 19 Nov 2015, Jike Song wrote:
> Hi Alex, thanks for the discussion.
>
> In addition to Kevin's replies, I have a high-level question: can VFIO
> be used by QEMU for both KVM and Xen?
No. VFIO cannot be used with Xen today. When running on Xen, the IOMMU
is owned by Xen.
--
To unsubscribe
On Thu, Nov 19, 2015 at 09:39:02PM +0800, Andy Yan wrote:
> Hi Thierry:
>
> 2015-11-19 20:56 GMT+08:00 Thierry Reding :
>
> > On Thu, Nov 19, 2015 at 09:17:37AM +0800, Andy Yan wrote:
> > > Hi Rob:
> > >
> > > On 2015年11月19日 06:59, Rob Herring wrote:
> > > >On Wed, Nov 18, 2015 at 05:53:30PM
On Tuesday 17 November 2015 12:35:58 Nicolas Ferre wrote:
> Arnd, Olof, Kevin,
>
> This is the first "fixes" pull-request for AT91. I tried to collect little
> patches that didn't make it for -rc1.
> It can be due to synchronization between trees like the addition of some
> sama5d2 Xplained nodes
The return value should be non-zero under error conditions.
Remove nvme_free(dev) to avoid free dev more than once.
Signed-off-by: Wenwei Tao
---
drivers/lightnvm/core.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/lightnvm/core.c b/drivers/lightnvm/core.c
On Thu, 2015-11-19 at 14:26 +0200, Irina Tirdea wrote:
> After power on, it is recommended that the driver resets the device.
> The reset procedure timing is described in the datasheet and is used
> at device init (before writing device configuration) and
> for power management. It is a sequence
On Wed, Nov 18, 2015 at 12:00:17AM +0200, Octavian Purdila wrote:
> On Tue, Nov 17, 2015 at 10:12 PM, Richard Weinberger wrote:
> > Am 17.11.2015 um 20:25 schrieb Octavian Purdila:
> >> On Tue, Nov 17, 2015 at 9:21 PM, Seth Forshee
> >> wrote:
> >>>
> >>> On Tue, Nov 17, 2015 at 08:12:31PM
On Tuesday 17 November 2015 17:30:14 Punit Agrawal wrote:
> Arnd Bergmann writes:
>
> > The scpi_clock driver can be built-in when CONFIG_COMPILE_TEST
> > is set even when ARM_SCPI_PROTOCOL is a loadable module, and
> > that results in a link error:
> >
> > drivers/built-in.o: In function
> Subject: Re: [PATCH] input: i8042: add quirk to implement i8042 detect for AMD
>
> On Fri, Oct 16, 2015 at 12:21:55PM +0200, Borislav Petkov wrote:
> > On Fri, Oct 16, 2015 at 05:35:40PM +0800, Wan ZongShun wrote:
> > > 2015-10-16 16:58 GMT+08:00 Borislav Petkov :
> > > > On Fri, Oct 16, 2015
On Thu, Nov 19, 2015 at 03:49:00PM +0100, Richard Weinberger wrote:
> Am 19.11.2015 um 15:37 schrieb Colin Walters:
> > On Thu, Nov 19, 2015, at 02:53 AM, Richard Weinberger wrote:
> >
> >> Erm, I don't want this in the kernel. That's why I've proposed the lklfuse
> >> approach.
> >
> > I
On Thu, Nov 19, 2015 at 11:35:23AM +0800, Chris Zhong wrote:
> From: Liu Ying
>
> This patch adds device tree bindings for Synopsys DesignWare MIPI DSI
> host controller DRM bridge driver.
>
> Signed-off-by: Liu Ying
> Signed-off-by: Chris Zhong
>
> ---
>
> Changes in v3:
> move the
Am 19.11.2015 um 15:21 schrieb Serge E. Hallyn:
> On Thu, Nov 19, 2015 at 08:53:26AM +0100, Richard Weinberger wrote:
>> Am 19.11.2015 um 08:47 schrieb James Morris:
>>> On Wed, 18 Nov 2015, Richard Weinberger wrote:
>>>
On Wed, Nov 18, 2015 at 4:13 PM, Al Viro wrote:
> On Wed, Nov 18,
Implements kvm_vgic_[set|unset]_forward.
Handle low-level VGIC programming: physical IRQ/guest IRQ mapping,
list register cleanup, VGIC state machine. Also interacts with
the irqchip.
Signed-off-by: Eric Auger
---
v3 -> v4:
- use the target vCPU in set/unset_forward
- rebase after removal of
On Wed, Nov 18, 2015 at 09:51:48PM +0100, Josef Gajdusek wrote:
> This patch adds support for the Sunxi thermal sensor on the Allwinner H3.
> Also adds declaration of the H3 THS clock to clk-sunxi.c ignoring the
> dividers as they are not continuous (clk-divider.c cannot be used as it
> does not
Select IRQ_BYPASS_MANAGER when CONFIG_KVM is set
Signed-off-by: Eric Auger
---
arch/arm/kvm/Kconfig | 2 ++
arch/arm64/kvm/Kconfig | 2 ++
2 files changed, 4 insertions(+)
diff --git a/arch/arm/kvm/Kconfig b/arch/arm/kvm/Kconfig
index 95a0005..73d7201 100644
--- a/arch/arm/kvm/Kconfig
+++
Add a new forwarded flag in vfio_platform_irq. In case the IRQ
is forwarded, the VFIO platform IRQ handler does not need to
disable the IRQ anymore.
When setting the IRQ handler we now also test the forwarded state. In
case the IRQ is forwarded we select the vfio_irq_handler.
Signed-off-by:
On Wed, Nov 18, 2015 at 10:29:38PM -0500, Cory Tusar wrote:
> This commit documents bindings to be added to the eeprom_93xx46 driver
> which will allow:
>
> - Device word size and read-only attributes to be specified.
> - A device-specific compatible string for use with Atmel AT93C46D
>
A single handler now is registered whatever the use case: automasked
or not. A function pointer is set according to the wished behavior
and the handler calls this function.
The irq lock is taken/released in the root handler. eventfd_signal can
be called in regions not allowed to sleep.
This function returns whether the IRQ is active at irqchip level or
VFIO masked. If either is true, the IRQ is considered active.
Currently there is no way to differentiate userspace masked IRQ from
automasked IRQ. There might be false detection of activity. However
it is currently acceptable to
On Wed, Nov 18, 2015 at 03:13:35PM +, Al Viro wrote:
> On Wed, Nov 18, 2015 at 09:05:12AM -0600, Seth Forshee wrote:
>
> > Yes, the host admin. I'm not talking about trusting the admin inside the
> > container at all.
>
> Then why not have the same host admin just plain mount it when setting
From: Marc Zyngier
So far, the only user of the mapped interrupt facility was the timer:
the physical distributor active state needed to be context-switched
for each vcpu, as the device is shared across all vcpus.
This patch allows to indicate whether a mapped IRQ originates from a
device
Up to now irqfd injection was only possible for unmapped IRQ. This
patch adds support for injecting mapped interrupts.
Signed-off-by: Eric Auger
---
virt/kvm/arm/vgic.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/virt/kvm/arm/vgic.c b/virt/kvm/arm/vgic.c
index
On Wed, Nov 18, 2015 at 03:57:47PM -0500, Akshay Bhat wrote:
> Add support for Innolux CheMei 12" G121X1-L03 XGA LVDS display.
>
> Datasheet: http://www.azdisplays.com/PDF/G121X1-L03.pdf
> Signed-off-by: Akshay Bhat
Acked-by: Rob Herring
> ---
>
Hi Jeff,
On Mon 16-11-15 12:23:05, Jeff Moyer wrote:
> Jens Axboe writes:
> > On 11/16/2015 08:11 AM, Jan Kara wrote:
> >> Hello,
> >>
> >> lately I was looking into a big performance hit we take when blkio
> >> controller is enabled and jbd2 thread ends up in a different cgroup than
> >> user
When disabling a non shared mapped IRQs, we must manually deactivate
the corresponding physical IRQ on top of removing the active state
from the distributor.
Signed-off-by: Eric Auger
---
virt/kvm/arm/vgic.c | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff
This patch populates the IRQ bypass callacks:
- stop/start producer simply consist in disabling/enabling the host irq
- add/del consumer: basically set the automasked flag to false/true
Signed-off-by: Eric Auger
---
v3 -> v4:
- use vfio_platform_set_forwarded in place of
Implement IRQ bypass callbacks for arm/arm64 IRQ forwarding:
- kvm_arch_irq_bypass_add_producer: perform VGIC/irqchip
settings for forwarding
- kvm_arch_irq_bypass_del_producer: same for inverse operation
- kvm_arch_irq_bypass_stop: halt guest execution
- kvm_arch_irq_bypass_start: resume guest
This patch implements the clear of a pending non shared mapped IRQ.
In case of an edge IRQ, we deactivate the physical IRQ that will never
be deactivated by the guest. In case of a level sensitive IRQ we check
the level of the input signal. If it is asserted we leave the virtual
IRQ pending. In
This function allows to change the forwarded mode and selects
the IRQ handler accordingly.
Signed-off-by: Eric Auger
---
v3 -> v3:
- renamed vfio_platform_set_automasked into
vfio_platform_set_forwarded
- do not change VFIO_IRQ_INFO_AUTOMASKED setting when turning
forwarding on/off
v1 ->
Register a dummy producer with void callbacks
Signed-off-by: Eric Auger
---
v3 -> v3:
- replace WARN_ON by pr_info() in case irq_bypass_register_producer
fails
v2 -> v3:
- rename vfio_platform_irq_bypass_resume into *_start
---
drivers/vfio/platform/vfio_platform_irq.c | 34
This series allows to optimize the deactivation of virtual interrupts
associated to a vfio platform device IRQ. Let's call this optimization:
ARM IRQ forwarding.
Without that optimization the deactivation of the physical IRQ is done
by the host and the deactivation of the virtual IRQ, by the
Currently on clear-enable MMIO we retire the corresponding LR whatever
its state. More precisely we do not sync ACTIVE state but we erase the LR
state.
In case of a forwarded IRQ, the physical IRQ source is also erased meaning
the physical IRQ will never be deactivated. In case of a non forwarded
On Wed, Nov 18, 2015 at 02:47:12PM -0600, Benoit Parrot wrote:
> Device Tree bindings for the DRA72 Camera Adaptation Layer (CAL)
> H/W module.
>
> Signed-off-by: Benoit Parrot
Acked-by: Rob Herring
> ---
> Documentation/devicetree/bindings/media/ti-cal.txt | 72
> ++
>
The driver uses `struct counter_mode_register_t` to describe the 16-bit
counter mode register as a sequence of bitfield members. The struct
appears as the type of one of the members of `union cmReg`, the other
member of which is of type `unsigned short`, so the driver can
manipulate the register
On Tue, Nov 17, 2015 at 05:00:26PM -0800, Stephen Boyd wrote:
> The drivers don't really need to know which PMIC they're for, so
> make a generic binding for them. This alleviates us from updating
> the drivers every time a new PMIC comes out. It's still
> recommended that we update the binding
501 - 600 of 1776 matches
Mail list logo
