Jan,
having run into that warning too, I looked into it a little, and now
having found that patch am pretty uncertain: Both truncate_setsize()
and pagecache_isize_extended() document that they want to be
called with i_mutex held, so removing the WARN_ON() alone seems
either incomplete or wrong.
On Mon, Nov 03, 2014 at 10:32:30AM -0600, Felipe Balbi wrote:
> From: George Cherian
>
> Add support for using cable names. Enables other drivers to register interest
> and get notified using extcon provided notifier call backs.
>
> Signed-off-by: George Cherian
> Signed-off-by: Sekhar Nori
I agree that there should be a generic fake getgeo routine; but fixing that is
a topic for a different patchset and it doesn't need to get folded into this
driver submission process.
-Original Message-
From: Elliott, Robert (Server Storage) [mailto:elli...@hp.com]
Sent: Saturday,
On Mon, Nov 3, 2014 at 2:15 PM, Lee Jones wrote:
> /* Clean up the mailbox interrupts after pre-kernel code. */
> @@ -3179,15 +3179,14 @@ static int db8500_prcmu_probe(struct platform_device
> *pdev)
> irq = platform_get_irq(pdev, 0);
> if (irq <= 0) {
Shouldn't this be
From: George Cherian
Add device tree support to extcon-gpio driver.
Add devicetree binding documentation
Cc: devicet...@vger.kernel.org
Signed-off-by: George Cherian
Signed-off-by: Sekhar Nori
Signed-off-by: Felipe Balbi
---
.../devicetree/bindings/extcon/extcon-gpio.txt | 21 ++
Hi,
this series has been tested with v3.18-rc2 with a
yet-to-be-released board (called X15). That board
is DT-only and we use extcon-gpio to decide which
USB mode should be used (host or peripheral).
George Cherian (4):
extcon: gpio: Convert the driver to use gpio desc API's
extcon: gpio:
From: George Cherian
Some gpio's can sleep while reading, so always use gpio_get_value_cansleep
to get data. This fixes warning from gpiolib due to wrong API usage.
Reviewed-by: Roger Quadros
Signed-off-by: George Cherian
Signed-off-by: Sekhar Nori
Signed-off-by: Felipe Balbi
---
From: George Cherian
Add support for using cable names. Enables other drivers to register interest
and get notified using extcon provided notifier call backs.
Signed-off-by: George Cherian
Signed-off-by: Sekhar Nori
---
Documentation/devicetree/bindings/extcon/extcon-gpio.txt | 2 ++
From: George Cherian
Convert the driver to use gpiod_* API's.
Reviewed-by: Roger Quadros
Signed-off-by: George Cherian
Signed-off-by: Sekhar Nori
Signed-off-by: Felipe Balbi
---
drivers/extcon/extcon-gpio.c | 16 ++--
1 file changed, 6 insertions(+), 10 deletions(-)
diff --git
From: Clemens Ladisch
Date: Mon, 03 Nov 2014 10:44:40 +0100
> David Miller wrote:
>> I'd also rather the kernel use Kconfig based symbols to detect for
>> arch availability of feature X or Y, assuming things are CPP symbols
>> is very fragile at best.
>
> It is certainly possible to use
On Mon, Nov 03, 2014 at 05:10:35PM +0100, SF Markus Elfring wrote:
> > I agree with your proposed debug_unregister() changes, but not with your
> > kfree_fsm() change.
>
> Why do you want to keep an additional null pointer check before the call
> of the kfree_fsm() function within the
On Tue, Oct 21, 2014 at 12:22:23PM -0500, Nishanth Menon wrote:
> On 15:37-20141021, Mugunthan V N wrote:
> > Nishanth
> >
> > On Tuesday 21 October 2014 03:30 PM, Mugunthan V N wrote:
> > > Adding device tree entry for CPSW to make it work in Dual EMAC mode.
> > > These patches were tested with
On Sat, Nov 01, 2014 at 02:29:42AM +0200, Laurent Pinchart wrote:
> Hi Krzysztof,
>
> On Friday 31 October 2014 15:40:16 Krzysztof Kozlowski wrote:
> > On pią, 2014-10-31 at 15:22 +0100, Pavel Machek wrote:
> > > On Fri 2014-10-31 10:14:55, Krzysztof Kozlowski wrote:
> > >> On pon, 2014-10-20 at
On Mon, Nov 03, 2014 at 04:55:12PM +0100, SF Markus Elfring wrote:
> > This one is buggy.
>
> I am still interested to clarify this opinion a bit more.
>
After your patch then it will print warning messages.
The truth is I think that all these patches are bad and they make the
code harder to
Em Sat, Nov 01, 2014 at 01:30:39AM -0400, Vince Weaver escreveu:
> On Fri, 31 Oct 2014, Stephane Eranian wrote:
>
> > On Fri, Oct 31, 2014 at 1:28 PM, Matt Fleming
> > wrote:
> > >
> > > I guess we'd run into a problem if userspace doesn't want to just print
> > > the kernel string but instead
On Fri, Oct 31, 2014 at 10:41:47AM +0100, Jean Delvare wrote:
> Hi Michael,
>
> On Fri, 31 Oct 2014 17:45:22 +1100, Michael Ellerman wrote:
> > Because we build kernels with drivers built in for many platforms, it's
> > normal for the ibmpowernv driver to be loaded on systems that don't have
> >
I really wish people wouldn't use my Exchange email address for patches. It's
completely impossible to have a meaningful conversation this way. I've
resorted to inserting extra quotation marks by hand so people can stand at
least some chance of understanding what the hell's going on.
> >
On Mon, Nov 03, 2014 at 03:42:55PM +0100, Kamil Debski wrote:
> The state of a PWM output is not clearly defined after resume. Some PWM
> drivers do not restore the duty cycle upon resume, thus it is necessary to
> manually restore the correct value.
>
> Signed-off-by: Kamil Debski
Applied.
Em Mon, Nov 03, 2014 at 09:11:18PM +0900, Masami Hiramatsu escreveu:
> (2014/10/31 21:13), Arnaldo Carvalho de Melo wrote:
> > Em Fri, Oct 31, 2014 at 02:51:29PM -0400, Masami Hiramatsu escreveu:
> >> p:probe/reset_early_page_tables _text+12980741
> >> p:probe/copy_bootdata _text+12980830
From: Torsten Fleischer
In order to describe a single slave device that has no chip select line
the 'num-chipselects' property has to be <0> and the 'cs-gpios' property
doesn't need to be set.
Signed-off-by: Torsten Fleischer
---
Documentation/devicetree/bindings/spi/spi-gpio.txt | 6 --
Building with the attached random configuration file,
fs/open.c: In function ‘SYSC_fchmod’:
fs/open.c:530:3: error: implicit declaration of function ‘audit_file’
[-Werror=implicit-function-declaration]
audit_file(f.file);
^
cc1: some warnings being treated as errors
make[1]: *** [fs/open.o]
Also rid superfluous gotos and label.
Cc: Linus Walleij
Signed-off-by: Lee Jones
---
drivers/mfd/db8500-prcmu.c | 19 ---
1 file changed, 8 insertions(+), 11 deletions(-)
diff --git a/drivers/mfd/db8500-prcmu.c b/drivers/mfd/db8500-prcmu.c
index 89ae8bf..a820473 100644
---
On 3 November 2014 16:51, Peter Zijlstra wrote:
> On Fri, Oct 31, 2014 at 09:47:32AM +0100, Vincent Guittot wrote:
>> The call to arch_scale_frequency_capacity in the rt scheduling path might be
>> a concern for RT folks because I'm not sure whether we can rely on
>> arch_scale_freq_capacity to
> I agree with your proposed debug_unregister() changes, but not with your
> kfree_fsm() change.
Why do you want to keep an additional null pointer check before the call
of the kfree_fsm() function within the implementation of the
netiucv_free_netdevice() function?
Regards,
Markus
--
To
Andrzej Hajda writes:
> On 10/30/2014 08:36 AM, Krzysztof Kozlowski wrote:
>> On śro, 2014-10-29 at 10:46 -0700, Kevin Hilman wrote:
>>> Krzysztof Kozlowski writes:
>>>
When resuming the system the power domain has to be powered on early so
any runtime PM aware devices could resume.
On 11/03/2014 04:59 PM, Mark Brown wrote:
> No, it's only *currently* used for that. If we don't bother passing the
> descriptor in then future additions which make use of it (including
> adding mode operations to existing drivers) won't work and it might not
> be obvious why.
>
fair enough.
>
16z135 IP Core has changed so the driver needs to be updated to respect
these changes. The following changes have been made:
* Don't invert the 16z135 modem status register when reading.
* Add module parameter to configure the (baud rate dependent) RX timeout.
Character timeout in seconds =
Hi,
On Fri, Oct 31, 2014 at 09:27:43AM +0530, Kiran Raparthy wrote:
> >>> Thank you very much for taking time in reviewing the patch.
> >>> I will try to improve the patch as per your suggestions.
> >>> however,i have few queries which i wanted to understand from you.
> >>
> >> sure thing.
> >>
>
Hi,
On Thu, Oct 09, 2014 at 03:21:51PM +0200, Robert Baldyga wrote:
> Since we can compose gadgets from many functions, there is the problem
> related to gadget breakage while FunctionFS daemon being closed. FFS
> function is userspace code so there is no way to know when it will close
> files
On Mon, Nov 03, 2014 at 10:45:14AM +, Stefano Stabellini wrote:
> On Mon, 27 Oct 2014, Stefano Stabellini wrote:
> > Introduce an arch specific function to find out whether a particular dma
> > mapping operation needs to bounce on the swiotlb buffer.
> >
> > On ARM and ARM64, if the page
Winkle is a deep idle state supported in power8 chips. A core enters
winkle when all the threads of the core enter winkle. In this state
power supply to the entire chiplet i.e core, private L2 and private L3
is turned off. As a result it gives higher powersavings compared to
sleep.
But entering
From: Paul Mackerras
Currently, when going idle, we set the flag indicating that we are in
nap mode (paca->kvm_hstate.hwthread_state) and then execute the nap
(or sleep or rvwinkle) instruction, all with the MMU on. This is bad
for two reasons: (a) the architecture specifies that those
From: "Preeti U. Murthy"
The secondary threads should enter deep idle states so as to gain maximum
powersavings when the entire core is offline. To do so the offline path
must be made aware of the available deepest idle state. Hence probe the
device tree for the possible idle states in powernv
Deep idle states like sleep and winkle are per core idle states. A core
enters these states only when all the threads enter either the
particular idle state or a deeper one. There are tasks like fastsleep
hardware bug workaround and hypervisor core state save which have to be
done only by the last
On Mon, Nov 03, 2014 at 03:40:47PM +0100, Javier Martinez Canillas wrote:
> All function dealing with operating modes use unsigned int for modes
> so change max77802_map_mode() function signature for consistency.
Applied, thanks.
signature.asc
Description: Digital signature
On Mon, Nov 03, 2014 at 03:54:43PM +, Mark Brown wrote:
> On Mon, Nov 03, 2014 at 03:40:35PM +0100, Javier Martinez Canillas wrote:
> > Hello Mark,
> >
> > This is the fourth version of the series that adds operating modes
> > support for the regulators in the max77802 PMIC. This version uses
On Mon, Oct 27, 2014 at 09:48:39PM +0100, Roman Byshko wrote:
> musb registers can be dumped using the file regdump
> which is created in debugfs. Up to now hard coded
> register addresses are used for that. Different glue
> layers however have different register addresses. The
> patch addresses
On Sun, 02 Nov 2014, Tony Lindgren wrote:
> Commit e7cd1d1eb16f ("mfd: twl4030-power: Add generic reset
> configuration") accidentally removed the compatible flag for
> "ti,twl4030-power" that should be there as documented in the
> binding.
>
> If "ti,twl4030-power" only the poweroff
Deep idle states like sleep and winkle are per core idle states. A core
enters these states only when all the threads enter either the particular
idle state or a deeper one. There are tasks like fastsleep hardware bug
workaround and hypervisor core state save which have to be done only by
the last
On 11/03/2014 04:54 PM, Mark Brown wrote:
>
> No, it's not. This is a a patch series doing a whole bunch of different
> things, there's at least bug fixes to existing drivers, new features and
> also this new driver in what I've glanced at so far. These things
> shouldn't just be being thrown
On 11/03/2014 08:49 AM, Herbert Xu wrote:
On Mon, Nov 03, 2014 at 03:18:29PM +0100, Stephan Mueller wrote:
+ * CRYPTO_ALG_TYPE_DIGEST Raw message digest
+ * CRYPTO_ALG_TYPE_HASHAlias for CRYPTO_ALG_TYPE_DIGEST
+ * CRYPTO_ALG_TYPE_SHASH Synchronous multi-block hash
+
On Thu, 30 Oct 2014, Pramod Gurav wrote:
> Error check around return value of devm_ioremap is missing. Add the same
> to avoid NULL pointer dereference.
>
> Cc: Linus Walleij
> Cc: Samuel Ortiz
> Cc: Lee Jones
> Signed-off-by: Pramod Gurav
> ---
> drivers/mfd/db8500-prcmu.c |5 +
>
From: Rusty Russell
There's currently a big lock around everything, and it means that we
can't query sysfs (eg /sys/devices/virtual/misc/hw_random/rng_current)
while the rng is reading. This is a real problem when the rng is slow,
or blocked (eg. virtio_rng with qemu's default /dev/random
From: Rusty Russell
Interesting anti-pattern.
Signed-off-by: Rusty Russell
---
drivers/char/hw_random/core.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/char/hw_random/core.c b/drivers/char/hw_random/core.c
index c31bf91..fc5de7d 100644
---
From: Rusty Russell
The previous patch added one potential problem: we can still be
reading from a hwrng when it's unregistered. Add a wait for zero
in the hwrng_unregister path.
v4: add cleanup_done flag to insure that cleanup is done
Signed-off-by: Rusty Russell
Signed-off-by: Amos Kong
On Mon, Nov 03, 2014 at 04:48:34PM +0100, Javier Martinez Canillas wrote:
> On 11/03/2014 04:33 PM, Mark Brown wrote:
> > On Mon, Nov 03, 2014 at 03:40:38PM +0100, Javier Martinez Canillas wrote:
> >>if (!of_node_cmp(np->name, info->desc.name)) {
> >>
In next patch, we use reference counting for each struct hwrng,
changing reference count also needs to take mutex_lock. Before
releasing the lock, if we try to stop a kthread that waits to
take the lock to reduce the referencing count, deadlock will
occur.
Signed-off-by: Amos Kong
---
On Mon, Nov 03, 2014 at 03:40:44PM +0100, Javier Martinez Canillas wrote:
> The struct of_regulator_match rmatch[] is declared as a non-static local
> variable so the structure members are not auto-initialized.
Applied, thanks.
signature.asc
Description: Digital signature
From: Rusty Russell
Another interesting anti-pattern.
Signed-off-by: Rusty Russell
---
drivers/char/hw_random/core.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/char/hw_random/core.c b/drivers/char/hw_random/core.c
index fc5de7d..b2cc8a1 100644
---
On Mon, Nov 03, 2014 at 03:40:43PM +0100, Javier Martinez Canillas wrote:
> The struct of_regulator_match rmatch[] is declared as a non-static local
> variable so the structure members are not auto-initialized.
Applied, thanks.
signature.asc
Description: Digital signature
When I hotunplug a busy virtio-rng device or try to access
hwrng attributes in non-smp guest, it gets stuck.
My hotplug tests:
| test 0:
| hotunplug rng device from qemu monitor
|
| test 1:
| guest) # dd if=/dev/hwrng of=/dev/null &
| hotunplug rng device from qemu monitor
|
| test 2:
|
From: Rusty Russell
current_rng holds one reference, and we bump it every time we want
to do a read from it.
This means we only hold the rng_mutex to grab or drop a reference,
so accessing /sys/devices/virtual/misc/hw_random/rng_current doesn't
block on read of /dev/hwrng.
Using a kref is
On Mon, Nov 03, 2014 at 03:40:41PM +0100, Javier Martinez Canillas wrote:
> The struct of_regulator_match is declared as a non-static local variable
> so the structure members are not auto-initialized.
Applied, thanks.
signature.asc
Description: Digital signature
On Mon, Nov 03, 2014 at 03:40:42PM +0100, Javier Martinez Canillas wrote:
> The struct of_regulator_match is declared as a non-static local variable
> so the structure members are not auto-initialized.
Applied, thanks.
signature.asc
Description: Digital signature
On Mon, Nov 03, 2014 at 03:40:35PM +0100, Javier Martinez Canillas wrote:
> Hello Mark,
>
> This is the fourth version of the series that adds operating modes
> support for the regulators in the max77802 PMIC. This version uses
No, it's not. This is a a patch series doing a whole bunch of
> This one is buggy.
I am still interested to clarify this opinion a bit more.
> I'm sorry, but please stop sending these.
I am going to improve more implementation details in affected source files.
> But for this one:
> 1) I don't know what the functions do so I have to look at the code.
I
On Fri, Oct 31, 2014 at 09:47:32AM +0100, Vincent Guittot wrote:
> The call to arch_scale_frequency_capacity in the rt scheduling path might be
> a concern for RT folks because I'm not sure whether we can rely on
> arch_scale_freq_capacity to be short and efficient ?
Well, you put it in quite a
On 11/03/2014 04:41 PM, Mark Brown wrote:
> On Mon, Nov 03, 2014 at 03:40:40PM +0100, Javier Martinez Canillas wrote:
>> The struct of_regulator_match rmatch[] is declared as a non-static local
>> variable so the structure members are not auto-initialized.
>
> Applied, thanks.
>
> This is a bug
"Elliott, Robert (Server Storage)" writes:
>> +config BLK_DEV_PMEM_COUNT
>> +int "Default number of PMEM disks"
>> +default "4"
>
> For real use I think a default of 1 would be better.
For "real" use, it will be the number of actual DIMMs, not a config
option, I would think. I don't
Hi,
On Mon, Nov 03, 2014 at 05:42:07PM +0200, Mika Westerberg wrote:
> On Mon, Nov 03, 2014 at 05:27:43PM +0200, Mika Westerberg wrote:
> > On Mon, Nov 03, 2014 at 09:00:48AM -0600, Felipe Balbi wrote:
> > > On Mon, Nov 03, 2014 at 11:24:02AM +0200, Mika Westerberg wrote:
> > > > On Fri, Oct 31,
On 11/03/2014 04:33 PM, Mark Brown wrote:
> On Mon, Nov 03, 2014 at 03:40:38PM +0100, Javier Martinez Canillas wrote:
>
>> for_each_child_of_node(nproot, np) {
>> if (!of_node_cmp(np->name, info->desc.name)) {
>> config->init_data =
>> -
On 11/03/2014 07:22 AM, Laszlo Ersek wrote:
On 10/27/14 14:44, Vitaly Kuznetsov wrote:
Guard against issuing unsupported REQ_FUA and REQ_FLUSH was introduced
in d11e61583 and was factored out into blkif_request_flush_valid() in
0f1ca65ee. However:
1) This check in incomplete. In case we
On 10/31/2014 02:41 PM, Dan Streetman wrote:
> In powerpc pseries platform dlpar operations, Use device_online() and
> device_offline() instead of cpu_up() and cpu_down().
>
> Calling cpu_up/down directly does not update the cpu device offline
> field, which is used to online/offline a cpu from
On Mon, Nov 03, 2014 at 10:41:02AM -0500, Alan Stern wrote:
> Bear in mind, however, that once the irq_safe flag has been set, the
> runtime PM core offers no way to turn it off again.
Ah, I thought it did permit it to change both ways. In that case, we
don't need to validate that it doesn't
On Mon, Nov 3, 2014 at 7:20 AM, Al Viro wrote:
> On Mon, Nov 03, 2014 at 11:48:23AM +, David Drysdale wrote:
>> Add a new O_BENEATH flag for openat(2) which restricts the
>> provided path, rejecting (with -EACCES) paths that are not beneath
>> the provided dfd. In particular, reject:
>> -
On Mon, Nov 03, 2014 at 03:40:40PM +0100, Javier Martinez Canillas wrote:
> The struct of_regulator_match rmatch[] is declared as a non-static local
> variable so the structure members are not auto-initialized.
Applied, thanks.
This is a bug fix not *that* closely related to the rest of the
Hi Rafael, Simon, Magnus,
This patch series enables DT support for PM domains on Renesas R-Mobile SoCs.
Currently it's limited to R-Mobile A1 (r8a7740), but given the similarity of
the SYSC System-Controller on the various SH-Mobile/R-Mobile SoCs, and the
abstraction of PM domains in DT,
On Mon, Nov 03, 2014 at 05:27:43PM +0200, Mika Westerberg wrote:
> On Mon, Nov 03, 2014 at 09:00:48AM -0600, Felipe Balbi wrote:
> > On Mon, Nov 03, 2014 at 11:24:02AM +0200, Mika Westerberg wrote:
> > > On Fri, Oct 31, 2014 at 11:45:09AM -0700, David Cohen wrote:
> > > > > I think adding the
On Mon, 3 Nov 2014, Russell King - ARM Linux wrote:
> That makes it pretty horrid from the point of view of having bus
> management code, because we now have the management of the bus clock
> split between the bus layer and the device driver.
>
> This is /really/ a problem for runtime PM.
Hi Rafael,
While reviewing and testing these patches I ran into serious bugs in
the string parsers (in both the existing code and the new functions
here). It took me a number of days, but I've got a fix now which I'll
be posting shortly and I want to get into mainline right away. I'll cc
you when
PM domain power on/off-latencies are properties of the hardware.
In legacy code, they're specified from platform code.
On DT platforms, their values should come from DT.
Signed-off-by: Geert Uytterhoeven
Acked-by: Kevin Hilman
Reviewed-by: Ulf Hansson
---
v4:
- Add Reviewed-by,
- Replace
Hi,
On Mon, Nov 03, 2014 at 05:27:43PM +0200, Mika Westerberg wrote:
> On Mon, Nov 03, 2014 at 09:00:48AM -0600, Felipe Balbi wrote:
> > On Mon, Nov 03, 2014 at 11:24:02AM +0200, Mika Westerberg wrote:
> > > On Fri, Oct 31, 2014 at 11:45:09AM -0700, David Cohen wrote:
> > > > > I think adding the
Populate the PM domains from DT, and provide support to hook up devices
to their respective PM domain.
The always-on power area (e.g. C5 on r8a7740) is created as a PM domain
without software control, to allow Run-Time management of module clocks
for hardware blocks inside this area.
If the default PM domain using PM_CLK is used for PM runtime, the real PM
domain(s) cannot be registered from DT later.
Hence do not enable it when running a multi-platform kernel with genpd
support on an r8a7740. The R-Mobile PM domain driver will take care of
PM runtime management of the module
Replace the hardcoded addresses for accessing the SYSC PM domain
registers by register offsets, relative to the SYSC base address stored
in struct rmobile_pm_domain.
In the future, the SYSC base address will come from DT.
Signed-off-by: Geert Uytterhoeven
Reviewed-by: Ulf Hansson
---
v4:
-
Use the just introduced genpd attach/detach callbacks to register the
devices' module clocks, instead of doing it directly, to make it
DT-proof.
Signed-off-by: Geert Uytterhoeven
Reviewed-by: Ulf Hansson
---
v4:
- Add Reviewed-by,
- Add missing pm_clk_create()/pm_clk_destroy() calls,
-
Add a device node for the System Controller, with subnodes that
represent the hardware power area hierarchy.
Hook up all devices to their respective PM domains.
Add a minimal device node for the Coresight-ETM hardware block, and hook
it up to the D4 PM domain, so the R-Mobile System Controller
If CONFIG_PM_RUNTIME is not set, the clocks must be enabled before the
devices can be used.
Currently these clocks are enabled by the !CONFIG_PM_RUNTIME version of
pm_clk_notify, activated by the hack in drivers/sh/pm_runtime.c, but
this will go away soon (at least for DT).
On detach, disabling
From: Ulf Hansson
Convert the prototype to return and int. This is just an initial step,
needed to support error handling.
Signed-off-by: Ulf Hansson
Acked-by: Geert Uytterhoeven
Acked-by: Pavel Machek
Acked-by: Kevin Hilman
Signed-off-by: Geert Uytterhoeven
---
Prerequisite
Ulf wrote:
The Renesas R-Mobile System Controller provides a.o. power management
support, following the generic PM domain bindings in
Documentation/devicetree/bindings/power/power_domain.txt.
For now this supports the R-Mobile A1 (r8a7740) only, but it should be
sufficiently generic to handle other members
On Mon, Nov 03, 2014 at 03:40:38PM +0100, Javier Martinez Canillas wrote:
> for_each_child_of_node(nproot, np) {
> if (!of_node_cmp(np->name, info->desc.name)) {
> config->init_data =
> - of_get_regulator_init_data(>dev, np);
>
On Fri, Oct 31, 2014 at 2:20 PM, Felipe Balbi wrote:
> [Me]
>> But another way to get rid of the dilemma is to set
>> .suppress_bind_attrs = true on the .driver field of the
>> device driver. The one can't unbind it through sysfs anymore.
>>
>> .driver = {
>> .name =
On Sun, 02 Nov 2014, Tony Lindgren wrote:
> Commit e7cd1d1eb16f ("mfd: twl4030-power: Add generic reset
> configuration") enabled configuring the PM features for twl4030.
>
> This caused poweroff command to fail on devices that have the
> BCI charger on twl4030 wired, or have power wired for
On Mon, 2014-11-03 at 13:31 +0800, chenweilong wrote:
> Hi Eric,
>
> I check the code and find that:
>
> 1.In function "tcp_rcv_state_process",
> the "tcp_initialize_rcv_mss" is called at "step 5: check the ACK field" when
> the sk->sk_state is TCP_SYN_RECV
> and there is a
On 03/11/2014 14:44, Ben Hutchings wrote:
>> You can just use the same scheme as your patch 88/102:
> Why is that? Why should I not use the upstream version?
Because it makes no sense to invalidate nested EPT page tables, if the
kernel cannot make nested EPT page tables in the first place.
I
On Fri, Oct 31, 2014 at 09:47:29AM +0100, Vincent Guittot wrote:
> @@ -6414,11 +6399,12 @@ static inline void calculate_imbalance(struct lb_env
> *env, struct sd_lb_stats *s
>*/
> if (busiest->group_type == group_overloaded &&
> local->group_type == group_overloaded) {
>
> > This isn't unreasonable but there are drivers with userspace helpers that
> > use iopl/ioperm type functionality where you should be doing a SELECT of
> > X86_IOPORT. The one that comes to mind is the uvesa driver. From a quick
> > scan it may these days be the only mainstream one that needs
On Sat 01-11-14 23:14:20, Johannes Weiner wrote:
> There is no cgroup-specific page lock anymore.
>
> Signed-off-by: Johannes Weiner
Acked-by: Michal Hocko
> ---
> mm/memcontrol.c | 4
> 1 file changed, 4 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index
Hi,
On Fri, Oct 31, 2014 at 02:31:31PM -0500, Dinh Nguyen wrote:
> On 10/31/2014 12:42 PM, Felipe Balbi wrote:
> > Hi,
> >
> > On Fri, Oct 31, 2014 at 10:20:06AM -0500, Dinh Nguyen wrote:
> @@ -339,7 +339,8 @@ static void dwc2_handle_wakeup_detected_intr(struct
> dwc2_hsotg *hsotg)
>
On Mon, Nov 03, 2014 at 09:00:48AM -0600, Felipe Balbi wrote:
> On Mon, Nov 03, 2014 at 11:24:02AM +0200, Mika Westerberg wrote:
> > On Fri, Oct 31, 2014 at 11:45:09AM -0700, David Cohen wrote:
> > > > I think adding the module exit + allowing this driver to be a module
> > > > would be a good
On Mon, Nov 3, 2014 at 1:57 PM, Lee Jones wrote:
> On Mon, 03 Nov 2014, Linus Walleij wrote:
>
>> Lee, can Dmitry take these through input?
>
> That was weird, I replied at the same as as you sent this.
Synchronicity... :)
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line
From: Stanimir Varbanov
The voltage ADC is peripheral of Qualcomm SPMI PMIC chips. It has
15 bits resolution and register space inside PMIC accessible across
SPMI bus.
The vadc driver registers itself through IIO interface.
Signed-off-by: Stanimir Varbanov
Signed-off-by: Ivan T. Ivanov
---
On Tue, Oct 21, 2014 at 10:15:23PM +0800, Herbert Xu wrote:
> On Thu, Sep 18, 2014 at 12:18:24PM +0930, Rusty Russell wrote:
> > The previous patch added one potential problem: we can still be
> > reading from a hwrng when it's unregistered. Add a wait for zero
> > in the hwrng_unregister path.
>
Hi,
This is the forth version of this driver. V3 could be found here [1].
Changes since v3.
- Addressed review comments from Hartmut Knaack and Mark Rutland:
Better description of 'reg' property.
Add # to address-cells and size-cells DT document.
Dropped interrupt-names property, it was
From: Stanimir Varbanov
Document DT binding for Qualcomm SPMI PMIC voltage ADC
driver.
Signed-off-by: Stanimir Varbanov
Signed-off-by: Ivan T. Ivanov
---
.../devicetree/bindings/iio/adc/qcom,spmi-vadc.txt | 129 +
include/dt-bindings/iio/qcom,spmi-vadc.h | 119
On Mon, Nov 03, 2014 at 09:32:23AM -0500, Prarit Bhargava wrote:
[..]
> +
> +static int __init panic_on_warn_setup(char *s)
> +{
> + /* Enabling this on a kdump kernel could cause a bogus panic. */
> + if (!is_kdump_kernel())
> + panic_on_warn = 1;
I think it would be better
On Mon, Nov 03, 2014 at 11:48:23AM +, David Drysdale wrote:
> Add a new O_BENEATH flag for openat(2) which restricts the
> provided path, rejecting (with -EACCES) paths that are not beneath
> the provided dfd. In particular, reject:
> - paths that contain .. components
> - paths that begin
At Mon, 03 Nov 2014 07:08:08 -0800,
Joe Perches wrote:
>
> On Mon, 2014-11-03 at 15:17 +0100, Takashi Iwai wrote:
> > At Mon, 3 Nov 2014 16:04:12 +0530,
> > Sudip Mukherjee wrote:
> > >
> > > added reference of struct echoaudio to free_firmware function.
> > > this structure will be later used
On Mon, Nov 03, 2014 at 08:32:42AM -0500, Prarit Bhargava wrote:
>
>
> On 10/30/2014 09:58 PM, Hedi Berriche wrote:
> > On Thu, Oct 30, 2014 at 17:06 Prarit Bhargava wrote:
> > | There have been several times where I have had to rebuild a kernel to
> > | cause a panic when hitting a WARN() in
Hi Andrey,
On 10/29/2014 05:03 PM, Andrey Utkin wrote:
> The used approach actually cannot prevent new encoder interrupt to
> appear, because interrupt handler can execute in different thread, and
> in current implementation there is still race condition regarding this.
I don't understand what
601 - 700 of 2138 matches
Mail list logo
