On Thu, Jun 06, 2013 at 01:41:33AM -0400, Matt Porter wrote:
> This series follows the same approach as taken on Tegra and
> OMAP DT files to use the C preprocessor in order to improve
> readability. Since bcm281xx does not yet have gpio and pinctrl
> support, this series just enables the C preproc
On Mon, 2013-06-10 at 23:49 -0500, Rob Landley wrote:
> Quite possibly the answer is "no", but the MAINTAINERS file is
> approaching 10,000 lines. Getting a bit unwieldy.
I think it hasn't been much of a bottleneck problem.
> The question is: would this be an improvement? (And worth the changes
The am33xx platforms suppors dual musb instance which need two instances
of usb-phy. Add dual instance usb-phy DT bindings for am333x platform.
Signed-off-by: Ravi Babu
---
arch/arm/boot/dts/am33xx.dtsi | 17 +
1 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/arc
This patch set series
- adds dual musb instances support for am335x platform
- adds phy-dsps-usb driver based on TI's gs70 driver
- adds DT bindings for am33xx usb-phy
- removed references to usb-nop-xceiv from musb
has been verified on tree [1]
[1] git://git.kerne
use usb-phy driver API for powering on/off phy and removed
usage of the phy control access in platform glue driver.
Signed-off-by: Ravi Babu
---
drivers/usb/musb/musb_dsps.c | 22 +-
1 files changed, 13 insertions(+), 9 deletions(-)
diff --git a/drivers/usb/musb/musb_dsps.
removed nop xceiv (un_)register API's references from musb dsps
platform, as it uses saperate phy driver.
Signed-off-by: Ravi Babu
---
drivers/usb/musb/musb_dsps.c |4
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/musb/musb_dsps.c b/drivers/usb/musb/musb_dsp
Remove usb-phy control access from platform glue, after moving
usb-phy controls to saperate phy-dsps-usb driver.
Signed-off-by: Ravi Babu
---
drivers/usb/musb/musb_dsps.c | 51 --
1 files changed, 0 insertions(+), 51 deletions(-)
diff --git a/drivers/us
On Tuesday 28 May 2013 08:46 PM, Stephen Warren wrote:
On 05/27/2013 01:40 AM, Prashant Gaikwad wrote:
Use common of_clk_init() function for clocks initialization.
Mike,
Please merge this patch in your tree.
Thanks,
PrashantG
Acked-by: Stephen Warren
--
To unsubscribe from this list: sen
The dsps am33xx platform has two instances of musb controller,
enable the support for dual musb instances
Signed-off-by: Ravi Babu
---
drivers/usb/musb/musb_dsps.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/musb/musb_dsps.c b/drivers/usb/musb/musb_dsps.
In case of mutli instance support, use get-phy object using phandle
to return to repsective phy xceiv object for each instance
Signed-off-by: Ravi Babu
---
drivers/usb/musb/musb_dsps.c |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/musb/musb_dsps.c b/dr
Adds usb-phy driver support for am33xx platform, the host/device
peripheral controller shall get this phy object to control the phy
operations.
Signed-off-by: Ravi Babu
---
drivers/usb/phy/Kconfig|9 ++
drivers/usb/phy/Makefile |1 +
drivers/usb/phy/phy-dsps-usb.c | 236 ++
On Tue, 11 Jun, at 07:52:38AM, Matt Fleming wrote:
> From: Zach Bobroff
>
> ExitBootServices is absolutely supposed to return a failure if any
> ExitBootServices event handler changes the memory map. Basically the
> get_map loop should run again if ExitBootServices returns an error the
> first t
Hi Pavel,
On Mon, Jun 10, 2013, Pavel Machek wrote:
> < HCI Command: Delete Stored Link Key (0x03|0x0012) plen 7
> bdaddr 00:00:00:00:00:00 all 1
> > HCI Event: Command Complete (0x0e) plen 4
> Delete Stored Link Key (0x03|0x0012) ncmd 1
> status 0x11 deleted 0
> Error: Unsupported
On Mon, Jun 10, 2013 at 11:23:42PM +0200, Sebastian Hesselbarth wrote:
> Current DRM slave encoder API conflicts with auto-registration of i2c client
> when using DT probed clients. To allow DRM slave encoders passed by DT, this
> patch adds a check to drm_i2c_encoder_init for a non-NULL .of_node o
On Monday 10 June 2013 17:52:33 Scott Wood wrote:
> On 06/10/2013 12:07:43 PM, Michael Guntsche wrote:
> > Good evening,
> >
> > On Mon, Jun 10, 2013 at 1:41 PM, Rojhalat Ibrahim
> >
> > wrote:
> > > Hi Mike,
> > >
> > > could you please try this patch:
> > > https://lists.ozlabs.org/pipermail/
On Fri, Jun 07, 2013 at 01:18:35PM -0600, Stephen Warren wrote:
> On 06/06/2013 09:30 AM, Christian Ruppert wrote:
> > On Thu, Jun 06, 2013 at 10:32:21PM +0800, Haojian Zhuang wrote:
> >> On 6 June 2013 22:11, Christian Ruppert
> >> wrote:
> >>> On Wed, Jun 05, 2013 at 09:44:27AM +0800, Haojian Z
>>> On 10.06.13 at 23:06, Konrad Rzeszutek Wilk wrote:
> There are two tool-stack that can instruct the Xen PCI frontend
> and backend to change states: 'xm' (Python code with a daemon),
> and 'xl' (C library - does not keep state changes).
>
> With the 'xm', the path to disconnect a PCI device (
On Friday 07 June 2013 10:36 PM, Paul Walmsley wrote:
Hi Stephen,
On Fri, 7 Jun 2013, Stephen Warren wrote:
On 06/07/2013 06:19 AM, Paul Walmsley wrote:
Add DFLL DVCO reset line control functions to the CAR IP block driver.
The DVCO present in the DFLL IP block has a separate reset line,
exp
On Mon, Jun 10, 2013 at 09:55:12PM +0200, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Wed, Jun 05, 2013 at 12:27:31AM +0530, Jay Agarwal wrote:
> [...]
> > @@ -29,7 +29,7 @@
> > ranges = <0x8200 0 0x 0x 0 0x1000 /*
> > port 0 configuration s
On Tue, Jun 11, 2013 at 12:26 AM, Tony Luck wrote:
> On Sat, Jun 8, 2013 at 3:08 AM, Chen Gang wrote:
>> using 'unsigned int *', implicitly:
>> ./ia64/include/asm/bitops.h:63:__set_bit (int nr, volatile void *addr)
>
> There is some downside on ia64 to your suggestion. If "addr" is properly
>
On Tue, 2013-06-11 at 09:49 +0300, Eliezer Tamir wrote:
> I would like to hear opinions on what needs to be added to make this
> feature complete.
>
> The list I have so far is:
> 1. add a socket option
Yes, please. I do not believe all sockets on the machine are candidate
for low latency. In fa
On 10/06/13 15:02, Arnd Bergmann wrote:
> There are multiple ways of doing that, e.g. you could export a function
> from syscon.c that you call to register the device node and then import
> the regmap from syscon into your high-level driver again.
>
Hi Arnd/Linus,
Thankyou for your comments,
I d
>>> On 10.06.13 at 18:43, Konrad Rzeszutek Wilk wrote:
> On Mon, Jun 10, 2013 at 04:52:35PM +0100, Jan Beulich wrote:
>> >>> On 07.06.13 at 22:11, Konrad Rzeszutek Wilk
>> >>> wrote:
>> > On Tue, Jun 04, 2013 at 03:57:06PM -0400, Konrad Rzeszutek Wilk wrote:
>> >> + /* N.B. 'rp', not 'rc'. */
>>
When executing a date command to set the system date and time to a few
seconds before the 2038 problem expiration time, we got a WARN_ON_ONCE()
like this:
root@renesas:~# date -s "2038-1-19 3:14:00"
Tue Jan 19 03:14:00 GMT 2038
(then wait for 7-8 seconds)
root@renesas:~# [ 27.662658] ---
On Sat, Jun 08, 2013 at 07:46:28PM +0200, Arnd Bergmann wrote:
> On Saturday 08 June 2013 11:42:54 Daniel Tang wrote:
> >
> > On 08/06/2013, at 3:55 AM, Arnd Bergmann wrote:
> >
> > If it hasn't been merged yet, would it be possible for me to
> > send version 2 of the patches? Or would you rather
2013/6/10 Oliver Neukum
>
> On Sunday 09 June 2013 16:28:21 Morales, Alejandra wrote:
>
> > I did a test with an external USB hard drive, checking the runtime power
> > state before and after issuing a sleep command with hdparm -Y. The drive
> > effectively spinned down, but the runtime power st
On 06/11/13 09:24, Daniel Vetter wrote:
On Mon, Jun 10, 2013 at 11:23:42PM +0200, Sebastian Hesselbarth wrote:
Current DRM slave encoder API conflicts with auto-registration of i2c client
when using DT probed clients. To allow DRM slave encoders passed by DT, this
patch adds a check to drm_i2c_e
On 06/11/2013 08:51 AM, Linus Torvalds wrote:
> On Mon, Jun 10, 2013 at 5:44 PM, Steven Rostedt wrote:
>>
>> OK, I haven't found a issue here yet, but youss are beiing trickssy! We
>> don't like trickssy, and we must find preiouss!!!
>
> .. and I personally have my usual reservations. I absol
From: Eliezer Tamir
Date: Tue, 11 Jun 2013 09:49:31 +0300
> I would like to hear opinions on what needs to be added to make this
> feature complete.
>
> The list I have so far is:
> 1. add a socket option
> 2. support for poll/select
> 3. support for epoll
I actually would like to see the Kconf
On Tuesday 11 June 2013 07:53:10 Morales, Alejandra wrote:
> 2013/6/10 Oliver Neukum
> > You need to furthermore realise that there are forms of runtime PM
> > independent
> > of the generic kernel based runtime PM (hdparm, USB LPM, ...)
>
>
> Thanks Oliver, that was helpful. I will try now to
On Wed, Jun 5, 2013 at 7:22 PM, Stephen Warren wrote:
>> diff --git a/drivers/pinctrl/core.c b/drivers/pinctrl/core.c
>
>> +int pinctrl_pm_select_default_state(struct device *dev)
>
>> +int pinctrl_pm_select_sleep_state(struct device *dev)
>
>> +int pinctrl_pm_select_idle_state(struct device *dev
W dniu 07.06.2013 17:36, Michal Hocko pisze:
On Fri 07-06-13 17:13:55, Piotr Nowojski wrote:
W dniu 06.06.2013 17:57, Michal Hocko pisze:
In our system we have hit some very annoying situation (bug?) with
cgroups. I'm writing to you, because I have found your posts on
mailing lists with similar
This patch adds support for the TI-Nspire platform.
Changes between v1 and v2:
* Added GENERIC_IRQ_CHIP to platform Kconfig
Signed-off-by: Daniel Tang
---
arch/arm/Kconfig | 2 +
arch/arm/Kconfig.debug | 16 +
arch/arm/Makefile | 1 +
arch
This patch adds device trees for describing the TI-Nspire hardware.
Changes between v1 and v2:
* Change "keymap" binding to the standard "linux,keymap" binding.
Signed-off-by: Daniel Tang
---
Documentation/devicetree/bindings/arm/nspire.txt | 14 ++
.../devicetree/bindings/vendor-prefixes.tx
Hi,
On Tuesday 11 June 2013 12:47 PM, Ravi Babu wrote:
Adds usb-phy driver support for am33xx platform, the host/device
peripheral controller shall get this phy object to control the phy
operations.
Signed-off-by: Ravi Babu
---
drivers/usb/phy/Kconfig|9 ++
drivers/usb/phy/Makef
From: Linus Walleij
In addition to the recently introduced pinctrl core
control, the PM runtime pin control for the OMAP platforms
require a fourth state in addtition to the default, idle and
sleep states already handled by the core: an explicit "active"
state. Let's introduce this to the core in
On Mon, Jun 10, 2013 at 12:23 PM, Lee Jones wrote:
> Change compatible string to something more standard.
>
> Signed-off-by: Lee Jones
Thanks, applied to ux500-devicetree.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message t
On Thu, 6 Jun 2013, Sebastian Hesselbarth wrote:
> This patch set introduces DT-aware irqchip and clocksource drivers for
> Marvell Orion SoCs (Kirkwood, Dove, Orion5x, MV78x00) and corresponding
> patches for Dove and Kirkwood to enable them for DT-boards.
>
> The irqchip driver, of course, depe
On Thu, 6 Jun 2013, Sebastian Hesselbarth wrote:
> This patch adds an irqchip driver for the main interrupt controller found
> on Marvell Orion SoCs (Kirkwood, Dove, Orion5x, Discovery Innovation).
> Corresponding device tree documentation is also added.
>
> Signed-off-by: Sebastian Hesselbarth
On Mon, Jun 10, 2013 at 9:40 PM, Heiko Stübner wrote:
> pinconf_generic_parse_dt_config() takes a node as input and generates an
> array of generic pinconfig values from the properties of this node.
>
> As I couldn't find a mechanism to count the number of properties of a node
> the function uses
From: Patrice Chotard
pinctrl-abx500.c: In function 'abx500_gpio_dbg_show_one':
pinctrl-abx500.c:534:14: warning: 'pud' may be used
uninitialized in this function [-Wuninitialized]
Signed-off-by: Patrice Chotard
---
drivers/pinctrl/pinctrl-abx500.c |2 +-
1 file changed, 1 insertion(+), 1
On Mon, Jun 10, 2013 at 8:23 PM, Stephen Warren wrote:
> The entire reason I created the directory (rather than
> just putting *.h into e.g. arch/arm/boot/dts) was to provide a place to
> share binding-defined constants between the DT files and drivers that
> implement that binding. It's certain
According to documentation bit 3:2 in register SSS_CTRL are
reserved and zero, so initially setting the register to 0x0008
does not make much sense. Instead, bit 4 should be marked set,
as this is the power up default.
Further, mask computation in declarative part is obviously wrong:
Fix FRAC DIVI
On Mon, Jun 10, 2013 at 10:16 PM, Heiko Stübner wrote:
> This driver adds support the Cortex-A9 based SoCs from Rockchip,
> so at least the RK2928, RK3066 (a and b) and RK3188.
> Earlier Rockchip SoCs seem to use similar mechanics for gpio
> handling so should be supportable with relative small c
On Tue, Jun 11, 2013 at 10:48 AM, wrote:
> From: Patrice Chotard
>
> pinctrl-abx500.c: In function 'abx500_gpio_dbg_show_one':
> pinctrl-abx500.c:534:14: warning: 'pud' may be used
> uninitialized in this function [-Wuninitialized]
>
> Signed-off-by: Patrice Chotard
Patch applied, thanks!
Yo
On 06/11/2013 08:29 AM, Jan Beulich wrote:
On 10.06.13 at 23:06, Konrad Rzeszutek Wilk wrote:
There are two tool-stack that can instruct the Xen PCI frontend
and backend to change states: 'xm' (Python code with a daemon),
and 'xl' (C library - does not keep state changes).
With the 'xm', the p
This patch series introduces support for CPU overclocking technique
called Boost.
It is a follow up of a LAB governor proposal. Boost is a LAB component:
http://thread.gmane.org/gmane.linux.kernel/1484746/match=cpufreq
Boost unifies hardware based solution (e.g. Intel Nehalem) with
software orien
This commit adds support for software based frequency boosting.
Some SoC (like Exynos4 - e.g. 4x12) allow setting frequency above
its normal condition limits. Such a change shall be only done for a short
time.
Overclocking (boost) support is essentially provided by platform
dependent cpufreq drive
The struct cpufreq_driver has been extended to embrace the information
related to boost support.
When "boost_mode" device tree attribute is defined for a platform, the
low_level_boost pointer is filled with proper address. The
.low_level_boost field filled to NULL, indicates that boost is not
supp
The Intel's hardware based boost solution driver has been changed to cooperate
with
common cpufreq boost framework.
The global sysfs boost attribute entry code
(/sys/devices/system/cpu/cpufreq/boost)
has been moved to a core cpufreq code. This attribute is now only visible,
when cpufreq driver s
Hi Samuel,
if nobody has objections I think this set is ready to get merged. As
Nico mentioned in:
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-June/173541.html
since we would like to get it merged through the ARM SoC tree owing to
dependencies between this code and ARM power manag
While profiling kernel functions via ftrace I noticed values of s^2 that
seemed odd. I implemented a test to verify correctness of averages and
s^2 calculations and proved the latter to be wrong. Then I fixed them up.
The first patch refactors function_stat_show() code a bit in order to be
able to
Refactor function_stat_show() code grouping avg and stddev calculations
inside a single function (function_stat_calc()). We are now able to call
it from different places.
Signed-off-by: Juri Lelli
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Cc: Ingo Molnar
---
kernel/trace/ftrace.c | 46
Perform a simple test comparing static and running (implemented by
function_stat_calc()) average and stddev calculations.
Signed-off-by: Juri Lelli
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Cc: Ingo Molnar
---
kernel/trace/trace_selftest.c | 72 +
1
When FUNCTION_GRAPH_TRACER is enabled, ftrace can profile kernel functions
and print basic statistics about them. Unfortunately, running stddev
calculation is wrong. This patch corrects it implementing Welford’s method:
s^2 = 1 / (n * (n-1)) * (n * \Sum (x_i)^2 - (\Sum x_i)^2) .
Signed-of
> > This patch enables clocks to be specified from Device Tree via phandles
> > to the "prcc-kernel-clock" node.
> >
> > Cc: Mike Turquette
> > Cc: Ulf Hansson
> > Signed-off-by: Lee Jones
>
> Could you please fold this patch into a "common PRCC device tree
> support" patch instead. Thus handli
Change log from v1:
o declare *static* to f2fs_dirty_inode (reported by kbuild-test-robot)
From 6b523242fa7b301653e83496fb065d5c0cbe7968 Mon Sep 17 00:00:00 2001
From: Jaegeuk Kim
Date: Mon, 10 Jun 2013 09:17:01 +0900
Subject: [PATCH] f2fs: avoid freqeunt write_inode calls
Cc: linux-fsde...@vger
On Mon, 10 Jun 2013, Ulf Hansson wrote:
> On 6 June 2013 14:17, Lee Jones wrote:
> > PRCC (peripheral and kernel) clocks are specified using a property tuple
> > <&phandle base bit>, where 'base' is the peripheral (1, 2, 3, 5 or 6),
> > and bit is read-in value into that peripheral stipulated by
On Mon, Jun 10, 2013 at 10:16:04PM +0900, Takuya Yoshikawa wrote:
> On Mon, 10 Jun 2013 10:57:50 +0300
> Gleb Natapov wrote:
>
> > On Fri, Jun 07, 2013 at 04:51:25PM +0800, Xiao Guangrong wrote:
>
> > > +
> > > +/*
> > > + * Return values of handle_mmio_page_fault_common:
> > > + * RET_MMIO_PF_E
2013/6/10 Yinghai Lu :
> On Mon, Jun 10, 2013 at 3:55 AM, Sergey Meirovich
> wrote:
>
>> patches 1,2(latest one) have not helped me on 3.9.5:
>
> So v1:
> https://patchwork.kernel.org/patch/2694981/
> https://patchwork.kernel.org/patch/2694971/
>
> and v2:
> https://patchwork.kernel.org/patch/269
(2013/06/11 15:50), Gleb Natapov wrote:
On Mon, Jun 10, 2013 at 05:28:23PM -0300, Marcelo Tosatti wrote:
On Mon, Jun 10, 2013 at 07:38:34PM +0300, Gleb Natapov wrote:
Guest traces contain vcpu number and not pid (because guest is unaware
of host PID).
No, guest trace is just a regular ftrace
On 11/06/2013 10:32, Eric Dumazet wrote:
On Tue, 2013-06-11 at 09:49 +0300, Eliezer Tamir wrote:
I would like to hear opinions on what needs to be added to make this
feature complete.
The list I have so far is:
1. add a socket option
Yes, please. I do not believe all sockets on the machine a
On Mon, Jun 10, 2013 at 11:15 AM, Lee Jones wrote:
> On Wed, 15 May 2013, Linus Walleij wrote:
>
>> On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
>>
>> > It was required to pass DMA channel configuration information to the
>> > MMC driver before the new DMA API was in place. Now that it is,
On Tue, Jun 11, 2013 at 07:49:12AM +0100, Matt Fleming wrote:
> OK, I chickened out of sending this in my latest pull request
> after reading Linus' -rc5 email about him not wanting to see any
> non-critical changes. I've stuck it in the 'next' branch with the rest
> of the stuff for v3.11.
Yep, d
Hi Benjamin,
Are you still working on this problem ?
Thanks. :)
On 05/21/2013 10:27 AM, Benjamin LaHaise wrote:
On Tue, May 21, 2013 at 10:07:52AM +0800, Tang Chen wrote:
I'm not saying using two callbacks before and after migration is better.
I don't want to use address_space_operations
On Mon, Jun 10, 2013 at 11:17 AM, Lee Jones wrote:
> On Wed, 15 May 2013, Linus Walleij wrote:
>
>> On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote:
>>
>> > Now DMA DT bindings exist and are in use by he MMC and UART drivers, it
>> > should be possible to remove them from the auxdata structure.
Kishon
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Balbi, Felipe
> Subject: Re: [PATCH v2 2/7] usb: phy: dsps: adding usbphy driver for am33xx
> platform
>> +
>> +res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "phy_wkup");
>> +phy->phy_wkup = ioremap(res->sta
On Tue, 11 Jun 2013, Prashant Gaikwad wrote:
> Why not implement these APIs in DFLL clock driver itself and pass RST address
> register to driver?
The DFLL DVCO reset registers are CAR registers, not DFLL registers.
Functions that operate on registers in one IP block shouldn't be located
in an
From: "Michael S. Tsirkin"
Date: Thu, 6 Jun 2013 15:20:39 +0300
> If device has an owner, we shouldn't touch ubuf_info
> since it might be in use.
>
> Signed-off-by: Michael S. Tsirkin
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
From: "Michael S. Tsirkin"
Date: Thu, 6 Jun 2013 15:20:46 +0300
> vhost_net_clear_ubuf_info didn't clear ubuf_info
> after kfree, this could trigger double free.
> Fix this and simplify this code to make it more robust: make sure
> ubuf info is always freed through vhost_net_clear_ubuf_info.
>
>
On Tue 11-06-13 10:35:01, Piotr Nowojski wrote:
> W dniu 07.06.2013 17:36, Michal Hocko pisze:
> >On Fri 07-06-13 17:13:55, Piotr Nowojski wrote:
> >>W dniu 06.06.2013 17:57, Michal Hocko pisze:
> >In our system we have hit some very annoying situation (bug?) with
> >cgroups. I'm writing to
On Mon, Jun 10, 2013 at 09:04:09PM -0400, Steven Rostedt wrote:
> On Sun, 2013-06-09 at 12:36 -0700, Paul E. McKenney wrote:
> > Breaking up locks is better than implementing high-contention locks, but
> > if we must have high-contention locks, why not make them automatically
> > switch between lig
On Mon, Jun 10, 2013 at 08:44:40PM -0400, Steven Rostedt wrote:
> On Sun, 2013-06-09 at 12:36 -0700, Paul E. McKenney wrote:
>
> > +#else /* #ifndef CONFIG_TICKET_LOCK_QUEUED */
> > +
> > +bool tkt_spin_pass(arch_spinlock_t *ap, struct __raw_tickets inc);
> > +
> > +static __always_inline void __t
> > Nice and simple implementation using standard Clk APIs.
> Hi Lee,
>
> I may be a bit tired, but I am having a bit hard to follow the steps
> taken in this patch set. :-)
>
> I should of course tell you why:
> 1. You start out by adding DT definitions in the DT files, should that
> not be done
2013/6/11 Joshua C. :
> 2013/6/10 Yinghai Lu :
>> On Mon, Jun 10, 2013 at 3:55 AM, Sergey Meirovich
>> wrote:
>>
>>> patches 1,2(latest one) have not helped me on 3.9.5:
>>
>> So v1:
>> https://patchwork.kernel.org/patch/2694981/
>> https://patchwork.kernel.org/patch/2694971/
>>
>> and v2:
>> htt
On Mon, Jun 10, 2013 at 05:51:14PM -0700, Linus Torvalds wrote:
> On Mon, Jun 10, 2013 at 5:44 PM, Steven Rostedt wrote:
> >
> > OK, I haven't found a issue here yet, but youss are beiing trickssy! We
> > don't like trickssy, and we must find preiouss!!!
Heh! You should see what it looks lik
On 06/10/2013 11:36 PM, Thierry Reding wrote:
> On Mon, Jun 10, 2013 at 12:13:43PM +0300, Tuomas Tynkkynen wrote:
>> In Tegra20 memory controller any MC interrupt would cause an
>> infinite loop in the IRQ handler.
>>
>> Signed-off-by: Tuomas Tynkkynen
>> ---
>> drivers/memory/tegra20-mc.c | 5 ++
In Tegra30 any memory controller interrupt would cause an infinite loop in the
IRQ handler. Additionally, a garbage pointer was used to read the MC
status registers, which causes wrong values to be printed if a MC error
occurred.
Signed-off-by: Tuomas Tynkkynen
---
drivers/memory/tegra30-mc.c |
In Tegra20 any memory controller interrupt would cause an
infinite loop in the IRQ handler.
Signed-off-by: Tuomas Tynkkynen
---
drivers/memory/tegra20-mc.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/memory/tegra20-mc.c b/drivers/memory/tegra20-mc.c
index 2ca5
Hi,
Here's two simple bugfixes for the Tegra memory controllers.
v2: Fix a dumb bug in the bit masking.
Tuomas Tynkkynen (2):
memory: tegra20-mc: Fix hang in IRQ handler.
memory: tegra30-mc: Fix IRQ handler.
drivers/memory/tegra20-mc.c | 5 -
drivers/memory/tegra30-mc.c | 9 ++---
On Tue, Jun 11, 2013 at 03:53:17PM +0800, Lai Jiangshan wrote:
> On 06/11/2013 08:51 AM, Linus Torvalds wrote:
> > On Mon, Jun 10, 2013 at 5:44 PM, Steven Rostedt wrote:
> >>
> >> OK, I haven't found a issue here yet, but youss are beiing trickssy! We
> >> don't like trickssy, and we must find pre
On Mon, Jun 10, 2013 at 04:12:07PM -0700, H Hartley Sweeten wrote:
[...]
> +What:/sys/class/pwm/pwmchipN/pwmX/duty
> +Date:May 2013
> +KernelVersion: 3.11
> +Contact: H Hartley Sweeten
> +Description:
> + Sets the PWM duty cycle in nanoseconds.
On Tue, Jun 11, 2013 at 10:13:38AM +0530, Jay Agarwal wrote:
> > * PGP Signed by an unknown key
> >
> > On Tue, Jun 04, 2013 at 01:17:15PM -0600, Stephen Warren wrote:
> > > On 06/04/2013 12:57 PM, Jay Agarwal wrote:
> > [...]
> > > > struct tegra_pcie_port {
> > > > @@ -384,7 +408,7 @@ static in
Hi Pavel,
On Tue, Jun 11, 2013, Johan Hedberg wrote:
> On Mon, Jun 10, 2013, Pavel Machek wrote:
> > < HCI Command: Delete Stored Link Key (0x03|0x0012) plen 7
> > bdaddr 00:00:00:00:00:00 all 1
> > > HCI Event: Command Complete (0x0e) plen 4
> > Delete Stored Link Key (0x03|0x0012) ncmd 1
On Tue, Jun 11, 2013 at 01:11:17PM +0300, Tuomas Tynkkynen wrote:
> Hi,
>
> Here's two simple bugfixes for the Tegra memory controllers.
>
> v2: Fix a dumb bug in the bit masking.
>
> Tuomas Tynkkynen (2):
> memory: tegra20-mc: Fix hang in IRQ handler.
> memory: tegra30-mc: Fix IRQ handler.
On 5/22/2013 12:40 PM, Philip Avinash wrote:
> From: KV Sujith
>
> Add struct davinci_gpio_platform_data davinci gpio module.
>
> Signed-off-by: KV Sujith
> Signed-off-by: Philip Avinash
As Linus commented before, this should be merged with 03/11.
> ---
> include/linux/platform_data/gpio-da
Mark Brown wrote:
> I don't think you're using the usual definition of "register map" here.
> You seem to be switching between talking about this object model the
> device has and device registers - perhaps the objects are also registers
> sometimes?
Yes, in Atmel Object Protocol "instances" of "o
> > I have mentioned it in description as -> "Corrected logic in read/write
> config space to display right device number on bus 0"
> >
> > > Device 0:00.0 is usually the root complex, and device 0:01.0, 0:02.0
> > > etc are the root ports. The change proposed above makes 0:00.0 the
> > > first roo
On Tue, May 28, 2013 at 01:12:12PM -0600, Keith Packard wrote:
> Thierry Reding writes:
>
>
> > That doesn't sound right. Maybe drmIoctl() needs fixing instead. Looking
> > at the history, drmIoctl() was introduced to automatically loop if a
> > signal was received (commit 8b9ab108ec1f2ba2b503f7
On Mon, Jun 10, 2013 at 10:21:58AM +0100, Srinivas KANDAGATLA wrote:
> It is common to access regmap registers at bit level, using
> regmap_update_bits or regmap_read functions, however the end user has to
> take care of a mask or shifting. This becomes overhead when such use
> cases are high. Havi
On Tue, Jun 11, 2013 at 12:43 AM, Oliver Schinagl
wrote:
> On 06/06/13 21:16, Andy Shevchenko wrote:
>> On Sun, Jun 2, 2013 at 5:58 PM, Oliver Schinagl
>> wrote:
>>> From: Oliver Schinagl
>>> + if (likely((SID_SIZE))) {
>>
>> Extra braces.
>> Use antipattern here.
>
> While I accidentally
Hello,
This patch series is a porposal to enhance the sam9 watchdog timer support.
The at91sam9 watchdog timer cannot configured twice, and the current
implementation only tries to configure in a static way:
- 2 seconds timeout
- wdt restart every 500ms
If the timer has already been configured w
The at91sam9 watchdog timer cannot configured twice, and the current
implementation only tries to configure in a static way:
- 2 seconds timeout
- wdt restart every 500ms
If the timer has already been configured with different values, it returns an
error and do not create any watchdog device.
Thi
Set default watchdog options in every SoC compatible with the sam9 watchdog.
Signed-off-by: Boris BREZILLON
---
arch/arm/boot/dts/at91sam9260.dtsi |5 +
arch/arm/boot/dts/at91sam9263.dtsi |5 +
arch/arm/boot/dts/at91sam9g45.dtsi |5 +
arch/arm/boot/dts/at91sam9n12.dtsi |
Add watchdog specific config for kizbox board.
Signed-off-by: Boris BREZILLON
---
arch/arm/boot/dts/kizbox.dts |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/kizbox.dts b/arch/arm/boot/dts/kizbox.dts
index 02df191..928f6ee 100644
--- a/arch/arm/boot/dts/kizbox.dts
The driver can be used on either arm or arm64 platforms, but
the latter doesn't have any platform-specific configuration
options, so it must be possible to manually enable the driver.
As the gpiolib is optional for arm64 arch, the gpio/led code
must be compiled conditionally.
Signed-off-by: Pawel
Changing size of a file on server and local update (fuse_write_update_size)
should be always protected by inode->i_mutex. Otherwise a race like this is
possible:
1. Process 'A' calls fallocate(2) to extend file (~FALLOC_FL_KEEP_SIZE).
fuse_file_fallocate() sends FUSE_FALLOCATE request to the serve
On Tue, Jun 11, 2013 at 12:48 PM, Thierry Reding
wrote:
> On Tue, May 28, 2013 at 01:12:12PM -0600, Keith Packard wrote:
>> Thierry Reding writes:
>>
>>
>> > That doesn't sound right. Maybe drmIoctl() needs fixing instead. Looking
>> > at the history, drmIoctl() was introduced to automatically lo
Add new at91sam9 watchdog properties to the documentation.
Signed-off-by: Boris BREZILLON
---
.../devicetree/bindings/watchdog/atmel-wdt.txt | 30 ++--
1 file changed, 28 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/watchdog/atmel-wdt.txt
b
Hello,
On 6/11/2013 4:34 AM, Bjorn Helgaas wrote:
[+cc Marek]
On Mon, Jun 3, 2013 at 6:44 AM, Michal Simek wrote:
> Check that dma_ops are initialized correctly.
>
> Signed-off-by: Michal Simek
> ---
> Functions dma_mmap_attrs(), dma_get_sgtable_attrs()
> already have this checking.
>
> ---
>
1 - 100 of 759 matches
Mail list logo
