Hi Kamal et al,
On Thu, Mar 31, 2016 at 10:13 PM, Kamal Mostafa wrote:
> 4.2.8-ckt7 -stable review patch. If anyone has any objections, please let me
> know.
>
> ---8<
>
> From: Geert Uytterhoeven
>
> commit b26a719bdba9aa926ceaadecc6
Some ehci compatible controllers have more than one reset signal lines,
e.g., Synopsys DWC USB2.0 Host-AHB Controller has two resets hreset_i_n
and phy_rst_i_n. Two more resets are added in this patch in order for
this kind of controller to use this driver directly.
Signed-off-by: Jiancheng Xue
-
On (05/03/16 14:03), Minchan Kim wrote:
> > will io_stat node work for you?
>
> Firstly, I thought io_stat would be better. However, on second thought,
> I want to withdraw.
>
> I think io_stat should go away.
>
> failed_read
> failed_write
> invalid_io
>
> I think Above
On Fri, Apr 29, 2016 at 10:09:07PM +0200, Julia Lawall wrote:
> Dma_pool_zalloc combines dma_pool_alloc and memset 0. The semantic patch
> that makes this transformation is as follows: (http://coccinelle.lip6.fr/)
Applied all dmaengine patches
--
~Vinod
On Tue, 03 May 2016 06:52:02 +0200
Greg Kurz wrote:
> The KVM_MAX_VCPUS define provides the maximum number of vCPUs per guest, and
> also the upper limit for vCPU ids. This is okay for all archs except PowerPC
> which can have higher ids, depending on the cpu/core/thread topology. In the
> worst
Perhaps what you should to be arguing then that the default
permissions of the cgroup directories need to be all rwx for
everyone and then your patch becomes unnecessary?
I don't think that would be the nicest way of dealing with this (then
a process can make very large numbers of cgroups all ov
* Dave Hansen wrote:
>
> From: Dave Hansen
>
> Big core processors (Xeon/Core) are affected by an MPX erratum.
> This erratum can only be triggered when a system is not using
> Supervisor Mode Execution Prevention (SMEP). To work around
> this, we ensure that MPX can only be used in cases wh
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in:
drivers/staging/lustre/lustre/llite/rw26.c
between commit:
c8b8e32d700f ("direct-io: eliminate the offset argument to ->direct_IO")
from the vfs tree and commit:
8c7b0e1a6747 ("staging/lustre/llite: rename ccc_obje
On Mon, May 02, 2016 at 12:28:02PM +, Appana Durga Kedareswara Rao wrote:
> Hi,
>
> > -Original Message-
> > From: dmaengine-ow...@vger.kernel.org [mailto:dmaengine-
> > ow...@vger.kernel.org] On Behalf Of Pramod Gurav
> > Sent: Monday, May 02, 2016 5:48 PM
> > To: vinod.k...@intel.com
On Monday 02 May 2016 16:32:25 Andrew Morton wrote:
> On Tue, 03 May 2016 01:10:16 +0200 Arnd Bergmann wrote:
>
> > On Monday 02 May 2016 16:02:18 Andrew Morton wrote:
> > > On Mon, 02 May 2016 23:48:19 +0200 Arnd Bergmann wrote:
> > >
> > > > This is another attempt to avoid a regression in ww
On 01/27/2016, 07:12 PM, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Michael Neuling
>
> commit 7f821fc9c77a9b01fe7b1d6e72717b33d8d64142 upstream.
>
> Currently we can hit a scenario where we'll tm_rec
在 2016年04月28日 05:52, Eduardo Valentin 写道:
On Mon, Apr 25, 2016 at 11:02:45AM +0800, Caesar Wang wrote:
From: Sascha Hauer
Signed-off-by: Sascha Hauer
Signed-off-by: Caesar Wang
Cc: Zhang Rui
Cc: Eduardo Valentin
Cc: linux...@vger.kernel.org
---
drivers/thermal/of-thermal.c | 12 ++
In "make menuconfig", reset drivers are currently lined up together
with the reset sub-system menu, like this:
-*- Reset Controller Support
< > Hi6220 Reset Driver
(It also means, the menu "Reset Controller Support" is always empty.)
"Hi6220 Reset Driver" should go into the sub-men
On 05/03/2016 10:55 AM, Michael Neuling wrote:
>
>> diff --git a/arch/powerpc/include/asm/cputable.h
>> b/arch/powerpc/include/asm/cputable.h
>> index df4fb5f..a4739a1 100644
>> --- a/arch/powerpc/include/asm/cputable.h
>> +++ b/arch/powerpc/include/asm/cputable.h
>> @@ -205,6 +205,7 @@ enum {
On Fri, 29 Apr 2016 18:55:22 Alexey Kardashevskiy wrote:
> The upcoming NVLink passthrough support will require NPU code to cope
> with two DMA windows.
>
> This adds a pnv_npu_set_window() helper which programs 32bit window to
> the hardware. This also adds multilevel TCE support.
>
> This adds
> From: Yongji Xie [mailto:xyj...@linux.vnet.ibm.com]
> Sent: Tuesday, May 03, 2016 2:08 PM
>
> On 2016/5/3 13:34, Tian, Kevin wrote:
>
> >> From: Yongji Xie
> >> Sent: Wednesday, April 27, 2016 8:43 PM
> >>
> >> This patch enables mmapping MSI-X tables if hardware supports
> >> interrupt remappi
On Tue, May 03, 2016 at 02:57:15PM +0900, Sergey Senozhatsky wrote:
> On (05/03/16 14:40), Minchan Kim wrote:
> [..]
> > > At least, we need sanity check code, still?
> > > Otherwise, user can echo "garbage" > /sys/xxx/max_comp_stream" and then
> > > cat /sys/xxx/max_comp_stream returns num_online_
在 2016年04月28日 05:48, Eduardo Valentin 写道:
A couple of comments as follows,
On Mon, Apr 25, 2016 at 11:02:44AM +0800, Caesar Wang wrote:
From: Sascha Hauer
This adds support for hardware-tracked trip points to the device tree
thermal sensor framework.
The framework supports an arbitrary num
> From: Yongji Xie [mailto:xyj...@linux.vnet.ibm.com]
> Sent: Tuesday, May 03, 2016 1:52 PM
>
> >> +
> >> + if (!(res->start & ~PAGE_MASK)) {
> >> + /*
> >> + * Add shadow resource for sub-page bar whose mmio
> >> + * page is exclusive
On 2016/5/3 13:34, Tian, Kevin wrote:
From: Yongji Xie
Sent: Wednesday, April 27, 2016 8:43 PM
This patch enables mmapping MSI-X tables if hardware supports
interrupt remapping which can ensure that a given pci device
can only shoot the MSIs assigned for it.
With MSI-X table mmapped, we also n
"Serge E. Hallyn" writes:
> Quoting Andrew G. Morgan (mor...@kernel.org):
>>
>> I guess I'm confused how we have strayed so far that this isn't an obvious
>> requirement. Uid=0 as being the root of privilege was the basic problem
>> that capabilities were designed to change.
>
> The task executi
On 2016/5/3 10:59, Tian, Kevin wrote:
From: Yongji Xie
Sent: Wednesday, April 27, 2016 8:22 PM
Current vfio-pci implementation disallows to mmap
sub-page(size < PAGE_SIZE) MMIO BARs because these BARs' mmio
page may be shared with other BARs. This will cause some
performance issues when we pass
On Tue, 3 May 2016 15:46:33 Alistair Popple wrote:
> There's one call to pr_warn() in pnv_npu_disable_bypass() that could
arguably
> be converted to pe_warn(), but we can clean that up later as the patch looks
> fine and I'm assuming subsequent patches make use of these.
And inevitably the next
On (05/03/16 14:40), Minchan Kim wrote:
[..]
> > At least, we need sanity check code, still?
> > Otherwise, user can echo "garbage" > /sys/xxx/max_comp_stream" and then
> > cat /sys/xxx/max_comp_stream returns num_online_cpus.
>
> One more thing,
>
> User:
> echo 4 > /sys/xxx/max_comp_stream"
> c
Addiing DT binding doc for the extcon gpios properties.
Signed-off-by: Venkat Reddy Talla
---
.../devicetree/bindings/extcon/extcon-gpio.txt| 19 +++
1 file changed, 19 insertions(+)
create mode 100644 Documentation/devicetree/bindings/extcon/extcon-gpio.txt
diff --git
Hi,
This patch series should have no perceivable changes to load
and util except that load's range is increased by 1024.
My initial tests suggest that. See attached figures. The workload
is running 100us out of every 200us, and 2000us out of every 8000us.
Again fixed workload, fixed CPU, and fixe
Adding device tree support for extcon-gpio driver.
Signed-off-by: Venkat Reddy Talla
---
drivers/extcon/extcon-gpio.c | 80 +++---
include/linux/extcon/extcon-gpio.h | 2 +
2 files changed, 76 insertions(+), 6 deletions(-)
diff --git a/drivers/extcon/extco
There's one call to pr_warn() in pnv_npu_disable_bypass() that could arguably
be converted to pe_warn(), but we can clean that up later as the patch looks
fine and I'm assuming subsequent patches make use of these.
Reviewed-By: Alistair Popple
On Fri, 29 Apr 2016 18:55:21 Alexey Kardashevskiy
On (05/03/16 14:23), Minchan Kim wrote:
[..]
> > - zram->max_comp_streams = num;
> > - ret = len;
> > -out:
> > - up_write(&zram->init_lock);
> > - return ret;
>
> At least, we need sanity check code, still?
> Otherwise, user can echo "garbage" > /sys/xxx/max_comp_stream" and then
> cat /s
On Mon, Feb 15, 2016 at 3:58 PM, Enric Balletbo i Serra
wrote:
> From: Olof Johansson
>
> Accidentally specified a smaller record size, bring it back
> to the same size as we had when we used the config file.
>
> Signed-off-by: Olof Johansson
> Signed-off-by: Enric Balletbo i Serra
> Reviewed-b
On Tue, May 03, 2016 at 02:23:24PM +0900, Minchan Kim wrote:
> On Mon, May 02, 2016 at 05:06:00PM +0900, Sergey Senozhatsky wrote:
> > On (05/02/16 16:25), Sergey Senozhatsky wrote:
> > [..]
> > > > Trivial:
> > > > We could remove max_strm now and change description.
> > >
> > > oh, yes.
> >
> >
__update_sched_avg() has these steps:
1. add the left of the last incomplete period
2. decay old sum
3. accumulate new sum since last_update_time
4. add the current incomplete period
5. update averages
Previously, we separately computed steps 1, 3, and 4, leading to
each one of them ugly in codes
After cleaning up the sched metrics, these two definitions that cause
ambiguity are not needed any more. Use NICE_0_LOAD_SHIFT and NICE_0_LOAD
instead (the names suggest clearly who they are).
Suggested-by: Ben Segall
Signed-off-by: Yuyang Du
---
kernel/sched/fair.c |4 ++--
kernel/sched/s
Hi Enric,
On Mon, Feb 15, 2016 at 3:58 PM, Enric Balletbo i Serra
wrote:
> From: Gene Chen
>
> Add support for Leon touch devices, which is the same as
> slippy/falco/peppy/wolf on the same buses using the LynxPoint-LP I2C via
> the i2c-designware-pci driver.
>
> Based on the following patch:
>
The increased scale or precision for kernel load has been disabled
since the commit e4c2fb0d5776 ("sched: Disable (revert) SCHED_LOAD_SCALE
increase"). But we do need it when we have task groups, especially on
bigger machines. Otherwise, we probably will run out of precision for
load distribution.
Everybody has it. If code-size is not the problem, __accumulate_sum()
should have it too.
Signed-off-by: Yuyang Du
---
kernel/sched/fair.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 17bc721..1655280 100644
--- a/kernel/s
These sched metrics have become complex enough. We introduce them
at their definitions.
Signed-off-by: Yuyang Du
---
include/linux/sched.h | 60 -
1 file changed, 49 insertions(+), 11 deletions(-)
diff --git a/include/linux/sched.h b/include/lin
Currently, load_avg = scale_load_down(load) * runnable%. The extra scaling
down of load does not make much sense, because load_avg is primarily THE
load and on top of that, we take runnable time into account.
We therefore remove scale_load_down() for load_avg. But we need to
carefully consider the
Rename scale_load() and scale_load_down() to user_to_kernel_load()
and kernel_to_user_load() respectively. This helps us tag them
clearly and avoid confusion.
[update calculate_imbalance]
Signed-off-by: Vincent Guittot
Signed-off-by: Yuyang Du
---
kernel/sched/core.c |8
kernel/sc
Integer metric needs fixed point arithmetic. In sched/fair, a few
metrics, including weight, load, load_avg, util_avg, freq, and capacity,
may have different fixed point ranges.
In order to avoid errors relating to the fixed point range of these
metrics, we definie a basic fixed point range, and t
This doc file has the programs to generate the constants to compute
sched averages.
Signed-off-by: Yuyang Du
---
Documentation/scheduler/sched-avg.txt | 137 +
1 file changed, 137 insertions(+)
create mode 100644 Documentation/scheduler/sched-avg.txt
diff --git
__compute_runnable_contrib() uses a loop to compute sum, whereas a
table lookup can do it faster in a constant time.
The program to generate the constants is located at:
Documentation/scheduler/sched-avg.txt
Signed-off-by: Yuyang Du
Reviewed-by: Morten Rasmussen
Acked-by: Vincent Guittot
Signe
From: Roman Pen
This patch has been added to the 3.12 stable tree. If you have any
objections, please let us know.
===
commit 346c09f80459a3ad97df1816d6d606169a51001a upstream.
The bug in a workqueue leads to a stalled IO request in MQ ctx->rq_list
with the following backtrace:
[
In sched average update, a period is about 1ms, so a 32-bit unsigned
integer can approximately hold a maximum of 49 (=2^32/1000/3600/24)
days, which means it is big enough and 64-bit is needless.
Signed-off-by: Yuyang Du
---
kernel/sched/fair.c | 27 +--
1 file changed,
Hi Peter,
This patch series combines the previous cleanup and optimization
series. And as you and Ingo suggested, the increased kernel load
scale is reinstated when on 64BIT and FAIR_GROUP_SCHED. In addition
to that, the changes include Vincent's fix, typos fixes, changelog
and comment reword.
Th
The names of sched averages (including load_avg and util_avg) have
been changed and added in the past a couple of years, some of
the names are a bit confusing especially to people who first read them.
This patch attempts to make the names more self-explaining. And some
comments are updated too.
Si
> From: Yongji Xie
> Sent: Wednesday, April 27, 2016 8:43 PM
>
> This patch enables mmapping MSI-X tables if hardware supports
> interrupt remapping which can ensure that a given pci device
> can only shoot the MSIs assigned for it.
>
> With MSI-X table mmapped, we also need to expose the
> read/
> diff --git a/arch/powerpc/include/asm/cputable.h
> b/arch/powerpc/include/asm/cputable.h
> index df4fb5f..a4739a1 100644
> --- a/arch/powerpc/include/asm/cputable.h
> +++ b/arch/powerpc/include/asm/cputable.h
> @@ -205,6 +205,7 @@ enum {
> #define CPU_FTR_DABRX
> LONG_A
From: Joonsoo Kim
split_page() calls set_page_owner() to set up page_owner to each pages.
But, it has a drawback that head page and the others have different
stacktrace because callsite of set_page_owner() is slightly differnt.
To avoid this problem, this patch copies head page's page_owner to
th
From: Joonsoo Kim
Currently, we store each page's allocation stacktrace on corresponding
page_ext structure and it requires a lot of memory. This causes the problem
that memory tight system doesn't work well if page_owner is enabled.
Moreover, even with this large memory consumption, we cannot ge
On Mon, May 02, 2016 at 05:06:00PM +0900, Sergey Senozhatsky wrote:
> On (05/02/16 16:25), Sergey Senozhatsky wrote:
> [..]
> > > Trivial:
> > > We could remove max_strm now and change description.
> >
> > oh, yes.
>
> how about something like this? remove max_comp_streams entirely, but
> leave t
From: Joonsoo Kim
It's not necessary to initialized page_owner with holding the zone lock.
It would cause more contention on the zone lock although it's not
a big problem since it is just debug feature. But, it is better
than before so do it. This is also preparation step to use stackdepot
in pag
From: Joonsoo Kim
Currently, copy_page_owner() doesn't copy all the owner information.
It skips last_migrate_reason because copy_page_owner() is used for
migration and it will be properly set soon. But, following patch
will use copy_page_owner() and this skip will cause the problem that
allocated
From: Joonsoo Kim
Page owner will be changed to store more deep stacktrace
so current temporary buffer size isn't enough. Increase it.
Signed-off-by: Joonsoo Kim
---
tools/vm/page_owner_sort.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/tools/vm/page_owner_sort
From: Joonsoo Kim
We don't need to split freepages with holding the zone lock. It will cause
more contention on zone lock so not desirable.
Signed-off-by: Joonsoo Kim
---
include/linux/mm.h | 1 -
mm/compaction.c| 42 ++
mm/page_alloc.c| 27
From: Joonsoo Kim
This patchset changes a way to store stacktrace in page_owner in order to
reduce memory usage. Below is motivation of this patchset coped
from the patch 6.
Currently, we store each page's allocation stacktrace on corresponding
page_ext structure and it requires a lot of memory.
Quoting Andrew G. Morgan (mor...@kernel.org):
> On 2 May 2016 6:04 p.m., "Eric W. Biederman" wrote:
> >
> > "Serge E. Hallyn" writes:
> >
> > > On Tue, Apr 26, 2016 at 03:39:54PM -0700, Kees Cook wrote:
> > >> On Tue, Apr 26, 2016 at 3:26 PM, Serge E. Hallyn
> wrote:
> > >> > Quoting Kees Cook (
From: Joonsoo Kim
Recently, we allow to save the stacktrace whose hashed value is 0.
It causes the problem that stackdepot could return 0 even if in success.
User of stackdepot cannot distinguish whether it is success or not so we
need to solve this problem. In this patch, 1 bit are added to hand
Currently, in an ACPI based system, the processor driver registers
one cooling device per processor. However, the cooling device type
is the same for each processor. For example, on a system with four
processors, the sysfs reading of each cooling device would look like:
ebv@besouro ~ $ cat /sys/cla
On Tue, May 03, 2016 at 01:29:02PM +0900, Sergey Senozhatsky wrote:
> On (05/03/16 11:30), Sergey Senozhatsky wrote:
> > > We are concerning about returing back to no per-cpu options but actually,
> > > I don't want. If duplicate compression is really problem(But It's really
> > > unlikely), we sho
"Andrew G. Morgan" writes:
> On 2 May 2016 6:04 p.m., "Eric W. Biederman"
> wrote:
>>
>> "Serge E. Hallyn" writes:
>>
>> > On Tue, Apr 26, 2016 at 03:39:54PM -0700, Kees Cook wrote:
>> >> On Tue, Apr 26, 2016 at 3:26 PM, Serge E. Hallyn
> wrote:
>> >> > Quoting Kees Cook (keesc...@chromium.org
In testing with HiKey, we found that since commit 3f30b158eba5c60
(asix: On RX avoid creating bad Ethernet frames), we're seeing lots of
noise during network transfers:
[ 239.027993] asix 1-1.1:1.0 eth0: asix_rx_fixup() Data Header
synchronisation was lost, remaining 988
[ 239.037310] asix 1-1.1
The KVM_MAX_VCPUS define provides the maximum number of vCPUs per guest, and
also the upper limit for vCPU ids. This is okay for all archs except PowerPC
which can have higher ids, depending on the cpu/core/thread topology. In the
worst case (single threaded guest, host with 8 threads per core), it
From: Wanpeng Li
max_idle_balance_cost and avg_idle which used to capture short idle
are not associated with schedstats, however, the information of these
two factors are't printed out if w/o CONFIG_SCHEDSTATS.
This patch fix it by moving max_idle_balance_cost and avg_idle print
out of CONFIG
On (05/03/16 11:30), Sergey Senozhatsky wrote:
> > We are concerning about returing back to no per-cpu options but actually,
> > I don't want. If duplicate compression is really problem(But It's really
> > unlikely), we should try to solve the problem itself with different way
> > rather than roll-
Hi Jens,
Today's linux-next merge of the block tree got a conflict in:
drivers/nvme/host/pci.c
between commit:
9bf2b972afea ("NVMe: Fix reset/remove race")
from Linus' tree and commit:
bb8d261e0888 ("nvme: introduce a controller state machine")
from the block tree.
I fixed it up (I th
On Monday 02 May 2016 10:42 PM, J.D. Schroeder wrote:
> This series of patches fixes several discrepancies between the
> AM57/DRA7 clock tree description and the actual hardware behavior and
> frequencies. With these changes a more complete picture of the clock
> tree is represented for a few of
Salutations
http://kaminoexpress.com/jet.php?garden=1pbbqhgcy4f346prg
cputrdoc
Hi John,
On 4/30/2016 15:00, John Keeping Wrote:
Hi Enric,
On Fri, Apr 29, 2016 at 04:59:27PM +0200, Enric Balletbo Serra wrote:
2015-12-09 11:32 GMT+01:00 John Keeping :
If we only clear the tx/rx state when both are disabled it is not
possible to start/stop one multiple times while the othe
On Thu, 2016-04-28 at 00:34 +0200, Arnd Bergmann wrote:
> The rtc-generic driver provides an architecture specific
> wrapper on top of the generic rtc_class_ops abstraction,
> and powerpc has another abstraction on top, which is a bit
> silly.
>
> This changes the powerpc rtc-generic device to pr
On Fri, 29 Apr 2016, Nicolas Morey Chaisemartin wrote:
> Hi everyone,
>
> This is a repost from a different address as it seems the previous one ended
> in Gmail junk due to a domain error..
linux-kernel is a very high volume list which few are reading:
that also will account for your lack of r
On Mon, May 02, 2016 at 12:20:08PM +0200, Thomas Renninger wrote:
> On Sunday, May 01, 2016 01:11:33 PM Sean Fu wrote:
> > Hi guys:
> > I encountered a build error when running "make V=1 tools/all".
> > Shall we write a patch to fix it?
>
> This is not a bug.
>
> > The fol
Dear purchasing manager,
We have rich experience in manufacturing and exporting all kinds of bags, We
have our own production base with advanced machine equipment, and employ
professional workforce of technicians and engineers.
Our products range from tote bags, drawstring bags, luggage bags,
On Tue, May 3, 2016 at 9:00 AM, Baolin Wang wrote:
> Integrate with the newly added USB charger interface to limit the current
> we draw from the USB input based on the input device configuration
> identified by the USB stack, allowing us to charge more quickly from high
> current inputs without d
On Tue, May 3, 2016 at 5:45 AM, Greg KH wrote:
> On Mon, May 02, 2016 at 08:58:34AM +0530, Pranay Srivastava wrote:
>> Hi,
>>
>> Can the following patch be reviewed? I'm working on some more changes
>> on top of this change,
>> so it'll be really helpful if someone can review this patch and let me
Linux-pm,
As a continuation of the work done in 2015, I am proposing this year a
micro conference (MC) to gather thermal interested parties to discuss
improvements to the thermal subsystem [1]. Last year, I believe it was a
success in terms of achieving the goal of creating awareness, however, I
b
On Fri, Apr 29, 2016 at 9:36 PM, Rus wrote:
> Hi,
>
> After switching from 3.x to 4.x I'm observing strange filesystem (ext4
> used) slowdown just after fresh boot - it is 100% reproducible. The
> simple test just after boot at root fs first shows the good
> performance :
>
> dd if=/dev/zero of=/o
From: Wanpeng Li
Guest should only trust data to be valid when version haven't changed
before and after reads of steal time. Besides not changing, it has to
be an even number. Hypervisor may write an odd number to version field
to indicate that an update is in progress.
kvm_steal_clock() in g
在 4/29/2016 5:22 PM, Linus Walleij 写道:
> On Thu, Apr 28, 2016 at 11:32 AM, Jiang Qiu wrote:
>
>> This patch removed the name property from dwapb_port_property.
>> The name property is redundant, since we can get this info
>> from dwapb_gpio dev node.
>>
>> Reviewed-by: Andy Shevchenko
>> Signed-
Hi,
On Thu, Apr 28, 2016 at 3:19 PM, Olliver Schinagl wrote:
> There are 3 kinds of OLinuXino Lime2 boards.
> One without any on board storage, one with NAND storage and one with
> eMMC storage. This patch adds the eMMC variant of boards.
>
> eMMC storage is different from a regular SD card in th
On 05/02/16 at 10:39P, John Stultz wrote:
> On Mon, Apr 25, 2016 at 2:20 AM, Minfei Huang wrote:
> > It is unnecessary to continue looping the list, if we find there is an
> > entry that the value of rating is smaller than the new one. It is safe
> > to be out the loop, because all of entry are in
Integrate with the newly added USB charger interface to limit the current
we draw from the USB input based on the input device configuration
identified by the USB stack, allowing us to charge more quickly from high
current inputs without drawing more current than specified from others.
Signed-off-
For supporting the usb charger, it adds the usb_charger_init() and
usb_charger_exit() functions for usb charger initialization and exit.
It will report to the usb charger when the gadget state is changed,
then the usb charger can do the power things.
Signed-off-by: Baolin Wang
---
drivers/usb/g
This patch introduces the usb charger driver based on usb gadget that
makes an enhancement to a power driver. It works well in practice but
that requires a system with suitable hardware.
The basic conception of the usb charger is that, when one usb charger
is added or removed by reporting from the
When the usb gadget supporting for usb charger is ready, the usb charger
can implement the usb_charger_plug_by_gadget() function and usb_charger_exit()
function by getting 'struct usb_charger' from 'struct gadget'.
Signed-off-by: Baolin Wang
---
drivers/usb/gadget/udc/charger.c | 39 ++
Currently the Linux kernel does not provide any standard integration of this
feature that integrates the USB subsystem with the system power regulation
provided by PMICs meaning that either vendors must add this in their kernels
or USB gadget devices based on Linux (such as mobile phones) may not b
Hi Rob,
Today's linux-next merge of the drm-msm tree got a conflict in:
drivers/gpu/drm/msm/msm_atomic.c
between commit:
a3ccfb9feb46 ("drm/msm: Rename async to nonblock.")
from the drm-misc tree and commit:
afadc4bb9380 ("drm/msm: remove fence_cbs")
from the drm-msm tree.
I fixed it
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/i915/intel_display.c
between commits:
f7e5838bb37d ("drm/i915: Simplify reset_counter handling during atomic
modesetting")
from the drm-intel tree and commit:
81072bfd13f2 ("drm/i915: Rename async
>
> I think we we will just remove the name arg from the ioctl there.
> SW_SYNC ioctl is only for debugging test, we don't want to publicly
> export its ABI in the kernel uapi headers.
>
JFYI, be mindful please of removing the arg. If current uses are
broken, the mainline maintainer, MM, can be s
From: "Du, Changbin"
On most platforms, there is only one device controller available.
In this case, we desn't care the UDC's name. So let's ignore the
name by setting 'UDC' to 'any'. And also we can change UDC name
at any time if it is not binded (no need set to "" first).
Signed-off-by: Du, Ch
From: "Du, Changbin"
When I am configuring Gadget Configfs, I need found a exactly UDC name before
I can start my gadget. But, really I doesn't care about which UDC name is used,
because I have only controller. "any" is a good option.
Du, Changbin (2):
usb: configfs: allow UDC binding rule con
From: "Du, Changbin"
Add the usage of new binding mode 'any'.
$ echo any > UDC
Signed-off-by: Du, Changbin
Signed-off-by: Du, Changbin
---
Documentation/usb/gadget_configfs.txt | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/usb/gadget_configfs.txt
b/D
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
net/ipv4/ip_gre.c
between commits:
2090714e1d6e ("gre: build header correctly for collect metadata tunnels")
b7f8fe251e46 ("gre: do not pull header in ICMP error processing")
from Linus' tree and commit:
95f5c64c
On Mon, May 2, 2016 at 6:59 PM, George Spelvin wrote:
>
> AFAICT, none of the string-hash functions outside of fs/ are
> on particularly hot paths. The goal is deleting redundant code.
Yes, agreed.
>> We'll never get rid of "hash_name()", it not only has that '/' case,
>> it's also inlined for
> From: Yongji Xie
> Sent: Wednesday, April 27, 2016 8:22 PM
>
> Current vfio-pci implementation disallows to mmap
> sub-page(size < PAGE_SIZE) MMIO BARs because these BARs' mmio
> page may be shared with other BARs. This will cause some
> performance issues when we passthrough a PCI device with
>
On 04/28/2016 02:19 PM, Jason Wang wrote:
> On 04/27/2016 07:28 PM, Michael S. Tsirkin wrote:
>> > On Tue, Apr 26, 2016 at 03:35:53AM -0400, Jason Wang wrote:
>>> >> We don't stop polling socket during rx processing, this will lead
>>> >> unnecessary wakeups from under layer net devices (E.g
>>>
On Tue, May 03, 2016 at 01:26:46AM +, Rudoff, Andy wrote:
>
> >> The takeaway is that msync() is 9-10x slower than userspace cache
> >> management.
> >
> >An alternative viewpoint: that flushing clean cachelines is
> >extremely expensive on Intel CPUs. ;)
> >
> >i.e. Same numbers, different a
On Mon, 2 May 2016 22:14:14 +0800
Chunyu Hu wrote:
> Currently register function of the event will be called
> through the 'reg' field of event class directly without
> any check when seting up triggers.
>
> Triggers for events that don't support register through
> debug fs (events under event
Hi Marek
On 2 May 2016 at 11:57, Marek Szyprowski wrote:
> Hi Anand
>
>
> On 2016-04-30 08:06, Anand Moon wrote:
>>
>> Hi All,
>>
>> Using microSD card when I try to write into /dev/watchdog device
>> it triggers reboot of the board after timer expires.
>>
>> -
在 2016年04月28日 23:04, Eduardo Valentin 写道:
On Thu, Apr 28, 2016 at 09:50:29AM +0800, Caesar Wang wrote:
在 2016年04月28日 07:48, Eduardo Valentin 写道:
On Mon, Apr 18, 2016 at 11:35:56AM +0800, Caesar Wang wrote:
+ regmap_write(grf, GRF_TSADC_TESTBIT_L, GRF_TSADC_TSEN_PD_ON);
+
1 - 100 of 1103 matches
Mail list logo
