Get it.
Eric, thanks for your explaination. :-)
Jason, thank you! I will remember cc net...@vger.kernel.org next time.
-Original Message-
From: Eric Dumazet [mailto:eric.duma...@gmail.com]
Sent: Thursday, July 30, 2015 1:01 PM
To: Jason Wang
Cc: Zhangjie (HZ);
On Thu, Jul 30, 2015 at 8:18 AM, Fu, Zhonghui
wrote:
> Enable wiphy device to suspend/resume asynchronously. This can improve
> system suspend/resume speed.
>
How will that impact the timing with respect to the suspend call
coming from the bus?
I think that a few drivers rely on the suspend call
Hi Jens, did you get a chance to take a look at this patch?
On Thu, Jul 23, 2015 at 2:20 PM, Tahsin Erdogan wrote:
> Noop scheduler currently dispatches a request by calling
> elv_dispatch_sort(). In practice, sorting does not occur because
> __elv_next_request() asks the io scheduler to
On 30-07-15, 01:45, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> To protect against races with concurrent CPU online/offline, call
> get_online_cpus() before registering a cpufreq driver.
>
> Signed-off-by: Rafael J. Wysocki
> ---
> drivers/cpufreq/cpufreq.c | 13 ++---
>
Chunyan Zhang writes:
> If let stm_probe() implement probe deferral, it has to have a global
> variable for the later calling of "stm_register_device", because the
No, it doesn't. Please read about probe deferral.
Regards,
--
Alex
--
To unsubscribe from this list: send the line "unsubscribe
Around Wed 29 Jul 2015 21:08:51 +0200 or thereabout, Peter Zijlstra wrote:
> Fold the tracing hook into switch_to() in order to remove
> finish_arch_switch().
AFAICT this should work, I do not have a nexus debugger to verify behavior.
> Cc: Hans-Christian Egtvedt
> Signed-off-by: Peter Zijlstra
On Wed, 2015-07-29 at 21:34 -0400, Dave Perez wrote:
> This is a patch to the rtw_debug.c file that fixes styling errors relating to
> new lines after variable declarations.
[]
> diff --git a/drivers/staging/rtl8188eu/core/rtw_debug.c
> b/drivers/staging/rtl8188eu/core/rtw_debug.c
[]
> @@
Takao Indoh writes:
> Ok, I'm reading the code around perf_event_create_kernel_counter. It
> seems to work for my purpose, I'll try to update my patch with this.
Thank you.
Regards,
--
Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Enable wiphy device to suspend/resume asynchronously. This can improve
system suspend/resume speed.
Signed-off-by: Zhonghui Fu
---
net/wireless/core.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/net/wireless/core.c b/net/wireless/core.c
index 2a0bbd2..bc5e68f 100644
On Wed, Jul 29, 2015 at 6:39 PM, Theodore Ts'o wrote:
>
> It's here: https://goo.gl/photos/xHjn2Z97JQEw6k2C9
You didn't catch enough of the code line to decode the code, but it's
early enough in drm_crtc_index() (just five bytes in) that it's almost
certainly the very first dereference, so it's
On 07/30/15 at 11:07am, Baoquan He wrote:
> People reported that crash_notes in /proc/vmcore were corrupted and
> this cause crash kdump failure. With code debugging and log we got
> the root cause. This is because percpu variable crash_notes are
> allocated in 2 vmalloc pages. As you know percpu
On Thu, 2015-07-30 at 12:26 +0800, Jason Wang wrote:
> cc netdev for more experts
>
> On 07/28/2015 04:53 PM, Zhangjie (HZ) wrote:
> >
> > Hi,
> >
> > I generate a skb as follows:
> >
> > It has a linear data region, 17 frags and the last fragment is in
> > skb_shinfo(skb)->frag_list.
> >
> >
On Wed, Jul 29, 2015 at 03:28:57PM +0200, Paolo Bonzini wrote:
> The PIT is only created if irqchip_in_kernel returns true, so the
> check is superfluous.
I poked around. Looks to me like the existence of an IOAPIC is not
checked on the creation of the in-kernel PIT. Userspace might limit itself
When testing hibernate, I found the EFI runtime services was broken
on some old EFI machines on my hand, Intel DQ57TM development board
and Acer Gateway Z5WT2 notebook.
After printing the EFI memmap and virtual address mapping on -4G area,
found those issue machines keep the physical address of
cc netdev for more experts
On 07/28/2015 04:53 PM, Zhangjie (HZ) wrote:
>
> Hi,
>
> I generate a skb as follows:
>
> It has a linear data region, 17 frags and the last fragment is in
> skb_shinfo(skb)->frag_list.
>
> Before this skb is sent to driver, dev_hard_start_xmit() will segment
> it
On Tue, Jul 28, 2015 at 11:40 PM, Seth Forshee
wrote:
>
> On Wed, Jul 22, 2015 at 05:05:17PM -0700, Casey Schaufler wrote:
> > > This is what I currently think you want for user ns mounts:
> > >
> > > 1. smk_root and smk_default are assigned the label of the backing
> > > device.
Seth,
On Wed, Jul 29, 2015 at 10:57:26AM -0700, Andy Lutomirski wrote:
> OK if I do that as a follow-up? It would probably want to be a
> separate patch anyway.
Of course.
> Hmm, I'm starting to like this new regime in which we never ever
> switch to user mode from anywhere other than the standard
Hi Jens,
After merging the block tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/staging/lustre/lustre/llite/../include/obd_support.h:42:0,
from
drivers/staging/lustre/lustre/llite/../include/lustre_cfg.h:225,
from
On 7/29/2015 8:52 PM, Benjamin Tissoires wrote:
On Jul 29 2015 or thereabouts, Sivakumar Thulasimani wrote:
why not detect reverse in intel_dp_detect/intel_hpd_pulse ? that way you can
identify both lane count and reversal state without touching anything in the
link training code. i am yet to
On 2015/7/30 5:03, Thomas Gleixner wrote:
> On Mon, 27 Jul 2015, Matt Fleming wrote:
>> [BAD]
>> 3: 1 0 0 0 IR-IO-APIC 3-edge
>> 6: 0 0 0 0 IR-IO-APIC 6-edge
>> dw_dmac
>> 7: 15 1
On Wed, Jul 29, 2015 at 03:37:35PM +0200, Paolo Bonzini wrote:
> We can reuse the algorithm that computes the EOI exit bitmap to figure
> out which vectors are handled by the IOAPIC. The only difference
> between the two is for edge-triggered interrupts other than IRQ8
> that have no notifiers
> On Jul 29, 2015, at 18:34, Thomas Gleixner wrote:
>
> On Tue, 28 Jul 2015, Andrew Morton wrote:
>
>> On Tue, 28 Jul 2015 11:59:01 -0400 David Kershner
>> wrote:
>>
>>> The s-Par visornic driver, currently in staging, processes a queue
>>> being serviced by the an s-Par service partition.
On 30-07-15, 01:29, Rafael J. Wysocki wrote:
> > > There is a small problem with it that I've already pointed out to Viresh.
> > >
> > > Namely, while changing subsys_interface_(un)register() to handle return
> > > values from ->add_dev(), it doesn't do the same thing in
> > > bus_probe_device()
On Wed, Jul 29, 2015 at 9:46 PM, Alexander Shishkin
wrote:
> Mark Brown writes:
>
>> On Wed, Jul 29, 2015 at 04:25:10PM +0300, Alexander Shishkin wrote:
>>
>>> There has to be a way to defer stm_probe(), although a quick look at
>>> amba code suggests it's not implemented.
>>
>> What makes you
On Wed, Jul 29, 2015 at 03:37:34PM +0200, Paolo Bonzini wrote:
> Do not compute TMR in advance. Instead, set the TMR just before the interrupt
> is accepted into the IRR. This limits the coupling between IOAPIC and LAPIC.
>
> Signed-off-by: Paolo Bonzini
> ---
> arch/x86/kvm/ioapic.c | 9
On Wed, Jul 29, 2015 at 03:28:58PM +0200, Paolo Bonzini wrote:
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 2d62229aac26..23e47a0b054b 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -3626,30 +3626,25 @@ long kvm_arch_vm_ioctl(struct file *filp,
>
On 29-07-15, 14:19, Greg KH wrote:
> I don't see how this is a stable bug fix, what is resolved by it that
> doesn't work today? Is there some code that is expecting this
> functionality that has never been present?
>
> I'll go queue it up, but I don't think it is -stable material, but feel
>
On Tue, Jul 28, 2015 at 8:19 AM, Tomeu Vizoso
wrote:
> Delay matches of platform devices until late_initcall, when we are sure
> that all built-in drivers have been registered already. This is needed
> to prevent deferred probes because of some drivers not having registered
> yet.
>
> The reason
On Wed, Jul 29, 2015 at 9:25 PM, Alexander Shishkin
wrote:
> Chunyan Zhang writes:
>
>>> +/**
>>> + * stm_source_register_device() - register an stm_source device
>>> + * @parent:parent device
>>> + * @data: device description structure
>>> + *
>>> + * This will create a device of
Hi Jens,
Today's linux-next merge of the block tree got a conflict in:
fs/f2fs/data.c
between commit:
8e5b935bf1ce ("f2fs: maintain extent cache in separated file")
from the f2fs tree and commit:
4246a0b63bd8 ("block: add a bi_error field to struct bio")
from the block tree.
I fixed
Hi Jens,
Today's linux-next merge of the block tree got a conflict in:
block/bounce.c
between commit:
a3ad0a9da863 ("block: Remove forced page bouncing under IO")
from the ext3 tree and commit:
b7c44ed9d2fc ("block: manipulate bio->bi_flags through helpers")
from the block tree.
I
On Tue, Jul 28, 2015 at 8:19 AM, Tomeu Vizoso
wrote:
> This function is just a getter for struct acpi_device.dev and is needed
> in the implementation of the fwnode API when building with !CONFIG_ACPI.
>
> Signed-off-by: Tomeu Vizoso
> ---
>
> Changes in v2:
> - Add acpi_dev_get_device()
>
>
People reported that crash_notes in /proc/vmcore were corrupted and
this cause crash kdump failure. With code debugging and log we got
the root cause. This is because percpu variable crash_notes are
allocated in 2 vmalloc pages. As you know percpu is based on vmalloc
by default. Then vmalloc can't
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/drm_crtc.c
between commit:
5677d67ae394 ("drm: Stop resetting connector state to unknown")
from Linus' tree and commit:
1c473be11958 ("drm: Fixup locking WARNINGs in drm_mode_config_reset")
from
On Wed, 29 Jul 2015 09:17:32 +
Naoya Horiguchi wrote:
> # CC:ed linux-mm
>
> Hi Xiaoqiang,
>
> On Wed, Jul 29, 2015 at 03:52:46PM +0800, Wang Xiaoqiang wrote:
> > Hi,
> >
> > I find a little problem in the memory_failure function in
> > mm/memory-failure.c . Please check it.
> >
> >
On Wed, Jul 29, 2015 at 2:00 PM, Linus Walleij wrote:
> On Tue, Jul 28, 2015 at 4:17 PM, Vaishali Thakkar
> wrote:
>> On 28 Jul 2015 17:35, "Linus Walleij" wrote:
>
>>> Reviewed-by: Linus Walleij
>>> Please get this through ARM SoC or tell me if I should handle it.
>>
>> So, do you want me to
When system(one x86 soc) boot, we saw many normal dma allocation requests
goes to cma area. The call chain is
dma_generic_alloc_coherent
dma_alloc_from_contiguous -- arch/x86/kernel/pci-dma.c
cma_alloc(dev_get_cma_area(dev), count, align)
Current
Hi Stephen,
On Wed, 2015-07-29 at 17:27 -0700, Stephen Boyd wrote:
> On 07/29, James Liao wrote:
> > From: Sascha Hauer
> >
> > On the MT8173 the clocks are provided by different units. To enable
> > the critical clocks we must be sure that all parent clocks are already
> > registered,
On Wed, Jul 29, 2015 at 09:35:11PM -0400, Trond Myklebust wrote:
> Hi Stephen,
>
> On Wed, Jul 29, 2015 at 9:23 PM, Stephen Rothwell
> wrote:
> > Hi all,
> >
> > Today's linux-next merge of the nfsd tree got a conflict in:
> >
> > fs/nfs/nfs42proc.c
> >
> > between commit:
> >
> >
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
net/bridge/br_multicast.c
between commit:
544586f742b4 ("bridge: mcast: give fast leave precedence over multicast
router and querier")
from the net tree and commit:
09cf0211f970 ("bridge: mdb: fill state in
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/andrea/aa.git master
commit 112b650f83e5ccea260708f8b7ca747580584659 ("mm: gup: make
get_user_pages_fast and __get_user_pages_fast latency conscious")
On Thu, 2015-07-30 at 5:21, Scott Wood wrote:
> -Original Message-
> From: Wood Scott-B07421
> Sent: Thursday, July 30, 2015 12:19 AM
> To: Zhao Qiang-B45475
> Cc: lau...@codeaurora.org; linux-kernel@vger.kernel.org; linuxppc-
> d...@lists.ozlabs.org; a...@linux-foundation.org;
This is a patch to the rtw_debug.c file that fixes styling errors relating to
new lines after variable declarations.
Signed-off-by: Dave Perez
---
drivers/staging/rtl8188eu/core/rtw_debug.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
On 7/29/15 5:08 PM, Daniel Borkmann wrote:
On 07/28/2015 01:17 PM, Kaixu Xia wrote:
Previous patch v3 url:
https://lkml.org/lkml/2015/7/23/203
...
Kaixu Xia (3):
bpf: Add new bpf map type to store the pointer to struct perf_event
bpf: Implement function bpf_perf_event_read() that get
On 2015/07/29 18:09, Alexander Shishkin wrote:
> Takao Indoh writes:
>
>> On 2015/07/29 15:08, Alexander Shishkin wrote:
>>> Instead, we should be able to do use the existing perf functionality to
>>> enable the system-wide tracing, so that it goes through the
>>
>> "existing driver" means PMU
This is a patch to the rtw_debug.c file that fixes styling errors relating to
new lines after variable declarations.
Signed-off-by: Dave Perez
---
drivers/staging/rtl8188eu/core/rtw_debug.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
Hello, list.
Could any one take a look at on this? I believe this is a issue slowing
down ioctl(BTRFS_IOC_TREE_SEARCH) if the target key is missing.
On Tue, Jun 30, 2015 at 11:25 AM, Naohiro Aota wrote:
> The search key advancing condition used in copy_to_sk() is loose. It can
> advance the key
This patch series change the 32-bit time types (timespec/itimerspec) to
the 64-bit types (timespec64/itimerspec64), and add new 64bit accessor
functions, which are required in order to avoid y2038 issues in the
posix_clock subsystem.
In order to avoid spamming people too much, I'm only sending
On 7/29/15 4:30 PM, Daniel Borkmann wrote:
+if (map && map->map_type == BPF_MAP_TYPE_PERF_EVENT_ARRAY &&
+func_id != BPF_FUNC_perf_event_read)
this part belongs in patch 3, since patch 2 won't compile as-is.
Please keep bi-sectability intact.
--
To unsubscribe from this list: send
Hi,
> From: Michal Hocko [mailto:mho...@kernel.org]
>
> On Wed 29-07-15 09:09:18, 河合英宏 / KAWAI，HIDEHIRO wrote:
> > > From: Michal Hocko [mailto:mho...@kernel.org]
> > > On Wed 29-07-15 05:48:47, 河合英宏 / KAWAI，HIDEHIRO wrote:
> > > > Hi,
> > > >
> > > > > From: linux-kernel-ow...@vger.kernel.org
On 7/29/15 4:17 PM, Daniel Borkmann wrote:
-if (map->map_type == BPF_MAP_TYPE_PROG_ARRAY)
+if (map->map_type >= BPF_MAP_TYPE_PROG_ARRAY)
/* prog_array stores refcnt-ed bpf_prog pointers
* release them all when user space closes prog_array_fd
*/
-
On 2015/07/29 22:35, Thomas Gleixner wrote:
> On Wed, 29 Jul 2015, Peter Hurley wrote:
>> On 07/29/2015 07:53 AM, Thomas Gleixner wrote:
>>> On Wed, 29 Jul 2015, Peter Hurley wrote:
On 07/29/2015 06:32 AM, Thomas Gleixner wrote:
> On Wed, 29 Jul 2015, Taichi Kageyama wrote:
>> - Keep
On Wed, Jul 29, 2015 at 09:34:42PM -0400, Dave Perez wrote:
> This is a patch to the rtw_debug.c file that fixes styling errors relating to
> new lines after variable declarations.
>
> Signed-off-by: Dave Perez
> ---
> drivers/staging/rtl8188eu/core/rtw_debug.c | 2 ++
> 1 file changed,
On Wed, Jul 29, 2015 at 08:49:37PM -0400, Theodore Ts'o wrote:
>
> Unfortunately the failure causes a series of recursive faults and I
> haven't been able to capture the stack trace, but on 4.2-rcX kernels,
> I can reliably cause the system to crash if my T540p is booted with
> the docking
Prepare the driver for supporting two devices: Maxim 77693 and 77843:
1. Add table of device ids and store current device type for later
usage.
2. Differentiate the haptic device configuration.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Dmitry Torokhov
---
From: Murali Karicheri
Date: Tue, 28 Jul 2015 18:20:11 -0400
> This series fixes few bugs to allow keystone netcp modules to be
> dynamically loaded and removed. Currently it allows following
> sequence multiple times
...
Series applied, thanks.
--
To unsubscribe from this list: send the line
The Maxim 77843 haptic driver differs from 77693 by:
1. Setting the bias.
2. Different configuration register.
3. Not enabling the low-sys DAC.
4. Using same regmap for PMIC and haptic blocks.
Incorporate all differences into max77693 haptic driver so both devices
can be supported.
Hi Mark,
This patchset depends on "regulator: Merge max77843 into max77693" [0]
which you applied already. Dmitry agreed [1] to take this through
regulator tree.
Can you apply it?
Changes since v1
1. Fix signed-off-by in patch 4/4.
2. Add acked-by Dmitry.
Description
Storing a predefined PWM divisor in state container structure is
meaningless. The field, after initialization, is only read so this only
obfuscates the code. Remove the field and use directly enum value.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Dmitry Torokhov
---
The max77693 haptic driver supports Maxim 77843 device so remove the
max77843 driver.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Dmitry Torokhov
---
drivers/input/misc/Kconfig | 12 --
drivers/input/misc/Makefile | 1 -
drivers/input/misc/max77843-haptic.c | 359
Hi Stephen,
On Wed, Jul 29, 2015 at 9:23 PM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the nfsd tree got a conflict in:
>
> fs/nfs/nfs42proc.c
>
> between commit:
>
> bdcc2cd14e4e ("NFSv4.2: handle NFS-specific llseek errors")
>
> from Linus' tree and commit:
>
>
Hi,
2015-07-30 0:23 GMT+09:00 Rob Herring :
> On Wed, Jul 29, 2015 at 8:22 AM, Ian Campbell wrote:
>> On Wed, 2015-07-29 at 20:07 +0900, Masahiro Yamada wrote:
>>> Hi Ian,
>>>
>>>
>>> 2015-07-27 19:35 GMT+09:00 Ian Campbell :
>>> > Commit 9ccd608070b6 "arm64: dts: add device tree for ARM
On Wed, 2015-07-29 at 12:19 -0400, Paul Gortmaker wrote:
> Hi David,
>
> Does it make sense to build this sample when cross compiling?
>
> The reason I ask is that it has been breaking the linux-next build of
> allmodconfig for a while now, with:
>
> HOSTCC samples/kdbus/kdbus-workers
>
On 2015/7/30 3:16, Michael S. Tsirkin wrote:
> ACPI spec 5.0 allows the use of PCI vendor IDs.
>
But virtio-mmio is not a PCI device, it's a platform device.
Why do we drop the previous way using "QEMU"? Something I missed?
> Since we have one for virtio, it seems neater to use that
>
Hi all,
Today's linux-next merge of the nfsd tree got a conflict in:
fs/nfs/nfs42proc.c
between commit:
bdcc2cd14e4e ("NFSv4.2: handle NFS-specific llseek errors")
from Linus' tree and commit:
0183ae17c741 ("NFSv4.2: handle NFS-specific llseek errors")
from the nfsd tree.
The only
Quoting Lee Jones (2015-07-27 01:53:38)
> On Mon, 27 Jul 2015, Maxime Ripard wrote:
>
> > On Wed, Jul 22, 2015 at 02:04:13PM +0100, Lee Jones wrote:
> > > These new API calls will firstly provide a mechanisms to tag a clock as
> > > critical and secondly allow any knowledgeable driver to (un)gate
Quoting Lee Jones (2015-07-28 06:00:55)
> On Tue, 28 Jul 2015, Maxime Ripard wrote:
>
> > On Mon, Jul 27, 2015 at 09:53:38AM +0100, Lee Jones wrote:
> > > On Mon, 27 Jul 2015, Maxime Ripard wrote:
> > >
> > > > On Wed, Jul 22, 2015 at 02:04:13PM +0100, Lee Jones wrote:
> > > > > These new API
On 07/29/2015 05:22 PM, Alexandre Belloni wrote:
Commit dca1a4b5ff6e ("clk: at91: keep slow clk enabled to prevent system
hang") added a workaround for the slow clock as it is not properly handled
by its users.
Get and use the slow clock as it is necessary for the at91sam9 watchdog.
On 07/29/2015 05:21 PM, Alexandre Belloni wrote:
The watchdog has an input clock, the slow clock. It is required as it will
not function without it.
Signed-off-by: Alexandre Belloni
Reviewed-by: Guenter Roeck
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
Hi Lee,
+ linux-clk ml
Quoting Lee Jones (2015-07-22 06:04:13)
> These new API calls will firstly provide a mechanisms to tag a clock as
> critical and secondly allow any knowledgeable driver to (un)gate clocks,
> even if they are marked as critical.
>
> Suggested-by: Maxime Ripard
>
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm+acpi-4.2-rc5
to receive power management and ACPI fixes for v4.2-rc5 with
top-most commit d29809b8eb12d291d7b507fdaaa5e44707641685
Merge branches 'pm-cpufreq' and 'acpi-pm'
on top of commit
Unfortunately the failure causes a series of recursive faults and I
haven't been able to capture the stack trace, but on 4.2-rcX kernels,
I can reliably cause the system to crash if my T540p is booted with
the docking station attached.
It will also crash if I boot the system first, and then
On Wed, Jul 29, 2015 at 01:24:16PM -0400, Chris Metcalf wrote:
> On 07/29/2015 09:23 AM, Frederic Weisbecker wrote:
> >>At a higher level, is the posix-cpu-timers code here really providing the
> >>>right semantics? It seems like before, the code was checking a struct
> >>>task-specific state,
From: Andi Kleen
Now that we can modify the metrics printout functions easily,
it's straight forward to support metric printing for interval mode.
All that is needed is to print the time stamp on every new line.
Pass the prefix into the context and print it out.
Signed-off-by: Andi Kleen
---
Currently perf stat does not support printing computed metrics for interval (-I
xxx)
or CSV (-x,) mode. For example IPC or TSX metrics over time are quite useful to
know.
This patch implements them. The main obstacle was that the
metrics printing was all open coded all over the metrics
The system timer and the RTC need the slow clock, add it.
Signed-off-by: Alexandre Belloni
---
Cc: Jean-Christophe Plagniol-Villard
arch/arm/boot/dts/at91rm9200.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/at91rm9200.dtsi
b/arch/arm/boot/dts/at91rm9200.dtsi
The RTC needs an input clock, it is the slow clock. It is required as it
will not function without it.
Signed-off-by: Alexandre Belloni
---
Cc: Alessandro Zummo
Cc: rtc-li...@googlegroups.com
Documentation/devicetree/bindings/rtc/atmel,at91rm9200-rtc.txt | 2 ++
1 file changed, 2 insertions(+)
Hi,
It was discovered that all the slow clock user were not properly claiming it.
This can end up in a system hang because the last registered user is releasing
it, and it gets disabled.
commit dca1a4b5ff6e ("clk: at91: keep slow clk enabled to prevent system hang")
was a workaround. This series
The watchdog, the reset controller, the RTC, the real-time timer and the
shutdown controller need the slow clock, add it where necessary.
Signed-off-by: Alexandre Belloni
---
Cc: Jean-Christophe Plagniol-Villard
arch/arm/boot/dts/at91sam9g45.dtsi | 4
1 file changed, 4 insertions(+)
diff
The watchdog, the reset controller, the two real-time timers and the
shutdown controller need the slow clock, add it where necessary.
Signed-off-by: Alexandre Belloni
---
Cc: Jean-Christophe Plagniol-Villard
arch/arm/boot/dts/at91sam9263.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff
The watchdog, the reset controller, the real-time timer and the shutdown
controller need the slow clock, add it where necessary.
Signed-off-by: Alexandre Belloni
---
Cc: Jean-Christophe Plagniol-Villard
arch/arm/boot/dts/at91sam9261.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git
The watchdog, the reset controller, the RTC and the shutdown controller
need the slow clock, add it where necessary.
Signed-off-by: Alexandre Belloni
---
Cc: Jean-Christophe Plagniol-Villard
arch/arm/boot/dts/sama5d3.dtsi | 4
1 file changed, 4 insertions(+)
diff --git
The watchdog, the reset controller, the RTC and the shutdown controller
need the slow clock, add it where necessary.
Signed-off-by: Alexandre Belloni
---
Cc: Jean-Christophe Plagniol-Villard
arch/arm/boot/dts/at91sam9n12.dtsi | 4
1 file changed, 4 insertions(+)
diff --git
The watchdog, the reset controller, the RTC and the shutdown
controller need the slow clock, add it where necessary.
Signed-off-by: Alexandre Belloni
---
Cc: Jean-Christophe Plagniol-Villard
arch/arm/boot/dts/sama5d4.dtsi | 4
1 file changed, 4 insertions(+)
diff --git
Sort included headers alphabetically.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-at91sam9.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/rtc/rtc-at91sam9.c b/drivers/rtc/rtc-at91sam9.c
index 0a8485ac3864..23f721d049b2 100644
---
The watchdog, the reset controller, the RTC and the shutdown controller
need the slow clock, add it where necessary.
Signed-off-by: Alexandre Belloni
---
Cc: Jean-Christophe Plagniol-Villard
arch/arm/boot/dts/at91sam9x5.dtsi | 4
1 file changed, 4 insertions(+)
diff --git
rtc->sclk necessarily points to a valid clocks at this point. Else the
probe would have aborted.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-at91sam9.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-at91sam9.c b/drivers/rtc/rtc-at91sam9.c
index
We will need this calculation in other places, so
create functions to map between register value and uA value.
Acked-by: Pavel Machek
Signed-off-by: NeilBrown
---
drivers/power/twl4030_charger.c | 48 ---
1 file changed, 35 insertions(+), 13 deletions(-)
Sort included headers alphabetically.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-at91rm9200.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/rtc/rtc-at91rm9200.c b/drivers/rtc/rtc-at91rm9200.c
index 8093d9e50619..cb62e214b52a 100644
---
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
The twl4030 charger has two current sources, 'USB' and 'AC'
(presumably "Accessory Charger" because it isn't Alternating Current).
If 'AC' is providing current, we should set the current limit
differently to when it isn't (and so USB is used).
So split 'cur' into 'usb_cur' and 'ac_cur' and use
'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.
Acked-by: Pavel Machek
Signed-off-by:
On 30/07/2015 00:13, Andy Lutomirski wrote:
> On Wed, Jul 29, 2015 at 4:02 PM, Andrew Cooper
> wrote:
>> On 29/07/2015 23:49, Boris Ostrovsky wrote:
>>> On 07/29/2015 06:46 PM, David Vrabel wrote:
On 29/07/2015 23:11, Andrew Cooper wrote:
> On 29/07/2015 23:05, Andy Lutomirski wrote:
On Wed, Jul 29, 2015 at 12:36 PM, Josh Boyer wrote:
> On Wed, Jul 29, 2015 at 11:32 AM, Ming Lei wrote:
>> On Wed, Jul 29, 2015 at 9:51 AM, Johannes Weiner wrote:
>>> On Wed, Jul 29, 2015 at 09:27:16AM -0400, Josh Boyer wrote:
Hi All,
We've gotten a report[1] that any of the
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Jeff Moyer
> Sent: Wednesday, July 29, 2015 11:53 AM
> To: Christoph Hellwig
> Cc: Jens Axboe ; linux-kernel@vger.kernel.org;
> dmilb...@redhat.com
Adding
Quoting Lee Jones (2015-07-22 06:04:10)
> Lots of platforms contain clocks which if turned off would prove fatal.
> The only way to recover from these catastrophic failures is to restart
> the board(s). Now, when a clock provider is registered with the
> framework it is possible for a list of
On 07/29, James Liao wrote:
> From: Sascha Hauer
>
> On the MT8173 the clocks are provided by different units. To enable
> the critical clocks we must be sure that all parent clocks are already
> registered, otherwise the parents of the critical clocks end up being
> unused and get disabled
The usb phy driver already determines when VBUS is available,
so repeating the test in the charger driver is pointless duplication.
On probe, process the last event from the phy, and from then on,
do whatever the phy tells us without double-checking.
Signed-off-by: NeilBrown
---
'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.
Acked-by: Pavel Machek
Signed-off-by: NeilBrown
---
This allows AC charging to be turned off, much like usb charging.
"continuous" mode is not available though.
Acked-by: Pavel Machek
Signed-off-by: NeilBrown
---
.../ABI/testing/sysfs-class-power-twl4030 | 10 ++
drivers/power/twl4030_charger.c| 35
1 - 100 of 1826 matches
Mail list logo
