On Wed, Jun 18, 2014 at 5:36 PM, Sören Brinkmann
wrote:
> I did some of the changes for this v2 and a few things are not clear to
> me.
>
> The first is, how is userspace supposed to find the correct offset for a
> GPIO pin.
The sysfs interface to GPIO is *NOT* *GOOD* this is universally
agreed
On Wed, Jun 18, 2014 at 12:36:15PM -0400, Konrad Rzeszutek Wilk wrote:
> On Sun, Jun 15, 2014 at 02:47:04PM +0200, Peter Zijlstra wrote:
> > From: Waiman Long
> >
> > Currently, atomic_cmpxchg() is used to get the lock. However, this is
> > not really necessary if there is more than one task in
On Wed, Jun 25, 2014 at 10:28:21AM +0800, Chen, Tiejun wrote:
> On 2014/6/24 10:59, Zhenyu Wang wrote:
> >On 2014.06.19 17:53:51 +0800, Tiejun Chen wrote:
> >>Originally the reason to probe ISA bridge instead of Dev31:Fun0
> >>is to make graphics device passthrough work easy for VMM, that
> >>only
On 07/04/2014 09:57 AM, Joonsoo Kim wrote:
In __free_one_page(), we check the buddy page if it is guard page.
And, if so, we should clear guard attribute on the buddy page. But,
currently, we clear original page's order rather than buddy one's.
This doesn't have any problem, because resetting
On Sun, Jul 06, 2014 at 12:38:00PM +0530, Himangi Saraogi wrote:
> diff --git a/sound/soc/codecs/sgtl5000.c b/sound/soc/codecs/sgtl5000.c
> index 249fadb..0efd6d6 100644
> --- a/sound/soc/codecs/sgtl5000.c
> +++ b/sound/soc/codecs/sgtl5000.c
> @@ -841,14 +841,15 @@ static int
On Mon, 30 Jun, at 07:52:55PM, Daniel Kiper wrote:
> This is odd to use early_iounmap() function do tear down mapping
> created by early_memremap() function, even if it works right now,
> because they belong to different set of functions. The former is
> I/O related function and the later is
On Wed, Jun 25, 2014 at 08:48:32AM +0200, Paolo Bonzini wrote:
> It is only slightly better, but the right solution is to fix the driver.
> There is absolutely zero reason why a graphics driver should know about the
> vendor/device ids of the PCH.
There is a very valid reason to know about the
On Wed, Jun 18, 2014 at 1:39 PM, Harini Katakam wrote:
> From: Harini Katakam
>
> Add support for GPIO controller used by Xilinx Zynq.
>
> Signed-off-by: Harini Katakam
> Signed-off-by: Soren Brinkmann
> ---
>
> v2 changes:
> - convert to pm_runtime_force_(suspend|resume)
> - add
On Mon, 2014-07-07 at 14:57 +0200, Rafael J. Wysocki wrote:
> On Thursday, June 19, 2014 11:41:30 AM Andy Whitcroft wrote:
> > The recently merged change (in v3.14-rc6) to ACPI resource detection
> > (below) causes all zero length ACPI resources to be elided from the table:
> >
> > commit
On 07/07/2014 02:53 AM, Kieran Kunhya wrote:
Signed-off-by: should be here,
not in the Subject line.
> ---
> drivers/block/Kconfig |9 +
> drivers/block/Makefile |1 +
> drivers/block/sxs.c| 491
>
> 3 files changed, 501
On Mon, Jul 07, 2014 at 01:16:54PM +0100, Richard Fitzgerald wrote:
> Adds an equivalent of SOC_ENUM_EXT for value enums
Applied, thanks.
signature.asc
Description: Digital signature
`struct workspace' used for zlib compression contains two zlib
z_stream-s: `def_strm' used in zlib_compress_pages(), and `inf_strm'
used in zlib_decompress/zlib_decompress_biovec(). None of these
functions use `inf_strm' and `def_strm' simultaniously, meaning that
for every compress/decompress
Hi,
This patch uses a slightly modified version of envytools/headergen2 (thanks
Rob!) to add support for a newer version of MDP5: v1.3 (up to v1.2 is
supported as of now), through dynamic offsets.
Stephane Viau (1):
drm/msm/mdp5: add support for MDP5 v1.3
Hello,
This patch reduces zlib compression memory usage by `merging' inflate
and deflate streams into a single stream.
-- v2: rebased-on linux-next rc4 20140707
Sergey Senozhatsky (1):
btrfs compression: merge inflate and deflate z_streams
fs/btrfs/zlib.c | 138
MDP5 has several functional blocks (ie: VIG/RGB pipes, LMs, ...).
>From one revision to another, these blocks' base addresses might
change due to the number of instances present in the MDP5 hw.
A way of dealing with these offset changes is to introduce
dynamic offsets 'per block'.
This change
Adapt the ramc mapping code to handle multiple ram controllers in the DT.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-at91/setup.c | 26 ++
1 file changed, 14 insertions(+), 12 deletions(-)
diff --git a/arch/arm/mach-at91/setup.c b/arch/arm/mach-at91/setup.c
index
Most of the printed messages are using the "AT91:" prefix in the setup.c file,
but not all of them. Moreover, those who add it hardcode it directly in the
message, while the pr_fmt macro makes it easier for us to support such a case.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-at91/setup.c |
All the config option so far are depending on the POWER_RESET symbol
Signed-off-by: Maxime Ripard
---
drivers/power/reset/Kconfig | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/drivers/power/reset/Kconfig b/drivers/power/reset/Kconfig
index
On Wed, Jun 18, 2014 at 01:39:52PM +0200, Paolo Bonzini wrote:
> Il 15/06/2014 14:47, Peter Zijlstra ha scritto:
> >
> >-for (;;) {
> >-new = (val & ~_Q_PENDING_MASK) | _Q_LOCKED_VAL;
> >-
> >-old = atomic_cmpxchg(>val, val, new);
> >-if (old == val)
> >-
The SAMA5D3 has a shutdown controller identical to the sam9x5 SoC family.
Declare it in the DT.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sama5d3.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/sama5d3.dtsi b/arch/arm/boot/dts/sama5d3.dtsi
index
The G45 has two identical ram controller, that are defined as a single one,
with two reg cells.
The proper way to support such a case is to have two separate DT nodes.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/at91sam9g45.dtsi | 8 ++--
1 file changed, 6 insertions(+), 2
This time with proper Subject line :)
Dear RT Folks,
I'm pleased to announce the 3.14.10-rt7 release. 3.14.10-rt6 is a not
announced update to 3.14.10 without any RT changes aside of resolving
the patch conflicts.
Changes since 3.14.10-rt6:
* Do not clear PF_NO_SETAFFINITY flag in
On Wed, Jun 18, 2014 at 11:57:30AM -0400, Konrad Rzeszutek Wilk wrote:
> On Sun, Jun 15, 2014 at 02:47:02PM +0200, Peter Zijlstra wrote:
> > From: Peter Zijlstra
> >
> > When we allow for a max NR_CPUS < 2^14 we can optimize the pending
> > wait-acquire and the xchg_tail() operations.
> >
> >
Now that there's no user left for the global variables holding the reset and
shutdown controllers base address, we can remove these variables and their
associated mapping function.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-at91/at91sam9260.c | 2 --
arch/arm/mach-at91/at91sam9261.c | 2
Hi,
This patchset is an attempt to further cleanup mach-at91 by removing
code that can be put into a driver nowadays.
This time, the target is the reset and poweroff code, that can now be
put in drivers/power/reset.
Maxime
Changes from v1:
- Added the missing copyrights in the new reset and
These headers used to provide an "API" to access the rstc and shdwc registers.
Now that no-one uses this API anymore, we can safely remove those.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-at91/at91_rstc.h | 53 -
arch/arm/mach-at91/at91_shdwc.h
On 07/07/2014 06:49 AM, Joonsoo Kim wrote:
Ccing Lisa, because there was bug report it may be related this
topic last Saturday.
http://www.spinics.net/lists/linux-mm/msg75741.html
On Fri, Jul 04, 2014 at 05:33:27PM +0200, Vlastimil Babka wrote:
On 07/04/2014 09:57 AM, Joonsoo Kim wrote:
Implement the reset behaviour of the various AT91 SoCS in drivers/power/reset.
It used to be (and still is) located in arch/arm/mach-at91, and in order to
preserve bisectability is not removed yet, but every board should be converted
to use this driver instead.
Signed-off-by: Maxime Ripard
---
Now that the transition is over and that we probe our reset driver in every
case, we can remove the legacy code from the machine directory.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-at91/Kconfig | 8 --
arch/arm/mach-at91/Makefile | 2 --
Make every board call the register_devices callback so that the devices
declared by the SoC are registered.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-at91/board-afeb-9260v1.c | 2 ++
arch/arm/mach-at91/board-cam60.c| 2 ++
arch/arm/mach-at91/board-cpu9krea.c | 2 ++
Register the reset device in the right SoCs so that the reset driver is
actually probed even in the old-style probing case.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-at91/at91sam9260.c | 26 ++
arch/arm/mach-at91/at91sam9261.c | 26 ++
Now that the reset code is a driver of its own, just let the usual DT probing
mecanism do its job, and remove the code entirely in this case.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-at91/setup.c | 29 -
1 file changed, 29 deletions(-)
diff --git
Both the reset and poweroff drivers are now implementing what the
show_reset_status function used to do. Hence, we can remove this rather hackish
function that prevents us from doing further cleanup.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-at91/pm.c | 72
Register the poweroff driver in the old-style SoC definition so that the driver
is loaded and provide a shutdown hook.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-at91/at91sam9260.c | 15 +++
arch/arm/mach-at91/at91sam9261.c | 15 +++
arch/arm/mach-at91/at91sam9263.c
Now that all the SoC have been converted to use the new poweroff driver, we can
remove the poweroff code defined in mach-at91.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-at91/setup.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/arch/arm/mach-at91/setup.c
On Wed, Jun 18, 2014 at 6:49 AM, Andy Gross wrote:
> This patch adds the BUS_HOLD (Keeper) bias option for pins.
>
> Signed-off-by: Andy Gross
Patch applied with Björn's ACK, thanks Andy.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
gt; >
> > Signed-off-by: Sergey Senozhatsky
>
> Reviewed-by: David Sterba
>
Hello,
the patch does not apply against linux-next rc4-20140707 due to 130d5b415a091e.
unhappy hunk is:
+ if (workspace->strm.total_in > 8192 &&
Now that the poweroff code is a driver of its own, remove the DT probing in
mach-at91 and let the usual DT code do its job.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-at91/setup.c | 77 --
1 file changed, 77 deletions(-)
diff --git
Some core devices should be registered by the SoC itself rather than by every
board using this SoC. Introduce a register_devices callback that should be
called during the init_machine in order to do that.
Signed-off-by: Maxime Ripard
---
arch/arm/mach-at91/generic.h | 2 ++
Add a driver to handle the shutdown of the Atmel SoCs. This code used to be
(and still is) in arch/arm/mach-at91. We didn't remove it yet so that we can
convert all the boards to using this driver, before removing it entirely in a
separate patch.
Signed-off-by: Maxime Ripard
---
SMBus block commands are different to I2C block commands since
the returned data is not normally accessible with byte or word
commands on other command offsets. Add linked list of 'block'
commands to support those commands.
Access mechanism is quite simple: Block commands must be written
before
Hi Vladimir,
On Mon, Jul 07, 2014 at 04:00:05PM +0400, Vladimir Davydov wrote:
> Hi,
>
> This patch set introduces re-parenting of kmem charges on memcg css
> offline. The idea lying behind it is very simple - instead of pointing
> from kmem objects (kmem caches, non-slab kmem pages) directly to
On Sun, Jul 06, 2014 at 08:05:23PM +0100, Yuyang Du wrote:
> Hi Morten,
>
> Thanks, got it. Then another question,
>
> On Fri, Jul 04, 2014 at 12:06:13PM +0100, Morten Rasmussen wrote:
> > The patch set essentially puts tasks where it is most energy-efficient
> > guided by the platform energy
On Fri, 4 Jul 2014, Tuomas Tynkkynen wrote:
> The Tegra USB complex has a particularly annoying misdesign: some of the
> UTMI pad configuration registers are global for all the 3 USB controllers
> on the chip, but those registers are located in the first controller's
> register space and will be
On 03/07/14 16:29, Alexander Yarygin wrote:
> On s390, the vmexit event has a tree-like structure: between
> exit_event_begin and exit_event_end several other events may happen
> and with each of them refining the previous ones.
>
> This patch adds a decoder for such events to the generic code
>
On Mon, Jul 7, 2014 at 1:20 PM, Paolo Bonzini wrote:
> Il 07/07/2014 12:29, David Drysdale ha scritto:
>> Capsicum capabilities are associated with the file descriptor (a la
>> F_GETFD), not the open file itself -- different FDs with different
>> associated rights can map to the same underlying
On 03/07/14 16:29, Alexander Yarygin wrote:
> Current code skips output of the x86 specific HLT event in order to
> avoid flooding the output with enabled --duration option. The events to
> be skipped should be architecture dependent, though.
>
> Let's add an architecture specific array of events
Hi,
On Monday 07 July 2014 06:42 PM, Lee Jones wrote:
> On Fri, 04 Jul 2014, Kishon Vijay Abraham I wrote:
>
>> In case of multi-phy PHY providers, each PHY should be modeled as a sub
>> node of the PHY provider. Then each PHY will have a different node pointer
>> (node pointer of sub node) than
On 03/07/14 16:29, Alexander Yarygin wrote:
> Parts of a 'perf kvm stat' code make sense only for x86.
> Let's move this code into the arch/x86/kvm-stat.c file and add
> util/kvm-stat.h for generic structure definitions.
>
> Add a global array 'kvm_reg_events_ops' for accessing the
>
Otherwise, compiling iio_event_monitor program fails:
io_event_monitor.c: In function ‘event_is_known’:
iio_event_monitor.c:125:2: error: duplicate case value
case IIO_MOD_LIGHT_BOTH:
^
iio_event_monitor.c:121:2: error: previously used here
case IIO_MOD_LIGHT_BOTH:
Fixes: da4db94 (iio
On 03/07/14 16:29, Alexander Yarygin wrote:
> Currently perf-kvm uses string literals for kvm event names,
> but it works only for x86, because other architectures may have
> other names for those events.
>
> To reduce dependence on architecture, we add file with
> defines for:
> - kvm_entry and
On Sun, 6 Jul 2014, Rickard Strandqvist wrote:
> Variable ar assigned a value that is never used.
> I have also removed all the code that thereby serves no purpose.
>
> This was found using a static code analysis program called cppcheck
>
> Signed-off-by: Rickard Strandqvist
Acked-by:
In commit ae91d60ba88ef0bdb1b5e9b2363bd52fc45d2af7, a bug was fixed that
involved converting !x & y to !(x & y). The code below shows the same
pattern, and thus should perhaps be fixed in the same way.
The Coccinelle semantic patch that makes this change is as follows:
//
@@ expression E1,E2;
In commit ae91d60ba88ef0bdb1b5e9b2363bd52fc45d2af7, a bug was fixed that
involved converting !x & y to !(x & y). The code below shows the same
pattern, and thus should perhaps be fixed in the same way.
The Coccinelle semantic patch that makes this change is as follows:
//
@@ expression E1,E2;
On Sun, Jun 29, 2014 at 2:13 AM, Antonio Borneo
wrote:
> CP2112 does not offer an atomic method to set both gpio
> direction and value.
> Also it does not permit to set gpio value before putting
> gpio in output. In fact, accordingly to Silicon Labs
> AN495, Rev. 0.2, cpt. 4.4, the HID report to
On Mon, 07 Jul 2014 06:32:02 -0700, Guenter Roeck wrote:
> On 07/07/2014 01:27 AM, Jean Delvare wrote:
> > On Sun, 6 Jul 2014 20:55:12 -0700, Guenter Roeck wrote:
> >>chip->words[command] &= 0xff00;
> >>chip->words[command] |= data->byte;
> >>
Applied to wq/for-3.16-fixes with slightly updated $SUBJ.
Thanks.
-- 8< --
>From 5a6024f1604eef119cf3a6fa413fe0261a81a8f3 Mon Sep 17 00:00:00 2001
From: Yasuaki Ishimatsu
Date: Mon, 7 Jul 2014 09:56:48 -0400
When hot-adding and onlining CPU, kernel panic occurs, showing following
call
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus
to receive a few tiny HID subsystem fixes for 3.16.
Chen Gang (1):
HID: sensor-hub: introduce Kconfig dependency on IOMEM
Hi Catalin,
On Fri, Jul 04, 2014 at 05:55:52PM +0100, Catalin Marinas wrote:
> Hi Morten,
>
> On Thu, Jul 03, 2014 at 05:25:47PM +0100, Morten Rasmussen wrote:
> > This is an RFC and there are some loose ends that have not been
> > addressed here or in the code yet. The model and its
On Thu, 3 Jul 2014, Steven Rostedt wrote:
> [ NOT READY FOR INCLUSION! ]
>
> Note, this is based off of my remove ftrace_start/stop() patch set.
>
> I've been wanting to do this for years, and just never gotten around to it.
> But with all this talk of kpatch and kgraft live kernel patching
Hi Antonio,
On Sun, Jun 29, 2014 at 2:14 AM, Antonio Borneo
wrote:
> cp2112 supports single I2C read/write transactions.
> It can't combine I2C transactions.
>
> Add master_xfer, using similar code flow as for smbus_xfer.
Thanks for taking the time to implement it. I wanted to add this
>
> On Thu, Jul 03, 2014 at 05:52:37PM +0200, Andi Kleen wrote:
> > > If there's active LBR users out there, we should refuse to enable PT
> > > and vice versa.
> >
> > This doesn't work, e.g. hardware debuggers can take over at any time.
>
> Tough cookies. Hardware debuggers get to deal with
On 07/07/2014 04:30 AM, Peter Zijlstra wrote:
> On Sun, Jul 06, 2014 at 01:27:37PM -0400, Sasha Levin wrote:
>> Hi all,
>>
>> While fuzzing with trinity inside a KVM tools guest running the latest -next
>> kernel I've stumbled on the following spew:
>>
>> [10062.200152] BUG: spinlock recursion
Hi Heiko,
> On Fri, Jul 04, 2014 at 05:12:35PM +0200, Helge Deller wrote:
> > This patch affects big endian architectures only.
> >
> > On those with 32bit userspace and 64bit kernel (CONFIG_COMPAT=y) the
> > 64bit mask parameter is correctly constructed out of two 32bit values in
> > the
On Thu, 3 Jul 2014, Wei Yang wrote:
> Here is my refined version, hope this is more friendly to the audience.
Acked-by: Christoph Lameter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Mon, Jul 07, 2014 at 01:22:13AM -0400, Nick Krause wrote:
> Here are my logs of the builds attached with warnings if they succeed
> for now failing arm configs
> according to the tests here,
fs/direct-io.c: In function ‘__blockdev_direct_IO’:
fs/direct-io.c:1011:12: warning: ‘to’ may be used
On Wed, Jun 25, 2014 at 05:17:48PM -0400, Sasha Levin wrote:
> [ 1853.817250] 2 locks held by trinity-c3/29876:
> [ 1853.817250] #0: cpu_hotplug.lock){++}, at: get_online_cpus
> (kernel/cpu.c:90)
> [ 1853.924037] #1: (>lock){-.-...}, at: perf_lock_task_context
> (kernel/events/core.c:983)
- Robustify the user backtrace code, as done on other architectures.
- Provide the symbols resolution when triggering from tracepoints.
Big thanks to Steve Capper for the help in debugging and rephrasing the
commits descriptions.
Stress tested with perf record and tracepoints triggering (-e ),
When tracing with tracepoints events the IP and CPSR are set to 0,
preventing the perf code to resolve the symbols:
./perf record -e kmem:kmalloc cal
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.007 MB perf.data (~321 samples) ]
./perf report
Overhead
Under perf, the fp unwinding scheme requires access to user space memory
and can provoke a pagefault via call to __copy_from_user_inatomic from
user_backtrace. This unwinding can take place in response to an interrupt
(__perf_event_overflow). This is undesirable as we may already have
mmap_sem
An event may occur when an mm is already released.
As per commit 20afc60f892d285fde179ead4b24e6a7938c2f1b
'x86, perf: Check that current->mm is alive before getting user callchain'
Signed-off-by: Jean Pihet
Cc: Will Deacon
Acked-by: Will Deacon
---
arch/arm/kernel/perf_event.c | 4
1
On Fri, Jul 04, 2014 at 07:12:04PM -0700, Hugh Dickins wrote:
> On Thu, 3 Jul 2014, Johannes Weiner wrote:
> > On Thu, Jul 03, 2014 at 12:54:36PM -0700, Hugh Dickins wrote:
> > > On Wed, 2 Jul 2014, Hugh Dickins wrote:
> > > > On Wed, 2 Jul 2014, Johannes Weiner wrote:
> > > > >
> > > > > Could
On Fri, 04 Jul 2014, Kishon Vijay Abraham I wrote:
> Fixed of_phy_provider_lookup to return 'phy_provider' if _of_phy_get
> passes the node pointer of the sub-node of phy provider node. This is
> needed when phy provider implements multiple PHYs and each PHY is
> modelled as the sub-node of PHY
Will,
On 3 July 2014 19:54, Will Deacon wrote:
> On Fri, Jun 27, 2014 at 03:57:47PM +0100, Jean Pihet wrote:
>> When tracing with tracepoints events the IP and CPSR are set to 0,
>> preventing the perf code to resolve the symbols:
>>
>> ./perf record -e kmem:kmalloc cal
>> [ perf record: Woken
On Fri, 4 Jul 2014 11:13:11 +0100
Mike Cardwell wrote:
> I originally posted this two years ago (*) but received no response. I
> just had a look and the problem still exists on the 3.14 kernel I am
> currently running.
>
> I *think* I've uncovered a race condition bug in procfs. If I attempt
Hi Will,
On 3 July 2014 19:52, Will Deacon wrote:
> Hi Jean,
>
> On Fri, Jun 27, 2014 at 03:57:46PM +0100, Jean Pihet wrote:
>> As done on other architectures (ARM64, x86, Sparc etc.).
>>
>> This prevents a deadlock on down_read in do_page_fault when unwinding
>> using fp and triggering on
On Mon, 2014-07-07 at 13:01 +0100, Grant Likely wrote:
> On Sat, 05 Jul 2014 11:31:39 -0700, Joe Perches wrote:
> > On Sat, 2014-07-05 at 19:20 +0100, Maciej W. Rozycki wrote:
> > > On Sat, 5 Jul 2014, Joe Perches wrote:
> > > > I don't think %#p is valid so it
> > > > shouldn't have been set by
On Mon, Jul 07, 2014 at 12:55:44PM +, David Laight wrote:
> From: Olivier Sobrie
> > Hi David,
> >
> > On Mon, Jul 07, 2014 at 09:13:53AM +, David Laight wrote:
> > > From: Olivier Sobrie
> > > > When the module sends bursts of data, sometimes a deadlock happens in
> > > > the hso driver
On 07/07/14 14:56, Mimi Zohar wrote:
> On Fri, 2014-07-04 at 15:05 +0300, Dmitry Kasatkin wrote:
>> Async hash API allows to use HW acceleration for hash calculation.
>> It may give significant performance gain or/and reduce power consumption,
>> which might be very beneficial for battery powered
On Sun, Jul 6, 2014 at 10:49 AM, Dave Airlie wrote:
> On 6 July 2014 12:24, Ed Tomlinson wrote:
>> Hi Dave,
>>
>> This is NOT fixing problems with a stalled boot due to VGA problems as
>> reported in thread: [PATCH 5/5] drm/i915: Kick out vga console
>> It can be fixed by reverting:
On 07/07/2014 01:27 AM, Jean Delvare wrote:
Hi Guenter,
On Sun, 6 Jul 2014 20:55:12 -0700, Guenter Roeck wrote:
SMBus block commands are different to I2C block commands since
the returned data is not normally accessible with byte or word
commands on other command offsets. Add linked list of
On Mon, Jun 23, 2014 at 10:45 AM, Maarten Lankhorst
wrote:
> But in drivers/drm I can encounter a similar issue, people expect to be able
> to
> overwrite the contents of the currently displayed buffer, so I 'solved' it by
> not adding
> a fence on the buffer, only by waiting for buffer idle
On Fri, 4 Jul 2014 11:57:40 -0500
Robert Nelson wrote:
> On Fri, Jul 4, 2014 at 11:51 AM, Sebastian Andrzej Siewior
> wrote:
> > On 07/03/2014 09:34 AM, Tony Lindgren wrote:
> >> Heh. Just to summarize the reason ttyO needs to be a separate name
> >> and device entry from ttyS is because we
On Mon, 2014-07-07 at 08:26 +, David Laight wrote:
> From: Joe Perches
> > Because gcc issues a complaint about any pointer format with %#p,
> > remove the use of SPECIAL to prefix 0x to various pointer types.
> >
> > There are no uses in the kernel tree of %#p.
>
> I know you guys don't
On Wed, Jul 2, 2014 at 7:37 AM, Greg KH wrote:
>> Android can expose fences to userspace. It's possible to make the new fence
>> mechanism expose the same fences to userspace by changing sync_fence_create
>> to take a struct fence instead of a struct sync_pt. No other change is
>> needed,
>>
On Saturday, July 05, 2014 3:25 PM, Peter Griffin wrote:
>
> This patch adds the ST glue logic to manage the DWC3 HC
> on STiH407 SoC family. It manages the powerdown signal,
> and configures the internal glue logic and syscfg registers.
>
> Signed-off-by: Giuseppe Cavallaro
> Signed-off-by:
On Fri, 4 Jul 2014, Steven Rostedt wrote:
> Well, I guess the answer to that is what do you consider the trampoline?
> I'm currently considering it to be the assembly code that the
> mcount/fentry call jumps to. We only have two trampolines (three if you
> count the function graph code that
On Fri, 4 Jul 2014 18:34:10 +0200
Sebastian Andrzej Siewior wrote:
> While comparing the OMAP-serial and the 8250 part of this I noticed that
> the the latter does not use runtime-pm.
Yes it does, but 8250 parts (generally - omap presumably is special
here ?) need to be powered on to
From: Thierry Reding
The max98090_{suspend,resume}() functions are used for system sleep and
therefore need to be guarded by CONFIG_PM_SLEEP rather than CONFIG_PM.
Signed-off-by: Thierry Reding
---
sound/soc/codecs/max98090.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Tue, Jun 17, 2014 at 4:52 PM, Chen-Yu Tsai wrote:
> The A23 has a R_PIO pin controller, similar to the one found on the A31 SoC.
> Add support for the pins controlled by the R_PIO controller.
>
> Signed-off-by: Chen-Yu Tsai
> Acked-by: Maxime Ripard
Patch applied.
Yours,
Linus Walleij
--
On Fri, 04 Jul 2014, Kishon Vijay Abraham I wrote:
> In case of multi-phy PHY providers, each PHY should be modeled as a sub
> node of the PHY provider. Then each PHY will have a different node pointer
> (node pointer of sub node) than that of PHY provider. Added this provision
> in the PHY core.
On Fri, 4 Jul 2014 18:34:09 +0200
Sebastian Andrzej Siewior wrote:
> The OMAP version of the 8250 can actually use 1:1 serial8250_startup().
> However it needs to be extended by a wakeup irq which should to be
> requested & enabled at ->startup() time.
>
> Signed-off-by: Sebastian Andrzej
On Fri, 4 Jul 2014 18:34:08 +0200
Sebastian Andrzej Siewior wrote:
> There is no access to access a struct uart_8250_port for a specific
> line. This is only required outside of the 8250/uart callbacks like for
> devices' suspend & remove callbacks. For those the 8250-core provides
> wrapper
On Mon, 7 Jul 2014, One Thousand Gnomes wrote:
> > This removes the sizeof(frame) from the call to get_sigframe on line
> > 243 in order to fix the call to this function as the sizeof in not
> > needed to call this function.
>
> If you are going to submit patches then
>
> - actually read what
On Fri, 4 Jul 2014 21:20:28 + (UTC)
Mathieu Desnoyers wrote:
> Hi Greg,
>
> Reading this story about Qualcomm lawyers shooting
> DMCA takedown requests lightly against github projects:
>
>
Il 07/07/2014 10:46, Wanpeng Li ha scritto:
Hi Paolo,
Is it ok for you to apply this patch and then more effort should be taken
to figure out the other bug which don't have any relationship with the race
that this patch fixed?
Which patch? Yours or Bandan's?
Paolo
--
To unsubscribe from
Am 07.07.2014 13:50, schrieb Roman Fietze:
Hello list members,
And here the second part.
From e523006a34db26c274d3b71de5b914f476fb029e Mon Sep 17 00:00:00 2001
From: Roman Fietze
Date: Fri, 4 Jul 2014 10:05:08 +0200
Subject: [PATCH 2/2] rtc: add kernel parameter hctosys, use it instead of
On Thu, Mar 13, 2014 at 6:05 PM, Ruchi Kandoi wrote:
> For power management diagnostic purposes, it is often useful to know
> what interrupts are frequently waking the system from low power
> suspend mode, especially on battery-powered consumer electronics
> devices that are expected to spend
On Mon, 7 Jul 2014, Steven Rostedt wrote:
> For a minute there I thought you were taking over 3.4-rt stable. But then I
> noticed that the subject didn't match the body. ;-)
:)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Tue, Jun 17, 2014 at 4:52 PM, Chen-Yu Tsai wrote:
> The A23 uses the same pin controller as previous SoC's from Allwinner.
> Add support for the pins controlled by the main PIO controller.
>
> Signed-off-by: Chen-Yu Tsai
> Acked-by: Maxime Ripard
Patch applied, thanks!
Yours,
Linus
801 - 900 of 2228 matches
Mail list logo
