sdhci_init() will clear all irqs and set the needed irqs. So
logically sdhci_init() should be called before request irq.
If not, some irqs may be triggled and handled wrongly. Take
the following into consideration, after request irq, if
SDIO card interrupt enabled, a sd card in the sd slot will
tr
We are going to rework how compound_head() work. It will not use
page->first_page as we have it now.
The only other user of page->first_page beyond compound pages is
zsmalloc.
Let's use page->private instead of page->first_page here. It occupies
the same storage space.
Signed-off-by: Kirill A. S
Let's try to be consistent about data type of page order.
Signed-off-by: Kirill A. Shutemov
Acked-by: Michal Hocko
Acked-by: Vlastimil Babka
Reviewed-by: Andrea Arcangeli
---
include/linux/mm.h | 5 +++--
mm/hugetlb.c | 19 ++-
mm/internal.h | 4 ++--
mm/page_allo
Here's my attempt on fixing race in compound_head(). It should make
compound_head() reliable in all contexts.
The last patch is optional.
It applies cleanly into mmotm patchstack just before my page-flags
patchset.
As expected, it causes few conflicts with patches:
page-flags-introduce-page-fl
Hugh has pointed that compound_head() call can be unsafe in some
context. There's one example:
CPU0CPU1
isolate_migratepages_block()
page_count()
compound_head()
!!PageTail() == true
put_page()
v1 -> v2:
* enhance allocate/free_vpid to handle shadow vpid
* drop empty space
* allocate shadow vpid during initialization
* For each nested vmentry, if vpid12 is changed, reuse shadow vpid w/ an
invvpid.
VPID is used to tag address space and avoid a TLB flush. Currently L0 use
the same
Enhance allocate/free_vid to handle shadow vpid.
Suggested-by: Wincy Van
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/vmx.c | 33 +++--
1 file changed, 27 insertions(+), 6 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index da1590e..bd07d88 100644
VPID is used to tag address space and avoid a TLB flush. Currently L0 use
the same VPID to run L1 and all its guests. KVM flushes VPID when switching
between L1 and L2.
This patch advertises VPID to the L1 hypervisor, then address space of L1 and
L2 can be separately treated and avoid TLB flus
Since 8456a648cf44 ("slab: use struct page for slab management") nobody
uses slab_page field in struct page.
Let's drop it.
Signed-off-by: Kirill A. Shutemov
Acked-by: Christoph Lameter
Acked-by: David Rientjes
Acked-by: Vlastimil Babka
Reviewed-by: Andrea Arcangeli
Cc: Joonsoo Kim
Cc: Andi
Most media functions that unregister, check if the corresponding register
function succeed before. So these functions can safely be called even if a
registration was never made or the component as already been unregistered.
Add the same check to media_device_unregister() function for consistency.
fix clock issue for fsl,spdi in imx6.
Changes in v2:
move the dts change to another patch
Shengjiu Wang (2):
clk: imx6: Add SPDIF_GCLK clock in clock tree
ARM: dts: imx6: change the core clock of spdif
arch/arm/boot/dts/imx6qdl.dtsi| 2 +-
arch/arm/boot/dts/imx6sl.dtsi
Hello,
The Media Controller framework has an issue in which the media device node
is registered before all the media entities and pads links are created so
if user-space tries to enumerate the graph too early, it may get a partial
graph since not everything has been registered yet.
This series fi
The media device node is registered and so made visible to user-space
before entities are registered and links created which means that the
media graph obtained by user-space could be only partially enumerated
if that happens too early before all the graph has been created.
To avoid this race cond
Hi Rob, Mark,
We've been trying to figure out the right way to represent a class
of display encoder devices in DT.
These devices have registers that are generally configured via i2c. Once
the device is configured, it takes in video data from the mipi
dsi bus.
Until now, all the devices we've
Hi Rob, Mark,
We've been trying to figure out the right way to represent a class
of display encoder devices in DT.
These devices have registers that are generally configured via i2c. Once
the device is configured, it takes in video data from the mipi
dsi bus.
Until now, all the devices we've
Tony,
On 03/09/15 10:36, Roger Quadros wrote:
> Chanwoo,
>
> On 06/08/15 02:36, Chanwoo Choi wrote:
>> On 08/05/2015 07:37 PM, Tony Lindgren wrote:
>>> * Roger Quadros [150727 06:13]:
The VBUS line of USB2 is connected to VBUS detect logic on
the PMIC. Use the palmas-usb driver to repo
On Tue, 2015-09-15 at 10:37 +0100, Punit Agrawal wrote:
> "Jon Medhurst (Tixy)" writes:
>
> > On Mon, 2015-09-14 at 15:38 +0100, Punit Agrawal wrote:
> >> Mark Rutland writes:
> >>
[...]
> >> The way the SCP interface is defined, the sensor identifiers are
> >> contiguous,
> >
> > Is there any
BUG: unable to handle kernel NULL pointer dereference at 0024
BUG: sleeping function called from invalid context at include/linux/sched.h:2756
BUG: scheduling while atomic: spice-vdagentd/906/0x0002
BUG: spinlock lockup suspected on CPU#0, spice-vdagentd/906
https://bugzilla.kerne
Hi
Sorry for the late reply. Looking into this now and sending feedback
later today.
/Jarkko
On Mon, Sep 14, 2015 at 05:36:07PM -0400, Joseph Salisbury wrote:
> Hi Jarkko,
>
> A kernel bug report was opened against Ubuntu [0] and in bugzilla[1]. A
> kernel bisect was performed, and it identifi
Function group_classify() has not used parameter "env", so remove it.
And unify code to always use group_classify() to calculate group's
load type.
Signed-off-by: Leo Yan
---
kernel/sched/fair.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/kernel/sched/fair.c b/
Macro LOAD_AVG_MAX is defined far away from the precompuated tables
for decay calculation in code; So explicitly comments for this.
Also fix one typo: s/LOAD_MAX_AVG/LOAD_AVG_MAX.
Signed-off-by: Leo Yan
---
kernel/sched/fair.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --g
On 14.09.2015 18:44, Marc Zyngier wrote:
struct device_node is very much DT specific, and the original authors
of the irqdomain subsystem recognized that tie, and went as far as
mentionning that this could be replaced by some "void *token",
should another firmware infrastructure be using it.
As
Hi Javier,
Javier Martinez Canillas wrote:
> The media device node is registered and so made visible to user-space
> before entities are registered and links created which means that the
> media graph obtained by user-space could be only partially enumerated
> if that happens too early before all
On Tue 2015-09-15 13:42:21, Viresh Kumar wrote:
> The variable 'wakeup_irq' is defined within #ifdef CONFIG_PM_SLEEP_DEBUG
> and used outside of it. And that breaks kernel build:
>
> /home/viresh/linux/drivers/base/power/wakeup.c:871: undefined reference to
> `wakeup_irq'
> /home/viresh/drivers/b
On Tue, Sep 15, 2015 at 11:46:02AM +0100, Jon Medhurst (Tixy) wrote:
> On Tue, 2015-09-15 at 10:37 +0100, Punit Agrawal wrote:
> > "Jon Medhurst (Tixy)" writes:
> >
> > > On Mon, 2015-09-14 at 15:38 +0100, Punit Agrawal wrote:
> > >> Mark Rutland writes:
> > >>
> [...]
> > >> The way the SCP in
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 a backtrace for every CPU
except itself.
The new backtrace code introduced by commit 96f0e00378d4 ("ARM: add
basic sup
On Tue, Sep 15, 2015 at 12:55:15PM +0300, Mikko Perttunen wrote:
> The new determine_rate prototype allows for clock rates exceeding
> 2^31-1 Hz to be used. Switch the DFLL clock to use determine_rate
> instead of round_rate and unlock the top rates supported by the
> Tegra124.
>
> Signed-off-by:
On Fri 2015-08-14 16:59:27, check.ker...@gmail.com wrote:
> From: yangdongdong
>
> This aligns every column of elements in wakeup_sources to
> conveniently check any specific column for suspicious power
> consumption wakeup source or for other easily readable purpose.
>
> Signed-off-by: Dongdong
Hi Will,
On Fri, Aug 21, 2015 at 04:54:25PM +0100, Catalin Marinas wrote:
> On Fri, Aug 21, 2015 at 05:14:46PM +0800, Leo Yan wrote:
> > On Fri, Aug 21, 2015 at 10:00:43AM +0100, Catalin Marinas wrote:
> > > On Fri, Aug 21, 2015 at 11:40:22AM +0800, Leo Yan wrote:
> > > > Enable generic idle loop
On Mon, 2015-09-14 at 18:28 -0700, Stephen Boyd wrote:
> On 09/14/2015 02:54 PM, Stephen Boyd wrote:
> > The current driver implementation supports only 128 peripherals.
> > Add support for more than 128 peripherals by taking a lazy
> > caching approach to the mapping tables. Instead of reading th
On Wed 2015-09-09 21:58:09, Eduardo Valentin wrote:
> From: Pavel Machek
>
> This adds support for OMAP3 chips to ti-soc-thermal. As requested by
> TI people, it is marked unreliable and warning is printed.
>
> Cc: Zhang Rui
> Cc: linux...@vger.kernel.org
> Cc: linux-o...@vger.kernel.org
> Cc:
On Thu 2015-07-30 10:11:24, NeilBrown wrote:
>
> Add a 'continuous' option for usb charging which enables
> the "linear" charging mode of the twl4030.
>
> Linear charging does a good job with not-so-reliable power sources.
> Auto mode does not work well as it switches off when voltage drops
> mom
On Thu 2015-07-30 10:11:24, NeilBrown wrote:
> The twl4030 usb phy needs to be active while we are using
> the USB VBUS as a current source for charging.
> In particular, the usb3v1 regulator must be enabled and the
> PHY_PWR_PHYPWD bit must be set to keep the phy powered.
>
> commit ab37813f4093a
On Thu 2015-07-30 10:11:24, NeilBrown wrote:
> The usb phy driver already determines when VBUS is available,
> so repeating the test in the charger driver is pointless duplication.
>
> On probe, process the last event from the phy, and from then on,
> do whatever the phy tells us without double-ch
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 a backtrace for every CPU
> except itself.
>
>
On 5 September 2015 at 08:49, Michele Curti wrote:
> Add an entry to the sdhci_acpi_uids list to detect the SD card
> reader on the Asus X205Ta laptop.
>
> dstd table:
>
> Device (SDHC)
> {
> Name (_ADR, Zero) // _ADR: Address
> Name (_HID, "PNP0FFF") // _HID: Hardware ID
> Name (_CI
On Fri, 2015-01-23 at 16:19 -0800, Bjorn Andersson wrote:
> From: Courtney Cavin ca...@sonymobile.com>
>
> Signed-off-by: Courtney Cavin ca...@sonymobile.com>
> Signed-off-by: Bjorn Andersson anders...@sonymobile.com>
>
>
> +config INPUT_PM8941_PWRKEY
> + tristate "Qualcomm PM8941 powe
On Sun, 2015-09-13 at 00:56 +0200, Willy Tarreau wrote:
> 2.6.32-longterm review patch. If anyone has any objections, please let me
> know.
>
> --
>
> From: Ralf Baechle
>
> commit f05ff43355e6997c18f82ddcee370a6e5f8643ce upstream.
>
> This is no longer needed with the fixed,
On Tue, 2015-09-15 at 12:03 +0100, Mark Rutland wrote:
> On Tue, Sep 15, 2015 at 11:46:02AM +0100, Jon Medhurst (Tixy) wrote:
> > On Tue, 2015-09-15 at 10:37 +0100, Punit Agrawal wrote:
> > > "Jon Medhurst (Tixy)" writes:
> > >
> > > > On Mon, 2015-09-14 at 15:38 +0100, Punit Agrawal wrote:
> > >
From: Colin Ian King
static analysis with cppcheck detected the following error:
[drivers/media/platform/sti/c8sectpfe/c8sectpfe-core.c:1210]:
(error) Uninitialized variable: ret
ret is never initialised, so garbage is being returned. Instead
return the error return from the call of request_f
e
>> the wrong struct clk pointers are passed to PTR_ERR().
>
> This doesn't apply against current code, please check and resend.
>
Which branch should I use as a baseline then? The patch applies cleanly
on both today's linux-next (next-20150915) and your for-linus branch:
ht
If the size of the firmware is not as expected then we are jumping to the
error path but we missed releasing the firmware.
Signed-off-by: Sudip Mukherjee
---
drivers/staging/rtl8192e/rtl8192e/r8192E_firmware.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/rtl8192e/rtl8192e/
On 2 September 2015 at 17:16, Vaibhav Hiremath
wrote:
>
>
> On Wednesday 02 September 2015 08:37 PM, Joe Perches wrote:
>>
>> On Wed, 2015-09-02 at 18:37 +0530, Vaibhav Hiremath wrote:
>>>
>>> On Wednesday 02 September 2015 02:07 AM, Joe Perches wrote:
On Wed, 2015-09-02 at 00:54 +0530,
Fix the following 'make htmldocs' warnings:
.//include/linux/spi/spi.h:71: warning: No description found for parameter
'lock'
.//include/linux/spi/spi.h:71: warning: Excess struct/union/enum/typedef
member 'clock' description in 'spi_statistics'
Signed-off-by: Geliang Tang
---
include/lin
Takao Indoh writes:
> On 2015/09/08 18:32, Alexander Shishkin wrote:
>> Takao Indoh writes:
>>
>>> perf_event_create_kernel_counter is used to enable perf events in kernel
>>> without buffer for logging its events. This patch add new fucntion which
>>> enable perf events with ring buffer. Intel
Takao Indoh writes:
> On 2015/09/08 18:48, Alexander Shishkin wrote:
>> Takao Indoh writes:
>>
>>> +/* intel_pt */
>>> +static struct perf_event_attr pt_attr_pt = {
>>> + .config = 0x400, /* bit10: TSCEn */
>>
>> Doesn't it make sense to make these things configurable via sysfs or
>>
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 will move into cgroups
- each vcpu thread and each i/o thread)
When you now start lo
On Tue, 15 Sep 2015, Tomasz Nowicki wrote:
Can you folks please do proper quoting on reply? It's annoying to
scroll down 250+ lines to find TWO lines of reply and then have
another 250+ lines for nothing.
Here is the real gist of your reply:
> On 14.09.2015 18:44, Marc Zyngier wrote:
> > -struct
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 value displayed in the oom warning message.
This patch fix
On Sun, 2015-09-13 at 00:56 +0200, Willy Tarreau wrote:
> This is the start of the longterm review cycle for the 2.6.32.68 release.
> All patches will be posted as a response to this one. If anyone has any
> issue with these being applied, please let me know. If anyone is a
> maintainer of the prop
On 15.09.2015 14:04, Thomas Gleixner wrote:
On Tue, 15 Sep 2015, Tomasz Nowicki wrote:
Can you folks please do proper quoting on reply? It's annoying to
scroll down 250+ lines to find TWO lines of reply and then have
another 250+ lines for nothing.
Yeah, good point! Sorry.
Tomasz
--
To unsub
Hi all,
On Tue, Sep 15, 2015 at 1:28 PM, Pavel Machek wrote:
> On Thu 2015-07-30 10:11:24, NeilBrown wrote:
>>
>> Add a 'continuous' option for usb charging which enables
>> the "linear" charging mode of the twl4030.
>>
>> Linear charging does a good job with not-so-reliable power sources.
>> Aut
pid_t getvpid(pid_t pid, pid_t source, pid_t target);
This syscall converts pid from one pid-ns into pid in another pid-ns:
it takes @pid in namespace of @source task (zero for current) and
returns related pid in namespace of @target task (zero for current too).
If pid is unreachable from target p
Andy Shevchenko writes:
> On Tue, 2015-09-15 at 00:00 +0200, Rasmus Villemoes wrote:
>> On Mon, Sep 14 2015, Vitaly Kuznetsov wrote:
>>
>
> Vitaly, thanks for the test cases. My comments below.
>
>> > +static __init void test_string_get_size_one(u64 size, u64
>> > blk_size,
>> > +
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
> > > solution.
> >
> > Me too...
> >
> > But this change "documents" the nas
On Sat, Sep 12, 2015 at 9:19 AM, Ming Lei wrote:
> On Fri, 11 Sep 2015 17:43:15 -0400
> Mike Snitzer wrote:
>
>> Ming, Jens, others:
>>
>> Please see this BZ comment that speaks to a 4.3 regression due to the
>> late bio splitting changes:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1247382#c4
Fix the following 'make htmldocs' warnings:
.//drivers/gpu/drm/i915/intel_lrc.c:780: warning: No description found for
parameter 'req'
.//drivers/gpu/drm/i915/intel_lrc.c:780: warning: Excess function parameter
'request' description in 'intel_logical_ring_begin'
.//drivers/gpu/drm/i915/int
On Tue, 2015-09-15 at 14:10 +0200, Vitaly Kuznetsov wrote:
> Andy Shevchenko writes:
>
> > I prefer to put '\0' at the position after we expected have an
> > actual
> > '\0'. In this case we always be NULL terminated. I did this for
> > hexdump
> > test cases.
>
> Just to check I got your sugge
On 15/09/15 11:58, Tomasz Nowicki wrote:
> On 14.09.2015 18:44, Marc Zyngier wrote:
>> struct device_node is very much DT specific, and the original authors
>> of the irqdomain subsystem recognized that tie, and went as far as
>> mentionning that this could be replaced by some "void *token",
>> sho
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 unavailability.
>
> V1 => V2
>
> - Fixed all comme
[ + Stephen on cc: ]
On Friday, August 28, 2015 01:49:35 PM Bartlomiej Zolnierkiewicz wrote:
> CLK_CPU_HAS_DIV1 and CLK_CPU_NEEDS_DEBUG_ALT_DIV masks were
> incorrectly used as a bit numbers. Fix it.
>
> Tested on Exynos4210 based Origen board and on Exynos5250 based
> Arndale board.
>
> Cc: T
> >> added a new sel_clk but introduced bugs in the error paths since
> >> the wrong struct clk pointers are passed to PTR_ERR().
> > This doesn't apply against current code, please check and resend.
> Which branch should I use as a baseline then? The patch applies c
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 would
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 des
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 ifconf
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 -0
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 up
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
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 mo
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 funct
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 ++-
drivers/gpu/
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 softwar
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 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: Stephane
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 insertio
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 autho
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
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 messa
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 hardwa
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 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
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
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 D
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 b/drivers/tty/serial/sams
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 such
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
i
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
handling
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
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: warning:
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 Berg
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 descriptio
> +@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, s
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 a
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 deletions(-)
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 w
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 deletions(
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 +-
driver
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
Acked-by
301 - 400 of 1097 matches
Mail list logo
