Hi all.
Here is the third version of a patch set that adds some debugging facility for
CMA.
This patch set is based on v4.0-rc1 and Sasha Levin's patch set
"mm: cma: debugfs access to CMA" v5 [1].
It is also available on git:
git://github.com/stefanstrogin/linux -b cmainfo-v3
We want an interfac
Add trace events for cma_alloc() and cma_release().
Signed-off-by: Stefan Strogin
---
include/trace/events/cma.h | 57 ++
mm/cma.c | 6 +
2 files changed, 63 insertions(+)
create mode 100644 include/trace/events/cma.h
diff --gi
On Tue, 24 Feb 2015 13:39:46 -0500
Steven Rostedt wrote:
> +static void tell_cpu_to_push(int cpu, struct rq *rq, int prio)
> +{
> + /* We should never be here if the IPI is already out. */
> + BUG_ON(rq->rt.push_csd_pending);
> +
> + rq->rt.push_csd_pending = 1;
> + rq->rt.push_
It's more useful to print address and number of pages which are being released,
not only address.
Signed-off-by: Stefan Strogin
---
mm/cma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/cma.c b/mm/cma.c
index 3a63c96..111bf62 100644
--- a/mm/cma.c
+++ b/mm/cma.c
@@ -434
From: Dmitry Safonov
Here are two functions that provide interface to compute/get used size
and size of biggest free chunk in cma region. Add that information to debugfs.
Signed-off-by: Dmitry Safonov
Signed-off-by: Stefan Strogin
---
include/linux/cma.h | 2 ++
mm/cma.c| 30
When CONFIG_CMA_BUFFER_LIST is configured a file is added to debugfs:
/sys/kernel/debug/cma/cma-/buffers contains a list of currently allocated
CMA buffers for each CMA region (N stands for number of CMA region).
Format is:
- ( kB), allocated by ()
When CONFIG_CMA_ALLOC_STACKTRACE is configure
> If that is the case, the tolerance level might be the better approach
> after all...
We should also take a look at mce_start():
int cpus = num_online_cpus();
...
/*
* Wait for everyone.
*/
while (atomic_read(&mce_callin) != cpus) {
since offl
Hi Masami,
I'm adding thread refcounting in perf, and in this process I am
investigating a problem, so thought about using perf itself to match
thread__get with thread__put:
[root@ssdandy ~]# perf probe -x ~/bin/perf -V thread__put
Available variables at thread__put
@
PER_CPU(old_rsp) usage is simplified - now it is used only
as temp storage, and userspace stack pointer is immediately stored
in pt_regs->sp on syscall entry, instead of being used later,
on syscall exit. This allows to get rid of thread_struct::usersp.
The lazy store of pt_regs->cs and pt_regs->s
PER_CPU_VAR(kernel_stack) was set up in a way where it points
five stack slots below the top of stack.
Presumably, it was done to avoid one "sub $5*8,%rsp"
in syscall/sysenter code paths, where iret frame needs to be
created by hand.
Ironically, none of them benefit from this optimization,
since
On Tue, Feb 24, 2015 at 01:56:54PM +0900, Chanwoo Choi wrote:
> This patch fixes the wrong control of PD_DET_EN (power down detection mode)
> for Exynos7 because exynos7_tmu_control() always enables the power down
> detection
> mode regardless 'on' parameter.
>
> Cc: Zhang Rui
> Cc: Eduardo Vale
Replace printk KERN_DEBUG with pr_debug in dprintk macro
defined in au0828.h
Signed-off-by: Shuah Khan
---
drivers/media/usb/au0828/au0828.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/usb/au0828/au0828.h
b/drivers/media/usb/au0828/au0828.h
index eb15187..e
In all three 32-bit entry points, %eax is zero-extended to %rax.
It is safe to do 32-bit compare when checking that syscall#
is not too large.
The last instance of "mysterious" SS+8 constant is replaced by SIZEOF_PTREGS.
The $AUDIT_ARCH_X86_64 parameter to syscall_trace_enter_phase1/2
is a 32-bit
Before this patch, rcx and r11 were saved in pt_regs->rcx
and pt_regs->r11. Which looks natural, but requires messy
shuffling to/from iret stack whenever ptrace or e.g. iopl
wants to modify return address or flags - because that's
how these registers are used by SYSCALL/SYSRET.
This patch saves rc
Replace printk macro in dprintk macros in em28xx audio, dvb,
and input files with pr_* equivalent routines.
Signed-off-by: Shuah Khan
---
drivers/media/usb/em28xx/em28xx-audio.c | 3 +--
drivers/media/usb/em28xx/em28xx-dvb.c | 2 +-
drivers/media/usb/em28xx/em28xx-input.c | 2 +-
3 files chang
On Tue, Feb 24, 2015 at 06:09:17PM +, Sudeep Holla wrote:
> Sorry for the trouble and thanks for giving it a try. OK I will try to
> find one, but it may be difficult to grab one.
Well, either that or I can take a look as I have the box here but it
won't happen immediately as I'm swamped.
--
Imre Deak writes:
> The poweroff handlers undo the actions of the thaw handlers. As the
> original commit stated saving the registers is not needed there, but
> it's also not a big overhead and there should be no problem doing it. We
> are planning to optimize the hibernation sequence by for exam
On Tue, Feb 24, 2015 at 07:19:24PM +0100, Michal Hocko wrote:
> Tetsuo Handa has pointed out that __GFP_NOFAIL allocations might fail
> after OOM killer is disabled if the allocation is performed by a
> kernel thread. This behavior was introduced from the very beginning by
> 7f33d49a2ed5 (mm, PM/Fr
DT file to enable the Wireless Audio reference design based on the
BCM58305.
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
Tested-by: Scott Branden
Signed-off-by: Jonathan Richardson
---
arch/arm/boot/dts/Makefile |3 ++-
arch/arm/boot/dts/bcm958305k.dts | 53 +++
This patchset adds a DTS file to enable the BCM58305 Wireless Audio reference
design based on Cygnus. It will be kept up to date as Cygnus drivers are
accepted into the mainline.
Jonathan Richardson (1):
ARM: dts: Enable Broadcom Cygnus BCM958305K
arch/arm/boot/dts/Makefile |3 ++-
a
Hi,
[snip]
> Felipe suggested to "divide to conquer" instead of having a single
> extcon driver to handle all these functions:
>
> - The mux functions would be controlled by a possible new pinctrl-gpio
> driver (Linus, your input here would be nice :)
> - The VBUS would be a fixed regulator
> -
Arrays (when not in a struct) "shall have a value greater than zero".
GCC complains when it's not the case here.
Fixes: ba7d49b1f0 ("rtnetlink: provide api for getting and setting slave info")
Signed-off-by: Sasha Levin
---
net/core/rtnetlink.c |4 ++--
1 file changed, 2 insertions(+), 2 de
On Fri, Feb 20, 2015 at 7:58 PM, Andy Lutomirski wrote:
> We have eager and lazy fpu modes, introduced in:
>
> 304bceda6a18 x86, fpu: use non-lazy fpu restore for processors supporting
> xsave
>
> The result is rather messy. There are two code paths in almost all of the
> FPU code, and only one
On Wed, Feb 18, 2015 at 11:07:30AM +0100, Lukasz Majewski wrote:
> Odroid U3 fan can work without being registered as OF cooling device
> (with CONFIG_THERMAL{_OF|} disabled).
> In this situation it can be controlled via PWM entry at
> /sys/class/hwmon/hwmon0/pwm1.
>
> Therefore, the thermal_cdev_
On Wed, Feb 18, 2015 at 11:07:29AM +0100, Lukasz Majewski wrote:
> Odroid U3 fan can work without being registered as OF cooling device
> (with CONFIG_THERMAL_OF disabled).
> In this situation it can be controlled via PWM entry at
> /sys/class/hwmon/hwmon0/pwm1.
>
> Therefore, the thermal_of_cooli
On Tue, 24 Feb, at 10:13:27AM, Juergen Gross wrote:
> Areas mapped via early_memremap() should be unmapped via
> early_memunmap(), while I/O-areas should be mapped via early_ioremap()
> and unmapped via early_iounmap().
>
> There are multiple spots where an area is mapped via the mem variant
> and
On 24.02.2015 03:42, OGAWA Hirofumi wrote:
> Heinrich Schuchardt writes:
>
>> You have to put
>> __attribute__((optimize("unroll-loops")))
>> here to unroll the loop inside the function:
>>
>>
>> static __attribute__ ((noinline))
>> __attribute__((optimize("unroll-loops")))
>> int test(unsigned c
On Tue, Feb 24, 2015 at 10:36 AM, Peter Hurley wrote:
> Hi Greg & Andrew,
>
> This patch series implements:
> 1. console-definable (aka extensible) matching
> 2. generic earlycon-to-console handoff via extensible matching
> 3. arch/prom support for direct earlycon
>
>
> Extensible console ma
On Tuesday 24 February 2015 12:28:41 Ezequiel Garcia wrote:
>
> Gah, no, you are right. I got confused.
>
> So it would be OK to avoid remove pt_regs from the uapi headers?
> How does this affect the signal handling nios2 implementation?
>
We have a number of architectures that don't provide th
On Wed, Feb 18, 2015 at 11:07:31AM +0100, Lukasz Majewski wrote:
> Explanation of several properties, which allow PWM fan working as a cooling
> device, have been embraced in this commit.
>
> Signed-off-by: Lukasz Majewski
> ---
> Changes for v2:
> - Rename cooling-pwm-values to cooling-levels
>
Guenter,
On Thu, Jan 08, 2015 at 08:48:40PM -0800, Guenter Roeck wrote:
> On 01/08/2015 10:05 AM, Nishanth Menon wrote:
> > Allow gpio-fan to be used as thermal cooling device for platforms that
> > use GPIO maps to control fans.
> >
> > As part of this change, we make the shutdown and remove logi
On Tue, 24 Feb 2015 19:51:33 +0100
Denys Vlasenko wrote:
> PER_CPU_VAR(kernel_stack) was set up in a way where it points
> five stack slots below the top of stack.
>
> Presumably, it was done to avoid one "sub $5*8,%rsp"
> in syscall/sysenter code paths, where iret frame needs to be
> created by
On Wed, Feb 18, 2015 at 11:07:33AM +0100, Lukasz Majewski wrote:
> With those bindings it is possible to use pwm-fan device available in
> Odroid U3 as a cooling device.
>
> Signed-off-by: Lukasz Majewski
> ---
> Changes for v2:
> - Rename cooling-pwm-values property to cooling-levels
> Changes f
On Mon, Feb 23, 2015 at 04:15:41PM +1100, Stephen Rothwell wrote:
>
> There are also 265 commits in next-20150209 that didn't make it into
> v4.0-rc1.
>
> Top ten first word of commit summary:
>
> 25 rcu
> 24 arm
> 20 selftests
> 19 mm
> 11 arm-soc
> 6 documentatio
In fork_init a division by zero may occur.
In the first patch the calculation of max_threads is moved from fork_init
to a new separate function.
The incorrect calculation of max threads is addressed in the
second patch.
Furthermore max_threads is checked against FUTEX_TID_MASK.
The third patch
PAGE_SIZE is not guaranteed to be equal to or less than 8 times the
THREAD_SIZE.
E.g. architecture hexagon may have page size 1M and thread size 4096.
This would lead to a division by zero in the calculation of max_threads.
With this patch the buggy code is moved to a separate function
set_max_th
Users can change the maximum number of threads by writing to
/proc/sys/kernel/threads-max.
With the patch the value entered is checked against the same
limits that apply when fork_init is called.
Signed-off-by: Heinrich Schuchardt
---
include/linux/sysctl.h | 3 +++
kernel/fork.c | 24
PAGE_SIZE is not guaranteed to be equal to or less than 8 times the
THREAD_SIZE.
E.g. architecture hexagon may have page size 1M and thread size 4096.
This would lead to a division by zero in the calculation of max_threads.
With 32-bit calculation there is no solution which delivers valid results
The mm->exe_file is currently serialized with mmap_sem (shared) in order
to both safely (1) read the file and (2) compute the realpath by calling
tomoyo_realpath_from_path, making it an absolute overkill. Good users will,
on the other hand, make use of the more standard get_mm_exe_file(), requiring
I am announcing the release of the Linux 3.13.11-ckt16 kernel.
The updated 3.13.y-ckt tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.13.y
and can be browsed at:
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;h=refs/heads/linux-3.13.y;a=shortlog
The diff from v3.13.1
avoid out-of-bounds-read by checking count before indexing.
Signed-off-by: Ameen Ali
---
drivers/net/wan/cosa.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wan/cosa.c b/drivers/net/wan/cosa.c
index 83c39e2..5252e21 100644
--- a/drivers/net/wan/cosa.c
+++ b/dri
Hi Rob,
On 02/24/2015 02:27 PM, Rob Herring wrote:
> On Tue, Feb 24, 2015 at 10:36 AM, Peter Hurley
> wrote:
>> Hi Greg & Andrew,
>>
>> This patch series implements:
>> 1. console-definable (aka extensible) matching
>> 2. generic earlycon-to-console handoff via extensible matching
>> 3. ar
On Tue, Feb 24, 2015 at 03:29:35PM -0400, Eduardo Valentin wrote:
> Guenter,
>
> On Thu, Jan 08, 2015 at 08:48:40PM -0800, Guenter Roeck wrote:
> > On 01/08/2015 10:05 AM, Nishanth Menon wrote:
> > > Allow gpio-fan to be used as thermal cooling device for platforms that
> > > use GPIO maps to cont
Eduardo,
On Tue, Feb 24, 2015 at 1:36 PM, Eduardo Valentin wrote:
> The fix seams reasonable. Although, it remains the question what is
> applicability to other Armada chips? Besides, shouldn't we simply use it
> by default? Also, do you plan to send updates in the DTS files?
As far as I can tel
The CMA aligned offset calculation is incorrect for
non-zero order_per_bit values.
For example, if cma->order_per_bit=1, cma->base_pfn=
0x2f80 and align_order=12, the function returns
a value of 0x17c00 instead of 0x400.
This patch fixes the CMA aligned offset calculation.
Cc: sta...@vger.ke
On Tue, Feb 24, 2015 at 07:51:32PM +0100, Denys Vlasenko wrote:
> In all three 32-bit entry points, %eax is zero-extended to %rax.
> It is safe to do 32-bit compare when checking that syscall#
> is not too large.
>
> The last instance of "mysterious" SS+8 constant is replaced by SIZEOF_PTREGS.
>
Hello.
On 02/24/2015 10:52 PM, Ameen Ali wrote:
avoid out-of-bounds-read by checking count before indexing.
Signed-off-by: Ameen Ali
---
drivers/net/wan/cosa.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wan/cosa.c b/drivers/net/wan/cosa.c
index 83c3
On Tue, Feb 24, 2015 at 11:55:23AM -0800, Guenter Roeck wrote:
> On Tue, Feb 24, 2015 at 03:29:35PM -0400, Eduardo Valentin wrote:
> > Guenter,
> >
> > On Thu, Jan 08, 2015 at 08:48:40PM -0800, Guenter Roeck wrote:
> > > On 01/08/2015 10:05 AM, Nishanth Menon wrote:
> > > > Allow gpio-fan to be us
On Mon, Feb 23, 2015 at 11:20 PM, Boaz Harrosh wrote:
> On 02/23/2015 05:46 PM, Andy Lutomirski wrote:
>> On Mon, Feb 23, 2015 at 4:43 AM, Boaz Harrosh wrote:
>>>
>>> Resource providers set this flag if they want
>>> that request_region_XXX will print a warning in dmesg
>>> if this particular res
On Tue, Feb 24, 2015 at 2:50 PM, Mike Galbraith
wrote:
> On Tue, 2015-02-24 at 13:19 -0300, Gustavo Bittencourt wrote:
>>
>> The deadlock returned after I applied this patch in v3.18.7-rt2. Here is my
>> log:
>
>
> Hrmph. I definitely want your patch to die ;-) It adds a whole new
> dimension
On Tue, Feb 24, 2015 at 7:47 AM, Denys Vlasenko
wrote:
> On Tue, Feb 17, 2015 at 2:46 AM, Ben Hutchings wrote:
>> 3.2.67-rc1 review patch. If anyone has any objections, please let me know.
>>
>> --
>>
>> From: Andy Lutomirski
>>
>> commit f647d7c155f069c1a068030255c300663516420e
On 02/24/2015 08:30 PM, Steven Rostedt wrote:
> On Tue, 24 Feb 2015 19:51:33 +0100
> Denys Vlasenko wrote:
>
>> PER_CPU_VAR(kernel_stack) was set up in a way where it points
>> five stack slots below the top of stack.
>>
>> Presumably, it was done to avoid one "sub $5*8,%rsp"
>> in syscall/sysent
On Mon, 23 Feb 2015, Mika Westerberg wrote:
> The HID over I2C specification allows to have the interrupt for a HID
> device to be GPIO instead of directly connected to the IO-APIC.
>
> Add support for this so that when the driver does not find proper interrupt
> number from the I2C client struct
This patch adds support for spawning busses as children of the GPMC.
Signed-off-by: Robert ABEL
---
drivers/memory/omap-gpmc.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/memory/omap-gpmc.c b/drivers/memory/omap-gpmc.c
index 5cabac8..78b78a64 100644
--- a/driver
DTS output was formatted to require additional work when copy-pasting into DTS.
Nano-second timings were removed, because they were not a confidence interval
nor
an indication what timing values would result in the same #ticks
Signed-off-by: Robert ABEL
---
drivers/memory/omap-gpmc.c | 33 +
The WAITMONITORINGTIME is expressed as a number of GPMC_CLK clock cycles,
even though the access is defined as asynchronous, and no GPMC_CLK clock
is provided to the external device. Still, GPMCFCLKDIVIDER is used as a divider
for the GPMC clock, so it must be programmed to define the
correct WAITM
On Tue, Feb 24, 2015 at 1:55 PM, Guenter Roeck wrote:
> On Tue, Feb 24, 2015 at 03:29:35PM -0400, Eduardo Valentin wrote:
>> Guenter,
>>
>> On Thu, Jan 08, 2015 at 08:48:40PM -0800, Guenter Roeck wrote:
>> > On 01/08/2015 10:05 AM, Nishanth Menon wrote:
>> > > Allow gpio-fan to be used as thermal
These are the changes I proposed in two separate patchsets
#([1], [2]) rebased to 3.19 as well as new changes for little bugs
I noticed while preparing this patchset.
1. DEBUG was undefined in source code --> remove offending lines
2. add capability to have busses as children of the GPMC and mult
The WAITMONITORINGTIME is expressed as a number of GPMC_CLK clock cycles,
even though the access is defined as asynchronous, and no GPMC_CLK clock
is provided to the external device. Still, GPMCFCLKDIVIDER is used as a divider
for the GPMC clock, so it must be programmed to define the
correct WAITM
The WAITMONITORINGTIME is expressed as a number of GPMC_CLK clock cycles,
even though the access is defined as asynchronous, and no GPMC_CLK clock
is provided to the external device. Still, GPMCFCLKDIVIDER is used as a divider
for the GPMC clock, so it must be programmed to define the
correct WAITM
GPMC_CONFIG1_i parameters CLKACTIVATIONTIME and WAITMONITORINGTIME
have reserved values.
Raise an error if calculated timings try to program reserved values.
GPMC_CONFIG1_i ATTCHEDDEVICEPAGELENGTH and DEVICESIZE were already checked
when parsing the DT.
Explicitly comment invalid values on gpmc_c
GPMC debug output is aligned to 10 characters for field names.
However, some fields have bigger names, screwing up the alignment.
Consequently, alignment was changed to longest field name (17 chars) for now.
Signed-off-by: Robert ABEL
---
drivers/memory/omap-gpmc.c | 2 +-
1 file changed, 1 inse
OMAP2+ GPMC driver undefines DEBUG, which makes it unnecessarily
hard to turn DEBUG on. Remove the offending lines.
Signed-off-by: Robert ABEL
---
drivers/memory/omap-gpmc.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/memory/omap-gpmc.c b/drivers/memory/omap-gpmc.c
index 24696f5
On Tue, Feb 24, 2015 at 9:02 PM, Andy Lutomirski wrote:
>> This currently fails in 32-bit kernels (at least in qemu):
>>
>> / # ./es_test
>> Allocated GDT index 7
>> [FAIL]ES changed from 0x3b to 0x7b
>> [FAIL]ES was corrupted 1000/1000 times
>> / # uname -a
>> Linux (none) 4.0.0-rc1 #1 SM
On Tue, Feb 24, 2015 at 9:05 PM, Robert ABEL
wrote:
>
> These are the changes I proposed in two separate patchsets
> #([1], [2]) rebased to 3.19 as well as new changes for little bugs
> I noticed while preparing this patchset.
It seems my m4d s3d sk177z failed me. Disregard the missing Patch 2,
t
We have pci_ignore_hotplug(), but there's no way to undo this
without manipulating the device itself. It seems like the original
intention of the function is to provide the driver with a way to
ignore hotplug over a specific time window, ex. the time while the
device is powered off. Once the devi
Commit b440bde74f04 enabled drivers to be able to set an ignore
hotplug flag on the device and used it in the suspend routine for
nouveau and radeon to prevent hotplug when the device is powered off.
However, there was no undo function provided, so once set, the ignore
hotplug flag lives on for the
I'd kinda like to use pci_ignore_hotplug() for devices in use by a
user via vfio-pci, but the interface seems only partially implemented
since we can only set ignore_hotplug and not clear it. This adds the
capability to clear the flag and applies it as seems to be appropriate
to the existing users
On Tue, Feb 24, 2015 at 8:58 PM, Borislav Petkov wrote:
> On Tue, Feb 24, 2015 at 07:51:32PM +0100, Denys Vlasenko wrote:
>> In all three 32-bit entry points, %eax is zero-extended to %rax.
>> It is safe to do 32-bit compare when checking that syscall#
>> is not too large.
>>
>> The last instance
On Tue, Feb 24, 2015 at 1:53 PM, Peter Hurley wrote:
> Hi Rob,
>
> On 02/24/2015 02:27 PM, Rob Herring wrote:
>> On Tue, Feb 24, 2015 at 10:36 AM, Peter Hurley
>> wrote:
>>> Hi Greg & Andrew,
>>>
>>> This patch series implements:
>>> 1. console-definable (aka extensible) matching
>>> 2. gene
On Tue, 24 Feb 2015, Johannes Weiner wrote:
> On Tue, Feb 24, 2015 at 07:19:24PM +0100, Michal Hocko wrote:
> > Tetsuo Handa has pointed out that __GFP_NOFAIL allocations might fail
> > after OOM killer is disabled if the allocation is performed by a
> > kernel thread. This behavior was introduced
On Tue, Feb 24, 2015 at 3:12 PM, Alex Williamson
wrote:
> I'd kinda like to use pci_ignore_hotplug() for devices in use by a
> user via vfio-pci, but the interface seems only partially implemented
> since we can only set ignore_hotplug and not clear it. This adds the
> capability to clear the fla
On Tue, Feb 24, 2015 at 3:14 AM, Borislav Petkov wrote:
> From: Borislav Petkov
>
> [ Changelog is in version-increasing number so that one can follow the
> evolution of the patch set in a more natural way (i.e., latest version
> comes at the end. ]
>
> v0:
>
> this is something which h
>-Original Message-
>From: Hiroshi Shimamoto [mailto:h-shimam...@ct.jp.nec.com]
>Sent: Thursday, February 19, 2015 5:01 PM
> Subject: [E1000-devel] [PATCH v2 3/3] ixgbe: Add new ndo to allow VF
> multicast promiscuous mode
>
>From: Hiroshi Shimamoto
>
>Implements the new netdev op to all
On Tue, 24 Feb 2015 12:40:32 +0200 Tomi Valkeinen
wrote:
> Hi,
>
> On 24/02/15 11:37, NeilBrown wrote:
> >
> >
> > commit 303e4697e762dc92a40405f4e4b8aac02cd0d70b
> > OMAPDSS: rename display-sysfs 'name' entry
> >
> > broke the xorg X server on my device as it couldn't find the display
>
On Tue, Feb 24, 2015 at 9:42 AM, Bartosz Golaszewski
wrote:
>
> Searching for the member of an array closest to 'x' is
> duplicated in several places.
>
> Add two macros that implement this algorithm for arrays
> sorted both in ascending and descending order.
I don't see the point here. You're n
Hi,
> If we decide to go ahead with the solution proposed by this patch for
> practical reasons (which are good reasons indeed), I still have one
> problem with its current form.
>
> As the discussion highlighted, this is an ACPI problem, so I'd very
> much like it to be confined to the ACPI GPIO
On Tue, Feb 24, 2015 at 09:13:03PM +0100, Denys Vlasenko wrote:
> They aren't equal. $1 and $2 in two lowest bits will also
> be interpreted as "userspace" here. "Equal to $3" sends
> a wrong message here to a human reading the code,
> the code doesn't test for CPL=3, it tests for any nonzero CPL.
On Fri, 20 Feb 2015, Konstantin Khlebnikov wrote:
> diff --git a/include/linux/mm.h b/include/linux/mm.h
> index 028565a..0538de0 100644
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -1126,6 +1126,7 @@ extern void pagefault_out_of_memory(void);
> * various contexts.
> */
> #defin
From: Sasha Levin
Date: Tue, 24 Feb 2015 14:14:35 -0500
> Arrays (when not in a struct) "shall have a value greater than zero".
>
> GCC complains when it's not the case here.
>
> Fixes: ba7d49b1f0 ("rtnetlink: provide api for getting and setting slave
> info")
> Signed-off-by: Sasha Levin
Ap
On Tue, 24 Feb 2015, Rafael Aquini wrote:
> commit 6d2be915e589 ("mm/readahead.c: fix readahead failure for memoryless
> NUMA
> nodes and limit readahead pages")[1] imposed 2 mB hard limits to readahead by
> changing max_sane_readahead() to sort out a corner case where a thread runs
> on
> ame
* NeilBrown [150223 19:45]:
> Hi,
> the following 4 patches make some improvements to the twl4030
> phy. Together with some other patches I have for twl4030_charger,
> they allow for better automatic control of charging.
>
> In particular, the status of the ID pin is assessed and the
> resu
On Tue, Feb 24, 2015 at 12:33:06PM -0800, Phil Pokorny wrote:
> On Tue, Feb 24, 2015 at 9:42 AM, Bartosz Golaszewski
> wrote:
> >
> > Searching for the member of an array closest to 'x' is
> > duplicated in several places.
> >
> > Add two macros that implement this algorithm for arrays
> > sorted
[removed stable from cc]
On Tue, Feb 24, 2015 at 11:55 AM, Danesh Petigara
wrote:
> diff --git a/mm/cma.c b/mm/cma.c
> index 75016fd..58f37bd 100644
> --- a/mm/cma.c
> +++ b/mm/cma.c
> @@ -70,9 +70,13 @@ static unsigned long cma_bitmap_aligned_offset(struct cma
> *cma, int align_order)
>
>
'max_current' sysfs attributes are created which allow the
max to be set.
Whenever a current source changes, the default is restored.
This will be followed by a uevent, so user-space can decide to
update again.
Signed-off-by: NeilBrown
---
drivers/power/twl4030_charger.c | 76 +
If the phy has been told what current it can draw, it tells us
and now we use that number.
Note that 'vbus_draw' is in mA, while usb_cur is in uA.
Signed-off-by: NeilBrown
---
drivers/power/twl4030_charger.c |5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/power/twl4030_charg
* NeilBrown [150223 19:45]:
> A construct like:
>
> if (pm_runtime_suspended(twl->dev))
>pm_runtime_get_sync(twl->dev);
>
> is against the spirit of the runtime_pm interface as it
> makes the internal refcounting useless.
>
> In this case it is also racy, particularly as
'off' or 'auto' to
/sys/class/power/twl4030_usb/mode
will now enable or disable charging from USB port. Normally this is
enabled on 'plug' and disabled on 'unplug'.
Unplug will still disable charging. 'plug' will only enable it if
'auto' if selected.
Signed-off-by: NeilBrown
Conflicts:
The USB Battery Charging spec (BC1.2) suggests a dedicated
charging port can deliver from 0.5 to 5.0A at between 4.75 and 5.25
volts.
To choose the "correct" current voltage setting requires a trial
and error approach: try to draw current and see if the voltage drops
too low.
Even with a configur
If it cannot, we will stop pulling more current when voltage drops.
Signed-off-by: NeilBrown
---
drivers/power/twl4030_charger.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/power/twl4030_charger.c b/drivers/power/twl4030_charger.c
index 7ad6b4b531d7..89e2c12
Add a 'continuous' option for usb charging which enabled
the "linear" charging mode of the twl4030.
Linear charging does a good job with not so reliable power sources, since
several voltage controlling is then often too intelligent.
It was used with a bike hub dynamo since a year or so. In that ca
This allows AC charging to be turned off, much like usb charging.
"continuous" (aka "linear") mode maps to the CVENAC (constant voltage)
feature of the twl4030.
Signed-off-by: NeilBrown
---
drivers/power/twl4030_charger.c | 40 +--
1 file changed, 30 insert
From: Stephen Warren
Both nvidia,io-hv and nvidia,rcv-sel represent the fact that a particular
pin's IO buffers are configured to accept "high voltage" input signals.
The TRM for different chips names the register field rcv-sel on older
SoCs and io_hv on newer SoCs. Add the new naming option into
else if at line 406 has the same condition as the else if at line 404.
Signed-off-by : Ameen Ali
---
drivers/staging/rtl8188eu/hal/Hal8188ERateAdaptive.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8188eu/hal/Hal8188ERateAdaptive.c
b/drivers/staging/rt
* NeilBrown [150224 12:35]:
> On Tue, 24 Feb 2015 12:40:32 +0200 Tomi Valkeinen
> wrote:
>
> > Hi,
> >
> > On 24/02/15 11:37, NeilBrown wrote:
> > >
> > >
> > > commit 303e4697e762dc92a40405f4e4b8aac02cd0d70b
> > > OMAPDSS: rename display-sysfs 'name' entry
> > >
> > > broke the xorg X s
From: Stephen Warren
Tegra210's pinmux supports a different set of pins/options than earlier
SoCs, so requires its own driver (well, table of pin-specific data).
Cc: devicet...@vger.kernel.org
Signed-off-by: Stephen Warren
---
.../bindings/pinctrl/nvidia,tegra210-pinmux.txt| 166 ++
drive
From: Stephen Warren
Some of the pinmux configuration bits that exist in "drive group"
registers in Tegra30..Tegra124 move to the "pinmux" registers on future
chips. Add a flag to support this.
Signed-off-by: Stephen Warren
---
drivers/pinctrl/pinctrl-tegra.c| 27 +-
On Tue, 24 Feb 2015, Heinrich Schuchardt wrote:
> diff --git a/init/main.c b/init/main.c
> index 61b99376..21394ec 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -94,7 +94,7 @@
> static int kernel_init(void *);
>
> extern void init_IRQ(void);
> -extern void fork_init(unsigned long);
> +ex
On Tue, Feb 24, 2015 at 06:48:28PM +0100, Bartosz Golaszewski wrote:
> Replace RANGE_TO_REG() and FREQ_TO_REG() functions with calls
> to find_closest().
>
> Signed-off-by: Bartosz Golaszewski
> ---
> drivers/hwmon/lm85.c | 43 ---
> 1 file changed, 12 ins
From: Stephen Warren
Various non-semantic tweaks and layout/consistency fixes for existing
Tegra pinctrl drivers.
Move the definition of DRV_PINGROUP_REG() before the definition of
PINGROUP() so that a future SoC driver can invoke the former from the
latter.
PINGROUP_BIT_Y(n) is just n, so repl
501 - 600 of 923 matches
Mail list logo
