3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Arnd Bergmann
commit 92792e48e2ae6051af30468a87994b5432da2f06 upstream.
Recent gcc versions warn about reading from a negative offset of
an on-stack array:
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Heiko Stuebner
commit a8594f20cafadb6ba58f915dea5f2c94a9333b1a upstream.
Commit 371f0f085f629 ("ARM: 8426/1: dma-mapping: add missing range check
in dma_mmap()") introduced
Hi Daniel,
On 16/12/15 17:08, Daniel Thompson wrote:
> It is possible for the secure world to reserve certain SGI IDs for itself.
> Currently we have limited visibility of which IDs are safe to use for IPIs.
>
> Modify the GIC initialization code to actively search for reserved SGI IDs
> and
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Johannes Berg
commit c2e703a55245bfff3db53b1f7cbe59f1ee8a4339 upstream.
When using call_rcu(), the called function may be delayed quite
significantly, and without a matching
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Nikolay Aleksandrov
[ Upstream commit 4c6980462f32b4f282c5d8e5f7ea8070e2937725 ]
Similar to ipv4, when destroying an mrt table the static mfc entries and
the static devices are
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Eric Dumazet
commit 5d4c9bfbabdb1d497f21afd81501e5c54b0c85d9 upstream.
tcp_send_rcvq() is used for re-injecting data into tcp receive queue.
Problems :
- No check against size is
On Wed, Dec 16, 2015 at 09:35:59AM -0700, Toshi Kani wrote:
> We do not have enough bits left to cover any potential future use-cases
> with other strings if we are going to get rid of strcmp() completely.
Look at the examples I gave. I'm talking about having an additional
identifier which can be
On 12/07/2015 03:09 AM, Marc Titinger wrote:
+#define INA2XX_CHAN(_type, _index, _address) { \
+ .type = (_type), \
+ .address = (_address), \
+ .indexed = 1, \
+ .channel = (_index), \
+ .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), \
+
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Christoph Biedl
commit 19cebbcb04c8277bb8a7905957c8af11967c4e28 upstream.
Commit 35a4a57 ("isdn: clean up debug format string usage") introduced
a safeguard to avoid accidential
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Marcin Wojtas
commit db6ba9a5371f173489df126739d0a1c2a50f347b upstream.
This commit adds missing configuration of MBUS windows access protection
in mvneta_conf_mbus_windows function
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Marcin Wojtas
commit e5bdf689d32fcf3aaf548c71e715b303ba20b5d1 upstream.
MVNETA_RXQ_HW_BUF_ALLOC bit which controls enabling hardware buffer
allocation was mistakenly set as BIT(1).
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Helmut Klein
commit 5442f0eadf2885453d5b2ed8c8592f32a3744f8e upstream.
The "reg" entry in the "poweroff" section of "kirkwood-ts219.dtsi"
addressed the wrong uart (0 = console).
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Marcin Wojtas
commit dc1aadf6f1e7609590fadf7a0252413732289b2e upstream.
A value originally defined in the driver was inappropriate. Even though
the ingress was somehow working,
On Wed, Dec 16, 2015 at 06:26:32PM +0100, Oleg Nesterov wrote:
> clear_soft_dirty_pmd() is called by clear_refs_write(CLEAR_REFS_SOFT_DIRTY),
> VM_SOFTDIRTY was already cleared before walk_page_range().
Not only that, We shouldn't [generally] change vm_flags without exclusive
mmap_sem and we have
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Borkmann
commit fbca9d2d35c6ef1b323fae75cc9545005ba25097 upstream.
During own review but also reported by Dmitry's syzkaller [1] it has been
noticed that we trigger a heap
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Konstantin Khlebnikov
commit 6adc5fd6a142c6e2c80574c1db0c7c17dedaa42e upstream.
Proxy entries could have null pointer to net-device.
Signed-off-by: Konstantin Khlebnikov
Fixes:
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Xunlei Pang
commit 8295c69925ad53ec32ca54ac9fc194ff21bc40e2 upstream.
root_domain::rto_mask allocated through alloc_cpumask_var()
contains garbage data, this may cause problems. For
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mirza Krak
commit 7cecd9ab80f43972c056dc068338f7bcc407b71c upstream.
According to SJA1000 data sheet error-warning (EI) interrupt is not
cleared by setting the controller in to
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Rainer Weikusat
[ Upstream commit 7d267278a9ece963d77eefec61630223fce08c6c ]
Rainer Weikusat writes:
An AF_UNIX datagram socket being the client in an n:1 association with
some
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Andrew Lunn
commit 4eba7bb1d72d9bde67d810d09bf62dc207b63c5c upstream.
When a multicast group is joined on a socket, a struct ip_mc_socklist
is appended to the sockets mc_list
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Aaro Koskinen
commit 3c25a860d17b7378822f35d8c9141db9507e3beb upstream.
Commit fcb26ec5b18d ("broadcom: move all PHY_ID's to header")
updated broadcom_tbl to use PHY_IDs, but
On Wed, Dec 16, 2015 at 09:21:17AM -0500, Paul Gortmaker wrote:
> Looking at the existing use case - in:
> drivers/video/fbdev/mmp/panel/tpo_tj032md01bw.c
> it would appear that the SPI driver is embedded within another driver
> that the author decided to make non-modular. Others that don't
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Sasha Levin
commit 119d6f6a3be8b424b200dcee56e74484d5445f7e upstream.
Because wakeups can (fundamentally) be late, a task might not be in
the expected state. Therefore testing
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Peter Zijlstra
commit 68985633bccb6066bf1803e316fbc6c1f5b796d6 upstream.
Vladimir reported getting RCU stall warnings and bisected it back to
commit:
743162013d40 ("sched: Remove
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Eric Dumazet
commit 1b8e6a01e19f001e9f93b39c32387961c91ed3cc upstream.
When a passive TCP is created, we eventually call tcp_md5_do_add()
with sk pointing to the child. It is not
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Li Jun
commit 251b3c8b57481bcecd3f753108e36e7389ce12ac upstream.
Since the ci->role will be set after the host role start is complete, there
will be nobody cared irq during start
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Lorenzo Pieralisi
commit de818bd4522c40ea02a81b387d2fa86f989c9623 upstream.
The function graph tracer adds instrumentation that is required to trace
both entry and exit of a
This is the start of the review cycle for the Linux 3.19.8-ckt12 stable kernel.
This version contains 128 new patches, summarized below. The new patches are
posted as replies to this message and also available in this git branch:
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Michael Hennerich
commit 03fe472ef33b7f31fbd11d300dbb3fdab9c00fd4 upstream.
i2c_master_send() returns the number of bytes transferred on success while
the ad5064 driver expects that
Hi Chao,
We need to change this patch to avoid build warnings.
On Wed, Dec 16, 2015 at 01:23:44PM +0800, Chao Yu wrote:
> Add to stat dirty regular and symlink inode for showing in debugfs.
>
> Signed-off-by: Chao Yu
> ---
> v2:
> - rename F2FS_DIRTY_DATAS to F2FS_DIRTY_DATA
> ---
>
On 12/14/2015 5:33 PM, Andy Green wrote:
> Hi... looks good, just some small general comments.
>
> On 15 December 2015 at 06:42, Joshua Henderson
> wrote:
> > From: Andrei Pistirica
> >
> > This driver supports the SDHCI host controller found on a PIC32.
> >
> > Signed-off-by: Andrei Pistirica
clear_soft_dirty_pmd() is called by clear_refs_write(CLEAR_REFS_SOFT_DIRTY),
VM_SOFTDIRTY was already cleared before walk_page_range().
Signed-off-by: Oleg Nesterov
---
fs/proc/task_mmu.c |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/fs/proc/task_mmu.c
Krzysztof,
On 09/12/15 14:36, Krzysztof Kozlowski wrote:
> W dniu 09.12.2015 o 19:14, Sylwester Nawrocki pisze:
>> > Adding Stephen and linux-clk at Cc.
>> >
>> > On 09/12/15 05:49, Krzysztof Kozlowski wrote:
>>> >> On 08.12.2015 22:46, Marek Szyprowski wrote:
> This patch adds clocks,
On Wed, 09 Dec 2015 12:03:05 +1100
Michael Ellerman wrote:
> > > Should I take this via powerpc or do you want it to go in via tracing?
> >
> > You can take it. And you can replace the PT_R1 if you want. I just
> > noticed that it was defined, and I try to use macro names instead of
> > hard
Using __copy_user_nocache() as inspiration create a memory copy
routine for use by kernel code with annotations to allow for
recovery from machine checks.
Notes:
1) We align the source address rather than the destination. This
means we never have to deal with a memory read that spans two
Extend the severity checking code to add a new context IN_KERN_RECOV
which is used to indicate that the machine check was triggered by code
in the kernel with a fixup entry.
Add code to check for this situation and respond by altering the return
IP to the fixup address.
Major re-work to the tail
On 12/14/15, Jeff Merkey wrote:
> The current touch_nmi_watchdog() function in /kernel/watchdog.c does
> not always catch all cases when a processor is spinning in the nmi
> handler inside either KGDB, KDB, or MDB, in particular, the case where
> a processor is being held by a debugger inside an
Copy the existing page fault fixup mechanisms to create a new table
to be used when fixing machine checks. Note:
1) At this time we only provide a macro to annotate assembly code
2) We assume all fixups will in code builtin to the kernel.
3) Only for x86_64
4) New code under
This series is initially targeted at the folks doing filesystems
on top of NVDIMMs. They really want to be able to return -EIO
when there is a h/w error (just like spinning rust, and SSD does).
I plan to use the same infrastructure in parts 1&2 to write a
machine check aware "copy_from_user()"
On Wed, Dec 16, 2015 at 04:58:20PM +, Catalin Marinas wrote:
> On Wed, Dec 16, 2015 at 04:54:34PM +0100, Arnd Bergmann wrote:
> > On Wednesday 16 December 2015 00:42:35 Yury Norov wrote:
> > >
> > > #ifdef CONFIG_COMPAT
> > > -#define COMPAT_ELF_HWCAP (compat_elf_hwcap)
> > > -#define
On Tue, Dec 15, 2015 at 02:43:47PM +0100, Nicolas Ferre wrote:
> Le 02/12/2015 23:03, Alexandre Belloni a écrit :
> > From: Josh Wu
> >
> > The QiaoDian Xianshi QD43003C0-40 is a 4"3 TFT LCD panel.
> >
> > Timings from the OTA5180A document, ver 0.9, section
> > 10.1.1:
> >
On Wed, Dec 16, 2015 at 9:01 AM, Hannes Reinecke wrote:
> On Wednesday, December 16, 2015 08:52:10 AM Alexander Duyck wrote:
>> On Wed, Dec 16, 2015 at 2:49 AM, Hannes Reinecke wrote:
>> > + if (header[0] == 0xff) {
>> > + /* Invalid data from VPD read */
>>
After spotting some problems with the SysRq-L on Inforce IFC6410 I ran
some tests (see patch 2) and concluded that certain SGI IDs cannot be
used by Linux on these platforms because they have been reserved for use
by the secure world.
This patchset includes both a patch to resolve the problem on
SysRq-L does not generate a backtrace from all CPUs when I test it
on my Inforce IFC6410 platform (Snapdragon 600). The stack dump code,
triggered by IPI_CPU_BACKTRACE, never runs on the other CPUs.
Eventually we hit the 10 second timeout and a subset of the expected
stack dumps on are shown on
It is possible for the secure world to reserve certain SGI IDs for itself.
Currently we have limited visibility of which IDs are safe to use for IPIs.
Modify the GIC initialization code to actively search for reserved SGI IDs
and report if any are found. Warn even more loudly if the reserved SGIs
On Wed, 2015-12-16 at 10:03 -0800, Haiyang Zhang wrote:
> To avoid performance overhead when using skb_flow_dissect_flow_keys(),
> we switch to the simple parsers to get the IP and port numbers.
>
> Performance comparison: throughput (Gbps):
> Number of connections, before patch, after patch
> 1
Hi Geert,
On Wednesday 16 December 2015 11:31:12 Geert Uytterhoeven wrote:
> Add myself as a co-maintainer for Renesas Pin Controllers.
>
> Signed-off-by: Geert Uytterhoeven
Thank you for helping me with sh-pfc.
Acked-by: Laurent Pinchart
> ---
> To be included in next sh-pfc-for-v4.5 pull
This patch rearranges the switch statement in arizona_calc_fratio so
that older codecs are the special cases, with the default case
applying to newer codecs (WM8998 and later). This is preferable
because it avoids having to patch new cases in every time a new
codec is added.
Signed-off-by:
On 12/16/2015 07:36 AM, Anton Wuerfel wrote:
> This patch moves EXPORT_SYMBOL macros directly after the definition of
> the corresponding symbol to remove checkpatch warnings.
Ok.
> Signed-off-by: Anton Würfel
> Signed-off-by: Phillip Raffeck
> CC: linux-ker...@i4.cs.fau.de
> ---
>
Hi Anton,
On 12/16/2015 07:36 AM, Anton Wuerfel wrote:
> This patch removes code which has been commented out. It serves no
> documentary purposes and decreases the readability of the remaining code.
> Furthermore the comment style causes checkpatch warnings. If this code
> should ever be needed
Hi,
As discussed here[1], these patches implement a MEMREMAP_WC flag for
memremap(), which can be used to obtain writecombine mappings. This
is then used for setting up dma_coherent_mem regions which use the
DMA_MEMORY_MAP flag.
Patch 3 makes sure that the appropriate memset function is used
Hi Peter,
you are right the kernel 4.4-rc4 has it already fixed. It seems I
will need to redo the bisecting once again, starting with
2a595721a1fa6b684c1c818f379bef834ac3d65e
git bisect start -- kernel/sched
git bisect bad v4.4-rc4
git bisect good 2b49d84b259fc18e131026e5d38e7855352f71b9
On 2015-12-16 09:52, Jason Newton wrote:
How about changing how this mechanism works from a range of the lowest
N ports and instead have it as a user specifiable set? Towards more
proper security, this allows distros/admins to put any ports they
consider important to have security feature going
"Suzuki K. Poulose" writes:
> Add ARM CoreLink CCI-550 cache coherent interconnect PMU
> driver support. The CCI-550 PMU shares all the attributes of CCI-500
> PMU, except for an additional master interface (MI-6 - 0xe).
> CCI-550 requires the same work around as for CCI-500 to
> write to the
On Wednesday, December 16, 2015 08:52:10 AM Alexander Duyck wrote:
> On Wed, Dec 16, 2015 at 2:49 AM, Hannes Reinecke wrote:
> > PCI-2.2 VPD entries have a maximum size of 32k, but might actually
> > be smaller than that. To figure out the actual size one has to read
> > the VPD area until the
Hi Anton,
On 12/16/2015 07:36 AM, Anton Wuerfel wrote:
> This patch replaces printk by the corresponding variant of pr_* in order to
> fix checkpatch warnings.
Comments below.
> Signed-off-by: Anton Würfel
> Signed-off-by: Phillip Raffeck
> CC: linux-ker...@i4.cs.fau.de
> ---
>
On Wed, Dec 16, 2015 at 04:54:34PM +0100, Arnd Bergmann wrote:
> On Wednesday 16 December 2015 00:42:35 Yury Norov wrote:
> >
> > #ifdef CONFIG_COMPAT
> > -#define COMPAT_ELF_HWCAP (compat_elf_hwcap)
> > -#define COMPAT_ELF_HWCAP2 (compat_elf_hwcap2)
> > extern unsigned int
On 12/14/15, Jeff Merkey wrote:
> The current touch_nmi_watchdog() function in /kernel/watchdog.c does
> not always catch all cases when a processor is spinning in the nmi
> handler inside either KGDB, KDB, or MDB, in particular, the case where
> a processor is being held by a debugger inside an
Hi,
changbin...@intel.com writes:
> From: "Du, Changbin"
>
> To stop an out endpoint, software should set sets the Global OUT NAK,
> but not the Global Non-periodic IN NAK. This driver bug leads the out-ep
> failed be in disabled state with below error.
>
> dwc2_hsotg_ep_stop_xfr: timeout
When the DMA_MEMORY_MAP flag is used, memory which can be accessed
directly should be returned, so use memremap(..., MEMREMAP_WC) to
provide a writecombine mapping.
Signed-off-by: Brian Starkey
Reviewed-by: Catalin Marinas
---
drivers/base/dma-coherent.c | 20
1 file
Hi Maxime
You can add my Acked-by after fixing the patch 4/9
Thanks
Patrice
On 12/11/2015 09:24 AM, Maxime Coquelin wrote:
Hi Linus, Patrice,
I resend the series for Patrice to review it.
Thanks,
Maxime
This is the third round of STM32 pinctrl series, which improves DT
bindings
Use memset_io() for DMA_MEMORY_IO mappings which are mapped as I/O
memory, and regular memset() for DMA_MEMORY_MAP mappings.
This fixes the below alignment fault on arm64 for DMA_MEMORY_IO
mappings, where memset() uses the DC ZVA instruction which is
invalid on device memory.
Unhandled fault:
Add a flag to memremap() for writecombine mappings. Mappings satisfied
by this flag will not be cached, however writes may be delayed or
combined into more efficient bursts. This is most suitable for
buffers written sequentially by the CPU for use by other DMA devices.
Signed-off-by: Brian
Felipe Balbi writes:
> Hi,
>
> David Eccher writes:
>> Fix bad unlock balance: ep0_write enter with the locks locked from
>> inode.c:1769, hence it must exit with spinlock held to avoid double
>> unlock in dev_config.
>>
>> Signed-off-by: David Eccher
>
> which commit is this fixing ? Do we
Hi Maxime
On 12/11/2015 09:25 AM, Maxime Coquelin wrote:
This patch adds pinctrl and GPIO support to STMicroelectronic's STM32
family of MCUs.
While it only supports STM32F429 for now, it has been designed to enable
support of other MCUs of the family (e.g. STM32F746).
Signed-off-by: Maxime
"Suzuki K. Poulose" writes:
> CCI-550 PMU shares most of the CCI-500 PMU attributes including the
> event format, PMU event codes. The only difference is an additional
> master interface (MI6 - 0xe). Hence we share the driver code for both,
> except for a model specific event validate method.
>
On Wed, Dec 16, 2015 at 11:19:06AM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> > Sent: Wednesday, December 16, 2015 10:49 AM
> > To: Chao Yu
> > Cc: linux-f2fs-de...@lists.sourceforge.net; linux-kernel@vger.kernel.org
>
Hi,
David Eccher writes:
> Fix bad unlock balance: ep0_write enter with the locks locked from
> inode.c:1769, hence it must exit with spinlock held to avoid double
> unlock in dev_config.
>
> Signed-off-by: David Eccher
which commit is this fixing ? Do we need this backported to stable
On Wed, Dec 16, 2015 at 2:49 AM, Hannes Reinecke wrote:
> PCI-2.2 VPD entries have a maximum size of 32k, but might actually
> be smaller than that. To figure out the actual size one has to read
> the VPD area until the 'end marker' is reached.
> Trying to read VPD data beyond that marker results
Hi,
"Du, Changbin" writes:
>> diff --git a/include/linux/usb/gadget.h b/include/linux/usb/gadget.h
>> index 3d583a1..b566a4b 100644
>> --- a/include/linux/usb/gadget.h
>> +++ b/include/linux/usb/gadget.h
>> @@ -402,6 +402,9 @@ static inline void usb_ep_free_request(struct usb_ep
>> *ep,
>>
On 12/16/2015 07:36 AM, Anton Wuerfel wrote:
> Checkpatch outputs some warnings about incorrect comment style,
> which is fixed by this patch.
>
Please fix the comments in a consistent fashion. For example ...
> Signed-off-by: Anton Würfel
> Signed-off-by: Phillip Raffeck
> CC:
On 16/12/15 16:32, Daniel Lezcano wrote:
>
> Marc,
>
> can you have a look ?
Thanks for putting me in the loop. I'll look at it.
M.
--
Jazz is not dead. It just smells funny...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hi Anton,
On 12/16/2015 07:36 AM, Anton Wuerfel wrote:
> Checkpatch complains about incorrect indentation of switch/case statements.
> This patch fixes the corresponding warnings. Additionally some indentation
> is changed to match the correct format specified in the Linux Kernel
> Coding Style.
On 12/14/2015 01:38 PM, Frederic Weisbecker wrote:
Export fetch_or() that's implemented and used internally by the
scheduler. We are going to use it for NO_HZ so make it generally
available.
I'm still really dubious about the precedent of putting fetch_or() in
the global namespace, but if no
On Wed 16-12-15 10:55:25, Abhijith Das wrote:
> > > @@ -439,14 +441,13 @@ __generic_file_splice_read(struct file *in, loff_t
> > > *ppos,
> > > error = mapping->a_ops->readpage(in, page);
> > > if (unlikely(error)) {
> > > /*
> > > -
Building with the attached random configuration file,
ERROR: "i2c_parse_fw_timings" [drivers/i2c/busses/i2c-rcar.ko] undefined!
--
Jim
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86 4.4.0-rc5 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
Hi Anton,
On 12/16/2015 07:36 AM, Anton Wuerfel wrote:
> This patch fixes whitespace errors reported by checkpatch to increase
> readability. Main focus is on missing spaces after commas in
> function headers and macros (like foo,bar edited to foo, bar).
Comments below.
> Signed-off-by: Anton
From: Maxime Ripard
Like the previous designs, the A80 has a special pin controller for the
critical pins, like the PMIC bus.
Add a driver for this controller.
Signed-off-by: Maxime Ripard
[wens: Add A80 compatible strings to bindings doc; fix pin function
names based on v1.3
From: David Decotigny
Date: Mon, 14 Dec 2015 13:03:52 -0800
> +static int ethtool_get_ksettings(struct net_device *dev, void __user
> *useraddr)
> +{
...
> + if (__ETHTOOL_LINK_MODE_MASK_NU32
> + != ksettings.parent.link_mode_masks_nwords) {
> + /* wrong link mode nbits
On Wed, 2015-12-16 at 16:49 +0100, Borislav Petkov wrote:
> On Wed, Dec 16, 2015 at 08:44:02AM -0700, Toshi Kani wrote:
> > Besides "System RAM", which is commonly searched by multiple callers,
> > we
> > only have a few other uncommon cases:
> > - crash.c searches for "GART", "ACPI Tables", and
The first argument passed to axp20x_match_device(), struct axp20x_dev *,
already contains a pointer to the device. By rearranging some code,
moving the assignment of the pointer before axp20x_match_device() is
called, we can eliminate the second parameter.
Suggested-by: Andy Shevchenko
In axp20x_match_device(), match the of_device_id table bound to the
device driver instead of pointing to axp20x_of_match directly. This
will allow us to keep axp20x_match_device() unmodified when we expand
the axp20x driver into multiple ones covering different interface
types.
The AXP223 is a new PMIC commonly paired with Allwinner A23/A33 SoCs.
It is functionally identical to AXP221; only the regulator default
voltage/status and the external host interface are different.
Signed-off-by: Chen-Yu Tsai
Acked-by: Maxime Ripard
Acked-by: Rob Herring
Acked-by: Lee Jones
Hi everyone,
This is v6 of the AXP223 PMIC series. v6 fixes the address of the AXP223
in the DT. Hope this series makes it into 4.5, and we can then support
even more AXP PMICs in 4.6+.
Lee, can you take the first 7 patches. Once they're in, Maxime can take
the DTS patches.
Changes since v5:
The axp20x driver assumes the device is i2c based. This is not the
case with later chips, which use a proprietary 2 wire serial bus
by Allwinner called "Reduced Serial Bus".
This patch follows the example of mfd/wm831x and splits it into
an interface independent core, and an i2c specific glue
This fixes some leftover code style issues in the axp20x core.
Signed-off-by: Chen-Yu Tsai
---
drivers/mfd/axp20x.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c
index 631ad64ddf69..54a00168da26 100644
---
The AXP223 is a new PMIC commonly paired with Allwinner A23/A33 SoCs.
It is functionally identical to AXP221; only the regulator default
voltage/status and the external host interface are different.
Signed-off-by: Chen-Yu Tsai
---
drivers/mfd/Kconfig| 11 +++
drivers/mfd/Makefile
The AXP223 is a new PMIC commonly paired with Allwinner A23/A33 SoCs.
It is functionally identical to AXP221; only the regulator default
voltage/status and the external host interface are different.
Signed-off-by: Chen-Yu Tsai
Reviewed-by: Mark Brown
---
drivers/regulator/axp20x-regulator.c |
This board has a X-Powers AXP223 PMIC connected via RSB. Its regulators
provide power to various parts of the SoC and the board.
Also update the regulator supply phandles.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a33-sinlinx-sina33.dts | 76 +-
1 file
A23/A33 Q8 tablets have an X-Powers AXP223 PMIC connected via RSB. Its
regulators provide power to various parts of the SoC and the board.
Also add lcd regulator supply for simplefb and update the existing
vmmc-supply for mmc0.
Signed-off-by: Chen-Yu Tsai
---
Marc,
can you have a look ?
Thanks
-- Daniel
On 12/02/2015 06:43 AM, fu@linaro.org wrote:
From: Fu Wei
This patchset:
(1)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c
Parse all kinds of timer in GTDT table of ACPI:arch timer,
memory-mapped timer and SBSA Generic
On Mon, Dec 14, 2015 at 5:19 PM, Andrew F. Davis wrote:
> On 12/14/2015 04:36 PM, Rob Herring wrote:
>>
>> On Mon, Dec 14, 2015 at 10:41 AM, Andrew F. Davis wrote:
>>>
>>> On 12/11/2015 03:48 PM, Linus Walleij wrote:
On Fri, Dec 11, 2015 at 8:46 PM, Andrew F. Davis wrote:
[...]
To avoid performance overhead when using skb_flow_dissect_flow_keys(),
we switch to the simple parsers to get the IP and port numbers.
Performance comparison: throughput (Gbps):
Number of connections, before patch, after patch
1 8.5610.18
4
On Mon, Nov 02, 2015 at 12:14:21PM +0100, Neil Armstrong wrote:
> Adds support for using a OMAP dual-mode timer with PWM capability
> as a Linux PWM device. The driver controls the timer by using the
> dmtimer API.
>
> Add a platform_data structure for each pwm-omap-dmtimer nodes containing
> the
On Wed, Dec 16, 2015 at 04:48:52AM -0800, Stephane Eranian wrote:
> Andi,
>
> On Tue, Dec 15, 2015 at 4:54 PM, Andi Kleen wrote:
> >
> > From: Andi Kleen
> >
> > Add a way to show different sysfs events attributes depending on
> > HyperThreading is on or off. This is difficult to determine
> >
On Wednesday 16 December 2015 00:42:26 Yury Norov wrote:
> This is still RFC because we have no glibc yet, that correspnds new ABI
> introduced here. And so we cannot run tests. LP64 and AARCH32 tests show
> no regression though.
>
> v3: https://lkml.org/lkml/2014/9/3/704
> v4:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/15/2015 07:52 PM, Ani Sinha wrote:
> Rik, should I send a separate email with the patch or you are OK
> with what I sent in the email? Are you queueing up my patch for
> applying upstream?
I don't have a git tree for people to pull from, and
On 12/16/2015 07:43 AM, One Thousand Gnomes wrote:
> otherwise I'd really suggest someone just deletes it instead.
Yes, please.
Or at least demote it to staging where it can languish until deleted.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
This is to re-notify you of the $8,564 USD that was deposited here in
the Western Union office in your name.We have successfully complete
your fund transfer to you, You should contact Transaction Manager
Monica Winks to collect your money transfer control number (M.T.C.N).
Contact Email:
Hello Richard,
Public reply this time. :-)
On Wednesday, December 16, 2015 10:42:32 AM Richard Guy Briggs wrote:
> Nothing prevents a new auditd starting up and replacing a valid
> audit_pid when an old auditd is still running, effectively starving out
> the old auditd since audit_pid no longer
501 - 600 of 1744 matches
Mail list logo
