On Sat, Feb 15, 2014 at 04:27:37PM +0100, Wolfram Sang wrote:
> On Tue, Feb 04, 2014 at 04:31:19PM +0200, Mika Westerberg wrote:
> > Intel Baytrail I2C controllers can be enumerated from PCI as well as from
> > ACPI. In order to support this add the Baytrail PCI IDs to the driver.
> >
> > Signed-o
On Fri, 2014-02-14 at 21:05 +, Mark Brown wrote:
> On Fri, Feb 14, 2014 at 02:05:56PM +0100, Krzysztof Kozlowski wrote:
> > On Thu, 2014-02-13 at 17:46 +0530, Yadwinder Singh Brar wrote:
>
> > - low-power mode;
> > - low-power mode controlled by PWREN;
> > Although not all are present for ea
On Fri, 2014-02-14 at 20:59 +, Mark Brown wrote:
> On Fri, Feb 14, 2014 at 09:15:12AM +0100, Krzysztof Kozlowski wrote:
>
> > My initial idea was to do this similarly to the S5M8767 regulator (where
> > there is also 4th mode: low power). The presence of GPIO in DTS can
> > simplify the bindin
Hi, Sasha
On 02/16/2014 07:27 AM, Sasha Levin wrote:
> Hi folks,
>
> While fuzzing with trinity inside a KVM tools guest running latest -next
> kernel, I've
> stumbled on the following:
I've reproduced the same issue with tip/master, and below patch fixed the
problem on my box along with some rc
From: Wei Chen
rpmsg_init() always return ERROR code or random integer now, this patch fixes
it.
Signed-off-by: Wei Chen
Signed-off-by: Barry Song
---
drivers/rpmsg/virtio_rpmsg_bus.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b
On Wed, Feb 12, 2014 at 06:18:52PM +0100, Miklos Szeredi wrote:
> On Tue, Feb 11, 2014 at 05:01:41PM +0100, Miklos Szeredi wrote:
> > On Mon, Feb 10, 2014 at 09:51:45PM +1100, Dave Chinner wrote:
>
> > > Miklos, can you please write an xfstest for this new API? That way
> > > we can verify that th
On Sun, Feb 16, 2014 at 06:15:27PM +0100, Paul Bolle wrote:
> The Kconfig symbols HAVE_MARCH_Z900_FEATURES and
> HAVE_MARCH_Z990_FEATURES were added in v3.5. They have never been used.
> Apparently they are not needed. They can safely be removed.
>
No, I want to keep them, so there is a config sy
> >>From: Roger Tseng
> >>
> >>Realtek USB card reader provides a channel to transfer command or data to
> >>flash
> >>memory cards. This driver exports host instances for mmc and memstick
> >>subsystems
> >>and handles basic works.
> >>
> >>Signed-off-by: Roger Tseng
> >>---
> >> drivers/mfd/
On 02/17/2014 10:44 AM, Viresh Kumar wrote:
> On 17 February 2014 05:58, Rafael J. Wysocki wrote:
>> On Friday, February 14, 2014 04:30:40 PM Viresh Kumar wrote:
>
>> Good to know that you chat with each other, but it really is not a useful
>> piece
>> of information until you say what *exactly*
>>> On 15.02.14 at 15:02, Petr Tesarik wrote:
> --- a/arch/x86/kernel/smpboot.c
> +++ b/arch/x86/kernel/smpboot.c
> @@ -1226,9 +1226,6 @@ __init void prefill_possible_map(void)
> #ifdef CONFIG_HOTPLUG_CPU
> if (setup_max_cpus)
> possible += disabled_cpus;
> -#e
On 02/15/2014 12:09 AM, Eric W. Biederman wrote:
> Pavel Emelyanov writes:
>
>> On 02/14/2014 11:16 PM, Eric W. Biederman wrote:
>>> Cyrill Gorcunov writes:
>>>
On Fri, Feb 14, 2014 at 09:43:14PM +0400, Andrew Vagin wrote:
>> My brain hurts just looking at this patch and how you are jus
Hi Maxime,
On Mon, 2014-02-17 at 08:57 +0100, Maxime Coquelin wrote:
> On 02/16/2014 08:05 PM, Paul Bolle wrote:
> > The Kconfig symbols SOC_STIH415 and SOC_STIH416 were added in v3.11.
> > They have never been used. They default to "y" but nothing cares. They
> > can safely be removed.
>
> This
On Fri, Feb 14, 2014 at 03:32:57PM -0800, Siva Yerramreddy wrote:
> When running dmatest with my yet-to-be submitted driver for the Intel MIC DMA
> engine, dmatest detected "dma0chan3-copy5: result #8096161:completion busy
> status with src_off=0x0 dst_off=0x0 len=0x40 (0)". This is caused by readi
On 17 February 2014 13:49, Srivatsa S. Bhat
wrote:
> Quick question: Looking at cpufreq_update_policy() and cpufreq_out_of_sync(),
> I understand that if the cpufreq subsystem's notion of the current frequency
> does not match with the actual frequency of the CPU, it tries to adjust and
> notify e
On Thu, Feb 13, 2014 at 10:39:01AM +0100, Linus Walleij wrote:
> It appears that in the DMA40 driver the DMA tasklet will very
> often dereference memory for a descriptor just free:d from the
> DMA40 slab. Nothing happens because no other part of the driver
> has yet had a chance to claim this memo
Add __initconst to 'regulator_desc' array with supported regulators.
During probe choose how many and which regulators will be supported
according to device ID. Then copy the 'regulator_desc' array to
allocated memory so the regulator core can use it.
Additionally allocate array of of_regulator_ma
Constify the regulator_desc 'regulators' array.
Signed-off-by: Krzysztof Kozlowski
Cc: Mark Brown
Cc: Liam Girdwood
---
drivers/regulator/s2mps11.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/s2mps11.c b/drivers/regulator/s2mps11.c
index acdd3b92b8d
This patch removes the code for initializing time if this is first boot.
The code for detecting first boot uses undocumented field RTC_TCON in
RTC_UDR_CON register. According to S5M8767's datasheet this field is
reserved. On S2MPS14 it is not documented at all. On device first boot
the registers w
This patch prepares for adding support for S2MPS14 RTC driver by
selecting different regmaps for S2MPS1X/S5M876X RTC devices.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Lee Jones
---
drivers/mfd/sec-core.c | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/
Add support for S2MPS14 to the rtc-s5m driver. Differences in S2MPS14
(in comparison to S5M8767):
- Layout of registers;
- Lack of century support for time and alarms (7 registers used for
storing time/alarm);
- Two buffer control registers: WUDR and RUDR;
- No register for enabling writing
This patch prepares for adding support for S2MPS14 RTC device to the
rtc-s5m driver:
1. Adds a map of registers used by the driver which differ between
the chipsets (S5M876X and S2MPS14).
2. Moves code of checking for alarm pending to separate function.
Signed-off-by: Krzysztof Kozlowski
Cc: Ales
Add bindings documentation for S2MPS14 device to the s2mps11 driver.
Signed-off-by: Krzysztof Kozlowski
Cc: Mark Brown
Cc: Liam Girdwood
Cc: Tomasz Figa
Cc: devicet...@vger.kernel.org
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
Acked-by: Tomasz Figa
--
Add support for S2MPS14 PMIC regulators to s2mps11 driver. The S2MPS14
has fewer BUCK-s and LDO-s than S2MPS11. It also does not support
controlling the BUCK ramp delay.
Signed-off-by: Krzysztof Kozlowski
Cc: Mark Brown
Cc: Liam Girdwood
Reviewed-by: Yadwinder Singh Brar
---
drivers/regulator
From: Micky Ching
First we fix the card poweroff bug: the card power is not shutdown when sd/mmc
card removed, this will make UHS-card failed to running in high speed mode if we
insert the card again.
We offer a concise tuning searching method, it is much easier to read.
At last we add support
Add maximum register to the regmap used by rtc-s5m driver.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Lee Jones
---
drivers/mfd/sec-core.c |2 ++
include/linux/mfd/samsung/rtc.h |2 ++
2 files changed, 4 insertions(+)
diff --git a/drivers/mfd/sec-core.c b/drivers/mfd/sec-cor
Add support for S2MPS14 PMIC device to the MFD sec-core driver.
The S2MPS14 is similar to S2MPS11 but it has fewer regulators, two
clocks instead of three and a little different registers layout.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Lee Jones
---
drivers/mfd/sec-core.c |
From: Micky Ching
If the host driver removed while card in the slot, the host will not
power off card power correctly. This bug is produced because host
eject flag set before the last mmc_set_ios callback, we should set the
eject flag after power off.
Signed-off-by: Micky Ching
---
drivers/mmc
From: Micky Ching
The new phase searching method is more concise and easier to
understand.
Signed-off-by: Micky Ching
---
drivers/mmc/host/rtsx_pci_sdmmc.c | 112 +++--
include/linux/mfd/rtsx_pci.h |2 +-
2 files changed, 33 insertions(+), 81 deletions
From: Micky Ching
Add support for non-blocking request, pre_req() runs dma_map_sg() and
post_req() runs dma_unmap_sg(). This patch can increase card read/write
speed, especially for high speed card and slow CPU(for some embedded
platform).
Users can get a great benefit from this patch. if CPU fr
:
regulator: s2mps11: Don't store registered regulators in state container
4. Dropped two patches adding opmode (regulator: s2mps11: Add opmode for
S2MPS14 regulators).
5. Rebased on current next (next-20140217).
Changes since v1
1. Added Lee Jones' ACK-s.
2. Applied sugges
Regulators registered by devm_regulator_register() do not have to be
stored in state container because they are never dereferenced later.
The array of regulator_dev can be safely removed from state container.
Signed-off-by: Krzysztof Kozlowski
---
drivers/regulator/s2mps11.c | 10 +-
1
This patch prepares for adding support for S2MPS14 RTC device to the
rtc-s5m driver:
1. Renames SEC* symbols to S5M.
2. Adds S5M prefix to some of defines which are different between S5M876X
and S2MPS14.
This is only a rename-like patch, new code is not added.
Signed-off-by: Krzysztof Kozlowski
On Sat, Feb 15, 2014 at 05:30:17PM +0530, Srikanth Thokala wrote:
> The current implementation of interleaved DMA API support multiple
> frames only when the memory is contiguous by incrementing src_start/
> dst_start members of interleaved template.
>
> But, when the memory is non-contiguous it w
The S2MPS11 RTC has two alarms: alarm0 and alarm1 (corresponding
interrupts are named similarly). Use consistent names for interrupts to
limit possible errors.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Lee Jones
---
drivers/mfd/sec-irq.c |8
include/linux/mfd/samsung/i
On 02/14/2014 04:30 PM, Viresh Kumar wrote:
> cpufreq_update_policy() is called from two places currently. From a workqueue
> handled queued from cpufreq_bp_resume() for boot CPU and from
> cpufreq_cpu_callback() whenever a CPU is added.
>
> The first one makes sure that boot CPU is running on the
On Mon, 2014-02-17 at 09:20 +0100, Heiko Carstens wrote:
> On Sun, Feb 16, 2014 at 06:15:27PM +0100, Paul Bolle wrote:
> No, I want to keep them, so there is a config symbol for each cpu generation
> and we don't have to add the config symbols again, if we actually use them.
Yes, that's the idea:
On Mon, Feb 17, 2014 at 12:34:12PM +0400, Pavel Emelyanov wrote:
...
> Maybe we can make prlctl() do lite-execve()? It will open the executable,
> read the
> required amount of headers and just put data red from there onto mm-struct?
> This
> should be MUCH better, that full execve() with loadin
Hi Bjorn,
Sorry to bother you, any comment about this series?
Thanks!
Yijing.
On 2014/2/12 10:52, Yijing Wang wrote:
> v5->v6: Add is_frozen flag to protect pci bus from double frozen.
>
> This series is based on Bjorn's pci-next branch.
> Currently, more and more PCIe devices support PCIe DS
On 17 February 2014 14:13, Srivatsa S. Bhat
wrote:
> On 02/14/2014 04:30 PM, Viresh Kumar wrote:
>> cpufreq_update_policy() is called from two places currently. From a workqueue
>> handled queued from cpufreq_bp_resume() for boot CPU and from
>> cpufreq_cpu_callback() whenever a CPU is added.
>>
>
On Fri, Feb 14, 2014 at 8:57 PM, Mark Brown wrote:
> On Fri, Feb 14, 2014 at 09:02:20AM +, Laszlo Papp wrote:
>> On Wed, Feb 12, 2014 at 5:50 PM, Mark Brown wrote:
>> > On Wed, Feb 12, 2014 at 04:02:40AM +, Laszlo Papp wrote:
>
>> >> +const struct regmap_config max665x_regmap_config = {
>
Hello Tomasz,
On 14 February 2014 16:24, Tomasz Figa wrote:
> Hi Kukjin,
>
>
> On 14.02.2014 00:28, Kukjin Kim wrote:
>>
>> On 02/07/14 14:24, Naveen Krishna Chatradhi wrote:
>>>
>>> This patch adds the device tree node for SSS module
>>> found on Exynos5420 and Exynos5250
>>>
>>> Signed-off-by:
On Tue, Feb 11, 2014 at 02:58:52PM -0600, Andy Gross wrote:
> On Tue, Feb 11, 2014 at 11:00:48PM +0530, Vinod Koul wrote:
> > On Tue, Feb 04, 2014 at 02:42:35PM -0600, Andy Gross wrote:
> > > Add the DMA engine driver for the QCOM Bus Access Manager (BAM) DMA
> > > controller
> > > found in the MS
Registering phy_provider before creating the PHY can result in PHY
callbacks being invoked which will lead to aborts. In order to avoid this
invoke phy_provider_register after phy_create and phy_set_drvdata.
Reported-by: Felipe Balbi
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Sylwester Nawr
From: Hans de Goede
include/phy/phy.h has stub code in there for when building without the
phy-core enabled. This is useful for generic drivers such as ahci-platform,
ehci-platoform and ohci-platform which have support for driving an optional
phy passed to them through the devicetree.
Since on s
From: Hans de Goede
The phy-core allows phy_init and phy_power_on to be called multiple times,
but before this patch -ENOSUPP from phy_pm_runtime_get_sync would be
propagated to the caller for the 2nd and later calls.
Signed-off-by: Hans de Goede
Signed-off-by: Kishon Vijay Abraham I
---
driv
From: Richard Weinberger
On archs like S390 or um this driver cannot build nor work.
Make it depend on HAS_IOMEM to bypass build failures.
drivers/phy/phy-bcm-kona-usb2.c:114: undefined reference to
`devm_ioremap_resource'
Signed-off-by: Richard Weinberger
Signed-off-by: Kishon Vijay Abraham
On 02/17/2014 02:09 PM, Viresh Kumar wrote:
> On 17 February 2014 13:49, Srivatsa S. Bhat
> wrote:
>> Quick question: Looking at cpufreq_update_policy() and cpufreq_out_of_sync(),
>> I understand that if the cpufreq subsystem's notion of the current frequency
>> does not match with the actual freq
From: Sachin Kamat
Silences the following warnings:
WARNING: sizeof *twl should be sizeof(*twl)
WARNING: sizeof *otg should be sizeof(*otg)
Signed-off-by: Sachin Kamat
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-twl4030-usb.c |4 ++--
1 file changed, 2 insertions(+), 2 delet
From: Sachin Kamat
PTR_ERR_OR_ZERO simplifies the code.
Signed-off-by: Sachin Kamat
Cc: Matt Porter
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-bcm-kona-usb2.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/phy/phy-bcm-kona-usb2.c b/drivers/ph
From: Sachin Kamat
Semicolon after switch statement is not needed.
Signed-off-by: Sachin Kamat
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-twl4030-usb.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/phy/phy-twl4030-usb.c b/drivers/phy/phy-twl4030
From: Hans de Goede
In various cases errors may be expected, ie probe-deferral or a call to
phy_get from a driver where the use of a phy is optional.
Rather then adding all sort of complicated checks for this, and/or adding
special functions like devm_phy_get_optional, simply don't log an error,
Hi Greg,
Here's the PULL requeust for PHY subsystem for this -rc cycle. There isn't
anything major but a bunch of obvious fixes and cleanup.
Let me know If I have to change anything.
Thanks
Kishon
The following changes since commit 6d0abeca3242a88cab8232e4acd7e2bf088f3bc2:
Linux 3.14-rc3 (20
On Mon, 2014-02-17 at 08:43 +0400, Alexander Shiyan wrote:
> It seems that even in the current state, Kconfig for i.MX contains an error.
> As a start, we should rename ARCH_MX1ADS to MACH_MX1ADS first.
Last year I admitted that I didn't entirely grasped the differences
between "arch", "platform",
On 02/17/2014 02:24 PM, Viresh Kumar wrote:
> On 17 February 2014 14:13, Srivatsa S. Bhat
> wrote:
>> On 02/14/2014 04:30 PM, Viresh Kumar wrote:
>>> cpufreq_update_policy() is called from two places currently. From a
>>> workqueue
>>> handled queued from cpufreq_bp_resume() for boot CPU and from
Add Maxim 77836 support to max14577 driver. The chipsets have same MUIC
component so the extcon, charger and regulators are almost the same. The
max77836 however has also PMIC and Fuel Gauge.
The MAX77836 uses three I2C slave addresses and has additional interrupts
(related to PMIC and Fuel Gauge)
This patch continues the preparation for adding support for max77836
device to existing max14577 driver.
The patch renames the struct "max14577" state container to "maxim_core".
This is only a rename-like patch, new code is not added.
Signed-off-by: Krzysztof Kozlowski
Cc: Kyungmin Park
Cc: Mar
Add max14577 prefix to muic_irqs array. This prepares for max77836
support in this extcon driver.
Signed-off-by: Krzysztof Kozlowski
Cc: Kyungmin Park
Cc: Marek Szyprowski
Acked-by: Chanwoo Choi
Tested-by: Chanwoo Choi
---
drivers/extcon/extcon-max14577.c | 12 ++--
1 file changed,
This patch prepares for changing the max14577 charger driver to allow
configuring battery-dependent settings from DTS.
The patch moves from regulator driver to MFD core driver and exports:
- function for calculating register value for charger's current;
- table of limits for chargers (MAX14577,
Add support for MAX77836 charger to the max14577 driver. The MAX77836
charger is almost the same as 14577 model except:
- No dead-battery detection;
- Support for special charger (like in max77693);
- Support for DX over-voltage protection (like in max77693);
- Lower values of charging current
From: Chanwoo Choi
This patch use device name to make sysfs path according to device type:
max14577-muic
- /sys/class/extcon/max14577-muic/
max77836-muic
- /sys/class/extcon/max77836-muic/
Signed-off-by: Chanwoo Choi
Signed-off-by: Krzysztof Kozlowski
Cc: Kyungmin Park
Cc: Marek Szyprowski
Add of_node_put to decrement the ref count.
Signed-off-by: Sachin Kamat
---
drivers/regulator/tps6507x-regulator.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/regulator/tps6507x-regulator.c
b/drivers/regulator/tps6507x-regulator.c
index 5a558dad27e3..e506e7f54253 100644
--- a
This patch continues the preparation for adding support for max77836
device to existing max14577 driver.
Add "muic" suffix to regmap and irq_data fields in maxim_core state
container to prepare for max77836 support.
This is only a rename-like patch, new code is not added.
Signed-off-by: Krzysztof
Remove hard-coded values for:
- Fast Charge current,
- End Of Charge current,
- Fast Charge timer,
- Overvoltage Protection Threshold,
- Battery Constant Voltage,
and use DTS to configure them. This allows using the max14577 charger
driver with different batteries.
Now the charger driver requ
Add of_node_put to decrement the ref count.
Signed-off-by: Sachin Kamat
---
drivers/regulator/tps65090-regulator.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/regulator/tps65090-regulator.c
b/drivers/regulator/tps65090-regulator.c
index 676f75548f00..5674f886c471 100644
--- a
Add of_node_put to decrement the ref count.
Signed-off-by: Sachin Kamat
---
drivers/regulator/max8998.c |7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/regulator/max8998.c b/drivers/regulator/max8998.c
index ae3f0656feb0..ce22d4f3f3eb 100644
--- a/drivers/reg
Add of_node_put to decrement the ref count.
Signed-off-by: Sachin Kamat
---
drivers/regulator/max8660.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/regulator/max8660.c b/drivers/regulator/max8660.c
index 70351abbd1e9..61ecd0892637 100644
--- a/drivers/regulator/max8660.c
+++ b
Hi, Vinod,
Could you please help merge this patch? We are having some other upstreaming
patches using the dma functionality pending the acceptance of the eDMA driver.
Many thanks!
Best Regards,
Jingchang
> -Original Message-
> From: Lu Jingchang-B35083
> Sent: Monday, January 27,
On Mon, Feb 17, 2014 at 09:50:40AM +0100, Paul Bolle wrote:
> On Mon, 2014-02-17 at 09:20 +0100, Heiko Carstens wrote:
> > On Sun, Feb 16, 2014 at 06:15:27PM +0100, Paul Bolle wrote:
> > No, I want to keep them, so there is a config symbol for each cpu generation
> > and we don't have to add the co
On 17 February 2014 14:25, Srivatsa S. Bhat
wrote:
> Specifically, I'm referring to the problem where there _is_ a difference,
> but the ->get() is not reporting it properly, like returning a 0 for example.
I think get() returning zero isn't acceptable at all. How can current freq be
zero :) .. T
Add of_node_put to decrement the ref count.
Signed-off-by: Sachin Kamat
---
drivers/regulator/max77693.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/regulator/max77693.c b/drivers/regulator/max77693.c
index 057d040e6feb..d6807fd7eadc 100644
--- a/drivers/re
Add of_node_put to decrement the ref count.
Signed-off-by: Sachin Kamat
---
drivers/regulator/max77686.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/regulator/max77686.c b/drivers/regulator/max77686.c
index 0e725f6ed455..b411af00065d 100644
--- a/drivers/regulator/max77686.c
Add of_node_put to decrement the ref count.
Signed-off-by: Sachin Kamat
---
drivers/regulator/act8865-regulator.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/regulator/act8865-regulator.c
b/drivers/regulator/act8865-regulator.c
index c9f98b061307..2d2c3b004ab7 100644
--- a/dr
Add of_node_put to decrement the ref count.
Signed-off-by: Sachin Kamat
---
drivers/regulator/da9063-regulator.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/regulator/da9063-regulator.c
b/drivers/regulator/da9063-regulator.c
index bfd7f2f795a6..a61b5d997a08 100644
--- a/drive
Add of_node_put to decrement the ref count.
Signed-off-by: Sachin Kamat
---
drivers/regulator/as3722-regulator.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/regulator/as3722-regulator.c
b/drivers/regulator/as3722-regulator.c
index 8b17d786cb71..85585219ce82 100644
--- a/drive
Add document describing device tree bindings for MAX14577 MFD
drivers: MFD core, extcon, regulator and charger.
Both MAX14577 and MAX77836 chipsets are documented.
Signed-off-by: Krzysztof Kozlowski
Cc: Kyungmin Park
Cc: Tomasz Figa
Cc: Marek Szyprowski
Cc: devicet...@vger.kernel.org
Cc: Rob
Add support for MAX77836 chipset and its additional two LDO regulators.
These LDO regulators are controlled by the PMIC block with additional
regmap (different I2C slave address).
The MAX77836 charger and safeout regulators are almost identical to
MAX14577. The registers layout is the same, except
On 02/17/2014 04:22 PM, Lee Jones wrote:
From: Roger Tseng
Realtek USB card reader provides a channel to transfer command or data to flash
memory cards. This driver exports host instances for mmc and memstick subsystems
and handles basic works.
Signed-off-by: Roger Tseng
---
drivers/mfd/Kco
Add support for MAX77836 chipset to the max14577 extcon driver. The
MAX77836 MUIC has additional interrupts (VIDRM, ADC1K) so IRQ handling
is split up into two functions: max14577_parse_irq() and
max77836_parse_irq().
Signed-off-by: Krzysztof Kozlowski
Signed-off-by: Chanwoo Choi
Cc: Kyungmin Pa
On Mon, 2014-02-17 at 10:10 +0100, Heiko Carstens wrote:
> On Mon, Feb 17, 2014 at 09:50:40AM +0100, Paul Bolle wrote:
> > Completeness of what?
>
> Each cpu generation we support is supposed to have a
> "HAVE_MARCH__FEATURES" config symbol.
But apparently these two generations can do fine withou
MAX77836 has the same Fuel Gauge as MAX17040. The max17040 driver can be
safely re-used. The patch adds MAX77836 ID to array with i2c_device_id.
Signed-off-by: Krzysztof Kozlowski
Cc: Kyungmin Park
Cc: Marek Szyprowski
Cc: Anton Vorontsov
Cc: Dmitry Eremin-Solenikov
Cc: David Woodhouse
---
This patch prepares for adding support for max77836 device to existing
max14577 driver:
1. Renames most of symbols and defines prefixed with MAX14577 to MAXIM.
2. Adds prefixes (MAXIM or MAX14577) to defines without any MAX* prefix.
This is only a rename-like patch, new code is not added.
Signed-
this would be probably the best
way to merge everything. I would be glad if I could get missing acks
(or comments).
Changes since v2
1. Added ACK-s.
2. Applied minor checkpatch fixes (pointed by Lee Jones).
3. Rebased on next-20140217.
Changes since v1
1. Added ACK
This patch continues the preparation for adding support for max77836
device to existing max14577 driver.
Add enum for types of devices supported by this driver. The device type
will be detected by matching of_device_id, or i2c_device_id as a
fallback.
The patch also moves to separate function the
This patch continues the preparation for adding support for max77836
device to existing max14577 driver.
During probe choose muic_irqs according to device type. Currently there
are only "max14577_muic_irqs" but later patch will add max77836
interrupts.
Signed-off-by: Krzysztof Kozlowski
Cc: Kyun
On Mon, Feb 17, 2014 at 10:02:48AM +0100, Paul Bolle wrote:
> On Mon, 2014-02-17 at 08:43 +0400, Alexander Shiyan wrote:
> > It seems that even in the current state, Kconfig for i.MX contains an error.
> > As a start, we should rename ARCH_MX1ADS to MACH_MX1ADS first.
No. Have a look at arch/arm/t
On 15 February 2014 05:33, Stephen Warren wrote:
> On 02/14/2014 03:23 PM, Rafael J. Wysocki wrote:
>> Well, it would be good to verify which part, then.
>
> Patch 2/7 appears to stop that message from being printed during
> suspend, and perhaps reduce the number of times it's printed during
> re
On Fri 14-02-14 20:12:17, Derek Basehore wrote:
> bdi_wakeup_thread_delayed used the mod_delayed_work function to schedule work
> to writeback dirty inodes. The problem with this is that it can delay work
> that
> is scheduled for immediate execution, such as the work from sync_inodes_sb.
> This c
On Mon, Feb 17, 2014 at 04:11:09PM +0800, Michael wang wrote:
> BTW, I reproduced it by steps:
> 1. change current to RT
> 2. move to a different depth cpu-cgroup
> 3. change it back to FAIR
>
> Seems like it was caused by that RT has no task_move_group() implemented
> which could maintain depth,
Earlier patch tried to do this but missed this piece of code to fix.
42f921a cpufreq: remove sysfs files for CPUs which failed to come back after
resume
Currently we are getting this on suspend/resume:
[ cut here ]
WARNING: CPU: 0 PID: 877 at fs/sysfs/dir.c:52 sysfs_warn_
> This adds a driver for the Atmel Microcontroller found on the
> iPAQ h3xxx series. This device handles some keys, the
> touchscreen, and the battery monitoring.
>
> This is a port of a driver from handhelds.org 2.6.21 kernel,
> written by Alessandro Gardich based on Andrew Christians
> original
This patch adds xilinx CAN controller support.
This driver supports both ZYNQ CANPS and Soft IP
AXI CAN controller.
Signed-off-by: Kedareswara rao Appana
---
This patch is rebased on the 3.14 rc3 kernel.
Changes for v3:
- Updated the driver with the review comments
- Modified the transmit logic a
Earlier cpufreq suspend/resume callbacks into drivers were getting called only
for the boot CPU, as by the time callbacks were called non-boot CPUs were
already removed. Because we might still need driver specific actions on
suspend/resume, its better to use earlier infrastructure from the early
su
This patchset creates/calls cpufreq suspend/resume callbacks from
dpm_{suspend|resume}()
for handling suspend/resume of cpufreq governors and core.
There are multiple problems that are fixed by this patch:
- Nishanth Menon (TI) found an interesting problem on his platform, OMAP. His
board
wasn
Previous patch added support for suspending governors, with callbacks being
called from dpm_{suspend|resume}_noirq(). The problem here is that most of the
devices (i.e. devices with ->suspend() callbacks) have already been suspended by
now and so if drivers want to change frequency before suspendin
Multiple platforms need to set CPU to a particular frequency before suspending
system. And so they need a common infrastructure which is provided by this
patch. Those platforms just need to initialize their ->suspend() pointers with
the generic routine.
Tested-by: Stephen Warren
Signed-off-by: Vi
Currently we have implemented PM notifiers to disable/enable ->target() routines
functionality during suspend/resume.
Now we have support present in cpufreq core, lets use it.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/s5pv210-cpufreq.c | 49 +++
1 file
Currently we have implemented PM notifiers to disable/enable ->target() routines
functionality during suspend/resume.
Now we have support present in cpufreq core, lets use it.
Tested-by: Stephen Warren
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/tegra-cpufreq.c | 46 +--
Currently we have implemented PM notifiers to disable/enable ->target() routines
functionality during suspend/resume.
Now we have support present in cpufreq core, lets use it.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/exynos-cpufreq.c | 96 +++-
1 file
This patch adds cpufreq suspend/resume calls to dpm_{suspend|resume}_noirq() for
handling suspend/resume of cpufreq governors.
Lan Tianyu (Intel) & Jinhyuk Choi (Broadcom) found an issue where tunables
configuration for clusters/sockets with non-boot CPUs was getting lost after
suspend/resume, as
On 02/16/2014 11:42 PM, Stefani Seibold wrote:
I think for the first time it will be okay to kick out the
_ASM_X86_SPINLOCK_H hack and accept the C=1 warnings.
At next step it is necessary to make the whole BUILD_VDSO32 path in
vclock_gettime.c independent from the kernel headers, only uapi/ sho
1 - 100 of 768 matches
Mail list logo
