The driver calls pci_set_mwi to enable memory-write-invalidate when it
is initialized, but does not call pci_clear_mwi when it is removed. Many
other drivers calls pci_clear_mwi when pci_set_mwi is called, such as
r8169, 8139cp and e1000.
This patch adds pci_clear_mwi in error handling and
Currently, when tring to set up a serial console with a higher
baud rate, it would fallback to 921600.
Tested-by: Jianqun Xu
Signed-off-by: Jeffy Chen
---
Changes in v2:
remove baud_rates as Alan's suggestion.
drivers/tty/serial/serial_core.c | 33 ++---
1 file
On 16/01/01, Sergey Senozhatsky wrote:
> On (12/31/15 19:18), Serge E. Hallyn wrote:
> > On Fri, Jan 01, 2016 at 10:10:35AM +0900, Sergey Senozhatsky wrote:
> > > On (12/31/15 19:08), Serge E. Hallyn wrote:
> > > > > re-upping
> > > > >
On Jan 4, 2016 5:08 AM, "Peter Hutterer" wrote:
>
> On Sat, Jan 02, 2016 at 08:39:21PM -0800, Dmitry Torokhov wrote:
> > On Thu, Dec 31, 2015 at 03:36:47AM +0530, Aniroop Mathur wrote:
> > > This patch introduces concept to drop partial events in evdev handler
> > > itself after emptying the
last_load is updated not cpufreq_get_actual_power()
but cpufreq_get_requested_power().
Signed-off-by: Inhyuk Kang
diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c
index e3fbc5a..3069ef5 100644
--- a/drivers/thermal/cpu_cooling.c
+++ b/drivers/thermal/cpu_cooling.c
@@
On Fri, Jan 1, 2016 at 11:40 PM, Arnd Bergmann wrote:
> The of_get_named_gpio_flags() function does nothing other than returning
> an error when CONFIG_OF_GPIO is disabled, but that causes spurious
> warnings about possible use of uninitialized variables in any code that
> does not check the
* Tony Luck wrote:
> On Wed, Dec 30, 2015 at 9:59 AM, Andy Lutomirski wrote:
> > This adds two bits of fixup class information to a fixup entry,
> > generalizing the uaccess_err hack currently in place.
> >
> > Forward-ported-from-3.9-by: Tony Luck
> > Signed-off-by: Andy Lutomirski
>
>
Unsigned expressions cannot be lesser than zero. Presence of comparisons
'unsigned (<|<=|>|>=) 0' often indicates a bug, usually wrong type of variable.
The patch beside finding such comparisons tries to eliminate false positives,
mainly by bypassing range checks.
gcc can detect such comparisons
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
drivers/gpu/drm/omapdrm/omap_gem.c
between commit:
f4302747af02 ("drm: omapdrm: gem: Move global usergart variable to
omap_drm_private")
from the drm tree and commit:
0cf445f1b0c1 ("mm, dax, gpu: convert
Hi,
On Tuesday 29 December 2015 07:22 AM, Shawn Lin wrote:
> This patch to add a generic PHY driver for ROCKCHIP eMMC PHY.
> Access the PHY via registers provided by GRF (general register
> files) module.
>
> Signed-off-by: Shawn Lin
> ---
>
> drivers/phy/Kconfig | 7 ++
>
Hi, Rafael
Acke-by: Lv Zheng
One more improvement is:
After applying this patch, I can still detect the following diff blocks using
ACPICA's divergence checking utility:
diff -E -b -w -B -rpuN linux-acpica/drivers/acpi/acpica/hwxfsleep.c
acpica-linuxized/drivers/acpi/acpica/hwxfsleep.c
---
Hi Eric,
On Sat, 26 Dec 2015 13:15:50 -0800 Eric Anholt wrote:
>
> I'll be sending pull-requests to Florian soon, but I would like to get
> my trees included in linux-next to get increased testing coverage of
> them against everything else going on for 4.5. I'm expecting to produce
> trees
On 2016/1/4 13:52, Jaehoon Chung wrote:
Hi, Shawn.
On 01/04/2016 11:50 AM, Shawn Lin wrote:
This patch implement hw_reset function for DesignWare
MMC controller. By adding this feature, mmc blk can
do some basic recovery.
>From Synopsys DesignWare Cores Mobile Storage Host Databook
(Section
On Wed, Dec 30, 2015 at 10:20:30PM +0100, Julia Lawall wrote:
> The drm_dp_mst_topology_cbs structures are never modified, so declare them
> as const.
>
> Done with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall
Applied to drm-misc, thanks.
-Daniel
>
> ---
>
On Wed, Dec 30, 2015 at 12:32:00PM +0200, Tomi Valkeinen wrote:
>
>
> On 30/12/15 11:31, Sebastian Frias wrote:
> > Hi,
> >
> > On 12/30/2015 09:06 AM, Tomi Valkeinen wrote:
> >>
> >> Also note that I don't want new fbdev drivers into the mainline kernel.
> >> You should implement a DRM based
From: "james.chen"
Fix function of wake-on-touch on suspend/resume.
The function of device_may_wakeup will return true if
the device supports wake-on-touch (for example, kitty and buddy).
So, modify the code from "if (device_may_wakeup(dev))" to
"if (!device_may_wakeup(dev))". And adjust the
On Sun, Dec 27, 2015 at 06:45:58PM +0800, Geliang Tang wrote:
> Use to_pci_dev() instead of open-coding it.
>
> Signed-off-by: Geliang Tang
Applied to drm-misc, thanks.
-Daniel
> ---
> drivers/gpu/drm/gma500/power.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
Hi Milan,
On 3 January 2016 at 06:46, Milan Broz wrote:
>
> Sorry for delay, I tried to compile it.
> It doesn't crash now, but it also does not work.
>
> You usage of IV in XTS mode is not correct - it cannot just work this way,
> you have to initialize IV after each block. And just one write
On Fri, 2015-12-18 at 16:09 +0800, Yong Wu wrote:
> This patch add SMI(Smart Multimedia Interface) driver. This driver
> is responsible to enable/disable iommu and control the power domain
> and clocks of each local arbiter.
Hi Matthias,
What's your opinion about the SMI in this version?
When the reset_resume() is called, the flag of SELECTIVE_SUSPEND should be
cleared and reinitialize the device, whether the SELECTIVE_SUSPEND is set
or not. If reset_resume() is called, it means the power supply is cut or the
device is reset. That is, the device wouldn't be in runtime suspend
On 01/04/2016 09:39 AM, Yang Zhang wrote:
> On 2015/12/31 15:13, Jason Wang wrote:
>> This patch tries to implement an device IOTLB for vhost. This could be
>> used with for co-operation with userspace(qemu) implementation of
>> iommu for a secure DMA environment in guest.
>>
>> The idea is
Add i2c dtsi node for MT2701.
Signed-off-by: Liguo Zhang
---
arch/arm/boot/dts/mt2701.dtsi | 42 ++
1 file changed, 42 insertions(+)
diff --git a/arch/arm/boot/dts/mt2701.dtsi b/arch/arm/boot/dts/mt2701.dtsi
index bd88ae9..bb34770 100644
---
Add a dt binding for the MT2701 soc.
Signed-off-by: Liguo Zhang
---
Documentation/devicetree/bindings/i2c/i2c-mt6577.txt | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt
On 12/31/2015 07:17 PM, Michael S. Tsirkin wrote:
> On Thu, Dec 31, 2015 at 03:13:45PM +0800, Jason Wang wrote:
>> This patch tries to implement an device IOTLB for vhost. This could be
>> used with for co-operation with userspace(qemu) implementation of
>> iommu for a secure DMA environment in
Hi Jaegeuk,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Monday, January 04, 2016 1:43 PM
> To: Chao Yu
> Cc: linux-f2fs-de...@lists.sourceforge.net; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] f2fs: introduce max_file_blocks in sbi
>
> Hi Chao,
>
On 04-01-16, 12:14, Chen Yu wrote:
> Currently the minimal up_threshold is 11, and user may want to
> use a smaller minimal up_threshold for performance tuning,
> so MIN_FREQUENCY_UP_THRESHOLD could be set to 1 because:
>
> 1. Current systems wouldn't be affected as they have already
>a value
Hi, Shawn.
On 01/04/2016 11:50 AM, Shawn Lin wrote:
> This patch implement hw_reset function for DesignWare
> MMC controller. By adding this feature, mmc blk can
> do some basic recovery.
>
>>From Synopsys DesignWare Cores Mobile Storage Host Databook
> (Section 7.4.4), we get the details:
> 1.
Its better to remove the dependency on uapi/kvm_perf.h to allow dynamic
discovery of kvm events (if its needed). To do this, some extern
variables have been introduced with which we can keep the generic
functions generic.
Signed-off-by: Hemant Kumar
Acked-by: Alexander Yarygin
---
Changelog:
v9
perf kvm can be used to analyze guest exit reasons. This support already
exists in x86. Hence, porting it to powerpc.
- To trace KVM events :
perf kvm stat record
If many guests are running, we can track for a specific guest by using
--pid as in : perf kvm stat record --pid
- To see the
Powerpc provides hcall events that also provides insights into guest
behaviour. Enhance perf kvm stat to record and analyze hcall events.
- To trace hcall events :
perf kvm stat record
- To show the results :
perf kvm stat report --event=hcall
The result shows the number of hypervisor
This patch removes the "const" qualifier from kvm_events_tp declaration
to account for the fact that some architectures may need to update this
variable dynamically. For instance, powerpc will need to update this
variable dynamically depending on the machine type.
Signed-off-by: Hemant Kumar
---
Hi Wang,
[auto build test WARNING on v4.4-rc8]
[cannot apply to tty/tty-testing pm/linux-next next-20151231]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
Hi Wang,
[auto build test WARNING on v4.4-rc8]
[cannot apply to tty/tty-testing pm/linux-next next-20151231]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
Hi Chao,
On Thu, Dec 31, 2015 at 02:35:37PM +0800, Chao Yu wrote:
> Introduce max_file_blocks in sbi to store max block index of file in f2fs,
> it could be used to avoid unneeded calculation of max block index in
> runtime.
>
> Signed-off-by: Chao Yu
> ---
> fs/f2fs/data.c | 2 +-
>
> -Original Message-
> From: Nicholas Krause [mailto:xerofo...@gmail.com]
> Sent: Friday, January 01, 2016 12:06 PM
> To: kashyap.de...@avagotech.com
> Cc: sumit.sax...@avagotech.com; uday.ling...@avagotech.com;
> jbottom...@odin.com; martin.peter...@oracle.com;
>
As CSRT table will not always work, 2 arguments, base_request_line
and num are added to acpi dma controller register
as another way to get device request line.
Signed-off-by: Wang Hongcheng
---
drivers/dma/acpi-dma.c| 25 -
drivers/dma/dw/platform.c | 2 +-
register acpi_dma controller, so ACPI devices can request pl330 DMA
channel. Request line info is get from private data.
Signed-off-by: Wang Hongcheng
---
drivers/acpi/acpi_apd.c| 34 +-
drivers/dma/pl330.c| 27 +++
Set a new port type for AMD Carrizo. Add has_pl330_dma to 8250_dw's
private data and init fcr,ier as well as dma rx size.
Signed-off-by: Wang Hongcheng
---
drivers/acpi/acpi_apd.c | 11 +++
drivers/tty/serial/8250/8250_dw.c | 15 +++
Hi, all
As AMD carrizo UART device is compatible with 8250 and has pl330 DMA
IP, our uart driver is serial:8250 and DMA engine is registered by
driver/dma/pl330. The following patches are made, in order to enable
DMA.
V1:
Add config option CONFIG_SERIAL_8250_AMD in use of AMD carrizo.
Because carrizo's UART DMA device is an amba device, it selects
ARM_AMBA option. Anything uses amba devices must select ARM_AMBA.
Signed-off-by: Wang Hongcheng
---
drivers/tty/serial/8250/Kconfig | 8
1 file changed, 8
The post_setup hook of AMD0020 device will create an amba device as
the child of a previously created platform device.
Signed-off-by: Wang Hongcheng
---
drivers/acpi/acpi_apd.c | 131
1 file changed, 121 insertions(+), 10 deletions(-)
diff --git
mcbuf_sz means bytes to allocate for MicroCode buffer.
flags is for irq sharing, default is non-shared, in AMD
Carrizo, pl330 shares IRQ with its corresponding UART device.
Signed-off-by: Wang Hongcheng
---
drivers/acpi/acpi_apd.c| 17 +
drivers/dma/pl330.c| 9
On 30-12-15, 12:18, Andrzej Hajda wrote:
> The function can return negative values so it should be assigned
> to signed type.
>
> The problem has been detected using proposed semantic patch
> scripts/coccinelle/tests/unsigned_lesser_than_zero.cocci [1].
>
> [1]:
Hi Mimi,
On Mon, 04 Jan 2016 00:06:37 -0500 Mimi Zohar wrote:
>
> On Mon, 2016-01-04 at 03:16 +, Al Viro wrote:
> >
> > FWIW, I'm going to pull the part that introduces memdup_user_nul() into
> > a never-rebased branch and if security.git is willing to pull it and handle
> > that conversion
Hi Baolin,
[auto build test ERROR on v4.4-rc8]
[cannot apply to balbi-usb/next usb/usb-testing next-20151231]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
Just got other one with rc8 (random, not easily reproducable):
[ 1254.780923] Unable to handle kernel NULL pointer dereference at
virtual address
[ 1254.789308] pgd = a920
[ 1254.789320] [] *pgd=39120831, *pte=, *ppte=
[ 1254.789331] Internal error: Oops: 817
If 68328serial.c is removed is there any point keeping the
architecture support for 68328 platforms?
The 68328serial.c provides pretty much the only type of console
that can be used on these devices. They are largely useless
without this.
Regards
Greg
On 19/12/15 00:27, Geert Uytterhoeven
On Mon, 2016-01-04 at 03:16 +, Al Viro wrote:
> On Mon, Jan 04, 2016 at 01:52:21PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next merge of the integrity tree got a conflict in:
> >
> > security/integrity/ima/ima_fs.c
> >
> > between commit:
> >
> > 3bc8f29b149e
On Thu, 2015-12-24 at 18:17 +0800, Bamvor Zhang Jian wrote:
> On 12/18/2015 07:44 AM, Michael Ellerman wrote:
> > On Thu, 2015-12-17 at 17:57 +0800, Bamvor Jian Zhang wrote:
> > > There is a discussion about improving the usability of kselftest by
> > > creating test-specific kconfig in recent
This introduces new compression APIs. Major change is that APIs are
stateless. Instead of previous implementation, tfm objects doesn't
embedded any context so we can de/compress concurrently with one tfm
object. Instead, thsi de/compression context is coupled with the request.
This architecture
For proof of concept, SCOMPRESS alg type is implemented for lzo.
Signed-off-by: Joonsoo Kim
---
crypto/Kconfig | 1 +
crypto/lzo.c | 94 ++
2 files changed, 82 insertions(+), 13 deletions(-)
diff --git a/crypto/Kconfig b/crypto/Kconfig
It is unused now, so remove it.
Signed-off-by: Joonsoo Kim
---
crypto/Kconfig | 19 --
crypto/Makefile| 2 -
crypto/pcompress.c | 115 ---
crypto/testmgr.c | 223 --
crypto/testmgr.h
From: Weigang Li
Now, asynchronous compression APIs are supported. There is no asynchronous
compression driver now but this APIs can be used as front-end to
synchronous compression algorithm. In this case, scatterlist would be
linearlized so it would cause some overhead.
Signed-off-by: Weigang
Signed-off-by: Joonsoo Kim
---
crypto/testmgr.c | 2 ++
include/crypto/compress.h | 8
include/linux/crypto.h| 6 ++
3 files changed, 16 insertions(+)
diff --git a/crypto/testmgr.c b/crypto/testmgr.c
index bd0c639..acd7428 100644
--- a/crypto/testmgr.c
+++
Signed-off-by: Joonsoo Kim
---
crypto/Kconfig | 1 +
crypto/testmgr.c | 173 ---
2 files changed, 165 insertions(+), 9 deletions(-)
diff --git a/crypto/Kconfig b/crypto/Kconfig
index b4b485c..f487502 100644
--- a/crypto/Kconfig
+++
Signed-off-by: Joonsoo Kim
---
crypto/lzo.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/crypto/lzo.c b/crypto/lzo.c
index 47998e9..90afbf9 100644
--- a/crypto/lzo.c
+++ b/crypto/lzo.c
@@ -142,7 +142,8 @@ static struct scomp_alg scomp = {
.base
Happy New Year!
This patchset is to introduce new compression APIs. It supports async/sync
compression although there is no async compression driver yet. But, async
APIs can be used as front-end to sync compression algorithm. Major change
is that now APIs are stateless. Instead of previous
This patch adds a compatibility path to support old applications
that do acept(2) before setkey.
Signed-off-by: Herbert Xu
diff --git a/crypto/algif_skcipher.c b/crypto/algif_skcipher.c
index f4431bc..110bab4 100644
--- a/crypto/algif_skcipher.c
+++ b/crypto/algif_skcipher.c
@@ -753,6 +753,99
On Sun, Jan 03, 2016 at 10:42:28AM +0100, Milan Broz wrote:
>
> yes, basically it prepares socket()/bind()/accept() and then it calls setkey
> once.
> (I'll try to fix in next releases to call setkey first though.)
OK please try these two patches (warning, totally untested).
---8<---
This
Atmel AIC disables RTT(Real Time Timer) interrupt on initialization.
Alarm interrupt(ALMIEN) and RTT increment interrupt(RTTINCIEN) are used.
However, the controller doesn't need to do it.
* RTT driver disables interrupts on _probe().
ALMIEN and RTTINCIEN bits in RTT_MR are cleared to disable
This patch-set provides unified Atmel AIC (Advanced Interrupt Controller)
driver. Currently, there are two AIC drivers, AIC and AIC5.
Each driver consists of chip specific part (irq-atmel-aic.o or
irq-atmel-aic5.o) and shared code (irq-atmel-aic-common.o).
But consolidated AIC driver is just one
Atmel AIC disables RTC interrupt on initialization. However, the controller
doesn't need to do it. There are two reasons.
* RTC driver disables interrupts on _probe()
RTC_IDR is set to 0x1f which means all RTC interrupts are disabled.
(drivers/rtc/rtc-at91rm9200.c)
Number of interrupts per each chip is determined when IRQ controller
allocates IRQ chip by calling irq_alloc_domain_generic_chips().
This number is fixed by atmel-aic-common part. The value is 32.
So each AIC driver can use this value directly in IRQ chip operation.
Cc: Thomas Gleixner
Cc: Jason
AIC has one register access to enable/disable an interrupt.
AIC5 requires two register accesses - SSR and IECR/IDCR.
This patch unifies interrupt mask and unmask operations.
Mask and unmask operations are moved into aic_common_of_init().
AIC5 can have multiple IRQ chips, mask/unmask should be
set_type() operation updates IRQ flag for selected IRQ.
By using aic_update_smr(), this operation can be unified.
Common set_type() handles interrupt type as below.
1. Set register value corresponding to IRQ type.
2. If SSR is used, write hwirq into SSR for IRQ selection
3. Read value of
AIC and AIC5 have same interrupt handling process.
1. Read IVR (Interrupt Vector Register) to get a HW IRQ number.
2. Read ISR (Interrupt Status Register) to get current IRQ source number.
3. Indicate the interrupt handling is complete if no interrupt condition.
Otherwise, handle
Structure 'aic_reg_data' has EOI data, chip type data can be moved to
common part.
Cc: Thomas Gleixner
Cc: Jason Cooper
Cc: Marc Zyngier
Cc: Alexandre Belloni
Cc: Boris BREZILLON
Cc: Ludovic Desroches
Cc: Nicolas Ferre
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Milo Kim
---
AIC and AIC5 have common interrupt initialization process.
With aic_reg_data configuration, chip specific init functions can be
combined into one function, aic_common_hw_init().
Cc: Thomas Gleixner
Cc: Jason Cooper
Cc: Marc Zyngier
Cc: Alexandre Belloni
Cc: Boris BREZILLON
Cc: Ludovic
To control IDCR, IECR and ICCR, AIC5 selects the number by checking
each mask bit. AIC provides simple register access.
This patch unifies suspend/resume/pm_shutdown operation.
aic_common_shutdown() is renamed as aic_irq_shutdown() to differentiate it
from aic_pm_shutdowm().
Cc: Thomas Gleixner
Now, AIC and AIC5 have common IRQ chip initialization function.
All IRQ chips are declared in common part.
Return type is changed from irq_domain pointer to integer.
IRQ domain name is fixed as 'atmel-aic'.
Delete irq-atmel-aic-common.h because it is not used any more.
Cc: Thomas Gleixner
Cc:
aic_common_of_init() needs an argument for number of interrupts.
Argument, 'nirqs' can be ignored if device compatible string is used.
This patch provides unified way to get total number of interrupts.
Chip specific register data is assigned as well.
Use single constant total AIC IRQ number,
AIC and AIC5 use same driver file, so IRQ chip specific driver files can
be deleted.
aic_common_ext_irq_of_init() is renamed as aic_ext_irq_of_init().
Fix checkpatch warning.
Cc: Thomas Gleixner
Cc: Jason Cooper
Cc: Marc Zyngier
Cc: Alexandre Belloni
Cc: Boris BREZILLON
Cc: Ludovic Desroches
'irq-aic' is consolidated interrupt driver for Atmel SoCs.
Rename the driver file:
irq-atmel-aic-common.c -> irq-aic.c
Kconfig:
ATMEL_AIC5_IRQ is removed
Cc: Thomas Gleixner
Cc: Jason Cooper
Cc: Marc Zyngier
Cc: Alexandre Belloni
Cc: Boris BREZILLON
Cc: Ludovic Desroches
Cc: Nicolas
AIC has one register access to retrigger an interrupt.
AIC5 requires two register accesses - SSR and ISCR.
This patch unifies interrupt retrigger operation.
Cc: Thomas Gleixner
Cc: Jason Cooper
Cc: Marc Zyngier
Cc: Alexandre Belloni
Cc: Boris BREZILLON
Cc: Ludovic Desroches
Cc: Nicolas
Atmel AIC has common structure for SMR (Source Mode Register).
bit[6:5] Interrupt source type
bit[2:0] Priority level
Other bits are unused.
To update new priority value, bit[2:0] should be cleared first and then
new priority level can be written. However, aic_common_set_priority()
helper
Now, aic_common_of_init() handles all IRQ chip operations.
Remove unused code for getting irq_chip_generic data.
Cc: Thomas Gleixner
Cc: Jason Cooper
Cc: Marc Zyngier
Cc: Alexandre Belloni
Cc: Boris BREZILLON
Cc: Ludovic Desroches
Cc: Nicolas Ferre
Cc: linux-kernel@vger.kernel.org
AIC5 and AIC have common translate interrupt specifiers.
HW IRQ number, interrupt type (flag) and interrupt priority.
For interrupt priority update, those systems look different handing.
AIC5 writes SSR (Source Select Register) first and read SMR (Source Mode
Register) to update interrupt
One AIC IRQ chip can have 32 interrupt source.
To enhance code readability, magic number is replaced with named constant,
'AIC_IRQS_PER_CHIP'.
aic_hw_init() initializes vector registers up to total number of
AIC interrupts. This magic number is replaced with NR_AIC_IRQS.
Cc: Thomas Gleixner
Cc:
Structure, 'aic_reg_offset' describes for device specific register offset.
Each offset is used for IRQ chip operation. AIC and AIC5 have different
register values, but the structure can be shared.
Please note that this is not complete patch, it's a preceding step for
making unified AIC driver.
Hi Arnd,
On Thu, 2015-12-31 at 15:45 +0100, Arnd Bergmann wrote:
> On Thursday 31 December 2015 17:16:34 James Liao wrote:
> >
> > """
> > Take a example for our IOMMU(M4U) and SMI. The IOMMU which is
> > subsys_init defaultly will depend on SMI.
> > The SMI is a bridge between m4u and the
Currently the minimal up_threshold is 11, and user may want to
use a smaller minimal up_threshold for performance tuning,
so MIN_FREQUENCY_UP_THRESHOLD could be set to 1 because:
1. Current systems wouldn't be affected as they have already
a value >= 11.
2. New systems with a default kernel
On 01/03/2016 03:11 PM, Guenter Roeck wrote:
The lifetime of the watchdog device pointer is different from the lifetime
of its character device. Remove it entirely to avoid race conditions, and
to make sure that drivers don't start to use it again.
I should have mentioned: The series applies
On 1/3/2016 10:36 PM, Vinod Koul wrote:
> On Sun, Jan 03, 2016 at 07:09:23PM -0500, Sinan Kaya wrote:
>> Hi Vinod,
>>
>>>
>>
>> Can I have your ACK on your series if you are OK?
>
> Why ACK, shouldn't this be merged thru dmaengine tree? I would need ack on
> DT patches first :)
>
You are right
On Sun, Jan 03, 2016 at 07:09:23PM -0500, Sinan Kaya wrote:
> Hi Vinod,
>
> >
>
> Can I have your ACK on your series if you are OK?
Why ACK, shouldn't this be merged thru dmaengine tree? I would need ack on
DT patches first :)
--
~Vinod
--
To unsubscribe from this list: send the line
On Tue, Dec 22, 2015 at 07:35:23PM -0800, Ashutosh Dixit wrote:
> This reverts commit e958e079e254 ("dmaengine: mic_x100: add missing
> spin_unlock").
>
> The above patch is incorrect. There is nothing wrong with the original
> code. The spin_lock is acquired in the "prep" functions and released
dw_mmc driver never use this macro, so remove it from
zx_defconfig
Signed-off-by: Shawn Lin
---
arch/arm/configs/zx_defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/configs/zx_defconfig b/arch/arm/configs/zx_defconfig
index b200bb0..ab683fb 100644
---
dw_mmc driver never use this macro, so remove it from
multi_v7_defconfig
Signed-off-by: Shawn Lin
---
arch/arm/configs/multi_v7_defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index 69a22fd..c362199 100644
dw_mmc driver never use this macro, so we remove it from
arch/arm64/configs/defconfig
Signed-off-by: Shawn Lin
---
arch/arm64/configs/defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index bdd7aa3..2c56551 100644
---
On Mon, Jan 04, 2016 at 01:52:21PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the integrity tree got a conflict in:
>
> security/integrity/ima/ima_fs.c
>
> between commit:
>
> 3bc8f29b149e ("new helper: memdup_user_nul()")
>
> from the vfs tree and commit:
>
Currently the Linux kernel does not provide any standard integration of this
feature that integrates the USB subsystem with the system power regulation
provided by PMICs meaning that either vendors must add this in their kernels
or USB gadget devices based on Linux (such as mobile phones) may not
Integrate with the newly added USB charger interface to limit the current
we draw from the USB input based on the input device configuration
identified by the USB stack, allowing us to charge more quickly from high
current inputs without drawing more current than specified from others.
For supporting the usb charger, it adds the usb_charger_init() and
usb_charger_exit() functions for usb charger initialization and exit.
It will report to the usb charger when the gadget state is changed,
then the usb charger can do the power things.
Introduce a callback 'get_charger_type' which
This patch introduces the usb charger driver based on usb gadget that
makes an enhancement to a power driver. It works well in practice but
that requires a system with suitable hardware.
The basic conception of the usb charger is that, when one usb charger
is added or removed by reporting from
When the usb gadget supporting for usb charger is ready, the usb charger
should get the type by the 'get_charger_type' callback which is implemented
by the usb gadget operations, and get the usb charger pointer from struct
'usb_gadget'.
Signed-off-by: Baolin Wang
---
On Thu, 2015-12-31 at 22:19 +0800, Daniel Kurtz wrote:
> On Wed, Dec 30, 2015 at 8:36 PM, Henry Chen wrote:
> >
> > The STAUPD_TRIG will be enable when WDT_INT enable on probe function, if
> > doesn't enable STAUPD_PRD together, interrupt will be triggered because
> > STAUPD timeout. To avoid
[Just cc'ing the security tree maintainer, since this will soon be in
his tree and is related to a conflict between that tree and the vfs
tree.]
On Mon, 4 Jan 2016 13:52:21 +1100 Stephen Rothwell
wrote:
>
> Hi all,
>
> Today's linux-next merge of the integrity tree got a conflict in:
>
>
This patch implement hw_reset function for DesignWare
MMC controller. By adding this feature, mmc blk can
do some basic recovery.
>From Synopsys DesignWare Cores Mobile Storage Host Databook
(Section 7.4.4), we get the details:
1. Program CMD12 to end any transfer in process.
2. Wait for DTO,
Hi all,
Today's linux-next merge of the integrity tree got a conflict in:
security/integrity/ima/ima_fs.c
between commit:
3bc8f29b149e ("new helper: memdup_user_nul()")
from the vfs tree and commit:
6427e6c71c8b ("ima: ima_write_policy() limit locking")
from the integrity tree.
I
On 01/03/2016 08:44 PM, Stephen Rothwell wrote:
> Hi all,
>
> On Thu, 31 Dec 2015 13:30:22 +1100 Stephen Rothwell
> wrote:
>>
>> Hi Doug,
>>
>> Today's linux-next merge of the rdma tree got conflicts in a quite a
>> few files between (mostly, I think) commit:
>>
>> 6c7b6d2d442c ("IB: merge
Hi, Rafael
> From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> Sent: Friday, January 1, 2016 11:05 AM
> Subject: Re: [PATCH 00/42] ACPICA: 20151218 Release
>
> On Tuesday, December 29, 2015 01:52:19 PM Lv Zheng wrote:
> > The 20151218 ACPICA kernel-resident subsystem updates are linuxized
1 - 100 of 572 matches
Mail list logo
