On Tuesday 15 September 2015 05:58 PM, Ulf Hansson wrote:
On 7 September 2015 at 13:31, Vaibhav Hiremath
wrote:
Trivial patch-series, which fixes the tabbing issue in the driver,
uses the BIT macro for bit fields and prints notice on -EPROBE_DEFER
in sdhci_add_host() function on regulator
On Tuesday 15 September 2015 21:43:19 Pingbo Wen wrote:
>
> On Tuesday, September 15, 2015 09:14 PM, Arnd Bergmann wrote:
> > On Tuesday 15 September 2015 20:56:15 WEN Pingbo wrote:
> >> The millisecond of the last second will be normal if tv_sec is
> >> overflowed. But for y2038 consistency and
On September 15, 2015 7:35:45 AM CDT, Aleksa Sarai wrote:
>Hi,
>
>I'm wondering if there's a reason that we do a linear search for the
>mapping translations between kuid_t and uid_t. Surely something like a
>radix trie would (potentially) allow for better storage and lookup? Is
>the whole "an
Hi Pavel,
I'd love to see the patches :-) I've been trying to figure out the
*right* way to add multiple codecs to a single card (and single CPU
DAI) for some days now. Any help would be greatly appreciated.
Thanks,
-Caleb
On Tue, Sep 15, 2015 at 1:35 AM, Pavel Machek wrote:
> Hi!
>
>> >
Hello!
On Sep 15, 2015, at 9:26 AM, Trevor Woerner wrote:
> On 09/14/15 18:41, gr...@linuxhacker.ru wrote:
>> Reviewed-on: http://review.whamcloud.com/14605
>
> I'm confused why the patch found in this email doesn't match the patch I
> find when I click on the above link? Some of the patches in
On Tue, 15 Sep 2015, Andrzej Hajda wrote:
> On 09/15/2015 03:31 PM, Julia Lawall wrote:
> > On Tue, 15 Sep 2015, SF Markus Elfring wrote:
> >
> v@p
> (
> *< 0
> |
> *<= 0
> )
> >>> It does not, and is not intended to, work. The branches of a disjunction
> >>>
> Subject: [PATCH 11/39] hfi1: drop null test before destroy functions
>
> Remove unneeded NULL test.
>
> The semantic patch that makes this change is as follows:
> (http://coccinelle.lip6.fr/)
>
> //
> @@ expression x; @@
> -if (x != NULL)
>
On Tue 15-09-15 14:05:57, Jerome Marchand wrote:
> Since commit <6539cc05386> (mm: memcontrol: fold mem_cgroup_do_charge()),
> the order to pass to mem_cgroup_oom() is calculated by passing the number
> of pages to get_order() instead of the expected size in bytes. AFAICT,
> it only affects the
On 09/15/2015 03:31 PM, Julia Lawall wrote:
> On Tue, 15 Sep 2015, SF Markus Elfring wrote:
>
v@p
(
*< 0
|
*<= 0
)
>>> It does not, and is not intended to, work. The branches of a disjunction
>>> should be complete expressions.
>> Will the following SmPL approach be
Some string_get_size() calls (e.g.:
string_get_size(1, 512, STRING_UNITS_10, ..., ...)
string_get_size(15, 64, STRING_UNITS_10, ..., ...)
) result in an infinite loop. The problem is that if size is equal to
divisor[units]/blk_size and is smaller than divisor[units] we'll end
up with size == 0
Add a couple of simple tests for string_get_size(). The last one will hang
the kernel without the 'lib/string_helpers.c: fix infinite loop in
string_get_size()' fix.
Signed-off-by: Vitaly Kuznetsov
---
lib/test-string_helpers.c | 27 +++
1 file changed, 27 insertions(+)
This patch series prevents string_get_size() from entering an infinite loop
on some inputs and adds several basic tests for string_get_size() including
one to test for the issue.
Changes since v3:
- NULL termination fixes in PATCH 2/2 [Rasmus Villemoes, Andy Shevchenko]
Vitaly Kuznetsov (2):
On Tue, Sep 15, 2015 at 03:04:58PM +0530, Ronit Halder wrote:
> This patch fixes the warning generated by sparse
> "Using plain integer as NULL pointer" by using NULL
> instead of zero.
>
> Signed-off-by: Ronit halder
> ---
>
> v2: added a new patch in this patch series to fix the NULL
Hello,
On Tue, Sep 15, 2015 at 03:36:34PM +0200, Christian Borntraeger wrote:
> >> The problem seems to be that the newly used percpu_rwsem does a
> >> rcu_synchronize_sched_expedited for all write downs/ups.
> >
> > Can you try:
> >
> >
Removed the curly braces of a single statement if block to remove a
coding style warning detected by checkpatch.
The warning is given below:
WARNING: braces {} are not necessary for single statement blocks
Signed-off-by: Aparna Karuthodi
---
drivers/staging/wilc1000/coreconfigurator.c |3
On Tue, 15 Sep 2015 17:10:11 +0800
Sean Fu wrote:
> According to POSIX standard, "The write() function shall attempt to
> write nbyte bytes from the buffer pointed to by buf to the file
> associated with the open file descriptor, fildes.".
> So it is not the length of string(strlen).
Why do we
On Tue, Sep 15, 2015 at 06:28:40AM -0700, Guenter Roeck wrote:
> On 09/15/2015 01:21 AM, Sudip Mukherjee wrote:
> >On Mon, Sep 14, 2015 at 02:22:08PM -0700, Guenter Roeck wrote:
> >>On Mon, Sep 14, 2015 at 05:19:27PM +0530, Sudip Mukherjee wrote:
>
> I am not building m32r:allmodconfig or
Hello Emilio,
On Mon, Sep 14, 2015 at 2:34 PM, Emilio López
wrote:
> The Peach boards use the EC to store the vboot context information,
> so add the corresponding properties on the EC node to indicate so.
>
> Signed-off-by: Emilio López
> ---
Acked-by: Javier Martinez Canillas
Best regards,
Hello Emilio,
Patch looks mostly good to me, I just have a few comments.
On Mon, Sep 14, 2015 at 2:34 PM, Emilio López
wrote:
> Some EC implementations include a small nvram space used to store
> verified boot context data. This patch offers a way to expose this
> data to userspace.
>
>
On Mon, Sep 14, 2015 at 04:57:35PM +0100, Juri Lelli wrote:
> On 04/09/15 14:27, Juri Lelli wrote:
> > So, just to recall what we discussed at LPC (I have Mike's slides
> > at hand :-)). It seems that key points are:
> >
> > 1- we agreed that locking in cpufreq core has to change as we
> >
Am 15.09.2015 um 15:05 schrieb Peter Zijlstra:
> On Tue, Sep 15, 2015 at 02:05:14PM +0200, Christian Borntraeger wrote:
>> Tejun,
>>
>>
>> commit d59cfc09c32a2ae31f1c3bc2983a0cd79afb3f14 (sched, cgroup: replace
>> signal_struct->group_rwsem with a global percpu_rwsem) causes some noticably
>>
On Tuesday, September 15, 2015 09:14 PM, Arnd Bergmann wrote:
> On Tuesday 15 September 2015 20:56:15 WEN Pingbo wrote:
>> The millisecond of the last second will be normal if tv_sec is
>> overflowed. But for y2038 consistency and demonstration purpose,
>> and avoiding further risks, we still
On 09/15/2015 03:01 PM, SF Markus Elfring wrote:
>> +@r depends on context || org || report@
>> +position p;
>> +typedef u8, u16, u32, u64;
> Can the involved data types be restricted for unsigned types for such
> a source code analysis in a more general way?
I am not sure if I understand
On Tue, Sep 15, 2015 at 02:12:01PM +0200, Oleg Nesterov wrote:
> On 09/14, Kirill A. Shutemov wrote:
> >
> > On Mon, Sep 14, 2015 at 07:05:47PM +0200, Oleg Nesterov wrote:
> > > On 09/14, Kirill A. Shutemov wrote:
> > > >
> > > > Fix is below. I don't really like it, but I cannot find any better
>
On Tue, Sep 15, 2015 at 02:15:10PM +0100, Daniel Thompson wrote:
> Actually it already gets masked out. The argument to raise_nmi() points to a
> data structure owned by the backtrace library functions and this structure
> if altered during the execution of nmi_cpu_backtrace() to clear the calling
Does this patch fix the problem?
David
---
commit 8c8ed9de80bc1bbfd0f1e9a018a0feffcf3c11f8
Author: David Howells
Date: Tue Sep 15 13:57:08 2015 +0100
MODSIGN: Change from CMS to PKCS#7 signing if the openssl is too old
The sign-file.c program actually uses CMS rather than PKCS#7
When putting back a descriptor to the free descs list, some fields are
not set to 0, it can cause bugs if someone uses it without having this
in mind.
Descriptor are not put back one by one so it is easier to clean
descriptors when we request them.
Signed-off-by: Ludovic Desroches
Cc:
In interleaved mode, when numf > 1, we have only one descriptor for the
transfer but this descriptor has to be added to the descs_list. If not,
when doing remove_xfer, the descriptor won't be put back in the
free_descs_list.
Signed-off-by: Ludovic Desroches
---
drivers/dma/at_xdmac.c | 4
From: Maxime Ripard
The addressing mode we were using was not only incrementing the address at
each microblock, but also at each data boundary, which was severely slowing
the transfer, without any benefit since we were not using the data stride.
Switch to the micro block increment only in order
On Mon, Aug 10, 2015 at 9:23 AM, Liang, Kan wrote:
>
>> On Thu, Aug 06, 2015 at 06:10:40PM +, Liang, Kan wrote:
>> > The issue may be caused by uncore box initialization.
>> >
>> > For preventing the potential issues of uncore box initialization, I
>> > once moved the uncore_box_init() out of
On Tue, 15 Sep 2015 15:10:43 +0800
Minfei Huang wrote:
> From: Minfei Huang
>
> Since the patch "ftrace: remove daemon(cb7be3b)" remove the function
> ftraced, the variant ftrace_update_time never be used any more.
>
> Remove the unused variant ftrace_update_time.
Actually, the patch I would
From: Maxime Ripard
Handle 'numf > 1' case for interleaved mode.
Signed-off-by: Maxime Ripard
Signed-off-by: Ludovic Desroches
---
drivers/dma/at_xdmac.c | 104 -
1 file changed, 50 insertions(+), 54 deletions(-)
diff --git
Add new device tree node for the control module register space where
PCIe registers are present.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/dra7.dtsi |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
index
Add "syscon-phy-power" property and remove the deprecated "ctrl-module"
property from SATA and USB PHY node. Also remove the unused control
module dt nodes.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/am4372.dtsi | 16 ++--
arch/arm/boot/dts/dra7.dtsi | 34
The USB2 PHY2 has a different register map compared to USB2 PHY1
to power on/off the PHY. In order to handle it, use the new compatible
string "ti,dra7x-usb2-phy2" for the second instance of USB2 PHY.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/dra7.dtsi |2 +-
1 file
Add "syscon-phy-power" property and "syscon-pcs" property which can
be used to perform the control module initializations and remove
the deprecated "ctrl-module" property from PCIe PHY dt nodes.
Phandle to "sysclk" clock node is also added to the PCIe PHY node
since some of the syscon
This series is basically to deprecate using ctrl-module property and use
corresponding syscon properties to program the control module registers.
Changes from v1:
*) Squashed the patches that replaces "ctrl-module" with
"syscon-phy-power"
*) Added "syscon-phy-power" for SATA dt node in OMAP5
On 15.09.2015 10:40, Mark Brown wrote:
> On Tue, Sep 15, 2015 at 09:40:30AM +0200, Jonas Gorski wrote:
>
>> Mark? If you can drop patches 2 to 4 that would be easiest for me, but if
>> you don't do rebases on your for-next branch, then I'll rewrite the
>> patches to apply on top of the already
On 11 September 2015 at 14:24, Mark Brown wrote:
> On Mon, Sep 07, 2015 at 02:23:46PM +0200, Tomeu Vizoso wrote:
>> Some initcalls in the late level assume that some devices will have
>> already probed without explicitly checking for that.
>>
>> After the recent move to defer most device probes
On Tue 15 Sep 05:43 PDT 2015, Sebastian Reichel wrote:
> Hi,
>
> On Thu, Jul 30, 2015 at 10:53:56AM -0700, Bjorn Andersson wrote:
> > From: Courtney Cavin
> >
> > Add the Qualcomm Switch-Mode Battery Charger and Boost driver, found in
> > pm8941.
> >
> > Signed-off-by: Courtney Cavin
> >
On Mon, Sep 14, 2015 at 04:28:20PM +0530, Anjali Menon wrote:
> Added a space to fix the following coding style error detected by
> checkpatch.
>
> ERROR: space required before the open parenthesis '('
>
> Signed-off-by: Anjali Menon
> ---
> drivers/staging/sm750fb/ddk750_dvi.c | 2 +-
> 1
On Tue, 15 Sep 2015, SF Markus Elfring wrote:
> >> v@p
> >> (
> >> *< 0
> >> |
> >> *<= 0
> >> )
> >
> > It does not, and is not intended to, work. The branches of a disjunction
> > should be complete expressions.
>
> Will the following SmPL approach be more appropriate then?
>
> (
> *v@p < 0
>
OMAP AES hw supports AES-GCM mode.
Adding support for GCM and RFC4106 GCM mode in omap-aes driver.
Signed-off-by: Lokesh Vutla
---
Tested on BeagleBone-Black: http://pastebin.ubuntu.com/12417512/
Changes since v1:
- Addressed comments by Herbert.
Previously posted here:
On Mon, Sep 14, 2015 at 05:23:17PM -0700, Stephen Boyd wrote:
[...]
> arch/arm/mach-tegra/hotplug.c| 2 +-
Acked-by: Thierry Reding
signature.asc
Description: PGP signature
was not exported.
I already submitted patches to fix those problems some 6+ weeks ago.
Hope you'll have more luck.
For my allmodconfig test with next-20150915 alpha, m32r and openrisc
failed. And ofcourse mn10300 is broken since many months now.
Have you already done something with m32r or should I try? If both
Hi Vinod,
This set of patches introduces the support of 'numf > 1' case for the
interleaved mode and several fixes: 'change block increment addressing mode'
and 'clean used descriptor' can be backported to 4.2.
Maxime,
I had some conflicts to merge on a mainline kernel the 'handle numf > 1'
On 09/14/15 18:41, gr...@linuxhacker.ru wrote:
> Reviewed-on: http://review.whamcloud.com/14605
I'm confused why the patch found in this email doesn't match the patch I
find when I click on the above link? Some of the patches in this series
match what I find on your jenkins URLs, and some do not.
On Tuesday 15 September 2015 14:14:09 David Vrabel wrote:
> On 14/09/15 12:32, Arnd Bergmann wrote:
> > On Monday 14 September 2015 13:04:59 Roger Pau Monné wrote:
> >>> TBH, I'm expecting a small impact to the performance. It would be hard
> >>> to get the exactly the same performance as today if
>> v@p
>> (
>> *< 0
>> |
>> *<= 0
>> )
>
> It does not, and is not intended to, work. The branches of a disjunction
> should be complete expressions.
Will the following SmPL approach be more appropriate then?
(
*v@p < 0
|
*v@p <= 0
)
Regards,
Markus
--
To unsubscribe from this list: send the
Tetsuo Handa wrote:
> > Thoughts? Opinions?
>
> To me, fixing callers (adding __GFP_NORETRY to callers) in a step-by-step
> fashion after adding proactive countermeasure sounds better than changing
> the default behavior (implicitly applying __GFP_NORETRY inside).
>
Ping?
I showed you at
On 15/09/15 12:30, Russell King - ARM Linux wrote:
On Tue, Sep 15, 2015 at 12:05:12PM +0100, Daniel Thompson wrote:
Currently on ARM when is triggered from an interrupt handler
(e.g. a SysRq issued using UART or kbd) the main CPU will wedge for ten
seconds with interrupts masked before issuing
On Tuesday 15 September 2015 20:56:15 WEN Pingbo wrote:
> The millisecond of the last second will be normal if tv_sec is
> overflowed. But for y2038 consistency and demonstration purpose,
> and avoiding further risks, we still need to fix it here,
> to avoid similair problems.
>
> Signed-off-by:
On 14/09/15 12:32, Arnd Bergmann wrote:
> On Monday 14 September 2015 13:04:59 Roger Pau Monné wrote:
>>> TBH, I'm expecting a small impact to the performance. It would be hard
>>> to get the exactly the same performance as today if we keep the helpers
>>> to avoid the backend dealing himself with
Fix the following 'make htmldocs' warnings:
.//drivers/gpu/drm/i915/intel_audio.c:439: warning: No description found for
parameter 'intel_encoder'
.//drivers/gpu/drm/i915/intel_audio.c:439: warning: Excess function parameter
'encoder' description in 'intel_audio_codec_disable'
On Tue, 15 Sep 2015, SF Markus Elfring wrote:
> > +@r depends on context || org || report@
> > +position p;
> > +typedef u8, u16, u32, u64;
>
> Can the involved data types be restricted for unsigned types for such
> a source code analysis in a more general way?
>
>
> > +{unsigned char, unsigned
No functional change. Previously omap_control_phy_power() was used to power
off the PHY during probe. But once PIPE3 driver is adapted to use syscon,
omap_control_phy_power() cannot be used. Hence used ti_pipe3_power_off
to power off the PHY.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Roger
Deprecate using phy-omap-control driver to power on/off the PHY and
use *syscon* framework to do the same.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/phy/ti-phy.txt | 10 ++-
drivers/phy/phy-ti-pipe3.c | 90 ++
2
No functional change. Introduce local struct device pointer in
probe and replace using >dev/phy->dev with the local
device pointer. This is in preparation to split ti_pipe3_probe
and add separate functions for getting mem resource, getting
sysctrl and getting clocks.
Signed-off-by: Kishon Vijay
On 11 September 2015 at 17:35, Mark Brown wrote:
> On Fri, Sep 11, 2015 at 04:06:07PM +0200, Tomeu Vizoso wrote:
>
>> Once a platform device (with the platform bus as its parent) is
>> retrieved from the deferred queue, both the parent and the device in
>> question are locked (because of the USB
No functional change. Moved mem resource initialization done in
probe to a separate function as part of cleaning up
ti_pipe3_probe.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-ti-pipe3.c | 52
1 file changed, 33 insertions(+), 19
Deprecate using phy-omap-control driver to set PCS value of the PHY
and start using *syscon* API to do the same.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Roger Quadros
---
Documentation/devicetree/bindings/phy/ti-phy.txt |2 ++
drivers/phy/phy-ti-pipe3.c | 34
Em Tue, Sep 15, 2015 at 09:52:56AM +0300, Adrian Hunter escreveu:
> On 08/09/15 11:08, Jiri Olsa wrote:
> > On Tue, Sep 08, 2015 at 10:58:48AM +0300, Adrian Hunter wrote:
> >> Hi
> >>
> >> Here is V3 of "Fix gaps propagating maps" that fixes some problems
> >> revealed by to d988d5ee6478 ("perf
No functional change. Previously omap_control_phy_power() was used to power
off the PHY during probe. But once phy-omap-usb2 driver is adapted to
use syscon, omap_control_phy_power() cannot be used. Hence used
omap_usb_power_off to power off the PHY.
Signed-off-by: Kishon Vijay Abraham I
Deprecate using phy-omap-control driver to power on/off the PHY,
and use *syscon* framework to do the same. This handles
powering on/off the PHY for the USB2 PHYs used in various TI SoCs.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/phy/ti-phy.txt |8 +-
No functional change. Moved sysctrl initialization done in probe to a
separate function as part of cleaning up ti_pipe3_probe.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-ti-pipe3.c | 78 +---
1 file changed, 45 insertions(+), 33
On Tue, Sep 15, 2015 at 02:05:14PM +0200, Christian Borntraeger wrote:
> Tejun,
>
>
> commit d59cfc09c32a2ae31f1c3bc2983a0cd79afb3f14 (sched, cgroup: replace
> signal_struct->group_rwsem with a global percpu_rwsem) causes some noticably
> hickups when starting several kvm guests (which libvirt
This series is basically to deprecate using phy-omap-control and use
syscon APIs to program the control module registers.
Changes from v1:
*) cleanup ti_pipe3_probe in multiple steps
*) other minor cleanups
Changes from [1] in PHY patches include
*) cleanup ti_pipe3_probe
*) have mask, power_on
No functional change. Moved clock initialization done in probe to a
separate function as part of cleaning up ti_pipe3_probe.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-ti-pipe3.c | 127 +---
1 file changed, 72 insertions(+), 55
> +@r depends on context || org || report@
> +position p;
> +typedef u8, u16, u32, u64;
Can the involved data types be restricted for unsigned types for such
a source code analysis in a more general way?
> +{unsigned char, unsigned short int, unsigned int, unsigned long, unsigned
> long long,
Fix the following 'make htmldocs' warnings:
.//drivers/gpu/drm/i915/i915_gem.c:1729: warning: No description found for
parameter 'vma'
.//drivers/gpu/drm/i915/i915_gem.c:1729: warning: No description found for
parameter 'vmf'
.//drivers/gpu/drm/i915/i915_gem.c:4962: warning: No
The millisecond of the last second will be normal if tv_sec is
overflowed. But for y2038 consistency and demonstration purpose,
and avoiding further risks, we still need to fix it here,
to avoid similair problems.
Signed-off-by: Pingbo Wen
Cc: Y2038
Cc: linux-kernel@vger.kernel.org
Cc: Arnd
Fix the following 'make htmldocs' warnings:
.//drivers/gpu/drm/i915/i915_gem_gtt.c:758: warning: No description found for
parameter 'length'
.//drivers/gpu/drm/i915/i915_gem_gtt.c:818: warning: No description found for
parameter 'length'
.//drivers/gpu/drm/i915/i915_gem_gtt.c:818:
On 15/09/2015 12:30, Wanpeng Li wrote:
> + if (!nested) {
> + vpid = find_first_zero_bit(vmx_vpid_bitmap, VMX_NR_VPIDS);
> + if (vpid < VMX_NR_VPIDS) {
> vmx->vpid = vpid;
> __set_bit(vpid, vmx_vpid_bitmap);
> + }
> + } else
Hello,
This patch set contains four patches: two minor fixes and two patches
fixing quite importatn bug which was missing UART status handling in
DMA mode. It fixes, among others, 'break' contition handling, which is
necessary if we want to use Magic SysRq. So this patch fixes Magic SysRq
This parameter is not used anywhere, so we can get rid of it.
Signed-off-by: Robert Baldyga
Reviewed-by: Krzysztof Kozlowski
---
drivers/tty/serial/samsung.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/tty/serial/samsung.c b/drivers/tty/serial/samsung.c
So far, when interrupt occured in DMA mode, it was handled by terminating
DMA transfer and draining data remaining in RX FIFO. It worked well
until interrupt was caused by timeout, but the same interrupt can be
alse caused by special condition (eg. 'break'), which requires special
handling. In
This patch introduces s3c24xx_serial_rx_drain_fifo() which reads data
from RX FIFO and writes it to tty buffer. It also checks for special
conditions (such as 'break') and handles it. This function has been
separated from s3c24xx_serial_rx_chars_pio() as it contains code which
can be used also in
This label does nothing special and we don't need to have it anymore.
Signed-off-by: Robert Baldyga
Reviewed-by: Krzysztof Kozlowski
---
drivers/tty/serial/samsung.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/tty/serial/samsung.c
On Mon, Sep 14, 2015 at 11:46:32PM -0400, Tejun Heo wrote:
> Hello,
>
> On Mon, Sep 14, 2015 at 08:27:08PM -0700, John Stultz wrote:
> > Yea. The above make sense to me, but I suspect there's some very
> > subtle reason for the existing separated logic.
> > But I'd have to defer to akpm for hints
On Tue, Sep 15, 2015 at 05:41:42AM -0700, Paul E. McKenney wrote:
> > Never mind, the PPC people will implement this with lwsync and that is
> > very much not transitive IIRC.
>
> I am probably lost on context, but...
>
> It turns out that lwsync is transitive in special cases. One of them
> is
Commit adcbcfea15d62 ("spi: mediatek: fix spi clock usage error")
added a new sel_clk but introduced bugs in the error paths since
the wrong struct clk pointers are passed to PTR_ERR().
Fixes: adcbcfea15d62 ("spi: mediatek: fix spi clock usage error")
Signed-off-by: Javier Martinez Canillas
---
On certain targets (eg, MSM8996) we need to set the following
domain attribute for correct operation of the SMMU:
DOMAIN_ATTR_COHERENT_HTW_DISABLE.
Setting that attribute is very important on 8996. Without it, we would
see crazy translation faults.
Note:
There could be support for coherent
Pixel Extension are extra pixels fed to the QSEED2 scalar; this
information is needed to produce an output image. These values
depend on various parameters, such as scalar type, initial phase,
phase step, etc.
Pixel extension values used to be handled and calculated by
hardware; however, software
Hi,
On Thu, Jul 30, 2015 at 10:53:56AM -0700, Bjorn Andersson wrote:
> From: Courtney Cavin
>
> Add the Qualcomm Switch-Mode Battery Charger and Boost driver, found in
> pm8941.
>
> Signed-off-by: Courtney Cavin
> Signed-off-by: Bjorn Andersson
> ---
>
> Changes since v1:
> - Corrected
The current behavior is to try to get optional clocks and print a
dev_err message in case of failure. This looks rather confusing
and may increase with the amount of optional clocks.
We may need a cleaner way to handle per-device clocks but in the
meantime, let's reduce the amount of dev_err
The HDMI controller is new in MDP5 v1.7. As of now, this change
doesn't reflect the novelty and only adds the basics so the probe
gets triggered.
Signed-off-by: Stephane Viau
---
Documentation/devicetree/bindings/drm/msm/hdmi.txt | 3 +++
drivers/gpu/drm/msm/hdmi/hdmi.c| 17
msm_iommu_new() can fail and this change makes sure that we
detect the failure and free the allocated domain before going
any further.
Signed-off-by: Stephane Viau
---
drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c | 1 +
drivers/gpu/drm/msm/msm_gpu.c | 8
2 files changed, 9
On most recent chipsets, clients need to vote for SMMU power
(regulator and clock) themselves for as long as they want the
SMMU to be on, performing translations.
This change enables (disables) the SMMU power just before
attaching (after detaching) MDP5 device to the SMMU.
Signed-off-by:
This change adds the basic MDP5 support for MSM8996.
Signed-off-by: Stephane Viau
---
Documentation/devicetree/bindings/drm/msm/mdp.txt | 2 +
drivers/gpu/drm/msm/mdp/mdp5/mdp5_cfg.c | 95 ++-
drivers/gpu/drm/msm/mdp/mdp5/mdp5_cfg.h | 9 ++-
This change is the output of Envytools change:
"rnndb: Add Pixel Extension registers"
Signed-off-by: Stephane Viau
---
drivers/gpu/drm/msm/mdp/mdp5/mdp5.xml.h | 82 +++-
drivers/gpu/drm/msm/mdp/mdp_common.xml.h | 11 -
2 files changed, 90 insertions(+),
In order to produce an image, the scalar needs to be fed extra
pixels. These top/bottom/left/right values depend on a various of
factors, including resolution, scaling type, phase step and
initial phase.
Pixel Extension are programmed by hardware in most targets - and
can be overwritten by
When calculating phase steps, let's use the same enum
mdp_component_type in order to ease the readability; 0/1 indexes
are a bit confusing and we now have explicit values to index
this type of arrays.
Signed-off-by: Stephane Viau
---
drivers/gpu/drm/msm/mdp/mdp5/mdp5_plane.c | 25
On 09/11/2015 08:15 AM, Krzysztof Kozlowski wrote:
> On 10.09.2015 22:41, Robert Baldyga wrote:
>> This patch introduces s3c24xx_serial_rx_drain_fifo() which reads data
>> from RX FIFO and writes it to tty buffer. It also checks for special
>> conditions (such as 'break') and handles it. This
On Monday 14 September 2015 04:31:43 Alex Deucher wrote:
> On Sun, Sep 13, 2015 at 2:57 PM, Ondrej Zary
> wrote:
> > Hello,
> > I have a PC Chips A31G board with AGPro slot and found that nouveau does
> > not work properly with it. Console works but reverts to software mode,
> > X11 hangs with
We want to make sure we control all the information being passed
down to SMP block. Having access to the cfg pointer here may create
bad things in the future.
Signed-off-by: Stephane Viau
---
drivers/gpu/drm/msm/mdp/mdp5/mdp5_cfg.h | 2 +-
drivers/gpu/drm/msm/mdp/mdp5/mdp5_smp.c | 8
2
This series of patches adds support for MSM8996, including MDP5 v1.7.
Note that only the HDMI interface is supported for now.
Stephane Viau (10):
drm/msm/mdp5: remove the cfg pointer from SMP struct
drm/msm/mdp5: Disable hardware translation table walks (MSM8996)
drm/msm: Fix IOMMU clean
On Tue, Sep 15, 2015 at 11:55:12AM +0200, Peter Zijlstra wrote:
> On Tue, Sep 15, 2015 at 11:49:49AM +0200, Peter Zijlstra wrote:
> > On Mon, Sep 14, 2015 at 02:08:06PM -0700, Davidlohr Bueso wrote:
> > > On Mon, 14 Sep 2015, Peter Zijlstra wrote:
> > >
> > > >On Mon, Sep 14, 2015 at 12:37:23AM
NULL pointer deference is observed in the wilc1000.ko module
with bus type SPI and when SPI is not ready.
Signed-off-by: Chandra S Gorentla
---
v2 - Subject corrected 'stating:' -> 'staging:'
Following are the steps to reproduce.
$ sudo insmod drivers/staging/wilc1000/wilc1000.ko
$ sudo
Hi,
I'm wondering if there's a reason that we do a linear search for the
mapping translations between kuid_t and uid_t. Surely something like a
radix trie would (potentially) allow for better storage and lookup? Is
the whole "an extent fits in a cache line" a good enough optimisation
that it
Fix the following 'make htmldocs' warnings:
.//include/media/v4l2-dv-timings.h:147: warning: No description found for
parameter 'frame_height'
.//include/media/v4l2-dv-timings.h:147: warning: No description found for
parameter 'hfreq'
.//include/media/v4l2-dv-timings.h:147: warning: No
601 - 700 of 2190 matches
Mail list logo
