While debugging some "sleeping function called from invalid context" bug I
realized that the debug message "Preemption disabled at:" pointed to an
incorrect function.
In particular if the function/action that disabled preemption was
spin_lock_bh() then current->preempt_disable_ip won't be updated.
On 2014/11/24 22:01, Yun Wu (Abel) wrote:
> On 2014/11/24 21:13, Thomas Gleixner wrote:
>
>> On Mon, 24 Nov 2014, Yun Wu (Abel) wrote:
>>> Hi Thomas, Jiang,
>>> On 2014/11/12 21:42, Thomas Gleixner wrote:
>>>
From: Jiang Liu
>>> [...]
/* Number of irqs reserved for a legacy isa
Add a PRE_DISABLE notification so that consumers can use a
notifier to run any steps required to prepare for the
regulator being switched off. Since the regulator disable
can fail an abort notification is also added.
Signed-off-by: Richard Fitzgerald
---
drivers/regulator/core.c |
2014-11-22 17:22+0100, Paolo Bonzini:
> On 21/11/2014 22:21, Radim Krčmář wrote:
> > - struct kvm_assigned_dev_kernel depends on struct kvm_irq_ack_notifier
>
> kvm_assign_device and kvm_deassign_device can also be moved to arch/x86,
> in a new assigned-dev.h header. The header could include
(CC'ed Shuah, since this is related to kselftest)
(2014/11/24 13:29), Steven Rostedt wrote:
> On Mon, 24 Nov 2014 11:50:06 +0900
> Masami Hiramatsu wrote:
>
>> (2014/11/22 6:03), Steven Rostedt wrote:
>>> On Fri, 21 Nov 2014 05:25:37 -0500
>>> Masami Hiramatsu wrote:
>>>
Add ftrace
On pseries system (LPAR) xmon failed to enter when running in LE mode, system
is hunging. Inititating xmon will lead to such an output on the console:
SysRq : Entering xmon
cpu 0x15: Vector: 0 at [c003f39ffb10]
pc: c007ed7c: sysrq_handle_xmon+0x5c/0x70
lr: c007ed7c:
On Thu, 2014-11-20 at 16:54 +, David Howells wrote:
>
> /*
> @@ -186,12 +81,8 @@ static struct key *request_asymmetric_key(const char
> *signer, size_t signer_len,
> */
> int mod_verify_sig(const void *mod, unsigned long *_modlen)
> {
> - struct public_key_signature *pks;
>
Hi.
With the libraries present in e2fsprogs, it is possible to open a plain file
(or any other reasonable storage) as an EXT2 filesystem and manipulate files
inside it.
Is it possible to use the implementations in the kernel to do the same thing
with any supported normal filesystem?
Obviously,
On 11/21/14, Anshuman Khandual wrote:
> On 11/14/2014 03:30 PM, Denis Kirjanov wrote:
>> On 11/13/14, Anshuman Khandual wrote:
>>> > On 11/11/2014 10:56 AM, Anshuman Khandual wrote:
>> This patch enables get and set of miscellaneous debug registers
>> through
>> ptrace
On 21 November 2014 at 13:35, Morten Rasmussen wrote:
> s/usage/utilization/ in subject.
>
> On Mon, Nov 03, 2014 at 04:54:39PM +, Vincent Guittot wrote:
>> From: Morten Rasmussen
>>
>> Adds usage contribution tracking for group entities. Unlike
>
> s/usage contribution/utilization/
>
>>
On 21 November 2014 at 13:34, Morten Rasmussen wrote:
> Should the subject mention that the patch adds utilization tracking?
> Maybe: 'sched: Add utilization tracking' ?
>
>
> On Mon, Nov 03, 2014 at 04:54:38PM +, Vincent Guittot wrote:
>> Add new statistics which reflect the average time a
I sent a patch [1] for unnecessary check in zsmalloc. And Minchan Kim
found zsmalloc even does not support allocating an obj with the size of
ZS_MAX_ALLOC_SIZE in some situations.
For example:
In system with 64KB PAGE_SIZE and 32 bit of physical addr. Then:
ZS_MIN_ALLOC_SIZE is 32 bytes
uninitialized_var() is not recommended to be used to
avoid compiler warnings
https://lkml.org/lkml/2012/10/27/71
So this patch initializes ret with *NOTIFY_OK*.
Signed-off-by: Mahendran Ganesh
---
mm/zsmalloc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 2014/11/24 21:13, Thomas Gleixner wrote:
> On Mon, 24 Nov 2014, Yun Wu (Abel) wrote:
>> Hi Thomas, Jiang,
>> On 2014/11/12 21:42, Thomas Gleixner wrote:
>>
>>> From: Jiang Liu
>>>
>> [...]
>>> /* Number of irqs reserved for a legacy isa controller */
>>> #define NUM_ISA_INTERRUPTS 16
>>> @@
This driver support setting the level shifter direction and/or enable
as needed.
Signed-off-by: Alban Bedel
---
drivers/gpio/Kconfig | 6 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-level-shifter.c | 248 ++
3 files changed,
Signed-off-by: Alban Bedel
---
.../devicetree/bindings/gpio/gpio-level-shifter.txt | 15 +++
1 file changed, 15 insertions(+)
create mode 100644
Documentation/devicetree/bindings/gpio/gpio-level-shifter.txt
diff --git
On Sunday 23 November 2014 18:40:46 Kevin Cernekee wrote:
> bmips_be_defconfig supports Linux running on the following CM and DSL
> SoCs:
>
> - BCM3384 (BMIPS5000) cable modem application processor, BE, SMP
> - BCM3384 (BMIPS4355) cable modem "spare CPU"*, BE
> - BCM6328 (BMIPS4355) ADSL chip,
Hi Lee Jones,
Thanks for the review and input. Here's the responses.
Warm Regards,
Raymond Tan
> -Original Message-
> From: Lee Jones [mailto:lee.jo...@linaro.org]
> Sent: Wednesday, November 19, 2014 1:22 AM
> To: Tan, Raymond
> Cc: Samuel Ortiz; linux-kernel@vger.kernel.org; Chen,
On Mon, Nov 24, 2014 at 7:25 AM, Mike Looijmans wrote:
> Building the adi_axi_hdmi driver as a module failed:
> ERROR: "drm_sysfs_connector_remove"
> [drivers/gpu/drm/adi_axi_hdmi/adi_axi_hdmi.ko] undefined!
>
> Mark drm_sysfs_connector_remove for export to fix this. Also mark
>
The memmove function never had unwinding annotations added.
Currently, when accessing invalid pointer by memmove occurs the
backtrace shown will stop at memmove or some completely unrelated
function. Add unwinding annotations in hopes of getting a more
useful backtrace in following cases:
1. die
Le 30/10/2014 19:41, Eric W. Biederman a écrit :
Nicolas Dichtel writes:
The goal of this serie is to be able to multicast netlink messages with an
attribute that identify a peer netns.
This is needed by the userland to interpret some informations contained in
netlink messages (like IFLA_LINK
Ping, I haven't heard anything on this.
-corey
On 11/14/2014 08:41 AM, miny...@acm.org wrote:
> From: Corey Minyard
>
> Some devices might need parameters to control their operation,
> add the ability to pass these parameters to the client.
>
> This also makes the parsing of sysfs-added I2C
On Mon, 2014-11-24 at 12:48 +, David Howells wrote:
> Mimi Zohar wrote:
>
> > Ok, PCKS#7 supports detached data. I assume this is not needed for
> > kernel modules. What is the motivation for adding this support to the
> > kernel?
>
> See patch #5. I should probably note that in the
Hi Seungwon,
Enabling UHS in dra7xx resulted in the below error (see blow). It was bisected
to
commit 5438ad95a57cbfd95708a5047a27ff3cce345b79
Author: Seungwon Jeon
Date: Fri Mar 14 21:12:27 2014 +0900
mmc: omap: clarify DDR timing mode between SD-UHS and eMMC
Replaced UHS_DDR50
Vivek Goyal wrote:
> A very minor nit. It might help if we put additional comment to explain what
> auth_id and auth_skid are composed of (like other key ids).
I thought it better to show what they match - ie. auth_id matches id and
auth_skid matches skid from the same structure. The id and
Hi Uwe,
On 11/23/2014 10:33 PM, Uwe Kleine-König wrote:
> On Fri, Nov 21, 2014 at 05:33:37PM +0200, Grygorii Strashko wrote:
>> On 11/21/2014 03:10 PM, Uwe Kleine-König wrote:
>>> On Fri, Nov 21, 2014 at 02:48:57PM +0200, Grygorii Strashko wrote:
On 11/21/2014 12:19 AM, Uwe Kleine-König
On Sunday 23 November 2014 18:40:35 Kevin Cernekee wrote:
> V2->V3:
>
> - Omit the BMIPS updates that have already been accepted into Ralf's tree.
>They are still needed, but not reposted.
>
> - Make USB endian swap options conditional on "if CPU_BIG_ENDIAN".
>
> - Remove board listing
(2014/11/24 20:13), Thomas Gleixner wrote:
> On Thu, 20 Nov 2014, Seth Jennings wrote:
>> This commit introduces code for the live patching core. It implements
>> an ftrace-based mechanism and kernel interface for doing live patching
>> of kernel and kernel module functions.
>>
>> It represents
On 21 November 2014 at 22:04, Doug Anderson wrote:
> Hi,
>
> On Fri, Nov 21, 2014 at 9:42 AM, Doug Anderson wrote:
>> Ulf,
>>
>> On Fri, Nov 21, 2014 at 4:06 AM, Ulf Hansson wrote:
>>> [...]
>>>
Sure
If the first card is sd2.0 since startup, dw_mci_switch_voltage will not
be
On Mon, Nov 24, 2014 at 02:26:08PM +0100, Thomas Gleixner wrote:
> On Mon, 24 Nov 2014, Jiri Kosina wrote:
> > On Mon, 24 Nov 2014, Thomas Gleixner wrote:
> > > How is determined whether a change can be applied w/o a consistency
> > > mechanism or not?
> >
> > By a human being producing the "live
Christian Borntraeger wrote:
> +#define get_scalar_volatile_pointer(x) ({ \
> + typeof(x) *__p = &(x); \
> + volatile typeof(x) *__vp = __p; \
> + (void)(long)*__p; __vp; })
> +#define ACCESS_ONCE(x) (*get_scalar_volatile_pointer(x))
Might this cause two loads from memory under some
On Mon, 24 Nov 2014, Thomas Gleixner wrote:
> > The person writing the patch would always need to understand what he is
> > doing to be able to pick correct consistency model to be used. I
> > personally think this is a good thing -- this is nothing where we should
> > be relying on any kinds
On Mon, 24 Nov 2014, Jiri Kosina wrote:
> On Mon, 24 Nov 2014, Thomas Gleixner wrote:
> > How is determined whether a change can be applied w/o a consistency
> > mechanism or not?
>
> By a human being producing the "live patch" code.
>
> If the semantics of the patch requires consistency
Hi Uwe,
On 11/23/2014 10:36 PM, Uwe Kleine-König wrote:
> On Fri, Nov 21, 2014 at 09:33:22PM +0200, Grygorii Strashko wrote:
>> On 11/21/2014 09:07 PM, Uwe Kleine-König wrote:
>>> On Thu, Nov 20, 2014 at 12:03:07PM +0200, Grygorii Strashko wrote:
>>> Just another general comment about the driver
From: Miklos Szeredi
If mount flags don't have MS_RDONLY, iso9660 returns EACCES without actually
checking if it's an iso image.
This tricks mount_block_root() into retrying with MS_RDONLY. This results
in a read-only root despite the "rw" boot parameter if the actual
filesystem was checked
On Mon, Nov 24, 2014 at 12:13:20PM +0100, Thomas Gleixner wrote:
> On Thu, 20 Nov 2014, Seth Jennings wrote:
> > This commit introduces code for the live patching core. It implements
> > an ftrace-based mechanism and kernel interface for doing live patching
> > of kernel and kernel module
Fastmap can miss a PEB if it is in the protection queue
and not jet in the used tree.
Treat every protected PEB as used.
Signed-off-by: Richard Weinberger
---
drivers/mtd/ubi/fastmap.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/mtd/ubi/fastmap.c
On 24 November 2014 at 01:34, Wanpeng Li wrote:
> Hi Vincent,
> On 5/28/14, 7:15 PM, Vincent Guittot wrote:
>>
>> On 28 May 2014 12:58, Peter Zijlstra wrote:
>>>
>>> On Fri, May 23, 2014 at 05:53:03PM +0200, Vincent Guittot wrote:
>
> [snip]
>>>
>>> Now I'm only struggling to understand the
ubi_wl_get_peb() has two problems, it reads the pool
size and usage counters without any protection.
While reading one value would be perfectly fine it reads multiple
values and compares them. This is racy and can lead to incorrect
pool handling.
Furthermore ubi_update_fastmap() is called without
On Mon, Nov 24, 2014 at 12:13:20PM +0100, Thomas Gleixner wrote:
> > This commit introduces code for the live patching core. It implements
> > an ftrace-based mechanism and kernel interface for doing live patching
> > of kernel and kernel module functions.
> >
> > It represents the greatest
Use power domain driver for Exynos7 SOC's
Signed-off-by: Amit Daniel Kachhap
---
arch/arm64/Kconfig |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 30bd4d5..b102d0b 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -154,6 +154,7 @@
Make it two functions, wl_get_wle() and wl_get_peb().
wl_get_peb() works exactly like __wl_get_peb() but wl_get_wle()
does not call produce_free_peb().
While refilling the fastmap user pool we cannot release ubi->wl_lock
as produce_free_peb() does.
Hence the fastmap logic uses now wl_get_wle().
...otherwise the deferred work might run after datastructures
got freed and corrupt memory.
Signed-off-by: Richard Weinberger
---
drivers/mtd/ubi/wl.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/mtd/ubi/wl.c b/drivers/mtd/ubi/wl.c
index 7f135df..cb2e571 100644
---
If the WL pool runs out of PEBs we schedule a fastmap write
to refill it as soon as possible.
Ensure that only one at a time is scheduled otherwise we might end in
a fastmap write storm because writing the fastmap can schedule another
write if bitflips are detected.
Signed-off-by: Richard
On Mon, Nov 24, 2014 at 01:58:50PM +0100, Romain Perier wrote:
> 2014-11-24 12:35 GMT+01:00 Johan Hovold :
> > You should also fix the commit message, which claims to define a "helper
> > function which is compatible with both properties", something which was
> > no longer the case.
> >
> So I
While turning power domain to on/off, some clocks rates might change and
need to be saved/restored in the Exynos7 SOC. This patch adds the
framework for saving those clocks before power off and restoring it back
after power on operation.
Signed-off-by: Amit Daniel Kachhap
---
While turning power domain to on/off, some clocks need to be enabled
in the Exynos7 SOC. This patch adds the framework for enabling those
clocks before on/off and restoring it back after the operation. Also
these list of clocks may be different for on/off operation so not using
the generic pm
Artem,
as requested I'm resending my fastmap work in smaller pieces.
This is pile 1 of 7.
Rebasing my patches to ubifs.git was a massive PITA because the
logging style changes touched a lot of code and almost every patch
failed to apply and needed inspection by hand.
The first patches are bug
On Mon, 24 Nov 2014, Thomas Gleixner wrote:
> > This commit introduces code for the live patching core. It implements
> > an ftrace-based mechanism and kernel interface for doing live patching
> > of kernel and kernel module functions.
> >
> > It represents the greatest common functionality set
Currently ubi_refill_pools() first fills the first and then
the second one.
If only very few free PEBs are available the second pool can get
zero PEBs.
Change ubi_refill_pools() to distribute free PEBs fair between
all pools.
Signed-off-by: Richard Weinberger
---
drivers/mtd/ubi/wl.c | 77
Hi,
On Monday, November 24, 2014 07:36:10 AM Amit Daniel Kachhap wrote:
> This patch series [1 - 5] performs,
>
> 1) Moves pmu driver to driver/soc/samsung folder. This is needed as exynos7 is
>an arm64 based platform and hence PMU driver should be in driver folder.
>Some discussion
This patch updates the parent clock bindings to make it more generic.
The current bindings limits the transient parent clocks to just one
clock as "oscclk". This patch extends it to allow any clock as
intermediate parent clock.
The reparent clock sets are of form tclkX, pclkX, clkX where X:0-9.
This patch adds supports for parent power domain. This will ensure
invoking of parent/child power domain on/off in a correct sequence.
In exynos7 SOC's, power domain controllers have parent and child
hierarchy.
Cc: Kukjin Kim
Signed-off-by: Amit Daniel Kachhap
---
This API may be needed to set the power domain parent/child relationship
in the power domain platform driver. The parent relationship is
generally set after the child power domain is registered with the power
domain subsystem. In this case, pm_genpd_lookup_name API might be
useful.
Signed-off-by:
Hi Uwe,
On 11/23/2014 07:04 PM, Uwe Kleine-König wrote:
> On Thu, Nov 20, 2014 at 12:03:08PM +0200, Grygorii Strashko wrote:
>> @@ -664,6 +759,7 @@ static int davinci_i2c_probe(struct platform_device
>> *pdev)
>> if (!of_property_read_u32(pdev->dev.of_node, "clock-frequency",
>>
On 11/24/2014 01:11 PM, Ondrej Zary wrote:
> Add read-only support for EEPROMs configured in 8-bit mode (ORG pin connected
> to GND).
> This will be used by wd719x driver.
>
> Signed-off-by: Ondrej Zary
Reviewed-by: Hannes Reinecke
Cheers,
Hannes
--
Dr. Hannes Reinecke
This patch uses the restructuring done in PD handlers and adds PD
on/off/status handlers for exynos7. In this SoC, some extra settings
need to be done prior to turning on/off power domains. Some of those
settings are also different from different power domains so is uses
the power domain
On 11/24/2014 01:11 PM, Ondrej Zary wrote:
> Introduce wd719x, a driver for Western Digital WD7193, WD7197 and WD7296 PCI
> SCSI controllers based on WD33C296A chip.
> Tested with WD7193 card.
>
> Reviewed-by: Christoph Hellwig
> Signed-off-by: Ondrej Zary
> ---
> drivers/scsi/Kconfig |8
This patch adds support for second optional compatible complate name. If
this compatible name is present then this name will be used to create
the Power Domain and not the DT node name. This will be useful to carry
out any power domain specific changes in the PD on/off handlers for new
SoCs.
This
This patch moves PD domain on/off implementation inside the PMU driver.
The handlers will be supplied via the MFD platform data. Power domains
are basically sparse memories in the Exynos PMU controllers, so with
this restructuring all the register access operations reside inside pmu
file.
This
BUS1 pinctrl provides gpios for usb and power regulator
available on exynos7-espresso board. So add relevant device
node for pinctrl-bus1.
Signed-off-by: Naveen Krishna Ch
Signed-off-by: Vivek Gautam
---
This patch was part of series:
"[PATCH 00/11] Exynos7: Adding USB 3.0 support"
On Mon, 24 Nov 2014, Yun Wu (Abel) wrote:
> Hi Thomas, Jiang,
> On 2014/11/12 21:42, Thomas Gleixner wrote:
>
> > From: Jiang Liu
> >
> [...]
> > /* Number of irqs reserved for a legacy isa controller */
> > #define NUM_ISA_INTERRUPTS 16
> > @@ -64,6 +66,16 @@ struct irq_domain_ops {
> >
This is used to probe exynos power domain. This method can be also used
for probing other PMU client drivers like pm sleep etc. Currently no
platform data is supplied but can be easily extended when required.
Reviewed-by: Pankaj Dubey
Signed-off-by: Amit Daniel Kachhap
---
This patch moves arch/arm/mach-exynos/pm_domains.c to driver/soc/samsung
folder. In this way it can be used for both arm and arm64 platforms.
This file is moved in this directory as this driver is soc specific and
only used by exynos platforms.
Cc: Kukjin Kim
Signed-off-by: Amit Daniel Kachhap
This patch modifies Exynos Power Domain driver initialization
implementation in following way:
- Added platform driver support and probe function where Exynos PM
Domain driver will finally register itself as MFD PMU client driver.
In this way,all the Exynos power domains are probed
On Thu, Nov 20, 2014 at 09:23:36PM +0530, Arjun Sreedharan wrote:
> When __of_usb_find_phy() fails, it returns -ENODEV - its
> error code has to be returned by devm_usb_get_phy_by_phandle().
> Only when the former function succeeds and try_module_get()
> fails should -EPROBE_DEFER be returned.
>
USB and Power regulator on Exynos7 require gpios available
in BUS1 pin controller block.
So adding the BUS1 pinctrl support.
Signed-off-by: Naveen Krishna Ch
Signed-off-by: Vivek Gautam
Cc: Linus Walleij
---
This patch was part of series:
"[PATCH 00/11] Exynos7: Adding USB 3.0 support"
Am Montag, 24. November 2014, 14:01:02 schrieb Romain Perier:
> 2014-11-24 13:58 GMT+01:00 Romain Perier :
> > So I need to resend this patch which would only introduce an helper
> > function which checks for "system-power-controller" property (it would
> > also have a new commit message).
> > As
ACCESS_ONCE does not work reliably on non-scalar types. For
example gcc 4.6 and 4.7 might remove the volatile tag for such
accesses during the SRA (scalar replacement of aggregates) step
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145)
Let's use a barrier instead of ACCESS_ONCE to avoid that
ACCESS_ONCE does not work reliably on non-scalar types. For
example gcc 4.6 and 4.7 might remove the volatile tag for such
accesses during the SRA (scalar replacement of aggregates) step
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145)
Change the spinlock code to access the union members with
As discussed on LKML http://marc.info/?i=54611D86.4040306%40de.ibm.com
ACCESS_ONCE might fail with specific compiler for non-scalar accesses.
Here is a set of patches to tackle that problem. (The first patch
is already in kvm/next).
The last patch will force ACCESS_ONCE to error-out if it is used
ACCESS_ONCE does not work reliably on non-scalar types. For
example gcc 4.6 and 4.7 might remove the volatile tag for such
accesses during the SRA (scalar replacement of aggregates) step
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145)
Let's change the code to access the page table elements
ipte_unlock_siif uses cmpxchg to replace the in-memory data of the ipte
lock together with ACCESS_ONCE for the intial read.
union ipte_control {
unsigned long val;
struct {
unsigned long k : 1;
unsigned long kh : 31;
unsigned long
On 11/24/2014 01:35 PM, Arnd Bergmann wrote:
On Monday 24 November 2014 12:39:12 Karol Wrona wrote:
It is possible that it can serve as input device sth else. So you are
right about MFD.
The structure of mfd directory is flat. I wonder what can be better:
just putting these sources inside mfd
ACCESS_ONCE does not work reliably on non-scalar types. For
example gcc 4.6 and 4.7 might remove the volatile tag for such
accesses during the SRA (scalar replacement of aggregates) step
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145)
Let's use a barrier instead of ACCESS_ONCE to avoid that
ACCESS_ONCE does not work reliably on non-scalar types. For
example gcc 4.6 and 4.7 might remove the volatile tag for such
accesses during the SRA (scalar replacement of aggregates) steps.
see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145
This patch is based on an initial proof-of-concept
ACCESS_ONCE does not work reliably on non-scalar types. For
example gcc 4.6 and 4.7 might remove the volatile tag for such
accesses during the SRA (scalar replacement of aggregates) step
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145)
Change the spinlock code to access the lock with a
Signed-off-by: Alban Bedel
---
.../devicetree/bindings/regulator/group.txt| 26 ++
1 file changed, 26 insertions(+)
create mode 100644 Documentation/devicetree/bindings/regulator/group.txt
diff --git a/Documentation/devicetree/bindings/regulator/group.txt
Signed-off-by: Alban Bedel
---
.../bindings/regulator/constrained-supply.txt | 29 ++
1 file changed, 29 insertions(+)
create mode 100644
Documentation/devicetree/bindings/regulator/constrained-supply.txt
diff --git
This driver is meant for devices that are supplied by a settable
regulator but that don't set their supply voltage explicitly.
With this reglator those simple driver can just get and enable the
regulator and they will get the correct voltage.
Signed-off-by: Alban Bedel
---
This driver allow using simple driver that expect a single regulator
on hardware that need to enable several regulators. Optionally the
driver can enforce the enable and disable order to provide a simple
power sequencing.
Signed-off-by: Alban Bedel
---
drivers/regulator/Kconfig | 8 +++
2014-11-24 13:58 GMT+01:00 Romain Perier :
> 2014-11-24 12:35 GMT+01:00 Johan Hovold :
>> On Mon, Nov 24, 2014 at 10:24:56AM +, Lee Jones wrote:
>>> On Fri, 21 Nov 2014, Johan Hovold wrote:
>>> > On Thu, Nov 13, 2014 at 01:34:58PM +, Auto Configured wrote:
>>> > > From: Romain Perier
>>>
Posting this series as RFC to get more clarity as lot of power domain related
discussion is happening in mailing lists.
This patch series[1 - 12] performs several implementations as listed below,
1) Converts power domain driver to platform driver.
2) Registers this driver as MFD client driver.
2014-11-24 12:35 GMT+01:00 Johan Hovold :
> On Mon, Nov 24, 2014 at 10:24:56AM +, Lee Jones wrote:
>> On Fri, 21 Nov 2014, Johan Hovold wrote:
>> > On Thu, Nov 13, 2014 at 01:34:58PM +, Auto Configured wrote:
>> > > From: Romain Perier
>> > >
>> > > It reverts commit a4b4e0461ec5 ("of:
On Mon, Nov 24, 2014 at 1:15 PM, Michael S. Tsirkin wrote:
> On Mon, Nov 24, 2014 at 01:03:24PM +0100, Geert Uytterhoeven wrote:
>> On Mon, Nov 24, 2014 at 12:52 PM, Michael S. Tsirkin wrote:
>> > virtio 1.0 makes all memory structures LE, so
>> > we need APIs to conditionally do a byteswap on
Dmitry Kasatkin wrote:
> Actually after cleaning the tree and re-signing the modules, I get following
>
> Unrecognized character \x7F; marked by <-- HERE after <-- HERE near
> column 1 at ./scripts/sign-file line 1.
> make[1]: *** [arch/x86/crypto/aes-x86_64.ko] Error 255
warthog>grep -r
Dmitry Kasatkin wrote:
> > (2) Makes use of the PKCS#7 facility to provide module signatures.
> >
> > sign-file is replaced with a program that generates a PKCS#7 message
> > that has no X.509 certs embedded and that has detached data (the
> > module content) and adds it onto the
Mimi Zohar wrote:
> Ok, PCKS#7 supports detached data. I assume this is not needed for
> kernel modules. What is the motivation for adding this support to the
> kernel?
See patch #5. I should probably note that in the commit message.
David
--
To unsubscribe from this list: send the line
On Mon, 24 Nov 2014, David Drysdale wrote:
> Hook up x86-64, i386 and x32 ABIs.
>
> Signed-off-by: David Drysdale
Reviewed-by: Thomas Gleixner
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info
Hello Vivek, Thierry,
On 11/24/2014 12:29 PM, Vivek Gautam wrote:
>> Yes. Back at the time a decision was made that device trees need to be
>> stable ABI because eventually they'd be shipped with the device rather
>> than the distribution. As such it may not at all be possible to update
>> them
FYI, we noticed the below changes on
commit 4ed2d765dfaccff5ebdac68e2064b59125033a3b ("net-timestamp: TCP
timestamping")
testbox/testcase/testparams: vm-vp-2G/ltp/syscalls
e7fd2885385157d4 4ed2d765dfaccff5ebdac68e20
--
fail:runs
On Monday 24 November 2014 12:39:12 Karol Wrona wrote:
> It is possible that it can serve as input device sth else. So you are
> right about MFD.
>
> The structure of mfd directory is flat. I wonder what can be better:
> just putting these sources inside mfd dir or to some new category inside
On 11/24/2014 01:16 PM, Vignesh R wrote:
> I have tried running both IIO and TSC at the same time. But I have never
> seen WARN_ON() even after running for close to 30 min. Can you send me
> the exact script, so that it will be easy to reproduce?
Sure thing.
- one shell
evtest
On 20/11/14 18:53, David Howells wrote:
> Here's a set of patches that does the following:
>
> (1) Extracts both parts of an X.509 AuthorityKeyIdentifier (AKID) extension.
> We already extract the bit that can match the subjectKeyIdentifier (SKID)
> of the parent X.509 cert, but we
Hi Thomas, Jiang,
On 2014/11/12 21:42, Thomas Gleixner wrote:
> From: Jiang Liu
>
[...]
> /* Number of irqs reserved for a legacy isa controller */
> #define NUM_ISA_INTERRUPTS 16
> @@ -64,6 +66,16 @@ struct irq_domain_ops {
> int (*xlate)(struct irq_domain *d, struct device_node
On Sat, Nov 22, 2014 at 1:18 PM, Jonathan Cameron wrote:
> On 22/11/14 11:05, Jonathan Cameron wrote:
>> On 10/11/14 12:45, Daniel Baluta wrote:
>>> Adds support for the new channel types in the dummy driver:
>>> * a new channel IIO_ACTIVITY
>>> * two state transition events (running and
Add device node for the ACTMON block to the Tegra124 device tree.
Signed-off-by: Tomeu Vizoso
---
v2: * Add operating-points property
---
arch/arm/boot/dts/tegra124.dtsi | 23 +++
1 file changed, 23 insertions(+)
diff --git a/arch/arm/boot/dts/tegra124.dtsi
The ACTMON block can monitor several counters, providing averaging and firing
interrupts based on watermarking configuration. This implementation monitors
the MCALL and MCCPU counters to choose an appropriate frequency for the
external memory clock.
This patch is based on work by Alex Frid and
This block gathers statistics about various counters and can be configured to
fire interrupts when thresholds are crossed.
Signed-off-by: Tomeu Vizoso
---
v2: * Add operating-points property
---
.../devicetree/bindings/arm/tegra/actmon.txt | 38 ++
1 file
Hello,
in this v2 I have made the driver use devfreq. It works just as fine as the
previous revision, but it's almost 200 lines more of code for not that much
gain.
Though I don't see much point in using devfreq, I think it's probably better
than an ad-hoc driver because in the future I hope
701 - 800 of 2022 matches
Mail list logo
