From: Oleg Drokin
new_disk_conf could be leaked if the follow on checks fail,
so make sure to free it on error if it was not assigned yet.
Found with smatch.
Signed-off-by: Oleg Drokin
---
I thought about just moving the allocation around so that
there is is no failure path after allocation,
From: Oleg Drokin
A couple of memory leaks found by smatch.
Oleg Drokin (2):
drm/qlx: Fix a memory leak on error path
drm: fix a memleak on mutex failure path
drivers/gpu/drm/drm_modeset_lock.c | 4 +++-
drivers/gpu/drm/qxl/qxl_fb.c | 7 +--
2 files changed, 8 insertions(+), 3
From: Oleg Drokin
shadow allocation could be leaked if framebuffer allocation failed,
so need to free it.
Also added handling for shadow allocation failure itself instead
of causing a crash.
Found with smatch.
Signed-off-by: Oleg Drokin
---
drivers/gpu/drm/qxl/qxl_fb.c | 7 +--
1 file
From: Oleg Drokin
Need to free just allocated ctx allocation if we cannot
get our config mutex.
This one has been flagged by kbuild bot all the way back in August,
but somehow nobody picked it up:
https://lists.01.org/pipermail/kbuild/2014-August/001691.html
Found with smatch.
Signed-off-by:
On Sat, Apr 25, 2015 at 11:32:47PM +0100, One Thousand Gnomes wrote:
> > +static int parport;
> > +module_param(parport, int, 0);
> > +MODULE_PARM_DESC(parport, "The parport to be used, default parport0\n");
>
> Minor suggested enhancement: this ought to be an array so you can attach
> multiple
Here's the problem:
[0.126595] ACPI Error: No handler for Region [CMS0]
(8802658a0438) [SystemCMOS] (20150410/evregion-163)
[0.126597] ACPI Error: Region SystemCMOS (ID=5) has no handler
(20150410/exfldio-297)
[0.126600] ACPI Error: Method parse/execution failed
[\_SB_.PCI0._INI]
On 04/21/2015 09:29 PM, Eunbong Song wrote:
> Currently, liblockdep has compilation error.
> This causes from lockdep.c code changes.
> This patch fixes compilation error.
>
> Signed-off-by: Eunbong Song
Applied, thanks.
Thanks,
Sasha
--
To unsubscribe from this list: send the line
On 04/24/2015 12:36 AM, Eunbong Song wrote:
>
> If we try to cross compile liblockdep, even if we set the CROSS_COMPILE
> variable
> the linker error can occur because LD is not set with CROSS_COMPILE.
> This patch adds "LD" can be set automatically with CROSS_COMPILE variable so
> fixes linker
On Sat, Apr 25, 2015 at 06:01:32PM -0400, Christopher Sacchi wrote:
> This is an experimental patch to put kmod in Ring 3, rather than Ring 0.
> Here it is, below the dashed lines:
*blink*
Pray, explain what and how is that supposed to achieve?
--
To unsubscribe from this list: send the line
On Sat, Apr 25, 2015 at 12:58 AM, Adam Goode wrote:
> On Fri, Apr 24, 2015 at 2:39 PM, Adam Goode wrote:
>> On Fri, Apr 24, 2015 at 7:46 AM, Andreas Noever
>> wrote:
>>> On Fri, Apr 24, 2015 at 6:50 AM, Adam Goode wrote:
On Thu, Apr 23, 2015 at 1:15 PM, Adam Goode wrote:
> On Thu,
Reviewed-by: Gwendal Grignou
Tested-by: Gwendal Grignou
On Mon, Apr 6, 2015 at 9:15 AM, Javier Martinez Canillas
wrote:
> From: Stephen Barber
>
> Add proto v3 support to the SPI, I2C, and LPC.
>
> Signed-off-by: Stephen Barber
> Signed-off-by: Javier Martinez Canillas
> ---
>
You can merge change
https://chromium-review.googlesource.com/#/c/262870/ with it, that
fixes an issue with newer firmware.
Reviewed-by: Gwendal Grignou
Tested-by: Gwendal Grignou
On Mon, Apr 6, 2015 at 9:15 AM, Javier Martinez Canillas
wrote:
> From: Stephen Barber
>
> Add support in
Reviewed-by: Gwendal Grignou
Tested-by: Gwendal Grignou
On Mon, Apr 6, 2015 at 9:15 AM, Javier Martinez Canillas
wrote:
> From: Stephen Barber
>
> Update cros_ec_commands.h to the latest version in the EC
> firmware sources and add power domain and passthru commands.
>
> Also, update lightbar
Reviewed-by: Gwendal Grignou
Tested-by: Gwendal Grignou
On Mon, Apr 6, 2015 at 9:15 AM, Javier Martinez Canillas
wrote:
> From: Todd Broch
>
> If the EC device tree node has sub-nodes, try to instantiate them as
> MFD sub-devices. We can configure the EC features provided by the board.
>
>
Reviewed-by: Gwendal Grignou
Tested-by: Gwendal Grignou
On Mon, Apr 6, 2015 at 9:15 AM, Javier Martinez Canillas
wrote:
> Commit 6db07b633658 ("mfd: cros_ec: Check result code from EC messages")
> added a common cros_ec_check_result() function that can be used to check
> the ec_msg->result for
(2015/04/25 17:08), He Kuang wrote:
> There are missing curly braces which causes find_variable() return wrong
> value when probing with global variables.
>
> This problem can be reproduced as following:
>
> $ perf probe -v --add='generic_perform_write global_variable_for_test'
> ...
> Try
On Saturday 25 April 2015 19:13:10 Frederic Weisbecker wrote:
> On Fri, Apr 24, 2015 at 04:07:52PM -0400, Gene Heskett wrote:
> > On Friday 24 April 2015 11:58:31 Frederic Weisbecker wrote:
> > > From: Chris Metcalf
> > >
> > > nohz_full is only useful with isolcpus also set, since otherwise
> >
On 04/24/2015 05:30 AM, Ouyang Zhaowei (Charles) wrote:
If a PVOPS VM has multi-cpu the vcpu_info of cpu0 is the member of the
structure HYPERVISOR_shared_info,
and the others is not, but after 'xl save -c/restore' the vcpu_info will be
reinitialized,
the vcpu_info of all the vcpus will be
On Fri, Apr 24, 2015 at 04:07:52PM -0400, Gene Heskett wrote:
> On Friday 24 April 2015 11:58:31 Frederic Weisbecker wrote:
> > From: Chris Metcalf
> >
> > nohz_full is only useful with isolcpus also set, since otherwise the
> > scheduler has to run periodically to try to determine whether to
On 20/04/15 05:24, Dan Carpenter wrote:
> Mk16_le() is a bad function name and as we can see from tkip.c it just
> duplicates get_unaligned_le16(). Better to make TK void pointer instead
> of a u8 pointer (because it doesn't point to u8s so we have to cast it
> every time we use it). This is
> for your testing I think you will need paride and pcd, I was looking at
> them now, but i suppose it will be little tricky to convert them as it
> is doing its own probing of the parallel port based on the base address.
> I will convert it and give you a patchset for your testing latest by
>
> +static int parport;
> +module_param(parport, int, 0);
> +MODULE_PARM_DESC(parport, "The parport to be used, default parport0\n");
Minor suggested enhancement: this ought to be an array so you can attach
multiple instances to a system.
Alan
--
To unsubscribe from this list: send the line
On Saturday 25 April 2015 23:13:20 Robert Jarzmik wrote:
> This serie was submitted to the lak list, then migrated to mfd drivers, to end
> up again here. There was no change since last submission. Let's hope this is
> the
> last spin and that these platform will be fixed at last.
>
Should
This is an experimental patch to put kmod in Ring 3, rather than Ring 0.
Here it is, below the dashed lines:
---
Signed-off-by: Christopher P. Sacchi
--- kmod.old
This serie was submitted to the lak list, then migrated to mfd drivers, to end
up again here. There was no change since last submission. Let's hope this is the
last spin and that these platform will be fixed at last.
Robert Jarzmik (3):
ARM: pxa: pxa_cplds: add lubbock and mainstone IO
ARM:
As the interrupt handling was transferred to the pxa_cplds driver,
make the switch in lubbock platform code.
Signed-off-by: Robert Jarzmik
---
Since v1: change the name from cottula to lubbock_io
Dmitry pointed out the Cottula was the pxa25x family name,
lubbock was the
Historically, this support was in arch/arm/mach-pxa/lubbock.c and
arch/arm/mach-pxa/mainstone.c. When gpio-pxa was moved to drivers/pxa,
it became a driver, and its initialization and probing happened at
postcore initcall. The lubbock code used to install the chained lubbock
interrupt handler at
As the interrupt handling was transferred to the pxa_cplds driver,
make the switch in mainstone platform code.
Signed-off-by: Robert Jarzmik
---
arch/arm/mach-pxa/include/mach/mainstone.h | 6 +-
arch/arm/mach-pxa/mainstone.c | 115 +++--
2 files changed,
On Thu, Apr 23, 2015 at 07:15:01PM -0700, Andy Lutomirski wrote:
> AMD CPUs don't reinitialize the SS descriptor on SYSRET, so SYSRET
> with SS == 0 results in an invalid usermode state in which SS is
> apparently equal to __USER_DS but causes #SS if used.
>
> Work around the issue by replacing
On Sat, Apr 25, 2015 at 07:52:37PM +0200, Gabriele Mazzotta wrote:
> When the LPM policy is set to ATA_LPM_MAX_POWER, the device might
> generate a spurious PHY event that cuases errors on the link.
> Ignore this event if it occured within 10s after the policy change.
>
> The timeout was chosen
On Sat, Apr 25, 2015 at 07:52:36PM +0200, Gabriele Mazzotta wrote:
> +bool sata_lpm_ignore_phy_events(struct ata_link *link)
> +{
> + /* if LPM is enabled, PHYRDY doesn't mean anything */
> + return !!(link->lpm_policy > ATA_LPM_MAX_POWER);
This gets removed by the next patch so it
On Sat, 25 Apr 2015, Minfei Huang wrote:
> > diff --git a/arch/x86/include/asm/livepatch.h
> > b/arch/x86/include/asm/livepatch.h
> > index 2d29197..84a3247 100644
> > --- a/arch/x86/include/asm/livepatch.h
> > +++ b/arch/x86/include/asm/livepatch.h
> > @@ -23,8 +23,12 @@
> >
> > #include
>
On Fri, 24 Apr 2015, Josh Poimboeuf wrote:
> > #if defined(CONFIG_RANDOMIZE_BASE)
> > - /* KASLR is enabled, disregard old_addr from user */
> > - func->old_addr = 0;
> > + /* If KASLR has been enabled, adjust old_addr accordingly */
> > + if (kaslr_enabled())
> > +
On Fri, 24 Apr 2015, Josh Poimboeuf wrote:
> > #if defined(CONFIG_RANDOMIZE_BASE)
> > - /* KASLR is enabled, disregard old_addr from user */
> > - func->old_addr = 0;
> > + /* If KASLR has been enabled, adjust old_addr accordingly */
> > + if (kaslr_enabled())
> > +
On 2015-04-25, at 3:19 PM, Meelis Roos wrote:
> I noticed that with 4.0 I'm running out of memory on HP A500 (1G RAM)
> and HP RP3410 (2G RAM) parisc machines during gentoo "revdep-rebuild
> -ip". Each time free shows less free memory until OOM killer visits us
> (and first revdep-rebuild
On Wed 2015-04-22 17:50:10, Jin Qian wrote:
> A rogue wakeup source not registered in wakeup_sources list is not visible
> from wakeup_sources_stats_show. Check if the wakeup source is registered
> properly by looking at the timer function.
How often does that happen?
Will people on your systems
On Wed 2015-04-22 17:50:11, Jin Qian wrote:
> user-space aborts suspend attempt if writing wakeup_count failed.
> Count the write failure towards wakeup_count.
Why should writing wakeup_count fail? Can you make sure it does not
happen, instead?
From: Murali Karicheri
Date: Fri, 24 Apr 2015 15:01:41 -0400
> Currently when interface type is MAC to Phy, netif_carrier_(on/off)
> is called which is not needed as Phy lib already updates the carrier
> status to net stack. This is needed only for other interface types
>
> Signed-off-by:
From: six...@microsoft.com
Date: Fri, 24 Apr 2015 11:34:48 -0700
> + net_device_ctx->msg_enable = netif_msg_init(debug, default_msg);
> + if (netif_msg_probe(net_device_ctx))
> + netdev_dbg(net, "netvsc msg_enable: %d",
> +net_device_ctx->msg_enable);
>
I noticed that with 4.0 I'm running out of memory on HP A500 (1G RAM)
and HP RP3410 (2G RAM) parisc machines during gentoo "revdep-rebuild
-ip". Each time free shows less free memory until OOM killer visits us
(and first revdep-rebuild after nontrivial emerge compilation loop kills
the smaller
On 04/25/2015 11:56, Joshua Kinard wrote:
> I keep tripping up a BUG() in isolate_lru_pages in mm/vmscan.c:1345:
>
> switch (__isolate_lru_page(page, mode)) {
> case 0:
> nr_pages = hpage_nr_pages(page);
> mem_cgroup_update_lru_size(lruvec, lru, -nr_pages);
Hi Caesar,
thanks for keeping this alive :-)
Am Freitag, 24. April 2015, 16:07:45 schrieb Caesar Wang:
> Add power domain drivers based on generic power domain for
> Rockchip platform, and support RK3288.
>
> Verified on url =
>
From: Vince Bridgers
Date: Fri, 24 Apr 2015 02:32:07 -0500
> From: Chee Nouk Phoon
>
> This patch resolves false errors from MSGDMA in TX mSGDMA MM to ST
> mode, and is a continuation of the patch recently submitted by Andrea
> Oetken. The MSGDMA had a logic bug that masked detection of this
On Thu, 2015-04-23 at 14:45 +0200, Thomas Gleixner wrote:
> You definitely have a point from the high throughput networking
> perspective.
>
> Though in a power optimizing scenario with minimal network traffic
> this might be the wrong decision. We have to gather data from the
> power maniacs
On Sat, Apr 25, 2015 at 10:47:00PM +0800, pang.xun...@zte.com.cn wrote:
> We want to do the operation in put_prev_task_rt(), and
> put_prev_task_rt() has many call sites.
>
So I've still no clue wtf you're trying to do, there's words in your
changelog but none of them seem to describe the
Hi Linus,
Please pull the below tree for some much needed love for the CRIS-port,
there's a bunch of changes this time, giving the CRISv32 port a bit of
modern makeover with device-tree, irq domain and gpiolib support,
and more switchover to generic frameworks.
Some small fixes and removal of
When the LPM policy is set to ATA_LPM_MAX_POWER, the device might
generate a spurious PHY event that cuases errors on the link.
Ignore this event if it occured within 10s after the policy change.
The timeout was chosen observing that on a Dell XPS13 9333 these
spurious events can occur up to
Changes since v1:
- Added generic helper to keep the logic in one place
Gabriele Mazzotta (2):
libata: Add helper to determine when PHY events should be ignored
libata: Ignore spurious PHY event on LPM policy change
drivers/ata/libahci.c | 3 +--
drivers/ata/libata-core.c | 32
This is a preparation commit that will allow to add other criteria
according to which PHY events should be dropped.
Signed-off-by: Gabriele Mazzotta
---
drivers/ata/libahci.c | 3 +--
drivers/ata/libata-core.c | 19 +++
include/linux/libata.h| 1 +
3 files changed, 21
On Saturday 25 April 2015 11:37:51 Tejun Heo wrote:
> I thought more about it and it's weird to have ATA_LFLAG_CHANGED and
> last_lpm_change timestamp in libata core side and then open-code the
> actual logic in ahci. How about implementing a generic helper, say,
> bool
If a PTE is unmapped and it's dirty then it was writable recently. Due
to deferred TLB flushing, it's best to assume a writable TLB cache entry
exists. With that assumption, the TLB must be flushed before any IO can
start or the page is freed to avoid lost writes or data corruption. This
patch
It is easy to trace when an IPI is received to flush a TLB but harder to
detect what event sent it. This patch makes it easy to identify the source
of IPIs being transmitted for TLB flushes on x86.
Signed-off-by: Mel Gorman
Reviewed-by: Rik van Riel
Reviewed-by: Dave Hansen
---
An IPI is sent to flush remote TLBs when a page is unmapped that was
recently accessed by other CPUs. There are many circumstances where this
happens but the obvious one is kswapd reclaiming pages belonging to a
running process as kswapd and the task are likely running on separate CPUs.
On small
The big change here is that I dropped the patch that batches TLB flushes
from migration context. After V3, I realised that there are non-trivial
corner cases there that deserve treatment in their own series. It did not
help that I could not find a workload that was both migration and IPI
On Fri, Apr 24, 2015 at 03:04:27PM -0400, Waiman Long wrote:
> >>Within a NUMA node, however, we can split the
> >>memory initialization to 2 or more local CPUs if the memory size is
> >>big enough.
> >>
> >I considered it but discarded the idea. It'd be more complex to setup and
> >the two CPUs
On Thu, Apr 16, 2015 at 02:23:44PM -0700, H.J. Lu wrote:
> GCC 5 added a compiler option, -mskip-rax-setup, for x86-64. It skips
> setting up the RAX register when SSE is disabled and there are no
> variable arguments passed in vector registers. Since kernel doesn't
> pass vector registers to
> -Original Message-
> From: Dan Carpenter [mailto:dan.carpen...@oracle.com]
> Sent: Saturday, April 25, 2015 12:05 AM
> To: KY Srinivasan
> Cc: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org;
> de...@linuxdriverproject.org; oher...@suse.com;
> jbottom...@parallels.com;
HOSTLD scripts/kconfig/mconf
/bin/ld: scripts/kconfig/lxdialog/checklist.o: undefined reference to symbol
'acs_map'
Add tinfo library to lxdiablog linking flags, if it exists.
Signed-off-by: Sylvain BERTRAND
---
--- a/scripts/kconfig/lxdialog/check-lxdialog.sh
+++
I keep tripping up a BUG() in isolate_lru_pages in mm/vmscan.c:1345:
switch (__isolate_lru_page(page, mode)) {
case 0:
nr_pages = hpage_nr_pages(page);
mem_cgroup_update_lru_size(lruvec, lru, -nr_pages);
list_move(>lru, dst);
On 4/25/15 8:05 AM, Yunlong Song wrote:
On 2015/4/24 21:58, David Ahern wrote:
On 4/24/15 7:31 AM, Yunlong Song wrote:
Now we are profiling the performance of ext4 and f2fs on an eMMC card with
iozone,
we find a case that ext4 is better than f2fs in random write under the test of
"iozone -s
The kernel pool is intended to serve kernel-internal callers only.
Its purpose and usage is identical to the blocking_pool.
As the kernel_pool is not available to user space, user space cannot
directly interfere with the blocking behavior when obtaining
data from the kernel_pool. Thus, if entropy
The kernel_pool is intended to be the in-kernel equivalent to the
blocking_pool, i.e. requests for random data may be blocked if
insufficient entropy is present.
The added API calls provide a synchronous function call
get_blocking_random_bytes where the caller is blocked.
In addition, an
The async seeding operation is triggered during initalization right
after the first non-blocking seeding is completed. As required by the
asynchronous operation of random.c, a callback function is provided that
is triggered by random.c once entropy is available. That callback
function performs the
During initialization, the DRBG now tries to allocate a handle of the
Jitter RNG. If such a Jitter RNG is available during seeding, the DRBG
pulls the required entropy/nonce string from get_random_bytes and
concatenates it with a string of equal size from the Jitter RNG. That
combined string is
In order to prepare for the addition of the asynchronous seeding call,
the invocation of seeding the DRBG is moved out into a helper function.
In addition, a block of memory is allocated during initialization time
that will be used as a scratchpad for obtaining entropy. That scratchpad
is used
Hi,
as of now, the DRBG is only seeded from get_random_bytes. In various
circumstances, the nonblocking_pool behind get_random_bytes may not be fully
seeded from hardware events at the time the DRBG requires to be seeded.
Based on the discussion in [1], the DRBG seeding is updated such that it
Hi,
On Fri, Apr 24, 2015 at 01:56:25PM -0700, David Cohen wrote:
> > > > > When going into bus suspend/resume we _must_
> > > > > call gadget driver's ->suspend/->resume callbacks
> > > > > accordingly. This patch implements that very feature
> > > > > which has been missing forever.
> > > > >
>
The CPU Jitter RNG provides a source of good entropy by
collecting CPU executing time jitter. The entropy in the CPU
execution time jitter is magnified by the CPU Jitter Random
Number Generator. The CPU Jitter Random Number Generator uses
the CPU execution timing jitter to generate a bit stream
- Original Message -
From: "Don Zickus"
[...]
> On Tue, Apr 21, 2015 at 10:07:00AM -0400, Ulrich Obergfell wrote:
>>
>> Chris,
>>
[...]
>> I think the user should only be allowed to specify a mask that is a subset of
>> tick_nohz_full_mask as only those CPUs don't have a watchdog thread
On Sat, Apr 25, 2015 at 11:34:29AM +0200, Gabriele Mazzotta wrote:
> When the LPM policy is set to ATA_LPM_MAX_POWER, the device might
> generate a spurious PHY event that might cause errors on the link.
> Ignore this event if it occurred within 10s after the policy change.
>
> The timeout was
Some architectures enable sg chaining option while others do not.
The requirement to enable sg chaining is that pages must be aligned
at a 32-bit boundary in order to overload the LSB of the pointer.
Regardless of whether ARCH_HAS_SG_CHAIN is defined or not, the above
requirement is always
Add support for ROHM BH1710/BH1715/BH1721/BH1750/BH1751 ambient light
sensors.
Signed-off-by: Tomasz Duszynski
---
Changes in v2:
- Store chip-dependent values in chip_info structure
- Add bh1750_remove to power down chip (necessary for BH1721)
- Use one time mode for
On 2015/4/24 21:58, David Ahern wrote:
> On 4/24/15 7:31 AM, Yunlong Song wrote:
>> Now we are profiling the performance of ext4 and f2fs on an eMMC card with
>> iozone,
>> we find a case that ext4 is better than f2fs in random write under the test
>> of
>> "iozone -s 262144 -r 64 -i 0 -i 2". We
On 2015/4/24 21:49, Yunlong Song wrote:
> On 2015/4/24 21:31, Yunlong Song wrote:
>> [Profiling Background]
>> Now we are profiling the performance of ext4 and f2fs on an eMMC card with
>> iozone,
>> we find a case that ext4 is better than f2fs in random write under the test
>> of
>> "iozone -s
On 04/25/2015 12:09 AM, Andy Lutomirski wrote:
> On AMD CPUs, SYSRET can return with a valid SS descriptor with with
> the hidden attributes set to an unusable state. Make sure the kernel
> doesn't let this happen. This detects an as-yet-unfixed regression.
>
> Note that the 64-bit version of
On Fri, Apr 24, 2015 at 11:38 PM, David Rientjes wrote:
> On Fri, 24 Apr 2015, Anisse Astier wrote:
>
>> diff --git a/mm/Kconfig b/mm/Kconfig
>> index 390214d..cb2df5f 100644
>> --- a/mm/Kconfig
>> +++ b/mm/Kconfig
>> @@ -635,3 +635,15 @@ config MAX_STACK_SIZE_MB
>> changed to a smaller
On Sat, Apr 25, 2015 at 03:26:48PM +0200, Hagen Paul Pfeifer wrote:
> On 25 April 2015 at 12:31, Paul E. McKenney
> wrote:
>
> > I am not arguing either way on the wisdom or lack thereof of gcc's
> > inlining decisions. But PROVE_RCU=n and CONFIG_DEBUG_LOCK_ALLOC=n should
> > make
Hi Stefan,
Am Samstag, 25. April 2015, 14:23:39 schrieb Stefan Wahren:
> > Heiko Stuebner hat am 22. April 2015 um 22:53
> > geschrieben:
> >
> >
> > Using orphan clocks can introduce strange behaviour as they don't have
> > rate information at all and also of course don't track
> >
> > [...]
Hi David,
First of all, thanks a lot for your time reviewing this series.
On Fri, Apr 24, 2015 at 11:36 PM, David Rientjes wrote:
> On Fri, 24 Apr 2015, Anisse Astier wrote:
>
>> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
>> index ebffa0e..05fcec9 100644
>> --- a/mm/page_alloc.c
>> +++
On 04/24/15 21:03, Arend van Spriel wrote:
On 04/24/15 20:24, John Tobias wrote:
Hi Arend,
Apologize for the confusion. I am asking the repo for the device
driver for 43340. Looking at the link you sent, it's more userspace
support and didn't see the device driver there...
crap. you are
On Sat, Apr 25, 2015 at 11:24:23AM +0530, Sudip Mukherjee wrote:
> On Fri, Apr 24, 2015 at 09:40:42AM -0400, Carlos E. Garcia wrote:
> >
> > Fixed multiple spelling errors.
> >
> > Signed-off-by: Carlos E. Garcia
> initials are usually discouraged in the Signed-off-by. The name here
> should be
On 25 April 2015 at 12:31, Paul E. McKenney wrote:
> I am not arguing either way on the wisdom or lack thereof of gcc's
> inlining decisions. But PROVE_RCU=n and CONFIG_DEBUG_LOCK_ALLOC=n should
> make rcu_read_lock() and rcu_read_unlock() both be empty functions in
> a CONFIG_PREEMPT=n, which
modify i2c-parport driver to use the new parallel port device model.
Signed-off-by: Sudip Mukherjee
---
H Jean,
based on our discussion I have given one more module parameter with
default as parport0 to connect to. And I have tested with i2c-parport
connected to my parport1 and staging/panel
modify panel driver to use the new parallel port device model.
Signed-off-by: Sudip Mukherjee
---
drivers/staging/panel/panel.c | 63 +--
1 file changed, 24 insertions(+), 39 deletions(-)
diff --git a/drivers/staging/panel/panel.c
another WIP for your review. since this is not a formal patch for
applying so writing the comments here.
all points raised by Dan in v2 and v1 has been covered in this patch.
almost all the points raised by Greg in v1 has also been covered.
apart from those points, v2 started using probe
On Fri, Apr 24, 2015 at 05:03:26PM -0300, Jonatas Rech wrote:
> On Fri, Apr 24, 2015 at 07:17:45PM +0100, Mark Brown wrote:
> > The commit message says "this correction has exposed an inconsistency"
> > which suggests that the problem was masked before this fix. Did you
> > mean to say that
On Sat, 2015-04-25 at 12:48 +0200, Paul Cercueil wrote:
> The MSB of the first byte read via I2C seems to indicate whether the
> data is valid (or ready) when an interrupt is raised. Previously,
> this
> bit was ignored, which resulted in a lot of incorrect detections of
> "finger removed"
On 04/25/2015 05:43 AM, Heiko Carstens wrote:
> On Fri, Apr 24, 2015 at 11:16:53AM -0400, Rik van Riel wrote:
>> V2: introduce signed_cputime_t to deal with 64 bit cputime_t on
>> 32 bit architectures, and use READ_ONCE to ensure the value
>> is always read atomically (Heiko Karstens)
>
>
On Wed, Apr 22, 2015 at 08:23:21PM +0900, Inha Song wrote:
> This patch add device tree bindings for the pdata needed to configure
> the Accessory Detect Mode select when Headphone detection.
>
> Signed-off-by: Inha Song
> ---
> Documentation/devicetree/bindings/mfd/arizona.txt | 6 ++
> 1
On Wed, Apr 22, 2015 at 08:23:20PM +0900, Inha Song wrote:
> This patch add support for select accessory detect mode to HPDETL or HPDETR.
> Arizona provides a headphone detection circuit on the HPDETL and HPDETR pins
> to measure the impedance of an external load connected to the headphone.
>
>
Hi Heiko,
> Heiko Stuebner hat am 22. April 2015 um 22:53 geschrieben:
>
>
> Using orphan clocks can introduce strange behaviour as they don't have
> rate information at all and also of course don't track
>
> [...]
>
>
> As this changes the behaviour for orphan clocks, it would of course
>
The iommu_free_table helper release memory it is using (the TCE table and
@it_map) and release the iommu_table struct as well. We might not want
the very last step as we store iommu_table in parent structures.
Signed-off-by: Alexey Kardashevskiy
---
arch/powerpc/include/asm/iommu.h | 1 +
This adds create/remove window ioctls to create and remove DMA windows.
sPAPR defines a Dynamic DMA windows capability which allows
para-virtualized guests to create additional DMA windows on a PCI bus.
The existing linux kernels use this new window to map the entire guest
memory and switch to the
This reverts commit 9e8d4a19ab66ec9e132d405357b9108a4f26efd3 as
tce32_table has exactly the same life time as the whole PE.
This makes use of a new iommu_reset_table() helper instead.
Signed-off-by: Alexey Kardashevskiy
---
arch/powerpc/include/asm/iommu.h | 3 ---
This moves page pinning (get_user_pages_fast()/put_page()) code out of
the platform IOMMU code and puts it to VFIO IOMMU driver where it belongs
to as the platform code does not deal with page pinning.
This makes iommu_take_ownership()/iommu_release_ownership() deal with
the IOMMU table bitmap
This is a part of moving DMA window programming to an iommu_ops
callback. pnv_pci_ioda2_set_window() takes an iommu_table_group as
a first parameter (not pnv_ioda_pe) as it is going to be used as
a callback for VFIO DDW code.
This adds pnv_pci_ioda2_tvt_invalidate() to invalidate TVT as it is
a
This enables sPAPR defined feature called Dynamic DMA windows (DDW).
Each Partitionable Endpoint (IOMMU group) has an address range on a PCI bus
where devices are allowed to do DMA. These ranges are called DMA windows.
By default, there is a single DMA window, 1 or 2GB big, mapped at zero
on a
This replaces direct accesses to TCE table with a helper which
returns an TCE entry address. This does not make difference now but will
when multi-level TCE tables get introduces.
No change in behavior is expected.
Signed-off-by: Alexey Kardashevskiy
---
Changes:
v9:
* new patch in the series
This moves iommu_table creation to the beginning to make following changes
easier to review. This starts using table parameters from the iommu_table
struct.
This should cause no behavioural change.
Signed-off-by: Alexey Kardashevskiy
---
Changes:
v9:
* updated commit log and did minor cleanup
This makes use of the it_page_size from the iommu_table struct
as page size can differ.
This replaces missing IOMMU_PAGE_SHIFT macro in commented debug code
as recently introduced IOMMU_PAGE_XXX macros do not include
IOMMU_PAGE_SHIFT.
Signed-off-by: Alexey Kardashevskiy
Reviewed-by: David
1 - 100 of 336 matches
Mail list logo
