* Ingo Molnar wrote:
>
> * Waiman Long wrote:
>
> > I do have a patchset that allow us to more accurately determine the state of
> > the lock owner.
> >
> > locking/rwsem: Add reader-owned state to the owner field
> >
The symbol bus_attr_resource_alignment is not exported or declared
elsewhere, so make it static to fix the following warning:
drivers/pci/pci.c:4900:1: warning: symbol 'bus_attr_resource_alignment' was not
declared. Should it be static?
Signed-off-by: Ben Dooks
---
On Thu, 2016-06-09 at 14:05 +1000, Stephen Rothwell wrote:
> Hi Kees,
>
> On Wed, 8 Jun 2016 19:56:38 -0700 Kees Cook wrote:
> >
> > Congratulations on having the gcc plugin development headers
> > successfully installed! ;)
>
> Thanks :-)
And on ppc64le too! (I think)
On Thu, 09 Jun 2016, Wadim Egorov wrote:
> On 08.06.2016 16:17, Lee Jones wrote:
> > On Thu, 02 Jun 2016, Wadim Egorov wrote:
> >
> >> The RK818 chip is a power management IC for multimedia and handheld
> > "Power Management IC (PMIC)"
> >
> >> devices. It contains the following components:
> >>
>
On Thu, Jun 09, 2016 at 01:21:18PM +0200, Paolo Bonzini wrote:
> This is basically implementing a seqcount. It needs two barriers and,
Why does it need the two barriers? More details please.
> technically, they should be virt_rmb() -- it really doesn't matter of
> course because reads are never
From: Michal Hocko
Currently we have two proc interfaces to set oom_score_adj. The legacy
/proc//oom_adj and /proc//oom_score_adj which both have their
specific handlers. Big part of the logic is duplicated so extract the
common code into __set_oom_adj helper. Legacy knob still
On Wed, 2016-06-08 at 15:59 +0200, Peter Zijlstra wrote:
> On Wed, Jun 08, 2016 at 11:49:20PM +1000, Michael Ellerman wrote:
>
> > > Ok; what tree does this go in? I have this dependent series which I'd
> > > like to get sorted and merged somewhere.
> >
> > Ah sorry, I didn't realise. I was going
* Alison Chaiken | 2016-06-07 17:19:43 [-0700]:
>Sorry to be obscure; I had applied that patch to v4.1.6-rt5.
Using the latest is often not a bad choice compared to the random tree
you have here.
>> What I remember from testing the two patches on am335x was that before a
>> ping flood on gbit
On Tuesday, June 7, 2016 4:29:21 PM CEST Baolin Wang wrote:
> Now on ARM64 platform, it will set 'dummy_dma_ops' for device dma_ops if
> it did not call 'arch_setup_dma_ops' at device creation time by issuing
> platform_device_alloc() function, that will cause failure when setting
> the dma mask
On Wednesday, June 8, 2016 10:21:27 AM CEST Marc Zyngier wrote:
> > + rockchip_pcie_enable_interrupts(port);
> > + if (!IS_ENABLED(CONFIG_PCI_MSI)) {
> > + err = rockchip_pcie_init_irq_domain(port);
> > + if (err < 0)
> > + goto err_vpcie;
>
>
On 09/06/2016 14:43, Roman Kagan wrote:
> On Thu, Jun 09, 2016 at 01:23:23PM +0200, Paolo Bonzini wrote:
>> The version field in struct pvclock_vcpu_time_info basically implements
>> a seqcount. Wrap it with the usual read_begin and read_retry functions,
>> and use these APIs instead of
Andrew Lunn writes:
> On Wed, Jun 08, 2016 at 08:44:53PM -0400, Vivien Didelot wrote:
>> Extract the allocation and registration code related to the dsa_switch
>> structure in a mv88e6xxx_register_switch helper function.
>>
>> For symmetry in the code, add a
On Wed, Jun 01, 2016 at 11:37:50PM +0800, Lijun Ou wrote:
> This patch mainly added icm support for RoCE. It initializes icm
> which managers the relative memory blocks for RoCE. The data
> structures of RoCE will be located in it. For example, CQ table,
> QP table and MTPT table so on.
I wonder
Prasun Maiti writes:
> Since add more warnings for inconsistent ops in cfg80211, the wireless
> core warns if a driver implements a cfg80211 callback but doesn't
> implements the inverse operation. The ath6kl driver implements a cfg80211
> .get_antenna operation handler
On Tue, 7 Jun 2016 22:41:47 +0200
Maxime Ripard wrote:
> Add support for the various dividers (linear, table or pow-of-two based)
> found in the CCU.
>
> Signed-off-by: Maxime Ripard
> ---
> drivers/clk/sunxi-ng/Makefile |
On Tue, 7 Jun 2016 22:41:50 +0200
Maxime Ripard wrote:
> Introduce support for clocks that multiply and divide using linear factors.
>
> Signed-off-by: Maxime Ripard
>
> ---
> Changes from v1:
> - Fixed the maximums for
On Wed 08-06-16 22:04:50, Deepa Dinamani wrote:
> CURRENT_TIME is not y2038 safe.
>
> CURRENT_TIME macro is also not appropriate for filesystems
> as it doesn't use the right granularity for filesystem
> timestamps.
>
> Logical Volume Integrity format is described to have the
> same timestamp
Hi Peter,
The attach/detach twice problem is worse than Vincent reported.
The attach twice issue can happen not only as Vincent raised when task moves
between groups, but also when switching to fair class. In addition, for newly
forked task, the detach also has a problem. This patchset attempts
attach_entity_load_avg() is called (indirectly) from:
- switched_to_fair(): switch between classes to fair
- task_move_group_fair(): move between task groups
- enqueue_entity_load_avg(): enqueue entity
Only in switched_to_fair() is it possible that the task's last_update_time
is not 0 and
Hi Peppe,
On Tue, 2016-06-07 at 10:30 +0200, Giuseppe CAVALLARO wrote:
> Hello
>
> On 6/7/2016 5:01 AM, th...@altera.com wrote:
> > From: Tien Hock Loh
> >
> > This adds support for TSE PCS that uses SGMII adapter when the phy-mode of
> > the dwmac is set to sgmii
> >
> >
On Wednesday, June 8, 2016 6:39:08 PM CEST Jan Kiszka wrote:
> >>
> >
> > I just don’t see how an ACPI based hypervisor can ever be certified for
> > safety critical applications. It might be possible but it should be
> > an enormous undertaking; perhaps a subset without AML, but then again
> >
From: Zhaoyang Huang
There should be a gap between tick_nohz_idle_enter and
tick_nohz_get_sleep_length when idle, which will cause the
sleep_length is not very precised. Change it in this patch.
Signed-off-by: Zhaoyang Huang
---
From: Zhaoyang Huang
In previous version, cpu_pm_enter is invoked after the governor
select the state, which cause the executing time of cpu_pm_enter
is included in the idle time. Moving it before the state selection.
Signed-off-by: Zhaoyang Huang
Hi Daniel,
On Wed, Jun 8, 2016 at 4:10 PM, Daniel Lezcano
wrote:
> On 06/07/2016 11:54 AM, Geert Uytterhoeven wrote:
>
> [ ... ]
>
>> in clockevents/clockevents/next breaks the boot on e.g. r8a7791/koelsch
>> (arm32) and r8a7795/salvator-x (arm64).
>>
>> Using
On 06/08/2016 05:26 PM, Rhyland Klein wrote:
> On 6/8/2016 2:35 AM, Krzysztof Kozlowski wrote:
>> On 06/07/2016 10:26 PM, Rhyland Klein wrote:
>>> Change power_supply_read_temp() to use power_supply_get_property()
>>> so that it will check the use_cnt and ensure it is > 0. The use_cnt
>>> will be
On Thu, Jun 09, 2016 at 12:01:13AM +0300, Roman Kagan wrote:
> On Wed, Jun 08, 2016 at 09:45:09PM +0200, Borislav Petkov wrote:
> > On Wed, Jun 08, 2016 at 09:11:39PM +0300, Roman Kagan wrote:
> > > --- a/arch/x86/include/asm/pvclock.h
> > > +++ b/arch/x86/include/asm/pvclock.h
> > > @@ -80,18
There is little obvious use case for a regualtor driver to know if it is
possible to vary voltages at all by itself. If a consumer needs to
limit what voltages it tries to set based on the system configuration
then it will need to enumerate the possible voltages, and without that
even if it is
On Wed, Jun 08, 2016 at 10:06:12AM +0800, Garlic Tseng wrote:
> On Tue, 2016-06-07 at 16:54 +0100, Mark Brown wrote:
> > Do you need to export the individual ops rather than just the ops
> > structure?
> Yes, in 2701 driver we modify some ops.
OK.
signature.asc
Description: PGP signature
The version field in struct pvclock_vcpu_time_info basically implements
a seqcount. Wrap it with the usual read_begin and read_retry functions,
and use these APIs instead of peppering the code with smp_rmb()s.
While at it, change it to the more pedantically correct virt_rmb().
With this change,
From: Michal Hocko
Currently oom_kill_process skips both the oom reaper and SIG_KILL if a
process sharing the same mm is unkillable via OOM_ADJUST_MIN. After "mm,
oom_adj: make sure processes sharing mm have same view of oom_score_adj"
all such processes are sharing the same
From: Michal Hocko
both oom_adj_write and oom_score_adj_write are using task_lock,
check for task->mm and fail if it is NULL. This is not needed because
the oom_score_adj is per signal struct so we do not need mm at all.
The code has been introduced by 3d5992d2ac7d ("oom: add
From: Michal Hocko
vforked tasks are not really sitting on any memory. They are sharing
the mm with parent until they exec into a new code. Until then it is
just pinning the address space. OOM killer will kill the vforked task
along with its parent but we still can end up
From: Michal Hocko
oom_reaper relies on the mmap_sem for read to do its job. Many places
which might block readers have been converted to use down_write_killable
and that has reduced chances of the contention a lot. Some paths where
the mmap_sem is held for write can take other
From: Michal Hocko
The only case where the oom_reaper is not triggered for the oom victim
is when it shares the memory with a kernel thread (aka use_mm) or with
the global init. After "mm, oom: skip vforked tasks from being selected"
the victim cannot be a vforked task of the
On Wed, 2016-06-08 at 22:55 -0400, Oleg Drokin wrote:
> It used to be the case that state had an rwlock that was locked for write
> by downgrades, but for read for upgrades (opens). Well, the problem is
> if there are two competing opens for the same state, they step on
> each other toes
Hi Roger,
> From: Roger Quadros
> Sent: Thursday, June 09, 2016 4:31 PM
>
> Peter & Yoshihiro,
>
> On 09/06/16 08:27, Peter Chen wrote:
> > On Wed, Jun 8, 2016 at 5:03 PM, Roger Quadros wrote:
> >> Hi,
> >>
> >> This series centralizes OTG/Dual-role functionality in the kernel.
On Thu, Jun 09, 2016 at 11:44:18AM +0200, Krzysztof Kozlowski wrote:
> Few drivers have a need of getting regulator supplies without knowing
> their names:
> 1. The Simple Framebuffer driver works on setup provided by bootloader
>(outside of scope of kernel);
> 2. Generic power sequence driver
On Thu, Jun 09, 2016 at 10:01:42AM +0100, Chris Wilson wrote:
>
> [15774.966082] divide error: [#1] SMP
> [15774.966137] Modules linked in: i915 intel_gtt
> [15774.966208] CPU: 1 PID: 15319 Comm: gemscript Not tainted 4.7.0-rc1+ #330
> [15774.966252] Hardware name:
On Thu, Jun 09, 2016 at 08:48:03AM +0200, Ingo Molnar wrote:
> * Lukas Wunner wrote:
> > On Wed, Jun 08, 2016 at 11:56:14AM -0700, Yinghai Lu wrote:
> > > How do you know that sec is valid ?
> > > How about on the system that have one bridge that still have sec num
> > > register
The functions inet_diag_msg_common_fill and inet_diag_msg_attrs_fill
seem to have been missed from the include/linux/inet_diag.h header
file. Add them to fix the following warnings:
net/ipv4/inet_diag.c:69:6: warning: symbol 'inet_diag_msg_common_fill' was not
declared. Should it be static?
On 07/06/2016 15:16, Minfei Huang wrote:
> ping. Any comment is appreciate.
The patch looks good, I'll follow up with another to introduce the
seqcount-like read_begin/read_retry API.
Thanks,
Paolo
> On 05/28/16 at 08:27P, Minfei Huang wrote:
>> There is a generic function
> > - case 0x10:
> > - /* Keys pressed */
> > + case 0x0010:
> > + /* Sequence of keys pressed */
> > for (i = 2; i < len; ++i)
> > - dell_wmi_process_key(buffer_entry[i]);
> > +
From: Claudio Fontana
Signed-off-by: Claudio Fontana
---
arch/x86/kernel/apic/apic.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
index
The lcm and lcm_not_zero() are producing sparse warnings due to
the use of __attribute_const__ in the header but not in the lcm.c
file. Add the __attribute_const__ to lcm.c and make the header
consistent with using the attribute before the function to fix
the following sparse warnings:
Use distinctive name for cpu_hotplug.dep_map to avoid the actual
cpu_hotplug.lock appearing as cpu_hotplug.lock#2 in lockdep splats.
Cc: Ingo Molnar
Cc: Peter Zijlstra
Cc: Gautham R. Shenoy
Cc: intel-...@lists.freedesktop.org
Cc:
In downstream Raspberry Pi kernel we noticed that audio didn't work
as expected, we got stuttering and overruns/underruns. Here's the
link to the original discussion on GitHub:
https://github.com/raspberrypi/linux/issues/1517
This issue is caused by a small bug in the period-splitting-code
and
Em Mon, 21 Mar 2016 14:30:38 +0100
Max Kellermann escreveu:
> Allow the client to free its data structures only after all files have
> been closed (fixing use-after-free bugs).
Hmm... Shuah is also working on fixing such issues at the media controller
stuff, and I made a few
> -Original Message-
> From: Thomas Gleixner [mailto:t...@linutronix.de]
> Sent: Thursday, June 09, 2016 5:01 AM
> To: Kershner, David A
> Cc: cor...@lwn.net; mi...@redhat.com; h...@zytor.com;
> gre...@linuxfoundation.org; Arfvidson, Erik; Sell, Timothy C;
> hof...@osadl.org;
On Wed 08-06-16 12:16:05, Johannes Weiner wrote:
> On Wed, Jun 08, 2016 at 02:51:37PM +0200, Michal Hocko wrote:
> > On Mon 06-06-16 15:48:33, Johannes Weiner wrote:
> > > Rename struct zone_reclaim_stat to struct lru_cost, and move from two
> > > separate value ratios for the LRU lists to a
On 09/06/2016 14:16, Peter Zijlstra wrote:
> On Sat, May 28, 2016 at 08:27:43PM +0800, Minfei Huang wrote:
>> +++ b/arch/x86/kernel/pvclock.c
>> @@ -61,11 +61,14 @@ void pvclock_resume(void)
>> u8 pvclock_read_flags(struct pvclock_vcpu_time_info *src)
>> {
>> unsigned version;
>> -
Lengthy output of sysrq-w may take a lot of time on slow serial console.
Currently we reset NMI-watchdog on the current CPU to avoid spurious
lockup messages. Sometimes this doesn't work since softlockup watchdog
might trigger on another CPU which is waiting for an IPI to proceed.
We reset
On Thu, 2016-05-19 at 09:16 +0200, Pavel Machek wrote:
> > In the original situation, without these patches, userspace has to
> > have a list of all LEDs that are supposed to indicate airplane
> > mode.
> Well, that's situation for many LEDs.
That doesn't make it a *good* situation though.
> >
On Thu, Jun 09, 2016 at 01:23:23PM +0200, Paolo Bonzini wrote:
> The version field in struct pvclock_vcpu_time_info basically implements
> a seqcount. Wrap it with the usual read_begin and read_retry functions,
> and use these APIs instead of peppering the code with smp_rmb()s.
> While at it,
Provide a small convenience wrapper that set/get the
display brightness value
Cc: John Stultz
Cc: Sumit Semwal
Cc: Archit Taneja
Cc: Rob Clark
Cc: Jani Nikula
The function early_init_dt_alloc_reserved_memory_arch is defined
in drivers/of/of_reserved_mem.c but is not declared in any of the
header files. Add the declaration of this to avoid the warning:
drivers/of/of_reserved_mem.c:31:19: warning: symbol
'early_init_dt_alloc_reserved_memory_arch' was
Hi Roger,
> From: Roger Quadros
> Sent: Wednesday, June 08, 2016 6:04 PM
>
> The OTG state machine needs a mechanism to start and
> stop the gadget controller as well as connect/disconnect
> from the bus. Add usb_gadget_start(), usb_gadget_stop()
> and usb_gadget_connect_control().
>
>
On 08/06/2016 10:17, Borislav Petkov wrote:
>> > - version = __pvclock_read_cycles(src, , );
>> > + version = src->version;
>> > + /* Make the latest version visible */
>> > + smp_rmb();
>> > +
>> > + flags = src->flags;
>> >/* Make sure
On Thursday 09 June 2016 13:27:21 Michał Kępień wrote:
> > > - case 0x10:
> > > - /* Keys pressed */
> > > + case 0x0010:
> > > + /* Sequence of keys pressed */
> > >
> > > for (i = 2; i < len; ++i)
> > >
> > > -
On Wed, 08 Jun 2016, Rob Herring wrote:
> On Wed, Jun 08, 2016 at 10:21:35AM +0100, Lee Jones wrote:
> > We're renaming the 'st,pwm-num-chan' binding to 'st,pwm-num-devs' to
> > be more inline with the naming conventions of the subsystem. Where
> > we used to treat each line as a channel, the
On Sat, May 28, 2016 at 08:27:43PM +0800, Minfei Huang wrote:
> +++ b/arch/x86/kernel/pvclock.c
> @@ -61,11 +61,14 @@ void pvclock_resume(void)
> u8 pvclock_read_flags(struct pvclock_vcpu_time_info *src)
> {
> unsigned version;
> - cycle_t ret;
> u8 flags;
>
> do {
> -
On Thu, Jun 9, 2016 at 5:21 AM, Viresh Kumar wrote:
> On 09-06-16, 01:45, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> There's no reason for gov_cancel_work() to exist at all, as it only
>> has one caller and the only thing done
On Wed 08-06-16 09:34:01, Dave Hansen wrote:
> On 06/08/2016 09:06 AM, Michal Hocko wrote:
> >> > Do we have any statistics that tell us how many pages are sitting the
> >> > lru pvecs? Although this helps the problem overall, don't we still have
> >> > a problem with memory being held in such an
On Wed, Jun 08, 2016 at 10:04:45PM -0700, Deepa Dinamani wrote:
> CURRENT_TIME_SEC is not y2038 safe. current_fs_time() will
> be transitioned to use 64 bit time along with vfs in a
> separate patch.
> There is no plan to transistion CURRENT_TIME_SEC to use
> y2038 safe time interfaces.
[...]
>
On 09/06/2016 13:28, Borislav Petkov wrote:
>> > technically, they should be virt_rmb() -- it really doesn't matter of
>> > course because reads are never reordered on x86.
> You mean
>
> version = src->version;
> flags = src->flags;
>
> are not reordered?
>
> I don't think so.
On Thu, Jun 09, 2016 at 02:26:59PM +0200, Paolo Bonzini wrote:
>
>
> On 09/06/2016 14:16, Peter Zijlstra wrote:
> > On Sat, May 28, 2016 at 08:27:43PM +0800, Minfei Huang wrote:
> >> +++ b/arch/x86/kernel/pvclock.c
> >> @@ -61,11 +61,14 @@ void pvclock_resume(void)
> >> u8
From: Daniel Wagner
Since the -Wincompatible-pointer-types is reported as error, alpha
doesn't build anymore. Let's fix it in a minimal way.
fs/binfmt_em86.c:73:35: error: passing argument 2 of ‘copy_strings_kernel’ from
incompatible pointer type
On Thu, Jun 9, 2016 at 12:29 PM, Mark Brown wrote:
> On Thu, Jun 09, 2016 at 11:44:18AM +0200, Krzysztof Kozlowski wrote:
>> Few drivers have a need of getting regulator supplies without knowing
>> their names:
>> 1. The Simple Framebuffer driver works on setup provided by
Hello.
On 6/9/2016 10:31 AM, Roger Quadros wrote:
The OTG core will use struct otg_hcd_ops to interface
with the HCD controller.
Host controller driver (HCD) controller? Maybe just HC? :-)
OK.
OTOH, my googling has shown that HCD may stand for both HC driver and HC
device... The
Hi,
Thanks for your contribution. Few comments below:
On Thu, Jun 2, 2016 at 8:44 AM, wrote:
> From: Chris Lapa
>
> This commit also adds requesting gpio's via devm_gpio_request() to ensure
> the gpio is available for usage by the driver.
>
>
On 06/09/2016 12:29 PM, Mark Brown wrote:
> On Thu, Jun 09, 2016 at 11:44:18AM +0200, Krzysztof Kozlowski wrote:
>> Few drivers have a need of getting regulator supplies without knowing
>> their names:
>> 1. The Simple Framebuffer driver works on setup provided by bootloader
>>(outside of
Hi,
this is the v4 version of the patchse. Previous version was posted
http://lkml.kernel.org/r/1464945404-30157-1-git-send-email-mho...@kernel.org
It's been mostly my screwups during the rebase that were fixed and
patch 10 reworked.
The following 10 patches should put some order to very rare
From: Michal Hocko
oom_score_adj is shared for the thread groups (via struct signal) but
this is not sufficient to cover processes sharing mm (CLONE_VM without
CLONE_SIGHAND) and so we can easily end up in a situation when some
processes update their oom_score_adj and confuse
From: Michal Hocko
0-day robot has encountered the following:
[ 82.694232] Out of memory: Kill process 3914 (trinity-c0) score 167 or
sacrifice child
[ 82.695110] Killed process 3914 (trinity-c0) total-vm:55864kB,
anon-rss:1512kB, file-rss:1088kB, shmem-rss:25616kB
[
From: Michal Hocko
task_will_free_mem is rather weak. It doesn't really tell whether
the task has chance to drop its mm. 98748bd72200 ("oom: consider
multi-threaded tasks in task_will_free_mem") made a first step
into making it more robust for multi-threaded applications so now
From: Michal Hocko
Oleg has pointed out that can simplify both oom_adj_{read,write}
and oom_score_adj_{read,write} even further and drop the sighand
lock. The main purpose of the lock was to protect p->signal from
going away but this will not happen since ea6d290ca34c ("signals:
> First patch describe problem about 0xe045 code. Second and third are just
> cosmetic and last rework code which processing WMI events. It should be
> properly tested on more Dell machines, to check that everything is still
> working correctly.
>
> Changes since v1:
> * Fixed comments
> * Fixed
This Replace all occurences of (1<
---
drivers/staging/comedi/drivers/dmm32at.c | 98
On Thu, Jun 09, 2016 at 02:16:03PM +0200, Peter Zijlstra wrote:
> What's wrong with:
>
> u8 flags = READ_ONCE(src->flags);
>
> ?
>
> (and have the flags store be done using WRITE_ONCE() of course).
>
> Sure, if your total state is larger than one word you need the
> seqcount for
On 6/9/2016 10:53 AM, Roger Quadros wrote:
It provides APIs for the following tasks
- Registering an OTG/dual-role capable controller
- Registering Host and Gadget controllers to OTG core
- Providing inputs to and kicking the OTG state machine
Provide a dual-role device (DRD) state machine.
Hi Seung-Woo,
On 06/08/2016 01:07 PM, Seung-Woo Kim wrote:
> This patch removes following UBSAN warnings in dw_mci_setup_bus().
> The warnings are caused because of shift with more than 31 on 32
> bit variable, so this patch fixes to shift only for less than 32.
>
> UBSAN: Undefined behaviour
TO Alex
TO Michael
In your solution you add a emulate PCI bridge to act as
a bridge between direct assigned devices and the host bridge.
Do you mean put all direct assigned devices to
one emulate PCI bridge?
If yes, this maybe bring some problems.
We are writing a patchset to
On Wed, Jun 08, 2016 at 11:50:35PM -0700, Tony Lindgren wrote:
> * Arnd Bergmann [160608 09:06]:
> > The downside would be any users that want the options we enable there
> > turned off and have them silently enabled when upgrading the kernel.
> I think the long term solution
On Wed, Jun 08, 2016 at 11:32:22AM +0800, Garlic Tseng wrote:
> On Tue, 2016-06-07 at 17:31 +0100, Mark Brown wrote:
> > > + SOC_DAPM_SINGLE_AUTODISABLE("Multi ch asrc out3", PWR2_TOP_CON, 7, 1,
> > > + 1),
> > > +};
> > On/off controls should end in Switch.
> Do you
I'm hitting 5 second timeout in rndis_filter_set_rss_param() while setting
RSS parameters for the device. When this happens we end up returning
-ETIMEDOUT from the function and rndis_filter_device_add() falls back to
setting
net_device->max_chn = 1;
net_device->num_chn = 1;
Hello Rob,
On 16-05-27 15:38:17, maitysancha...@gmail.com wrote:
> On 16-05-27 10:31:55, Arnd Bergmann wrote:
> > On Friday, May 27, 2016 12:03:01 PM CEST maitysancha...@gmail.com wrote:
> > >
> > > So if I understand correctly, the binding at the SoC level is fine.
> > > Keeping that but
Dne 9.6.2016 v 06:05 Stephen Rothwell napsal(a):
> On Wed, 8 Jun 2016 19:56:38 -0700 Kees Cook wrote:
>> Ah, yes, that should default to off. We'll get a fix landed ASAP.
>
> Note that this was an allmodconfig build. The default is 'n', but
> allmodconfig will turn it on
A parameter description for the interruptions of the
I2S controller was added.
Signed-off-by: Jose Abreu
Acked-by: Rob Herring
Cc: Carlos Palminha
Cc: Mark Brown
Cc: Liam Girdwood
Cc:
A PCM extension was added to I2S driver so that audio
samples are transferred using PIO mode.
The PCM supports two channels @ 16 or 32 bits with rates
32k, 44.1k and 48k.
Although the mainline I2S driver uses ALSA DMA engine the
I2S controller can be built without DMA support, therefore
this is
The code responsible for splitting periods into chunks that
can be handled by the DMA controller missed to update total_len,
the number of bytes processed in the current period, when there
are more chunks to follow.
Therefore total_len was stuck at 0 and the code didn't work at all.
This resulted
ARC AXS10x platforms consist of a mainboard with several peripherals.
One of those peripherals is an HDMI output port controlled by the ADV7511
transmitter.
This patch set adds I2S audio for the AXS10x platform.
NOTE:
Although the mainline I2S driver uses ALSA DMA engine, this controller
can be
The current cyclic DMA period splitting implementation can generate
very small chunks at the end of each period. For example a 65536 byte
period will be split into a 65532 byte chunk and a 4 byte chunk on
the "lite" DMA channels.
This increases pressure on the RAM controller as the DMA controller
On 09/06/16 11:43, Krzysztof Kozlowski wrote:
> On 06/09/2016 10:38 AM, Roger Quadros wrote:
>> Hi,
>>
>> On 08/06/16 16:48, Krzysztof Kozlowski wrote:
>>> Add VBUS pin detection support to extcon-usb-gpio driver for boards
>>> which have both VBUS and ID pins, or only one of them.
>>>
>>> The
> But...suppose we have two racing OPEN calls. They're both in
> nfs4_get_vfs_file. One opens the file and succeeds and the other fails
> and ends up in out_put_access. At that point, you could end up
> clobbering the successful update to st_access_bmap from the other task,
> and we'd end up not
On Wed 08-07-16 17:04:00, Michal Hocko wrote:
> I do not see how a SIGTERM would make any difference. But see below.
This is how we encounter this problem initially, by hitting ctr-c while
running parallel memory intensive workload, which ended up
not calling munmap on allocated memory.
> Is
On 09/06/16 07:51, Marek Szyprowski wrote:
> Hi
>
>
> On 2016-06-08 20:31, Matthew Leach wrote:
>> From: Ben Dooks
>>
>> Add initial support for big endian by always writing the pte
>> in le32. Note, revisit if hardware capable of doing big endian
>> fetches.
>>
>>
On Wed, Jun 08, 2016 at 10:45:34PM -0700, Greg Kroah-Hartman wrote:
> On Wed, Jun 08, 2016 at 04:07:59PM -0300, Gustavo Padovan wrote:
> > Hi Greg,
> >
> > Any comment on this?
>
> I am just starting to catch up on patches, please give me some time,
> staging patches are at the bottom of my
On 04/12/2016, 05:56 PM, Josh Poimboeuf wrote:
>> We had been using unwinder for over a decade in SUSE but it stopped
>> working for assembly recently (for obvious reasons). So having a working
>> and reliable unwinder again is one of the top priorities for us.
>
> Since you already have an
Chunyan Zhang writes:
> On Tue, Jun 7, 2016 at 6:04 PM, Alexander Shishkin
> wrote:
>> Chunyan Zhang writes:
>>
>>> This patch is introducing a new function to print Ftrace messages
>>> to STM buffer when
On 08/06/16 20:31, Jon Mason wrote:
On Wed, Jun 08, 2016 at 09:34:06AM +0100, Sudeep Holla wrote:
On 07/06/16 22:08, Jon Mason wrote:
Query the CPU core clock in the device tree to determine the core clock
speed.
How do guarantee that it's the current frequency of the CPU ?
I am basing
Hi Corey,
I wanted to send a global rev-by, but it looks like some changes in this
series are required from my point of view, so I'll just send individual
rev-by and change requests as my review progresses.
On May 29 2016 or thereabouts, Corey Minyard wrote:
> From: Corey Minyard
1 - 100 of 1970 matches
Mail list logo