On Thu, 2015-05-28 at 01:36 +0100, Alasdair G Kergon wrote:
On Wed, May 27, 2015 at 04:42:44PM -0700, Ming Lin wrote:
Here are fio results of XFS on a DM stripped target with 2 SSDs + 1 HDD.
Does it make sense?
To stripe across devices with different characteristics?
Some suggestions.
On Mon, Jun 01, 2015 at 01:19:16PM +0800, Wangnan (F) wrote:
On 2015/6/1 10:12, Namhyung Kim wrote:
Hi Alexei and Wang,
On Thu, May 28, 2015 at 08:35:19PM -0700, Alexei Starovoitov wrote:
On Thu, May 28, 2015 at 03:14:44PM +0800, Wangnan (F) wrote:
On 2015/5/28 14:09, Alexei Starovoitov
On Sat, May 23, 2015 at 7:15 AM, Christoph Hellwig h...@lst.de wrote:
On Fri, May 22, 2015 at 11:18:32AM -0700, Ming Lin wrote:
This will bring not only performance improvements, but also a great amount
of reduction in code complexity all over the block layer. Performance gain
is possible due
On Mon, Jun 01, 2015 at 11:16:51AM +0530, Sudip Mukherjee wrote:
On Mon, Jun 01, 2015 at 07:05:30AM +0900, Greg Kroah-Hartman wrote:
On Wed, May 20, 2015 at 08:56:56PM +0530, Sudip Mukherjee wrote:
After 5 versions of WIP, finally a patch submission.
parport subsystem is now in the
-Original Message-
From: Greg KH [mailto:gre...@linuxfoundation.org]
Sent: Monday, June 01, 2015 2:32 AM
To: Joe Perches
Cc: Badola Nikhil-B46172; linux-kernel@vger.kernel.org;
st...@rowland.harvard.edu; linux-...@vger.kernel.org
Subject: Re: [PATCH 3/5] drivers:usb:fsl: Replace
On Fri, 29 May 2015 18:36:50 +0200 Darren Hart wrote:
Making sure to lock only the intel GPU when present and especially
protecting
against nvidia driver will be hard if legacy-IO is being processed by a
hidden
device!
Ugh indeed. Worst case we can special case via dmi strings. Is
Add MT8173 I2C device nodes, include I2C controllers and pins.
MT8173 has six I2C controllers, from i2c0 to i2c6, exclude i2c5.
The 6th I2C controller register base doesn't next to 5th I2C,
and there is a hardware between 5th and 6th I2C controller. So
SoC designer name 6th controller as i2c6, not
This series add MT8173 watchdog and I2C device nodes. Both device nodes
are based on 4.1-rc1, but I2C need two extra CCF patches from Sascha [1][2].
[1] clk: Add common clock support for Mediatek MT8135 and MT8173
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-April/338763.html
Hi Dave,
here are three more important fixes I'm hoping to get to 4.1 still, I
hope I'm not too late with these. Please let me know if there are any
problems.
Kalle
The following changes since commit aefa441b150279dd8d25658e018898a3fe9a6769:
Merge tag 'iwlwifi-for-kalle-2015-05-21' of
Hi Paul,
Today's linux-next merge of the audit tree got a conflict in
security/lsm_audit.c between commit 5deeb5cece3f (lsm: copy comm
before calling audit_log to avoid race in string printing) from Linus'
tree and commit 5c5bc97e2fc8 (lsm: rename duplicate labels in
LSM_AUDIT_DATA_TASK audit
Add MT8173 watchdog device node.
Signed-off-by: Eddie Huang eddie.hu...@mediatek.com
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
index 30ac8dd..b52ec43
The problem showed up when running hotplug operations and changing
governors in parallel. The crash would be at:
[ 174.319645] Unable to handle kernel paging request for data at address
0x
[ 174.319782] Faulting instruction address: 0xc053b3e0
cpu 0x1: Vector: 300 (Data Access)
Hi Baoquan,
On Mon, Jun 01, 2015 at 11:09:40AM +0800, Baoquan He wrote:
I am reading amd iommu code because I have some knowledge about intel
iommu since review Zhenhua's fixing kdump error patches. Now there's
a question I didn't find answer.
In amd iommu state_next() is the state machine
On Fri, May 29, 2015 at 06:44:44PM +1000, Alexey Kardashevskiy wrote:
At the moment the DMA setup code looks for the ibm,opal-tce-kill
property which contains the TCE kill register address. Writing to
this register invalidates TCE cache on IODA/IODA2 hub.
This moves the register address from
On Fri, May 29, 2015 at 06:44:42PM +1000, Alexey Kardashevskiy wrote:
This adds tce_iommu_take_ownership() and tce_iommu_release_ownership
which call in a loop iommu_take_ownership()/iommu_release_ownership()
for every table on the group. As there is just one now, no change in
behaviour is
On Fri, May 29, 2015 at 06:44:45PM +1000, Alexey Kardashevskiy wrote:
The iommu_table struct keeps a list of IOMMU groups it is used for.
At the moment there is just a single group attached but further
patches will add TCE table sharing. When sharing is enabled, TCE cache
in each PE needs to
On Fri, May 29, 2015 at 06:44:41PM +1000, Alexey Kardashevskiy wrote:
Modern IBM POWERPC systems support multiple (currently two) TCE tables
per IOMMU group (a.k.a. PE). This adds a iommu_table_group container
for TCE tables. Right now just one table is supported.
For IODA, instead of
Andreas Mohr a...@lisas.de writes:
Hi,
I just had a not so nice experience
when finally upgrading to a new 4.1-rc5
with CONFIG_MODULE_COMPRESS newly enabled -
userspace binary parts (kmod 18 or 20 in my case)
did not have compression enabled
(at least on Debian 8pre, vs. encountering it
[cc: Willy Tarreau]
On Mon, Jun 1, 2015 at 3:26 AM, starlight.201...@binnacle.cx wrote:
Hello,
Apoligies if I have submitted to the wrong lists.
Encountered a regression in
2.6.32.66 relative to 2.6.32.65.
Crash eight minutes after boot.
Will responded with additional details
if the
Hi Borislav,
Today's linux-next merge of the edac-amd tree got a conflict in
arch/tile/Kconfig between commit 5bf6c07a1843 (tile: add
asm/word-at-a-time.h and enable support functions) from the tile
tree and commit b01aec9b2c7d (EDAC: Cleanup atomic_scrub mess) from
the edac-amd tree.
I fixed it
On Sun, May 31, 2015 at 08:54:11PM -0400, Paul Gortmaker wrote:
This was using module_init, but there is no way this code can
be modular.
No, I think you could actually make it modular if you really wanted to.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
On Sun, May 31, 2015 at 08:54:12PM -0400, Paul Gortmaker wrote:
This was using module_init, but there is no way this code can
be modular.
Same thing; you could actually make this modular if you wanted to.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
On Fri, May 29, 2015 at 06:44:47PM +1000, Alexey Kardashevskiy wrote:
At the moment writing new TCE value to the IOMMU table fails with EBUSY
if there is a valid entry already. However PAPR specification allows
the guest to write new TCE value without clearing it first.
Another problem this
Hi Borislav,
After merging the edac-amd tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/edac/xgene_edac.c: In function 'xgene_edac_pmd_l2c_version1':
drivers/edac/xgene_edac.c:792:2: error: implicit declaration of function
'MIDR_VARIANT'
On Fri, 2015-05-29 at 11:38 -0500, Rob Herring wrote:
Combine the ChipIdea USB binding into a single document to reduce
duplication and fragmentation. This marks use of the old PHY bindings as
deprecated. Future compatible bindings should use generic PHY binding.
Signed-off-by: Rob Herring
Hi,
On 06/01/2015 02:25 AM, Stephen Rothwell wrote:
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
arch/arm/boot/dts/zynq-7000.dtsi between commit 9eeb5161397a (ARM:
zynq: DT: Use the zynq binding with macb) from Linus' tree and commit
4481b18b7cf0 (ARM: zynq: DT:
On 30/05/15 10:15, Maxime Coquelin wrote:
Hi Daniel,
Nice driver, please find my comments below.
Once fixed, you can add:
Reviewed-by: Maxime Coquelin mcoquelin.st...@gmail.com
Thanks for the review.
No concerns at my end. I'll act on all of the issues you raised.
Daniel.
--
To
On 01-06-15, 01:40, Preeti U Murthy wrote:
I have to mention that this is somewhat inspired by:
https://git.linaro.org/people/viresh.kumar/linux.git/commit/1e37f1d6ae12f5896e4e216f986762c3050129a5
and I was waiting to finish some core-changes to make all this simple.
I am fine to you trying to
Hello.
On 6/1/2015 1:41 AM, Colin Ian King wrote:
From: Colin Ian King colin.k...@canonical.com
If kzalloc returns null then isp1760_ep_alloc_request performs
a null pointer deference on req.
Dereference, not deference.
Shall I send v2 for this stupid typo then?
Definitely,
Hi Nicholas,
Today's linux-next merge of the target-updates tree got a conflict in
drivers/target/target_core_transport.c between commit a3541703ebbf
(target: Use a PASSTHROUGH flag instead of transport_types) from
Linus' tree and commit 50c44f9b1587 (target: Add support for fabric
IRQ
This patch introduces the timer_get64 method with itimerspec64
type for k_clock structure, that makes it ready for the 2038 year.
Convert to the 64bit method with itimerspec64 type for the
timer_gettime syscall function, and change the timer_gettime syscall
implementation.
Also add a default
Hi Nicholas,
On Mon, 01 Jun 2015 04:35:52 -0700 Nicholas A. Bellinger
n...@linux-iscsi.org wrote:
Apologies for the conflicts vs. mainline in today's linux-next
The latest in target-pending/for-next from this morning should address
these conflicts vs. mainline.
Thanks, tomorrow should be
This patch introduces the timer_set64 method with itimerspec64 type
for k_clock structure, that makes it ready for the 2038 year.
Convert to the 64bit method with itimerspec64 type for the
timer_settime syscall function, and change the timer_settime syscall
implementation.
Also add a default
On 29 May 2015 at 15:23, Tomeu Vizoso tomeu.viz...@gmail.com wrote:
On 29 May 2015 at 12:48, Tomeu Vizoso tomeu.viz...@gmail.com wrote:
On 31 March 2015 at 01:20, Dmitry Torokhov dmitry.torok...@gmail.com wrote:
Some devices take a long time when initializing, and not all drivers are
suited to
To make it is ready for 2038 issue when implementing the conversion
between cputime and timespec64, this patch introduces the
timespec64_to_jiffies() and jiffies_to_timespec64() functions.
And move the old functions timespec64_to_jiffies() and
jiffies_to_timespec64() to jiffies.h file, for it is
retint_kernel doesn't require %rcx to be pointing to thread info
(anymore?), and the code on the two alternative paths is - not really
surprisingly - identical.
Signed-off-by: Jan Beulich jbeul...@suse.com
Cc: Andy Lutomirski l...@kernel.org
---
arch/x86/kernel/entry_64.S | 10 ++
1
On Fri, May 29, 2015 at 6:07 PM, Andrew Morton
a...@linux-foundation.org wrote:
On Thu, 28 May 2015 16:28:37 -0400 Dan Streetman ddstr...@ieee.org wrote:
Change frontswap single pointer to a singly linked list of frontswap
implementations. Update Xen tmem implementation as register no longer
No functional change, but now previously overloaded sram_probe() is
greatly simplified and perceptible, reserved regions logic also has
its own space.
Signed-off-by: Vladimir Zapolskiy vladimir_zapols...@mentor.com
---
Changes from v4 to v5:
- rebased on top of v5 series
Changes from v2 to v3:
-
Since some space in SRAM may be reserved, report the left free space
in the allocated memory pool instead of total physical size of the
SRAM device.
Signed-off-by: Vladimir Zapolskiy vladimir_zapols...@mentor.com
---
Changes from v4 to v5:
- rebased on top of v5 series
Changes from v1 to v2:
-
No functional change, this is a preceding change to simplify
separation of reserved partition handling logic from probe()
function.
Signed-off-by: Vladimir Zapolskiy vladimir_zapols...@mentor.com
---
Changes from v4 to v5:
- rebased on top of v5 series
Changes from v3 to v4:
- rebased on top of
Most of the included header files are already included as
dependencies.
Signed-off-by: Vladimir Zapolskiy vladimir_zapols...@mentor.com
---
drivers/misc/sram.c | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/drivers/misc/sram.c b/drivers/misc/sram.c
index
On Wed, May 20, 2015 at 10:42 AM, Masahiro Yamada
yamada.masah...@socionext.com wrote:
The address for SD0_WP_CD_SEL, SD1_WP_CD_SEL is 0xf8000830,
0xf8000834, respectively.
Each offset address must be prefixed with 0x.
Signed-off-by: Masahiro Yamada yamada.masah...@socionext.com
No reply
On Wed, May 20, 2015 at 10:42 AM, Masahiro Yamada
yamada.masah...@socionext.com wrote:
The offset to the mux register is missing.
Signed-off-by: Masahiro Yamada yamada.masah...@socionext.com
No reply from Sören, but applying anyway since it seems to make sense.
Only for -next though.
Yours,
On Wed, May 20, 2015 at 12:30 PM, Grygorii Strashko
grygorii.stras...@linaro.org wrote:
This patch updates GPIO debugfs code to show Linux IRQ number
for GPIOs requested as irq.
After this patch sys/kernel/debug/gpio will produce following output:
...
GPIOs 160-191,
Add MT8173 watchdog device node.
Signed-off-by: Eddie Huang eddie.hu...@mediatek.com
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
index 30ac8dd..b52ec43
Add MT8173 I2C device nodes, include I2C controllers and pins.
MT8173 has six I2C controllers, from i2c0 to i2c6, exclude i2c5.
The 6th I2C controller register base doesn't next to 5th I2C,
and there is a hardware between 5th and 6th I2C controller. So
SoC designer name 6th controller as i2c6, not
From: S Twiss stwiss.opensou...@diasemi.com
Remove the unused variable build warning for reg_matches that appears
during the compilation of the DA9062 regulator driver.
da9062-regulator.c: In function da9062_regulator_probe:
da9062-regulator.c:727:29: warning: unused variable reg_matches
The WM5102 and WM8997 codecs have an internal dynamic clock booster.
When this booster is active, the DCVDD voltage must be increased.
If all the currently active audio paths can run with the root SYSCLK
we can disable the booster, allowing us to turn down DCVDD voltage
to save power.
Previously
On Mon, Jun 01, 2015 at 03:02:23PM +0200, Jiri Olsa wrote:
On Tue, May 26, 2015 at 07:37:30PM +0200, Andi Kleen wrote:
hum, so this is assuming that having cycles fort 1st entry
means there'll be for the rest?
Also in that case why is there the '!= cycles' check within
This series add MT8173 watchdog and I2C device nodes. Both device nodes
are based on 4.1-rc1, but I2C need two extra CCF patches from Sascha [1][2].
[1] clk: Add common clock support for Mediatek MT8135 and MT8173
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-April/338763.html
On 06/01/15 at 12:33pm, Joerg Roedel wrote:
On Mon, Jun 01, 2015 at 06:19:26PM +0800, Baoquan He wrote:
On 06/01/15 at 11:21am, Joerg Roedel wrote:
Thanks for looking into this. Unfortunatly this somehow conflicts with
my recent default-domain patch-set, which moves functionality into the
Hi Nicholas,
Today's linux-next merge of the target-updates tree got so many
conflicts against Linus' tree that I just gave up and dropped it
completely. Please fix up this mess.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgpfUgfm4hBvx.pgp
Description: OpenPGP
On Mon, 01 Jun 2015 13:36:45 +0300
Adrian Hunter adrian.hun...@intel.com wrote:
On 01/06/15 12:20, David Jander wrote:
qty is the maximum number of discard that _do_ fit in the timeout, not
the first amount that does _not_ fit anymore.
This seemingly harmless error has a very severe
This patch introduces hrtimer_get_res64() function to get the timer
resolution with timespec64 type, and moves the hrtimer_get_res()
function into include/linux/hrtimer.h as a 'static inline' helper that
just calls hrtimer_get_res64.
It is ready for 2038 year when getting the timer resolution by
This patch splits out the guts of the clock_getres syscall and
changes the clock_getres syscall implementation to prepare the
converting to 64bit methods for the clock_getres syscall function
in posix-timers.c file.
Signed-off-by: Baolin Wang baolin.w...@linaro.org
---
kernel/time/posix-timers.c
On 05/29/2015 04:24 PM, John Stultz wrote:
As Prarit reported here:
https://lkml.org/lkml/2015/5/27/458
Since the leapsecond is applied at timer tick time, and not
the actual second edge, ABS_TIME CLOCK_REALTIME timers set for
right after the leapsecond could fire a second early, since
This patch converts the timespec type to timespec64 type for
timekeeping_clocktai() function which is used only in the
posix-timers.c file, that makes it ready for 2038 issue.
And remove the declaration of timekeeping_clocktai() in
kernel/time/timekeeping.h file, cause nothing uses that
This patch splits out the guts of the clock_settime syscall and
changes the clock_settime syscall implementation to prepare the
converting to 64bit methods for the clock_settime syscall function
in posix-timers.c file.
Signed-off-by: Baolin Wang baolin.w...@linaro.org
---
This patch introduces the clock_set64 method with timespec64 type for
k_clock structure, that makes it ready for the 2038 year.
Convert to the 64bit method with timespec64 type for the clock_settime
syscall function, and change the clock_settime syscall implementation.
Also add a default 64bit
This patch splits out the guts of the clock_gettime syscall and
changes the clock_gettime syscall implementation to prepare the
converting to 64bit methods for the clock_gettime syscall function
in posix-timers.c file.
Signed-off-by: Baolin Wang baolin.w...@linaro.org
---
This patch introduces the clock_get64 method with timespec64 type for
k_clock structure, that makes it ready for the 2038 year.
Convert to the 64bit method with timespec64 type for the clock_gettime
syscall function, and change the clock_gettime syscall implementation.
Also add a default 64bit
This patch introduces the clock_getres64 method with timespec64 type
for k_clock structure, that makes it ready for the 2038 year.
Convert to the 64bit method with timespec64 type for the clock_getres
syscall function, and change the clock_getres syscall implementation.
Also add a default 64bit
tbclk is used by ehrpwm to generate PWM waveform on DRA7 SoC. Add Linux
clock to control ehrpwm tbclk.
Signed-off-by: Vignesh R vigne...@ti.com
---
arch/arm/boot/dts/dra7.dtsi | 5 +
arch/arm/boot/dts/dra7xx-clocks.dtsi | 26 ++
2 files changed, 31
This patch converts the timespec type to timespec64 type and
converts the itimerspec type to itimerspec64 type for k_clock
callback functions in posix-timers.c file.
Signed-off-by: Baolin Wang baolin.w...@linaro.org
---
kernel/time/posix-timers.c | 92
tbclk is needed by ehrpwm to generate pwm waveforms. Hence, register
the required clock information.
Signed-off-by: Vignesh R vigne...@ti.com
---
drivers/clk/ti/clk-7xx.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/clk/ti/clk-7xx.c b/drivers/clk/ti/clk-7xx.c
index
This patch converts the timespec/itimerspec type to timespec64/itimerspec64
type for k_clock callback functions in mmtimer.c file, that makes it ready
for 2038 issue.
Signed-off-by: Baolin Wang baolin.w...@linaro.org
---
drivers/char/mmtimer.c | 36 +---
1 file
Add hwmod entries for the PWMSS on DRA7.
Signed-off-by: Vignesh R vigne...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 239 ++
1 file changed, 239 insertions(+)
diff --git a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c
panic_on_oom allows administrator to set OOM policy to panic the system
when it is out of memory to reduce failover time e.g. when resolving
the OOM condition would take much more time than rebooting the system.
out_of_memory tries to be clever and prevent from premature panics
by checking the
On Mon, Jun 01, 2015 at 07:18:02PM +0800, Baoquan He wrote:
Checked the code again, it may be a code bug if this is done in
device_dma_ops_init(). Since this is called in
amd_iommu_init_dma_ops()-amd_iommu_init_dma(). And amd_iommu_init_dma()
is only called in case IOMMU_INTERRUPTS_EN code
All of the k_clock users have been converted to the new methods,
this patch removes the older methods with timepsec/itimerspec type,
as a result, the k_clock structure is ready for the year 2038 year.
Signed-off-by: Baolin Wang baolin.w...@linaro.org
---
include/linux/posix-timers.h |9 -
On Mon, Jun 01, 2015 at 01:03:16PM +0900, Greg KH wrote:
On Sun, May 31, 2015 at 11:24:42PM -0300, Gaston Gonzalez wrote:
On Mon, Jun 01, 2015 at 10:53:20AM +0900, Greg KH wrote:
On Sun, May 31, 2015 at 10:41:52PM -0300, Gaston Gonzalez wrote:
On Mon, Jun 01, 2015 at 08:24:17AM +0900,
On Mon, Jun 01, 2015 at 12:39:31PM +, Dhere, Chaitanya (C.) wrote:
From: Chaitanya Dhere cvija...@visteon.com
This change was detected with help of coccinelle tool.
Hi,
can you please let me know how to use coccinelle to detect indention
issues. I never knew coccinelle can be used to check
Hi all,
Changes since 20150529:
New tree: pcmcia (reinstated)
Dropped tree: target-updates (to many conflicts)
The arm tree still had its build failure so I used the version from
next-20150528.
The arm-perf tree gained a conflict against Linus' tree.
The arm-soc tree gained a conflict
On Mon, May 25, 2015 at 8:54 PM, grygorii.stras...@linaro.org
grygorii.stras...@linaro.org wrote:
.. Looks like it's time to drop this stuff :,,(
Ooops missed this part of the discussion. Indeed it will call accessors
on non-requested GPIO lines. Damned. Taking these patches out again.
Yours,
On 06/01/15 at 11:21am, Joerg Roedel wrote:
Hi Baoquan,
On Mon, Jun 01, 2015 at 05:09:02PM +0800, Baoquan He wrote:
Then I am wondering how amd_iommu_dma_ops is assigned. Maybe I need
check all functions more clearly.
The AMD IOMMU driver only uses per-device dma_ops. They are assigned
Hi Stephen,
On Mon, 2015-06-01 at 20:48 +1000, Stephen Rothwell wrote:
Hi Nicholas,
Today's linux-next merge of the target-updates tree got a conflict in
drivers/target/target_core_configfs.c between commit d588cf8f618d
(target: Fix se_tpg_tfo-tf_subsys regression + remove tf_subsystem)
This patch series changes the 32-bit time types (timespec/itimerspec) to
the 64-bit types (timespec64/itimerspec64), since 32-bit time types will
break in the year 2038.
This patch series introduces new methods with timespec64/itimerspec64 type,
and removes the old ones with timespec/itimerspec
Legacy IPs like PWMSS, present under l4per2_7xx_clkdm, cannot support
smart-idle when its clock domain is in HW_AUTO on DRA7 SoCs. Hence,
program clock domain to SW_WKUP.
Signed-off-by: Vignesh R vigne...@ti.com
---
arch/arm/mach-omap2/clockdomains7xx_data.c | 2 +-
1 file changed, 1
These are new helper functions that convert between a user timespec/
itimerspec and a kernel timespec64/itimerspec64 structure.
These macros can change the types underneath from both ends and it
will work efficiently on both 32-bit and 64-bit that can avoid the
CONFIG_64BIT macro in syscall
2015-06-01 8:29 GMT+02:00 Eddie Huang eddie.hu...@mediatek.com:
Add MT8173 I2C device nodes, include I2C controllers and pins.
MT8173 has six I2C controllers, from i2c0 to i2c6, exclude i2c5.
The 6th I2C controller register base doesn't next to 5th I2C,
and there is a hardware between 5th and
Added support to ZynqMP SoC on the existing zynq gpio driver.
Signed-off-by: Anurag Kumar Vulisha anura...@xilinx.com
---
drivers/gpio/Kconfig |2 +-
drivers/gpio/gpio-zynq.c | 191 ++
2 files changed, 126 insertions(+), 67 deletions(-)
diff
Hi Shawn,
After merging the imx-mxs tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/clocksource/timer-imx-gpt.c: In function 'mxc_clocksource_init':
drivers/clocksource/timer-imx-gpt.c:173:2: error: invalid use of undefined type
'struct delay_timer'
On Thu, May 21, 2015 at 1:21 PM, Geert Uytterhoeven
geert+rene...@glider.be wrote:
If an interrupt controller doesn't support wake-up configuration,
irq_set_irq_wake() returns an error code. Then any subsequent call
trying to deconfigure wake-up will cause an imbalance, and a warning
will be
In theory the ADSP driver should not need to know anything
about the codec it is part of. But the WM5102 needs DVFS
control based on ADSP clocking speed. This was being handled
by bundling part of the knowledge of this into the ADSP driver.
This change moves this handling out of the ADSP driver
On Wed, May 27, 2015 at 2:55 PM, Seth Forshee
seth.fors...@canonical.com wrote:
I haven't seen anything to indicate that this filesystem will be broken
by this, just that it's broken by untranslated pids. Presumably it would
just reject any requests which aren't representable in its namespace.
The WM8997 and WM5102 codecs need to boost DVFS for higher sample rates.
Signed-off-by: Richard Fitzgerald r...@opensource.wolfsonmicro.com
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
sound/soc/codecs/arizona.c | 19 ++-
1 files changed, 18
Using the driver for the internal regulator to also enable/disable
the codec internal clock frequency controller is an unexpected
side-effect for a regulator, and also means that the core clocks
won't be changed as expected if an external regulator is used to
power the codec.
The DVFS is now
Hi Nicholas,
Today's linux-next merge of the target-updates tree got a conflict in
drivers/target/target_core_pr.c between commit d588cf8f618d (target:
Fix se_tpg_tfo-tf_subsys regression + remove tf_subsystem) from
Linus' tree and commits c6eec4d58f5d (target: remove tf_subsystem
pointers) and
On 27.05.15 14:05, Laurent Pinchart wrote:
Even though 'compatability' has a dedicated entry in the Wiktionary,
it's listed as 'Mispelling of compatibility'. Fix it.
Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
---
arch/metag/include/asm/elf.h | 2 +-
Add Holt descrete ADC driver for HI-8435/8436/8437 chips
Signed-off-by: Vladimir Barinov vladimir.bari...@cogentembedded.com
---
drivers/iio/adc/Kconfig | 12 +
drivers/iio/adc/Makefile | 1 +
drivers/iio/adc/hi-843x.c | 777 ++
3 files changed,
Add Holt Integrated Circuits, Inc. to the list of device tree vendor prefixes
Signed-off-by: Vladimir Barinov vladimir.bari...@cogentembedded.com
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
A pointer device node reference should be decremented on manual exit
from for_each_available_child_of_node() loop.
Signed-off-by: Vladimir Zapolskiy vladimir_zapols...@mentor.com
---
drivers/misc/sram.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/misc/sram.c
If devm_gen_pool_create() fails, the previously enabled sram-clk is
not disabled on probe() exit.
Because reserved block logic relies only on information from device tree,
there is no need to get and enable device clock in advance, especially
because not provided clock is not considered as an
On Wed, May 20, 2015 at 12:30 PM, Grygorii Strashko
grygorii.stras...@linaro.org wrote:
Now many of GPIO drivers implement two interfaces gpiolib and irqchip
which are essentially orthogonal. So, now GPIO line can be requested
in three ways:
1) As pure GPIO (gpioX_request())
2) As pure GPIO
On Tue, May 26, 2015 at 07:37:30PM +0200, Andi Kleen wrote:
hum, so this is assuming that having cycles fort 1st entry
means there'll be for the rest?
Also in that case why is there the '!= cycles' check within
addr_map_symbol__account_cycles ?
It means there might be. It's just a short
On Wed, May 20, 2015 at 4:23 PM, Sören Brinkmann
soren.brinkm...@xilinx.com wrote:
For the series:
Reviewed-by: Sören Brinkmann soren.brinkm...@xilinx.com
Ah that is Sören's Review tag.
It may be a good ides to add
Fixes: add958cee967 pinctrl: Add driver for Zynq
(I suspect that bug is
Em Mon, Jun 01, 2015 at 03:03:11PM +0900, Namhyung Kim escreveu:
On Mon, Jun 01, 2015 at 01:19:16PM +0800, Wangnan (F) wrote:
On 2015/6/1 10:12, Namhyung Kim wrote:
On Thu, May 28, 2015 at 08:35:19PM -0700, Alexei Starovoitov wrote:
On Thu, May 28, 2015 at 03:14:44PM +0800, Wangnan (F)
* Dave Hansen d...@sr71.net wrote:
Changes from take 7 / v22:
* Add Thomas's reviewed-by
* merge with tip/x86/fpu changes
* Fix tiny spelling nit
So you already sent 'take 8', so it's unclear to me what changed in this series.
Also, only 1,3,4,5 made it to lkml it appears. (it's not
On Fri, May 29, 2015 at 5:37 PM, Andrew Morton
a...@linux-foundation.org wrote:
On Fri, 29 May 2015 11:12:18 -0400 Dan Streetman ddstr...@ieee.org wrote:
Add zpool_has_pool() function, indicating if the specified type of zpool
is available (i.e. zsmalloc or zbud). This allows checking if a
On Mon, 2015-06-01 at 21:22 +1000, Stephen Rothwell wrote:
Hi Nicholas,
Today's linux-next merge of the target-updates tree got so many
conflicts against Linus' tree that I just gave up and dropped it
completely. Please fix up this mess.
Apologies for the conflicts vs. mainline in
1 - 100 of 1602 matches
Mail list logo
