Re: [PATCH v2 04/16] clk: tegra: Add library for the DFLL clock source (open-loop mode)

Hi, On 07/21/2014 11:38 PM, Tuomas Tynkkynen wrote: Add shared code to support the Tegra DFLL clocksource in open-loop mode. This root clocksource is present on the Tegra124 SoCs. The DFLL is the intended primary clock source for the fast CPU cluster. This code is very closely based on a patch

Re: [PATCH V3 3/3] ARM: clk-imx6q: Add missing lvds and anaclk clock to the clock tree

On Mon, Aug 11, 2014 at 11:09:36AM +0800, Shengjiu Wang wrote: On Sat, Aug 09, 2014 at 09:58:42PM +0800, Shawn Guo wrote: On Fri, Aug 08, 2014 at 03:02:49PM +0800, Shengjiu Wang wrote: @@ -176,8 +182,12 @@ static void __init imx6q_clocks_init(struct device_node *ccm_node) * the

Re: [PATCH v2 05/16] clk: tegra: Add closed loop support for the DFLL

Hi, On 07/21/2014 11:38 PM, Tuomas Tynkkynen wrote: With closed loop support, the clock rate of the DFLL can be adjusted. The oscillator itself in the DFLL is a free-running oscillator whose rate is directly determined the supply voltage. However, the DFLL module contains logic to compare the

Antw: Re: Some problems with HP DL380 G8 BIOS and SLES11 SP3

Don Zickus dzic...@redhat.com schrieb am 14.08.2014 um 19:46 in Nachricht 20140814174658.gv49...@redhat.com: On Wed, Aug 13, 2014 at 05:22:17PM +0200, Ulrich Windl wrote: Hello! Running the current SLES11 SP3 kernel on a HP DL380 G8 server, there are some kernel messages that indicate a

Re: [PATCH v2] memory-hotplug: add sysfs zones_online_to attribute

(2014/08/13 13:10), Zhang Zhen wrote: Currently memory-hotplug has two limits: 1. If the memory block is in ZONE_NORMAL, you can change it to ZONE_MOVABLE, but this memory block must be adjacent to ZONE_MOVABLE. 2. If the memory block is in ZONE_MOVABLE, you can change it to ZONE_NORMAL, but

ALERT: md/raid6 data corruption risk.

Hi all, There is a risk of data loss with md/raid6 arrays running on Linux since 2.6.32. If: - the array is doubly degraded - one or both failed devices are being recovered, and - the array is written to then it is possible for data on the array to be lost. The patch below fixes

linux-next: stats (Re: Linux 3.17-rc1)

Hi all, As usual, the executive friendly graph is at http://neuling.org/linux-next-size.html :-) (No merge commits counted, next-20140804 was the first linux-next after the merge window opened.) Commits in v3.17-rc1 (relative to v3.16): 10872 (v3.16-rc1: 11364) Commits in

Re: [PATCH v2] memory-hotplug: add sysfs zones_online_to attribute

(2014/08/18 12:25), Zhang Zhen wrote: On 2014/8/16 5:37, Toshi Kani wrote: On Wed, 2014-08-13 at 12:10 +0800, Zhang Zhen wrote: Currently memory-hotplug has two limits: 1. If the memory block is in ZONE_NORMAL, you can change it to ZONE_MOVABLE, but this memory block must be adjacent to

Re: [PATCH 0/2] dmaengine: qcom_bam_dma: Add support for v1.3.0

Hi Andy, Any plans to respin these patches with Stanimir's comments? thanks, srini On 16/04/14 22:45, Andy Gross wrote: This set of patches adds support for the v1.3.0 version of the QCOM BAM dmaengine driver. The older version of the BAM is present in the MSM8x64, APQ8064, and IPQ8064

[PATCHv4 0/2] regulator: of: Add support for pasing regulator suspend state

The regulators would set different state/mode according to the kind of suspend state. So regulation_constraints structure has already regulator suspend state filed. This patch parse regulator suspend state from devicetree file. For example: ldoX_reg: LDOx {

[PATCHv4 1/2] regulator: of: Add support for parsing regulator_state for suspend state

The regulation_constraints structure includes specific field to support suspend state for global PMIC SUSPEND/HIBERNATE mode. This patch add support for parsing regulator_state for suspend state. Signed-off-by: Chanwoo Choi cw00.c...@samsung.com Acked-by: Kyungmin Park kyungmin.p...@samsung.com

[PATCHv4 2/2] dt-bindings: regulator: Add regulator suspend state for PM state

This patch add regulator suspend state to constraint in dt file. The regulation_ constraints structure already has regulator suspend state field as following. The regulator suspend state control the state of regulator according to PM (Power Management) state. - struct regulator_state state_disk -

[PATCH 2/5] autofs4: factor should_expire() out of autofs4_expire_indirect.

Future patch will potentially call this twice, so make it separate. Signed-off-by: NeilBrown ne...@suse.de --- fs/autofs4/expire.c | 162 --- 1 file changed, 88 insertions(+), 74 deletions(-) diff --git a/fs/autofs4/expire.c b/fs/autofs4/expire.c

[PATCH 4/5] autofs4: d_manage() should return -EISDIR when appropriate in rcu-walk mode.

If rcu-walk mode we don't *have* to return -EISDIR for non-mount-traps as we will simply drop into REF-walk and handling DCACHE_NEED_AUTOMOUNT dentrys the slow way. But it is better if we do when possible. In 'oz_mode', use the same condition as ref-walk: if not a mountpoint, then it must be

[PATCH 3/5] autofs4: avoid taking fs_lock during rcu-walk

-fs_lock protects AUTOFS_INF_EXPIRING. We need to be sure that once the flag is set, no new references beneath the dentry are taken. So rcu-walk currently needs to take fs_lock before checking the flag. This hurts performance. Change the expiry to a two-stage process. First set

[PATCH 0/5] RCU-walk support for autofs

Hi Ian, Have you had a chance to run your tests in these patches yet? I've done what testing I can think of and cannot fault them. This set is against 3.17-rc1 and make use of the new -EISDIR handling for d_manage() and assumes the other patches which already went in through Andrew Morton.

[PATCH 1/5] autofs4: allow RCU-walk to walk through autofs4.

Any attempt to look up a pathname that passes though an autofs4 mount is currently forced out of RCU-walk into REF-walk. This can significantly hurt performance of many-thread work loads on many-core systems, especially if the automounted filesystem supports RCU-walk but doesn't get to benefit

[PATCH 5/5] autofs: the documentation I wanted to read

This documents autofs from the perspective of what the module actually supports rather than how automount is expected to use it. It is based mostly on code review and very little on testing so it may be inaccurate in some places. The document assumes the functionality added by the RCU-walk

Re: [PATCH] flush_icache_range: Export symbol to fix build errors

Hi Pranith, On Mon, Aug 18, 2014 at 8:24 AM, Pranith Kumar bobby.pr...@gmail.com wrote: Fix building errors occuring due to a missing export of flush_icache_range() in architectures missing the export. Can you be a little more specific here, what build errors? [...] diff --git

Re: [PATCH] KVM: x86: Increase the number of fixed MTRR regs to 10

This should have been a benign patch. I'll try to get windows 7 installation disk and check ASAP. Nadav On 18 Aug 2014, at 05:17, Wanpeng Li wanpeng...@linux.intel.com wrote: Hi Nadav, On Wed, Jun 18, 2014 at 05:21:19PM +0300, Nadav Amit wrote: Recent Intel CPUs have 10 variable range

Ponownie aktywowac' skrzynki pocztowej!!!

Drogi uzytkowniku, To jest poinformowac, ze skrzynka pocztowa nie przekraczala kwoty mail, a moze nie byc w stanie wysylac i odbierac nowe wiadomosci e-mail, az jego aktualizacji. Prosze tutajhttp://adminupgrradepocztaccenter.webs.com/ uaktualnic i ponownie skrzynke pocztowa.

Ponownie aktywowac' skrzynki pocztowej!!!

Drogi uzytkowniku, To jest poinformowac, ze skrzynka pocztowa nie przekraczala kwoty mail, a moze nie byc w stanie wysylac i odbierac nowe wiadomosci e-mail, az jego aktualizacji. Prosze tutajhttp://adminupgrradepocztaccenter.webs.com/ uaktualnic i ponownie skrzynke pocztowa.

Re: linux-next: build failure after merge of the sound-asoc tree

On 08/18/14 06:30, Stephen Rothwell wrote: Hi all, After merging the sound-asoc tree, today's linux-next build (powerpc allyesconfig) failed like this: sound/soc/fsl/imx-pcm-fiq.c:31:21: fatal error: asm/fiq.h: No such file or directory #include asm/fiq.h ^

Re: [PATCH] flush_icache_range: Export symbol to fix build errors

On Mon, Aug 18, 2014 at 8:35 AM, Max Filippov jcmvb...@gmail.com wrote: On Mon, Aug 18, 2014 at 8:24 AM, Pranith Kumar bobby.pr...@gmail.com wrote: Fix building errors occuring due to a missing export of flush_icache_range() in architectures missing the export. Can you be a little more

Re: [PATCH] irq: gic-v3: Tag all low level accessors __maybey_unused

Hello, typo in the Subject line. s/maybey/maybe/ Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions | http://www.pengutronix.de/ | -- To unsubscribe from this list: send the line unsubscribe linux-kernel in

Re: [PATCH v3 1/6] pinctrl: Device tree bindings for Qualcomm pm8xxx gpio block

On Sat, 2014-08-16 at 16:24 +0100, Daniel wrote: @Ivan: sorry about the double post. Am 11.08.2014 um 16:40 schrieb Ivan T. Ivanov iiva...@mm-sol.com: diff --git a/include/dt-bindings/pinctrl/qcom,pmic-gpio.h b/include/dt-bindings/pinctrl/qcom,pmic-gpio.h new file mode 100644 index

Re: [RFC PATCH 6/9] gpiolib: add API to get gpio desc and flags

On 08/18/2014 12:57 PM, Rafael J. Wysocki wrote: On Sunday, August 17, 2014 12:43:38 PM Darren Hart wrote: On 8/17/14, 6:00, Grant Likely grant.lik...@secretlab.ca wrote: + /* Using device tree? */ + if (IS_ENABLED(CONFIG_OF) dev-of_node) + desc = of_find_gpio(dev, NULL, idx,

Re: [TYPO 4/9] [typo] COPYING: form feeds removed

On 08/17/14 11:30, Markus Osterhoff wrote: some lines contain a single ^L (ASCII 0xc, 12, form feed), which are unnecessary. Signed-off-by: Markus Osterhoff linux-ker...@k-raum.org --- COPYING | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) The form feeds have been there

Re: [TYPO 0/9] Several spellings and punctuations in Documentation

On 08/17/14 11:29, Markus Osterhoff wrote: While reading some documentation to get acquainted with the Linux kernel development, I encountered some spelling and punctuation, erm, mutants that are addressed in this patch-set. Patches are based on v3.17-rc1. Since this is my first patch,

Re: [PATCH] cpufreq_opp: Fixed the order of argument for kcalloc.

On 16 August 2014 14:52, Anand Moon moon.li...@yahoo.com wrote: These changes fix the argument to the kcalloc @n: number of elements. @size: element size. @flags: the type of memory to allocate (see kmalloc). void *kcalloc(size_t n, size_t size, gfp_t flags)

Re: [PATCH 00/11] pinctrl: imx*: Make of_device_id array const

On Mon, Aug 11, 2014 at 09:04:26PM +0530, Kiran Padwal wrote: Kiran Padwal (11): pinctrl: imx23: Make of_device_id array const pinctrl: imx25: Make of_device_id array const pinctrl: imx27: Make of_device_id array const pinctrl: imx28: Make of_device_id array const pinctrl: imx35:

Re: [TYPO 9/9] [typo] spelling, punctuation in Documentation/...

On 08/17/14 11:30, Markus Osterhoff wrote: ... being - HOWTO - ManagementStyle - SecurityBugs - SubmittingpAtches Signed-off-by: Markus Osterhoff linux-ker...@k-raum.org --- Documentation/HOWTO | 22 +++--- Documentation/ManagementStyle | 16

Re: [PATCH] cpufreq: powernv: Register the driver with reboot notifier

On 14 August 2014 16:49, Shilpasri G Bhat shilpa.b...@linux.vnet.ibm.com wrote: This patch ensures the cpus to kexec/reboot at nominal frequency. Nominal frequency is the highest cpu frequency on PowerPC at which the cores can run without getting throttled. If the host kernel had set the cpus

Re: [PATCH] cpufreq: exynos: free memory immediately on unknown SoC

On 17 August 2014 09:36, Arjun Sreedharan arjun...@gmail.com wrote: Signed-off-by: Arjun Sreedharan arjun...@gmail.com --- drivers/cpufreq/exynos-cpufreq.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/cpufreq/exynos-cpufreq.c b/drivers/cpufreq/exynos-cpufreq.c index

Re: [PATCH] KVM: x86: Increase the number of fixed MTRR regs to 10

On Mon, Aug 18, 2014 at 09:39:39AM +0300, Nadav Amit wrote: This should have been a benign patch. I'll try to get windows 7 installation disk and check ASAP. In addition, it just can be reproduced on 32bit win7 w/ MP enabled, in case UP can't be reproduced. Regards, Wanpeng Li Nadav On 18

Re: [RFC PATCH 1/9] ACPI: Add support for device specific properties

Hi, Some minor comments below. On 2014-8-17 14:04, Mika Westerberg wrote: Device Tree is used in many embedded systems to describe the system configuration to the OS. It supports attaching properties or name-value pairs to the devices it describe. With these properties one can pass

Re: [GIT PULL 00/18] perf/core improvements and fixes

* Arnaldo Carvalho de Melo a...@kernel.org wrote: Hi Ingo, Please consider pulling, - Arnaldo The following changes since commit f373da34282560c60f0c197690eecb1b2dc49fc0: Merge tag 'perf-core-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into

Re: [PATCH] pwm: Fix period and polarity in pwm_get() for non-perfect matches

On Wed, Aug 13, 2014 at 05:18:53PM +0200, Geert Uytterhoeven wrote: If pwm_get() finds a look-up entry with a perfect match (both dev_id and con_id match), the loop is aborted, and p still points to the correct struct pwm_lookup. If only an entry with a matching dev_id or con_id is found,

[tip:perf/core] perf tools: Add arm64 triplets

Commit-ID: c4d2df495c5bf05661772abf9b88f2696fd810c4 Gitweb: http://git.kernel.org/tip/c4d2df495c5bf05661772abf9b88f2696fd810c4 Author: Elliott Hughes e...@google.com AuthorDate: Thu, 14 Aug 2014 12:39:20 -0700 Committer: Arnaldo Carvalho de Melo a...@redhat.com CommitDate: Fri, 15 Aug

[tip:perf/core] perf annotate: Don' t truncate Intel style addresses

Commit-ID: 1e2bb043f171084e5f34816a4268304512d35a46 Gitweb: http://git.kernel.org/tip/1e2bb043f171084e5f34816a4268304512d35a46 Author: Alex Converse aconve...@google.com AuthorDate: Thu, 14 Aug 2014 14:03:00 -0700 Committer: Arnaldo Carvalho de Melo a...@redhat.com CommitDate: Fri, 15

[tip:perf/core] perf probe: Warn user to rebuild target with debuginfo

Commit-ID: 92561cb7883194714475c7a7775a11a9c40f75cb Gitweb: http://git.kernel.org/tip/92561cb7883194714475c7a7775a11a9c40f75cb Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com AuthorDate: Fri, 15 Aug 2014 01:44:32 + Committer: Arnaldo Carvalho de Melo a...@redhat.com

Re: [RFC PATCH 1/9] ACPI: Add support for device specific properties

On Mon, Aug 18, 2014 at 04:13:29PM +0800, Hanjun Guo wrote: Hi, Some minor comments below. On 2014-8-17 14:04, Mika Westerberg wrote: Device Tree is used in many embedded systems to describe the system configuration to the OS. It supports attaching properties or name-value pairs to

[tip:perf/core] perf probe: Don' t use strerror if strlist__add failed

Commit-ID: 6eb08660962a91212902869672dab5199827cbfd Gitweb: http://git.kernel.org/tip/6eb08660962a91212902869672dab5199827cbfd Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com AuthorDate: Thu, 14 Aug 2014 02:22:30 + Committer: Arnaldo Carvalho de Melo a...@redhat.com

[tip:perf/core] perf tools: Annotate PMU related list_head members with type info

Commit-ID: 885b5930d6632fc7df55445d9021b87d8bb17a9b Gitweb: http://git.kernel.org/tip/885b5930d6632fc7df55445d9021b87d8bb17a9b Author: Cody P Schafer d...@codyps.com AuthorDate: Fri, 15 Aug 2014 00:26:14 -0700 Committer: Arnaldo Carvalho de Melo a...@redhat.com CommitDate: Fri, 15 Aug

[tip:perf/core] perf test: Use strerror_r instead of strerror

Commit-ID: ba3dfff8ad2d98df0c8116faaeb281c93e161636 Gitweb: http://git.kernel.org/tip/ba3dfff8ad2d98df0c8116faaeb281c93e161636 Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com AuthorDate: Thu, 14 Aug 2014 02:22:45 + Committer: Arnaldo Carvalho de Melo a...@redhat.com

[tip:perf/core] perf: Use strerror_r instead of strerror

Commit-ID: b2348e1d8a67c58de44820587fabc4f987eafbb6 Gitweb: http://git.kernel.org/tip/b2348e1d8a67c58de44820587fabc4f987eafbb6 Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com AuthorDate: Thu, 14 Aug 2014 02:22:32 + Committer: Arnaldo Carvalho de Melo a...@redhat.com

[tip:perf/core] perf report: Relax -g option parsing not to limit the option order

Commit-ID: e8232f1ad4682c34e7e774c212ccd0c15bb5aa26 Gitweb: http://git.kernel.org/tip/e8232f1ad4682c34e7e774c212ccd0c15bb5aa26 Author: Namhyung Kim namhy...@kernel.org AuthorDate: Thu, 14 Aug 2014 15:01:38 +0900 Committer: Arnaldo Carvalho de Melo a...@redhat.com CommitDate: Fri, 15 Aug

[tip:perf/core] perf help: Use strerror_r instead of strerror

Commit-ID: ede395d27c60c06a2173e7a9c0f4a929a1fef73e Gitweb: http://git.kernel.org/tip/ede395d27c60c06a2173e7a9c0f4a929a1fef73e Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com AuthorDate: Thu, 14 Aug 2014 02:22:53 + Committer: Arnaldo Carvalho de Melo a...@redhat.com

[tip:perf/core] perf stat: Use strerror_r instead of strerror

Commit-ID: 759e612bf96627b64fcafe4174b3f6f2dedf2c0d Gitweb: http://git.kernel.org/tip/759e612bf96627b64fcafe4174b3f6f2dedf2c0d Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com AuthorDate: Thu, 14 Aug 2014 02:22:55 + Committer: Arnaldo Carvalho de Melo a...@redhat.com

[tip:perf/core] perf buildid-cache: Use strerror_r instead of strerror

Commit-ID: 340481ada1af9322d99e9c1ba874391f53ff4fce Gitweb: http://git.kernel.org/tip/340481ada1af9322d99e9c1ba874391f53ff4fce Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com AuthorDate: Thu, 14 Aug 2014 02:22:49 + Committer: Arnaldo Carvalho de Melo a...@redhat.com

[tip:perf/core] perf sched: Use strerror_r instead of strerror

Commit-ID: fb74fbda42dc5bcbd9bae5d75bfb6755948db21d Gitweb: http://git.kernel.org/tip/fb74fbda42dc5bcbd9bae5d75bfb6755948db21d Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com AuthorDate: Thu, 14 Aug 2014 02:22:47 + Committer: Arnaldo Carvalho de Melo a...@redhat.com

Re: [PATCH 0/5] RCU-walk support for autofs

On Mon, 2014-08-18 at 16:33 +1000, NeilBrown wrote: Hi Ian, Have you had a chance to run your tests in these patches yet? I've done what testing I can think of and cannot fault them. I haven't, I've been plagued with illness so I'm not getting nearly enough done. I'll try to put a kernel

[tip:perf/core] perf record: Use strerror_r instead of strerror

Commit-ID: 35550da389ba8752f024a44ef14b74001c4fc4d3 Gitweb: http://git.kernel.org/tip/35550da389ba8752f024a44ef14b74001c4fc4d3 Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com AuthorDate: Thu, 14 Aug 2014 02:22:43 + Committer: Arnaldo Carvalho de Melo a...@redhat.com

[tip:perf/core] perf util: Replace strerror with strerror_r for thread-safety

Commit-ID: 6e81c74cbf4b64620170da14844f1dc8a9a5950f Gitweb: http://git.kernel.org/tip/6e81c74cbf4b64620170da14844f1dc8a9a5950f Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com AuthorDate: Thu, 14 Aug 2014 02:22:36 + Committer: Arnaldo Carvalho de Melo a...@redhat.com

[tip:perf/core] perf probe: Make error messages thread-safe

Commit-ID: 5f03cba41590b5e7db5b66d2b2aa3e146ff8a84f Gitweb: http://git.kernel.org/tip/5f03cba41590b5e7db5b66d2b2aa3e146ff8a84f Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com AuthorDate: Thu, 14 Aug 2014 02:22:34 + Committer: Arnaldo Carvalho de Melo a...@redhat.com

[tip:perf/core] perf trace: Use strerror_r instead of strerror

Commit-ID: 942a91ed30267944ed3161ae292d0960fd44 Gitweb: http://git.kernel.org/tip/942a91ed30267944ed3161ae292d0960fd44 Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com AuthorDate: Thu, 14 Aug 2014 02:22:41 + Committer: Arnaldo Carvalho de Melo a...@redhat.com

[tip:perf/core] perf kvm: Use strerror_r instead of strerror

Commit-ID: f9f33fdba159a9c163ecf1dc0106ebd4c2498130 Gitweb: http://git.kernel.org/tip/f9f33fdba159a9c163ecf1dc0106ebd4c2498130 Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com AuthorDate: Thu, 14 Aug 2014 02:22:51 + Committer: Arnaldo Carvalho de Melo a...@redhat.com

[tip:perf/core] perf top: Use strerror_r instead of strerror

Commit-ID: 809adea685f7dbc9bdcc38b27d24801c461d8413 Gitweb: http://git.kernel.org/tip/809adea685f7dbc9bdcc38b27d24801c461d8413 Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com AuthorDate: Thu, 14 Aug 2014 02:22:38 + Committer: Arnaldo Carvalho de Melo a...@redhat.com

[PATCH v9 6/6] clk: max77802: Add DT binding documentation

Add Device Tree binding documentation for the clocks outputs in the Maxim 77802 Power Management IC. Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk Acked-by: Mike Turquette mturque...@linaro.org --- Changes since v6: None Changes since v5: - Fix typo error in DT

[PATCH v9 3/5] rtc: max77686: Fail to probe if no RTC regmap irqchip is set

The max77686 mfd driver adds a regmap IRQ chip which creates an IRQ domain that is used to map the virtual RTC alarm1 interrupt. The RTC driver assumes that this will always be true since the PMIC IRQ is a required property according to the max77686 DT binding doc. If an interrupts property is

[PATCH v9 0/5] Add Maxim 77802 RTC support

for the max77686 rtc. The series were tested on an Exynos5250 Snow (max77686) and Exynos5420 Peach Pit (max77802) machines and applies cleanly to both 3.17-rc1 and today's linux-next (20140818). Doug Anderson (1): rtc: max77686: Allow the max77686 rtc to wakeup the system Javier Martinez Canillas (4

[PATCH v9 1/5] rtc: max77686: Allow the max77686 rtc to wakeup the system

From: Doug Anderson diand...@chromium.org The max77686 includes an RTC that keeps power during suspend. It's convenient to be able to use it as a wakeup source. NOTE: due to wakeup ordering problems this patch alone doesn't work so well on exynos5250-snow. You also need something that brings

[PATCH v9 2/2] regulator: Add DT bindings for max77802 PMIC regulators

Add Device Tree binding documentation for the regulators present in the Maxim 77802 Power Management IC. Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk --- .../devicetree/bindings/regulator/max77802.txt | 53 ++ 1 file changed, 53 insertions(+)

[PATCH v9 2/6] clk: Add generic driver for Maxim PMIC clocks

Maxim Integrated Power Management ICs are very similar with regard to their clock outputs. Most of the clock drivers for these chips are duplicating code and are simpler enough that can be converted to use a generic driver to consolidate code and avoid duplication. Signed-off-by: Javier Martinez

[PATCH v9 1/6] clk: max77686: Add DT include for MAX77686 PMIC clock

This patch adds a dt-binding include for Maxim 77686 PMIC clock IDs that can be used by both the max77686 clock driver and Device Tree source files. Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk Reviewed-by: Krzysztof Kozlowski k.kozlow...@samsung.com Reviewed-by: Mike

[PATCH v9 2/5] rtc: max77686: Remove dead code for SMPL and WTSR.

The MAX77686 RTC chip has two features called SMPL (Sudden Momentary Power Loss) and WTSR (Watchdog Timeout and Software Resets). Support for these features seems to be implemented in the driver but compilation is disabled using a C pre-processor conditional. This code has been disabled since the

[PATCH V1 1/3] ASoC: fsl: Kconfig: remove dependence of SND_IMX_SOC for SND_SOC_IMX_PCM_DMA

Build kernel with SND_SOC_IMC_PCM_DMA=m SND_IMX_SOC=n leads the following error: sound/built-in.o: In function `fsl_sai_probe': fsl_sai.c:(.text+0x5f662): undefined reference to `imx_pcm_dma_init' sound/built-in.o: In function `fsl_esai_probe': fsl_esai.c:(.text+0x6044b): undefined

[PATCH v9 4/5] rtc: max77686: Remove unneded info log

If devm_rtc_device_register() fails a dev_err() is already reported so there is no need to do an additional dev_info(). Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk --- drivers/rtc/rtc-max77686.c | 2 -- 1 file changed, 2 deletions(-) diff --git

[PATCH v9 1/2] regulator: Add driver for max77802 PMIC PMIC regulators

The MAX77802 PMIC has 10 high-efficiency Buck and 32 Low-dropout (LDO) regulators. This patch adds support for all these regulators found on the MAX77802 PMIC and is based on a driver added by Simon Glass to the Chrome OS kernel 3.8 tree. Signed-off-by: Javier Martinez Canillas

[PATCH v9 4/6] clk: max77686: Improve Maxim 77686 PMIC clocks binding

Like most clock drivers, the Maxim 77686 PMIC clock binding follows the convention that the #clock-cells property is used to specify the number of cells in a clock provider. But the binding document is not clear enough that it shall be set to 1 since the PMIC support multiple clocks outputs.

[PATCH v9 3/6] clk: max77686: Convert to the generic max clock driver

Clocks drivers for Maxim PMIC are very similar so they can be converted to use the generic Maxim clock driver. Also, while being there use module_platform_driver() helper macro to eliminate more boilerplate code. Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk

[PATCH v9 0/2] Add Maxim 77802 regulator support

on the max77802 driver since v7 of the old series. The series were tested on an Exynos5420 based Peach Pit board and applies cleanly to both 3.17-rc1 and today's next-20140818. Javier Martinez Canillas (2): regulator: Add driver for max77802 PMIC PMIC regulators regulator: Add DT bindings

[PATCH V1 3/3] ASoC: fsl: fsl-asoc-card: Select SND_SOC_IMX_AUDMUX

Building kernel with SND_SOC_IMX_AUDMUX=n leads to the following error: sound/built-in.o: In function `fsl_asoc_card_probe': fsl-asoc-card.c:(.text+0x1467b5): undefined reference to `imx_audmux_v2_configure_port' fsl-asoc-card.c:(.text+0x1467d0): undefined reference to

[PATCH v9 5/5] rtc: Add driver for Maxim 77802 PMIC Real-Time-Clock

The MAX7802 PMIC has a Real-Time-Clock (RTC) with two alarms. This patch adds support for the RTC and is based on a driver added by Simon Glass to the Chrome OS kernel 3.8 tree. Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk Reviewed-by: Krzysztof Kozlowski

[PATCH v9 0/6] Add Maxim 77802 clocks support

the patches had been already acked by you so I hope there won't be issues to get them merged. The series were tested on an Exynos5250 Snow (max77686) and Exynos5420 Peach Pit (max77802) machines and applies cleanly to both 3.17-rc1 and today's linux-next (20140818). Javier Martinez Canillas (6): clk

Re: [PATCH] KVM: x86: Avoid emulating instructions on #UD mistakenly

Il 13/08/2014 16:21, Nadav Amit ha scritto: Correction: the word “never” in the message is too harsh. Nonetheless, there is a regression bug. I encountered it with “wrfsbase” instruction. So KVM is emulating wrfsbase even if the host doesn't support it? I'm swapping the order of the two

[PATCH v9 5/6] clk: Add driver for Maxim 77802 PMIC clocks

The MAX77802 PMIC has two 32.768kHz Buffered Clock Outputs with Low Jitter Mode. This patch adds support for these two clocks. Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk Reviewed-by: Krzysztof Kozlowski k.kozlow...@samsung.com Acked-by: Mike Turquette

Re: [PATCH 0/8] mtd: nand: Support for new DT NAND driver

On Thu, 14 Aug 2014, Brian Norris wrote: On Wed, Aug 13, 2014 at 10:11:59AM +0100, Lee Jones wrote: Hi Brian, Pekon, I believe all of your queries have either been answered or addressed and I am hoping this will be the last submission. :) /me crosses fingers! Kind regards,

[PATCH V1 2/3] ASoC: fsl-asoc-card: Fix build warning for maybe-uninitialized

When build fsl-asoc-card as module, there is following error: sound/soc/fsl/fsl-asoc-card.c: In function 'fsl_asoc_card_probe': sound/soc/fsl/fsl-asoc-card.c:547:13: warning: 'asrc_np' may be used uninitialized in this function [-Wmaybe-uninitialized] of_node_put(asrc_np);

[PATCH V1 0/3] fix build error/warning in sound/soc/fsl

This series patch is for fixing build error/waring in sound/soc/fsl Shengjiu Wang (3): ASoC: fsl: Kconfig: remove dependence of SND_IMX_SOC for SND_SOC_IMX_PCM_DMA ASoC: fsl-asoc-card: Fix build warning for maybe-uninitialized ASoC: fsl: fsl-asoc-card: Select SND_SOC_IMX_AUDMUX

Re: [PATCH] pwm: Fix period and polarity in pwm_get() for non-perfect matches

Hi Thierry, On Mon, Aug 18, 2014 at 10:20 AM, Thierry Reding thierry.red...@gmail.com wrote: Could we achieve the same by storing a pointer to the best match and then use that instead of p? Perhaps something like this: struct pwm_lookup *entry; ... if

Re: [PATCH] brd: add ram disk visibility option

On Sun, 17 Aug 2014 12:45:31 -0600, Jens Axboe ax...@fb.com wrote: On 2014-08-16 09:55, Dmitry Monakhov wrote: Signed-off-by: Dmitry Monakhov dmonak...@openvz.org You forgot a commit message justifying this change? I've assumed that one line comment is enough :( Please take a look at the

[PATCH 3/3] cpuidle: Using the wake_up_all_cpus() to wake up all idle cpus

Currently kick_all_cpus_sync() or smp_call_function() can not break the polling idle cpu immediately. Here using wake_up_all_cpus() which can wake up the polling idle cpu quickly is much helpful for power. Signed-off-by: Chuansheng Liu chuansheng@intel.com --- drivers/cpuidle/cpuidle.c |

Re: [PATCH] staging: comedi: s626: remove unnecessary variable initialization

On 2014-08-18 04:43, Chase Southwood wrote: We initialize 'irqbit' to 0, only to properly set it immediately afterwards. Just remove the zero-initialization. Signed-off-by: Chase Southwood chase.southw...@gmail.com Cc: Ian Abbott abbo...@mev.co.uk Cc: H Hartley Sweeten

Re: [PATCH] staging: comedi: dt2801: change function return type to void

On 2014-08-18 04:43, Chase Southwood wrote: cppcheck was complaining that the variable 'stat' is being reassigned before the old value is used. Upon inspection, I found that dt2801_writecmd() cannot fail, always returns 0, and most callers already do not bother with assigning its return value

Re: [TYPO 9/9] [typo] spelling, punctuation in Documentation/...

Dear Randy, thanks for you reply. * Randy Dunlap rdun...@infradead.org [140818 09:37]: On 08/17/14 11:30, Markus Osterhoff wrote: diff --git a/Documentation/HOWTO b/Documentation/HOWTO -gcc`) for some information on them. +gcc') for some information on them. Backquotes imply that the

[PATCH 2/3] smp: Adding new function wake_up_all_cpus()

Currently kick_all_cpus_sync() can break non-polling idle cpus thru IPI interrupts. But sometimes we need to break the polling idle cpus immediately to reselect the suitable c-state, also for non-idle cpus, we need to do nothing if we try to wake up them. Here adding one new function

Re: [PATCH v3 1/3] init / kthread: add module_long_probe_init() and module_long_probe_exit()

At Sun, 17 Aug 2014 20:21:38 +0200, Oleg Nesterov wrote: On 08/17, Luis R. Rodriguez wrote: In the last iteration that I have stress tested for corner cases I just get_task_struct() on the init and then put_task_struct() at the exit, is that fine too or are there reasons to prefer

[PATCH v3 12/13] pmcraid: Get rid of a redundant assignment

Signed-off-by: Alexander Gordeev agord...@redhat.com Cc: Anil Ravindranath anil_ravindran...@pmc-sierra.com Cc: linux-s...@vger.kernel.org Cc: linux-...@vger.kernel.org --- drivers/scsi/pmcraid.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/scsi/pmcraid.c b/drivers/scsi/pmcraid.c

Re: [PATCH 3/5] watchdog: fix print-once on enable

* Don Zickus dzic...@redhat.com wrote: From: Ulrich Obergfell uober...@redhat.com This patch avoids printing the message 'enabled on all CPUs, ...' multiple times. For example, the issue can occur in the following scenario: 1) watchdog_nmi_enable() fails to enable PMU counters and sets

[PATCH v3 02/13] hpsa: Use pci_enable_msix_range() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

Re: [PATCH 2/5] softlockup: make detector be aware of task switch of processes hogging cpu

* Don Zickus dzic...@redhat.com wrote: From: chai wen chaiw.f...@cn.fujitsu.com For now, soft lockup detector warns once for each case of process softlockup. But the thread 'watchdog/n' may not always get the cpu at the time slot between the task switch of two processes hogging that cpu

[PATCH v3 03/13] megaraid: Fail resume if MSI-X re-initialization failed

Currently the driver fails to analize MSI-X re-enablement status on resuming and always assumes the success. This update checks the MSI-X initialization result and fails to resume if MSI-Xs re-enablement failed. Signed-off-by: Alexander Gordeev agord...@redhat.com Acked-by: Kashyap Desai

Re: [RFC] usb issue on imx27: 3 clocks are needed

On Sat, Aug 16, 2014 at 05:38:30PM +0200, Philippe Reynes wrote: Hi all, i.MX27's usb needs three clocks (usb_ipg_gate, usb_ahb_gate and usb_div) but the current chipidea driver implementation, and devicetree, provides only ipg and ahb. Consequently, if the bootloader don't enable the last

[PATCH v3 05/13] mpt2sas: Use pci_enable_msix_exact() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

[PATCH 1/1] iommu/vt-d : clear old root entry for dump kernel

If intel_iommu is enabled, when kdump kernel boots, the old root entry should be cleared, otherwise it may cause DMAR error. To make it works for more enviroments, this patch does not use is_kdump_kernel() to check it, but reads the register to check whether hardware is using old root entry.

Re: [RFC PATCH 1/9] ACPI: Add support for device specific properties

On 2014-8-18 16:27, Mika Westerberg wrote: On Mon, Aug 18, 2014 at 04:13:29PM +0800, Hanjun Guo wrote: Hi, Some minor comments below. On 2014-8-17 14:04, Mika Westerberg wrote: Device Tree is used in many embedded systems to describe the system configuration to the OS. It supports

[PATCH v3 01/13] hpsa: Fallback to MSI rather than to INTx if MSI-X failed

Currently the driver falls back to INTx mode when MSI-X initialization failed. This is a suboptimal behaviour for chips that also support MSI. This update changes that behaviour and falls back to MSI mode in case MSI-X mode initialization failed. Signed-off-by: Alexander Gordeev

[PATCH 1/3] sched: Add new API wake_up_if_idle() to wake up the idle cpu

Implementing one new API wake_up_if_idle(), which is used to wake up the idle CPU. Suggested-by: Andy Lutomirski l...@amacapital.net Signed-off-by: Chuansheng Liu chuansheng@intel.com --- include/linux/sched.h |1 + kernel/sched/core.c | 16 2 files changed, 17

[PATCH v3 11/13] lpfc: Use pci_enable_msix_range() instead of pci_enable_msix()

As result of deprecation of MSI-X/MSI enablement functions pci_enable_msix() and pci_enable_msi_block() all drivers using these two interfaces need to be updated to use the new pci_enable_msi_range() or pci_enable_msi_exact() and pci_enable_msix_range() or pci_enable_msix_exact() interfaces.

  1   2   3   4   5   6   7   8   9   10   >