MT2712 is a SoC based on 64bit ARMv8 architecture.
MT2712 share many HW IP with MT8173. This patchset was tested on MT2712
evaluation board, and boot to shell ok.
This series contains document bindings, device tree including interrupt
and uart.
Changes compared to v2:
- remove alias from serial1
This adds dt-binding documentation for Mediatek MT2712.
Only include very basic items: cpu, gic and uart.
Signed-off-by: YT Shen
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/arm/mediatek.txt| 4
.../devicetree/bindings/interrupt-controller/mediatek,sysirq
This adds basic chip support for Mediatek 2712
Signed-off-by: YT Shen
---
arch/arm64/boot/dts/mediatek/Makefile | 1 +
arch/arm64/boot/dts/mediatek/mt2712-evb.dts | 32 ++
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 166
3 files changed, 199 insertions
A Gentoo user reported a UBSAN signed integer overflow in atomic_add_return.
/**
* atomic_add_return - add integer and return
* @i: integer value to add
* @v: pointer of type atomic_t
*
* Atomically adds @i to @v and returns @i + @v
*/
static __always_inline int atomic_add_return(int i, atom
On Fri, Jun 16, 2017 at 08:28:31AM +1000, NeilBrown wrote:
> It wouldn't be too hard to create that scenario. It might be harder to
> find a way to expose the corruption.
Yes. Well, in any case, I assume this Al's to take. ACK to the patch,
and it should go to stable as well.
--b.
On Fri, Jun 16, 2017 at 04:19:08PM +0300, Kirill A. Shutemov wrote:
> On Fri, Jun 16, 2017 at 12:02:50PM +0900, Minchan Kim wrote:
> > Hello,
> >
> > On Thu, Jun 15, 2017 at 05:52:24PM +0300, Kirill A. Shutemov wrote:
> > > This patch uses modifed pmdp_invalidate(), that return previous value of
From: Logan Gunthorpe
> Hi,
>
> This patchset implements Non-Transparent Bridge (NTB) support for the
> Microsemi Switchtec series of switches. We're looking for some
> review from the community at this point but hope to get it upstreamed
> for v4.14.
>
> Switchtec NTB support is configured over
Update the PM code to suspend/resume the fbdev_cma console.
Signed-off-by: Liviu Dudau
---
drivers/gpu/drm/arm/hdlcd_drv.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/arm/hdlcd_drv.c b/drivers/gpu/drm/arm/hdlcd_drv.c
index d3da87fbd85a..89cd408
On Mon, 2017-06-12 at 11:13 +0200, Matthias Brugger wrote:
>
> On 01/06/17 08:08, Erin Lo wrote:
> > From: YT Shen
> >
> > This patch adds the device nodes for the DISP function blocks for MT2701
> >
> > Signed-off-by: YT Shen
> > Signed-off-by: Erin Lo
> > ---
> > arch/arm/boot/dts/mt2701.
On Wed, 2017-06-14 at 09:19 +0800, CK Hu wrote:
> On Mon, 2017-06-12 at 15:15 +0800, YT Shen wrote:
> > Previous patch (c5f228ef6c drm/mediatek: add *driver_data for different
> > hardware settings) calls devm_kfree() and then devm_kzalloc() to
> > reallocate color module data structure. But this
This patch-set handles the SPDIFRX on STM32 platforms.
The SPDIFRX peripheral, is designed to receive an S/PDIF flow compliant with
IEC-60958 and IEC-61937 standards.
SPDIFRX uses two DMA channels:
- one DMA channel for S/PDIF data stream.
- one DMA channel for control flow (channel status and us
Add SPDIFRX support to STM32.
Signed-off-by: olivier moysan
---
sound/soc/stm/Kconfig | 10 +
sound/soc/stm/Makefile| 4 +
sound/soc/stm/stm32_spdifrx.c | 998 ++
sound/soc/stm/stm32_spdifrx.h | 224 ++
4 files changed, 1236 inse
This adds documentation of device tree bindings for the
STM32 SPDIFRX interface.
Signed-off-by: olivier moysan
---
.../devicetree/bindings/sound/st,stm32-spdifrx.txt | 56 ++
1 file changed, 56 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/st,stm32
Previous patch (c5f228ef6c drm/mediatek: add *driver_data for different
hardware settings) calls devm_kfree() and then devm_kzalloc() to
reallocate color module data structure. But this reallocation cannnot
guarantee the new address is unchanged, but the caller will use the
old address, which is w
> Am 19.05.2017 um 01:01 schrieb Mauro Carvalho Chehab
> :
>
> Em Thu, 18 May 2017 11:26:08 -0600
> Jonathan Corbet escreveu:
>
>> On Tue, 16 May 2017 09:15:52 -0300
>> Mauro Carvalho Chehab wrote:
>>
>>> This patch series convert the remaining DocBooks to ReST.
>>
>> Gotta love this:
>>
>
This tool allow to set directly the time and date to a RTC device.
Unlike other tools isn't doens't use "strut timeval" or "time_t"
so it is safe for 32bits platforms when testing for y2038/2106 bug.
Signed-off-by: Benjamin Gaignard
---
tools/testing/selftests/timers/Makefile | 2 +-
On 32bits platforms "struct timeval" or "time_t" are using u32 to code the
date, this cause tools like "date" or "hwclock" failed even before setting
the RTC device if the date is superior to year 2038 (or 2106).
To avoid this problem I add two RTC tests files which directly use RTC ioctl
to set a
Make driver use u64 variables and functions to be sure that
it will support dates after year 2038.
Signed-off-by: Benjamin Gaignard
---
drivers/rtc/rtc-st-lpc.c | 19 ---
1 file changed, 8 insertions(+), 11 deletions(-)
diff --git a/drivers/rtc/rtc-st-lpc.c b/drivers/rtc/rtc-st-
The goal of this test is to check if a RTC device correctly support
dates after years 2038 or 2106.
It set a date (1-1-2200) on RTC and read it back to be sure that the
driver is working well.
The same thing is done on alarm.
Signed-off-by: Benjamin Gaignard
---
tools/testing/selftests/timers/Ma
On 16.06.2017 12:09, Mark Rutland wrote:
On Fri, Jun 16, 2017 at 01:10:10AM +0300, Alexey Budankov wrote:
On 15.06.2017 22:56, Mark Rutland wrote:
On Thu, Jun 15, 2017 at 08:41:42PM +0300, Alexey Budankov wrote:
This series of patches continues v2 and addresses captured comments.
Specifical
On 06/14/2017 03:18 PM, Krzysztof Kozlowski wrote:
When setting the pin function for external interrupts, the driver used
wrong IO memory address base. The pin function register is always under
pctl_base, not the eint_base.
By updating wrong register, the external interrupts for chosen GPIO
wou
On 16/06/17 07:53 AM, Allen Hubbe wrote:
> See what is staged in https://github.com/jonmason/ntb.git ntb-next, with the
> addition of multi-peer support by Serge. It would be good at this stage to
> understand whether the api changes there would also support the Switchtec
> driver, and what i
From: Joerg Roedel
When booting, make sure the IOMMUs are disabled. They could
be previously enabled if we boot into a kexec or kdump
kernel. So make sure they are off.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu_init.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers
From: Joerg Roedel
This check needs to happens later now, when all previously
enabled IOMMUs have been disabled.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu_init.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/iommu/amd_iommu_init.c b/drivers/iommu/amd_iommu_init.c
From: Joerg Roedel
The function will also be used to free iommu resources when
amd_iommu=off was specified on the kernel command line. So
rename the function to reflect that.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu_init.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-
From: Joerg Roedel
This will be used when during initialization we detect that
the iommu should be disabled.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu_init.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/amd_iommu_init.c b/drivers/iommu/
From: Joerg Roedel
After we made sure that all IOMMUs have been disabled we
need to make sure that all resources we allocated are
released again.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu_init.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/iommu/amd_iommu_in
Hi,
here is a patch-set refactoring the AMD IOMMU init code a
bit to make sure the IOMMUs get disabled at boot, even when
amd_iommu=off is specified on the kernel command line.
The patch-set is tested with various combinations of kernel
command-line parameters and with kexec. It applies to the
x8
From: Joerg Roedel
Avoid any tries to double-free these pointers.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu_init.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/iommu/amd_iommu_init.c b/drivers/iommu/amd_iommu_init.c
index a31f375..d04898c 100644
--- a/drivers/
From: Joerg Roedel
Check if we are in an error state already before calling
into state_next().
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu_init.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/amd_iommu_init.c b/drivers/iommu/amd_iommu_init.c
On Fri 16-06-17 21:22:20, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > OK, could you play with the patch/idea suggested in
> > http://lkml.kernel.org/r/20170615122031.gl1...@dhcp22.suse.cz?
>
> I think we don't need to worry about mmap_sem dependency inside __mmput().
> Since the OOM killer check
From: Xiaowei Song
Add PCIe node for hi3660
Cc: Guodong Xu
Signed-off-by: Xiaowei Song
Acked-by: Arnd Bergmann
Changes in v5:
* fix interrupt-map, to conform to gic's #address-cells = <0>
* remove redundant status = "ok"
---
arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 36 +
Hi Linus,
Please pull fbdev fixes for v4.12-rc6.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
The following changes since commit 32c1431eea4881a6b17bd7c639315010aeefa452:
Linux 4.12-rc5 (2017-06-11 16:48:20 -0700)
are available in the git repo
On 16/06/17 12:27 AM, Greg Kroah-Hartman wrote:
> Also looks like block devices have the same issue in this file, care to
> fix that up too while you are there? :)
Sure, I'll take a look at that and send another patch later.
Logan
Hello,
The Marvell Armada 7K/8K SoCs are composed of two parts: the AP (which
contains the CPU cores) and the CP (which contains most
peripherals). The 7K SoCs have one CP, while the 8K SoCs have two CPs,
doubling the number of available peripherals.
In terms of interrupt handling, all devices in
This commit modifies the Marvell EBU Armada 7K and 8K Device Tree files
to describe the ICU and GICP units, and use ICU interrupts for all
devices in the CP110 blocks.
Signed-off-by: Thomas Petazzoni
---
arch/arm64/boot/dts/marvell/armada-ap806.dtsi | 7 +++
.../boot/dts/marvell/armada-cp1
This commit adds the Device Tree binding documentation for the Marvell
ICU interrupt controller, which collects wired interrupts from the
devices located into the CP110 hardware block of Marvell Armada 7K/8K,
and converts them into SPI interrupts in the GIC located in the AP
hardware block, using t
This commit adds the Device Tree binding documentation for the Marvell
GICP, an extension to the GIC that allows to trigger GIC SPI interrupts
using memory transactions. It is used by the ICU unit in the Marvell
CP110 block to turn wired interrupts inside the CP into SPI interrupts
at the GIC level
This commit enables the newly introduced Marvell GICP and ICUs driver
for the 64-bit Marvell EBU platforms.
Signed-off-by: Thomas Petazzoni
---
arch/arm64/Kconfig.platforms | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
index 4af
This commit adds a simple driver for the Marvell GICP, a hardware unit
that converts memory writes into GIC SPI interrupts. The driver provides
a number of functions to the ICU driver to allocate GICP interrupts, and
get the physical addresses that the ICUs should write to to set/clear
interrupts.
The Marvell ICU unit is found in the CP110 block of the Marvell Armada
7K and 8K SoCs. It collects the wired interrupts of the devices located
in the CP110 and turns them into SPI interrupts in the GIC located in
the AP806 side of the SoC, by using a memory transaction.
Until now, the ICU was conf
When UBIFS prepares data structures which will be written to the MTD it
ensues that their lengths are multiple of 8. Since it uses kmalloc() the
padded bytes are left uninitialized and we leak a few bytes of kernel
memory to the MTD.
To make sure that all bytes are initialized, let's switch to kzal
On 16.06.2017 17:08, Alexey Budankov wrote:
On 16.06.2017 12:09, Mark Rutland wrote:
On Fri, Jun 16, 2017 at 01:10:10AM +0300, Alexey Budankov wrote:
On 15.06.2017 22:56, Mark Rutland wrote:
On Thu, Jun 15, 2017 at 08:41:42PM +0300, Alexey Budankov wrote:
This series of patches continues v2 a
CNN55XX driver is accepted and needs firmware to functional.
This patchset adds CNN55XX firmware v07 supports
symmetric crypto operations.
Srikanth Jampala (1):
cavium: Add firmware for CNN55XX crypto driver.
WHENCE| 9 +
cnn55xx_se.fw | Bin 0 -> 27698 bytes
2 files changed,
This patchset adds the firmware for CNN55XX cryto driver,
supports Symmetric crypto operations.
The version of the firmware is v07.
Signed-off-by: Srikanth Jampala
---
WHENCE| 9 +
cnn55xx_se.fw | Bin 0 -> 27698 bytes
2 files changed, 9 insertions(+)
create mode 100644 cnn55
2017-06-16 21:37 GMT+08:00 Radim Krčmář :
> 2017-06-14 19:26-0700, Wanpeng Li:
>> From: Wanpeng Li
>>
>> Add an async_page_fault field to vcpu->arch.exception to identify an async
>> page fault, and constructs the expected vm-exit information fields. Force
>> a nested VM exit from nested_vmx_check
Michal Hocko wrote:
> On Fri 16-06-17 19:27:19, Tetsuo Handa wrote:
> > Michal Hocko wrote:
> > > On Fri 16-06-17 09:54:34, Tetsuo Handa wrote:
> > > [...]
> > > > And the patch you proposed is broken.
> > >
> > > Thanks for your testing!
> > >
> > > > --
> > > > [ 161.846202] Out of me
Hello Minchan,
On Fri, Jun 16, 2017 at 10:52:09PM +0900, Minchan Kim wrote:
> > > > @@ -1995,8 +1984,6 @@ static void __split_huge_pmd_locked(struct
> > > > vm_area_struct *vma, pmd_t *pmd,
> > > > if (soft_dirty)
> > > > entry = pte_mksoft_
On Thu, 15 Jun 2017, Al Viro wrote:
On Wed, Jun 14, 2017 at 08:11:33AM +0100, Al Viro wrote:
FWIW, it seems to work here. Said that, *BSD fsck_ffs is not worth much -
play a bit with redundancy in UFS superblock (starting with fragment
and block sizes, their ratio, logarithms, bitmasks, etc.) a
On 06/15/2017 11:02 PM, NeilBrown wrote:
> Hi Jens,
> one of these is a resend of a patch I sent a while back.
> The other is new - loop closes files differently from close()
> and in a way that can confuse NFS.
Are you wanting to get these into 4.12, or defer to 4.13?
--
Jens Axboe
On Thu, Jun 15, 2017 at 12:55:21PM -0500, Kim Phillips wrote:
> cs_etm_evsel is guaranteed to be set at this point in the function.
>
> Signed-off-by: Kim Phillips
> ---
> tools/perf/arch/arm/util/cs-etm.c | 25 -
> 1 file changed, 12 insertions(+), 13 deletions(-)
>
> d
On 16/06/17 15:45, YT Shen wrote:
This adds basic chip support for Mediatek 2712
Signed-off-by: YT Shen
---
arch/arm64/boot/dts/mediatek/Makefile | 1 +
arch/arm64/boot/dts/mediatek/mt2712-evb.dts | 32 ++
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 166
On 2017-06-15 00:45:26 [+0200], Jason A. Donenfeld wrote:
> Odd versions of gcc for the sh4 architecture will actually warn about
> flags being used while uninitialized, so we set them to zero. Non crazy
> gccs will optimize that out again, so it doesn't make a difference.
that is minor
> Next, o
On 2017-06-16 14:12:42 [+0200], Jason A. Donenfeld wrote:
> I actually figured that out myself after sending the initial email, so
> then I wrote a follow-up patch which I attached to this thread. You
> should have received it. Can you take a look?
replied to the patch.
Sebastian
On Thu, Jun 15, 2017 at 6:10 PM, Ding Tianhong wrote:
>
>
> On 2017/6/13 5:28, Alexander Duyck wrote:
>> On Mon, Jun 12, 2017 at 4:05 AM, Ding Tianhong
>> wrote:
> ...
>>> /**
>>> + * pcie_clear_relaxed_ordering - clear PCI Express relaxed ordering bit
>>> + * @dev: PCI device to query
>>> + *
On Fri 16-06-17 23:26:20, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > On Fri 16-06-17 19:27:19, Tetsuo Handa wrote:
> > > Michal Hocko wrote:
> > > > On Fri 16-06-17 09:54:34, Tetsuo Handa wrote:
> > > > [...]
> > > > > And the patch you proposed is broken.
> > > >
> > > > Thanks for your testin
Hi Shaohua,
[auto build test ERROR on block/for-next]
[also build test ERROR on v4.12-rc5 next-20170616]
[cannot apply to driver-core/driver-core-testing]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On 6/16/2017 8:03 AM, Tom Lendacky wrote:
On 6/16/2017 5:58 AM, Thomas Gleixner wrote:
On Wed, 14 Jun 2017, Tom Lendacky wrote:
A recent change added a new system_state value, SYSTEM_SCHEDULING, which
exposed a warning issued by early_ioreamp() when the system_state was
not
SYSTEM_BOOTING. Sin
Archit Taneja writes:
> On 06/16/2017 02:11 AM, Eric Anholt wrote:
>> If the panel-bridge is being set up after the drm_mode_config_reset(),
>> then the connector's state would never get initialized, and we'd
>> dereference the NULL in the hotplug path. We also need to register
>> the connector,
On 6/16/2017 2:35 AM, Andrew Morton wrote:
diff --git a/mm/list_lru.c b/mm/list_lru.c
index 5d8dffd..1af0709 100644
--- a/mm/list_lru.c
+++ b/mm/list_lru.c
@@ -249,6 +249,8 @@ restart:
default:
BUG();
}
+ if (cond_resched_loc
On 06/15/2017 05:54 AM, Peter Dawson wrote:
On Thu, 15 Jun 2017 10:30:29 +0800
Haishuang Yan wrote:
Same as ip_gre, geneve and vxlan, use key->tos as tos value.
CC: Peter Dawson
Fixes: 0e9a709560db ("ip6_tunnel, ip6_gre: fix setting of DSCP on
encapsulated packets”)
Suggested-by: Daniel Bork
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Borislav Petkov
> Sent: Wednesday, June 14, 2017 10:21 AM
> To: Ghannam, Yazen
> Cc: linux-e...@vger.kernel.org; Tony Luck ;
> x...@kernel.org; linux-kernel@vger.kern
Hi Orson,
Thanks for the patch.
On 16 June 2017 at 14:58, Orson Zhai wrote:
> Sysctl test will fail in some items if the value of /proc/sys/kernel
> /sysctrl_writes_strict is 0 as the default value in kernel older than v4.5.
>
> Make this test more robust and compatible with older kernels by che
(adding Andrew)
On Fri, Jun 16, 2017 at 04:57:10PM +1000, Nicholas Piggin wrote:
> This is the latest series to make the hardlockup watchdog more
> easily replaceable by arch code. The last patch provides some
> justification for why we want to do this (existing sparc watchdog
> is another that co
Support for TRACE_DEFINE_SIZEOF() has been added to the kernel.
Lets document the use of the new macro and correct a couple of
minor spelling mistakes.
Signed-off-by: Jeremy Linton
---
samples/trace_events/trace-events-sample.h | 38 +++---
1 file changed, 24 insertions(+
On Fri, Jun 16, 2017 at 07:22:05AM +, Bridgman, John wrote:
> Hi Jerome,
>
> I'm just getting back to this; sorry for the late responses.
>
> Your description of HMM talks about blocking CPU accesses when a page
> has been migrated to device memory, and you treat that as a "given" in
> the
Hi Guodong,
On 2017/6/16 15:13, Guodong Xu wrote:
> From: Xiaowei Song
>
> Add PCIe node for hi3660
>
> Cc: Guodong Xu
> Signed-off-by: Xiaowei Song
> Acked-by: Arnd Bergmann
>
> Changes in v5:
> * fix interrupt-map, to conform to gic's #address-cells = <0>
> * remove redundant status = "
Hi Andrea,
On Fri, Jun 16, 2017 at 04:27:20PM +0200, Andrea Arcangeli wrote:
> Hello Minchan,
>
> On Fri, Jun 16, 2017 at 10:52:09PM +0900, Minchan Kim wrote:
> > > > > @@ -1995,8 +1984,6 @@ static void __split_huge_pmd_locked(struct
> > > > > vm_area_struct *vma, pmd_t *pmd,
> > > > >
Christoph Hellwig wrote:
> It might be good to just introduce the internal flags field first,
Internal flags field? Did you mean Al's suggested sb_readonly() wrapper?
David
[CC Andrew]
On Fri 16-06-17 21:26:53, Alice Ferrazzi wrote:
> Hello,
>
> a user reported a UBSAN signed integer overflow in memcontrol.c
> Shall we change something in mem_cgroup_event_ratelimit()?
It took me quite some staring but it seems the report is correct.
---
>From 5683a96c2bfe694b66c542
On 06/16/17 06:29, Alice Ferrazzi wrote:
> A Gentoo user reported a USBAN signed integer overflow in scsicam.c
> Shall we change something?
Hello Alice,
Some of the code in drivers/scsi/scsicam.c duplicates code in
block/partitions/msdos.c and block/genhd.c. I think patches that remove
the partit
Hi Sumit,
On 06/15/2017 11:29 PM, Sumit Semwal wrote:
> With older kernels, printf.sh and bitmap.sh fail because they can't find
> the respective test modules they are looking for.
>
> Add the skip portion on missing the respective test_XXX module. Error out
> the same way as prime_numbers.sh.
>
On 16/06/17 13:43, Andy Shevchenko wrote:
On Thu, 2017-06-15 at 17:54 +0200, Matthias Brugger wrote:
Commit e4fda3a04275 ("serial: don't register CIR serial ports") adds a
check for PORT_8250_CIR to serial8250_register_8250_port(). But the
code
isn't needed as the function never takes the bran
Commit e4fda3a04275 ("serial: don't register CIR serial ports") adds a
check for PORT_8250_CIR to serial8250_register_8250_port(). But the code
isn't needed as the function never takes the branch when the port is CIR
serial port.
This patch deletes the dead code.
Signed-off-by: Matthias Brugger
On Fri, 16 Jun 2017 09:50:42 -0500
Jeremy Linton wrote:
> Support for TRACE_DEFINE_SIZEOF() has been added to the kernel.
> Lets document the use of the new macro and correct a couple of
> minor spelling mistakes.
Break this up into two patches please. One trivial one that corrects
the spelling
On 06/16/2017 08:03 AM, Benjamin Gaignard wrote:
> On 32bits platforms "struct timeval" or "time_t" are using u32 to code the
> date, this cause tools like "date" or "hwclock" failed even before setting
> the RTC device if the date is superior to year 2038 (or 2106).
>
> To avoid this problem I ad
Hi,
On 06/16/2017 10:19 AM, Steven Rostedt wrote:
On Fri, 16 Jun 2017 09:50:42 -0500
Jeremy Linton wrote:
Support for TRACE_DEFINE_SIZEOF() has been added to the kernel.
Lets document the use of the new macro and correct a couple of
minor spelling mistakes.
Break this up into two patches pl
On Thu 15-06-17 12:09:01, Theodore Dubois wrote:
> This can be verified with a simple test program. I'm not sure if this is
> a kernel bug or a documentation bug, though...
THis is not a bug. You are not allowed to mmap anything below
/proc/sys/vm/mmap_min_addr. So your patch to update documentati
Hi Thierry,
Thank you for the patch. Please see inline.
W dniu 12.06.2017 o 19:13, Thierry Escande pisze:
From: henryhsu
On Exynos5420, the STREAM_STAT bit raised on the JPGINTST register means
there is a syntax error or an unrecoverable error on compressed file
when ERR_INT_EN is set to 1.
Hi,
On 16/06/2017 at 16:03:51 +0200, Benjamin Gaignard wrote:
> This tool allow to set directly the time and date to a RTC device.
>
> Unlike other tools isn't doens't use "strut timeval" or "time_t"
A small typo here-^
> so it is safe for 32bits platforms when testing for y2038/2106 bug.
>
From: Logan Gunthorpe
> On 16/06/17 07:53 AM, Allen Hubbe wrote:
> > See what is staged in https://github.com/jonmason/ntb.git ntb-next, with
> > the addition of multi-peer
> support by Serge. It would be good at this stage to understand whether the
> api changes there would
> also support the S
From: Andreas Dannenberg
The Texas Instruments TAS6424 device is a high-efficiency quad-channel
Class-D audio power amplifier. Its digital time division multiplexed
(TDM) interface enables up to 2 devices to share the same bus,
supporting a total of eight channels from one audio serial port.
Thi
Add the bindings for the TAS6424 digital amplifier.
Signed-off-by: Michael Stecklein
---
.../devicetree/bindings/sound/ti,tas6424.txt | 31 ++
1 file changed, 31 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/ti,tas6424.txt
diff --git a/Docum
Hello all,
This two-patch series adds the dt bindings, driver, and other related
changes for the TAS6424 digital amplifier. I am upstreaming this driver
on behalf of Andreas.
Regards,
Michael Stecklein
Andreas Dannenberg (1):
ASoC: add support for TAS6424 digital amplifier
Michael Stecklein
From: Hayes Wang
Date: Fri, 16 Jun 2017 03:29:01 +
> David Miller [mailto:da...@davemloft.net]
>> Sent: Wednesday, June 14, 2017 1:02 AM
>> > v2:
>> > For #1, replace GFP_KERNEL with GFP_NOIO for usb_submit_urb().
>> >
>> > v1:
>> > Improve the flow about runtime suspend/resume and make the c
On 06/06/2017 01:11 PM, Dmitry Vyukov wrote:
> CPP turns perfectly readable code into an unreadable,
> unmaintainable mess. Ingo suggested to write them out as-is.
> Do this.
>
> Signed-off-by: Dmitry Vyukov
> Suggested-by: Ingo Molnar
> Cc: Mark Rutland
> Cc: Andrey Ryabinin
> Cc: Thomas Glei
2017-06-16 22:24+0800, Wanpeng Li:
> 2017-06-16 21:37 GMT+08:00 Radim Krčmář :
> > 2017-06-14 19:26-0700, Wanpeng Li:
> >> From: Wanpeng Li
> >>
> >> Add an async_page_fault field to vcpu->arch.exception to identify an async
> >> page fault, and constructs the expected vm-exit information fields.
Hi Thierry,
Thank you for the patch.
Can you give a use case for resolution change event?
Also plase see inline.
W dniu 12.06.2017 o 19:13, Thierry Escande pisze:
From: henryhsu
This patch adds support for resolution change event to notify clients so
they can prepare correct output buffer.
On 06/06/2017 01:11 PM, Dmitry Vyukov wrote:
> atomic64_try_cmpxchg() declares old argument as long*,
> this makes it impossible to use it in portable code.
> If caller passes long*, it becomes 32-bits on 32-bit arches.
> If caller passes s64*, it does not compile on x86_64.
>
> Change type of old
On 2017-06-14 21:22:19 [+0800], Alex Shi wrote:
> This is a quick fix for a bug as 'scheduling while atomic' or
> 'scheduling from the idle thread' on arm/arm64.
>
> On arm/arm64, rwlock cpu_pm_notifier_lock in cpu_pm cause a potential
> schedule after irq disable in idle call chain:
>
> cpu_star
On 06/06/2017 01:11 PM, Dmitry Vyukov wrote:
> The new header allows to wrap per-arch atomic operations
> and add common functionality to all of them.
>
> Signed-off-by: Dmitry Vyukov
> Cc: Mark Rutland
> Cc: Peter Zijlstra
> Cc: Will Deacon
> Cc: Andrew Morton
> Cc: Andrey Ryabinin
> Cc: In
On Fri, Jun 16, 2017 at 3:02 PM, Greg Kroah-Hartman
wrote:
> On Fri, Jun 16, 2017 at 02:01:57PM +0200, Arnd Bergmann wrote:
>> On Thu, Jun 15, 2017 at 6:53 AM, Greg Kroah-Hartman
>> wrote:
>> > On Thu, Jun 15, 2017 at 06:52:21AM +0200, Greg Kroah-Hartman wrote:
>> >> On Wed, Jun 14, 2017 at 11:15
On 2017-06-16 01:22:38 [-0700], Tony Lindgren wrote:
> Recent change to use cpuhp_setup_state_cpuslocked() with commit
> fe2a5cd8aa03 ("ARM/hw_breakpoint: Use cpuhp_setup_state_cpuslocked()")
> missed to change the related paired cpuhp_remove_state_nocalls_cpuslocked().
>
> Now if arch_hw_breakpoi
On 06/16/2017 03:54 AM, Arvind Yadav wrote:
> of_device_ids are not supposed to change at runtime. All functions
> working with of_device_ids provided by work with const
> of_device_ids. So mark the non-const structs as const.
>
> File size before:
>text data bss dec hex
On Fri, Jun 16, 2017 at 03:53:30PM +0100, David Howells wrote:
> Christoph Hellwig wrote:
>
> > It might be good to just introduce the internal flags field first,
>
> Internal flags field? Did you mean Al's suggested sb_readonly() wrapper?
(1) Add a new SB field that is like s_flags but for th
Hi all,
+ Richard and Boris as MTD maintainers
Le 25/04/2017 à 14:18, Vignesh R a écrit :
>
>
> On Friday 21 April 2017 10:36 PM, Mark Brown wrote:
>> On Tue, Apr 11, 2017 at 05:22:25PM +0530, Vignesh R wrote:
>>> Flash filesystems like JFFS2, UBIFS and MTD block layer can provide
>>> vmalloc'd
On 16/06/2017 at 16:03:52 +0200, Benjamin Gaignard wrote:
> The goal of this test is to check if a RTC device correctly support
> dates after years 2038 or 2106.
> It set a date (1-1-2200) on RTC and read it back to be sure that the
> driver is working well.
> The same thing is done on alarm.
>
>
On 06/06/2017 01:11 PM, Dmitry Vyukov wrote:
> Add arch_ prefix to all atomic operations and include
> . This will allow
> to add KASAN instrumentation to all atomic ops.
>
> Signed-off-by: Dmitry Vyukov
> Cc: Mark Rutland
> Cc: Peter Zijlstra
> Cc: Will Deacon
> Cc: Andrew Morton
> Cc: Andre
Hi Hans,
On 16-06-2017 14:44, Hans Verkuil wrote:
>
>>>
>>>
+ /* CEC */
+ dw_dev->cec_adap = cec_allocate_adapter(&dw_hdmi_cec_adap_ops,
+ dw_dev, dev_name(dev), CEC_CAP_TRANSMIT |
+ CEC_CAP_PHYS_ADDR | CEC_CAP_LOG_ADDRS,
>>> Add CEC_CAP_RC
On 06/06/2017 01:11 PM, Dmitry Vyukov wrote:
> Currently kasan_check_read/write() accept 'const void*', make them
> accept 'const volatile void*'. This is required for instrumentation
> of atomic operations and there is just no reason to not allow that.
>
> Signed-off-by: Dmitry Vyukov
> Cc: Ma
301 - 400 of 798 matches
Mail list logo