Signed-off-by: Guo Ren
---
arch/csky/include/asm/uaccess.h | 398
arch/csky/lib/usercopy.c| 271 +++
2 files changed, 669 insertions(+)
create mode 100644 arch/csky/include/asm/uaccess.h
create mode 100644
Signed-off-by: Guo Ren
---
arch/csky/include/asm/uaccess.h | 398
arch/csky/lib/usercopy.c| 271 +++
2 files changed, 669 insertions(+)
create mode 100644 arch/csky/include/asm/uaccess.h
create mode 100644
Signed-off-by: Guo Ren
---
.../bindings/timer/csky,gx6605s-timer.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
Documentation/devicetree/bindings/timer/csky,gx6605s-timer.txt
diff --git
Signed-off-by: Guo Ren
---
.../bindings/timer/csky,gx6605s-timer.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
Documentation/devicetree/bindings/timer/csky,gx6605s-timer.txt
diff --git
Signed-off-by: Guo Ren
---
arch/csky/Kconfig | 231 +
arch/csky/Kconfig.debug| 14 ++
arch/csky/Makefile | 93 +
arch/csky/abiv1/Makefile | 8 ++
arch/csky/abiv2/Makefile
- abiv1 CPU (CK610) is VIPT cache and it doesn't support highmem.
- abiv2 CPUs are all PIPT cache and they could support highmem.
Here is our memory layout plan:
Fixmap : 0xffc02000 – 0xf000 (4 MB - 12KB)
Pkmap: 0xff80 – 0xffc0 (4 MB)
Vmalloc
Changelog:
- Add License and Copyright
- Use timer-of framework
- Change name with upstream feedback
- Use clksource_mmio framework
Signed-off-by: Guo Ren
---
drivers/clocksource/timer-gx6605s.c | 150
1 file changed, 150 insertions(+)
create mode
Signed-off-by: Guo Ren
---
.../bindings/interrupt-controller/csky,mpintc.txt | 40 ++
1 file changed, 40 insertions(+)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/csky,mpintc.txt
diff --git
Signed-off-by: Guo Ren
---
.../devicetree/bindings/timer/csky,mptimer.txt | 46 ++
1 file changed, 46 insertions(+)
create mode 100644 Documentation/devicetree/bindings/timer/csky,mptimer.txt
diff --git a/Documentation/devicetree/bindings/timer/csky,mptimer.txt
Signed-off-by: Guo Ren
---
arch/csky/Kconfig | 231 +
arch/csky/Kconfig.debug| 14 ++
arch/csky/Makefile | 93 +
arch/csky/abiv1/Makefile | 8 ++
arch/csky/abiv2/Makefile
- abiv1 CPU (CK610) is VIPT cache and it doesn't support highmem.
- abiv2 CPUs are all PIPT cache and they could support highmem.
Here is our memory layout plan:
Fixmap : 0xffc02000 – 0xf000 (4 MB - 12KB)
Pkmap: 0xff80 – 0xffc0 (4 MB)
Vmalloc
Changelog:
- Add License and Copyright
- Use timer-of framework
- Change name with upstream feedback
- Use clksource_mmio framework
Signed-off-by: Guo Ren
---
drivers/clocksource/timer-gx6605s.c | 150
1 file changed, 150 insertions(+)
create mode
Signed-off-by: Guo Ren
---
.../bindings/interrupt-controller/csky,mpintc.txt | 40 ++
1 file changed, 40 insertions(+)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/csky,mpintc.txt
diff --git
Signed-off-by: Guo Ren
---
.../devicetree/bindings/timer/csky,mptimer.txt | 46 ++
1 file changed, 46 insertions(+)
create mode 100644 Documentation/devicetree/bindings/timer/csky,mptimer.txt
diff --git a/Documentation/devicetree/bindings/timer/csky,mptimer.txt
Signed-off-by: Guo Ren
---
arch/csky/abiv1/alignment.c | 331 +
arch/csky/abiv1/inc/abi/entry.h | 159
arch/csky/abiv2/inc/abi/entry.h | 157
arch/csky/include/asm/traps.h | 39
arch/csky/include/asm/unistd.h | 3 +
Signed-off-by: Guo Ren
---
arch/csky/abiv1/cacheflush.c | 50
arch/csky/abiv1/inc/abi/cacheflush.h | 41 +++
arch/csky/abiv1/inc/abi/tlb.h | 11 ++
arch/csky/abiv2/cacheflush.c | 54 +
arch/csky/abiv2/inc/abi/cacheflush.h | 38 ++
Signed-off-by: Guo Ren
---
arch/csky/abiv1/alignment.c | 331 +
arch/csky/abiv1/inc/abi/entry.h | 159
arch/csky/abiv2/inc/abi/entry.h | 157
arch/csky/include/asm/traps.h | 39
arch/csky/include/asm/unistd.h | 3 +
Signed-off-by: Guo Ren
---
arch/csky/abiv1/cacheflush.c | 50
arch/csky/abiv1/inc/abi/cacheflush.h | 41 +++
arch/csky/abiv1/inc/abi/tlb.h | 11 ++
arch/csky/abiv2/cacheflush.c | 54 +
arch/csky/abiv2/inc/abi/cacheflush.h | 38 ++
Signed-off-by: Guo Ren
---
arch/csky/kernel/head.S| 78 +
arch/csky/kernel/setup.c | 150 +
arch/csky/kernel/vmlinux.lds.S | 64 ++
3 files changed, 292 insertions(+)
create mode 100644
Signed-off-by: Guo Ren
---
arch/csky/kernel/head.S| 78 +
arch/csky/kernel/setup.c | 150 +
arch/csky/kernel/vmlinux.lds.S | 64 ++
3 files changed, 292 insertions(+)
create mode 100644
Signed-off-by: Guo Ren
---
Documentation/devicetree/bindings/csky/cpus.txt | 70 +
1 file changed, 70 insertions(+)
create mode 100644 Documentation/devicetree/bindings/csky/cpus.txt
diff --git a/Documentation/devicetree/bindings/csky/cpus.txt
Signed-off-by: Guo Ren
---
Documentation/devicetree/bindings/csky/cpus.txt | 70 +
1 file changed, 70 insertions(+)
create mode 100644 Documentation/devicetree/bindings/csky/cpus.txt
diff --git a/Documentation/devicetree/bindings/csky/cpus.txt
This is the 3th version patchset to add the Linux kernel port for C-SKY(csky).
Thanks to everyone who provided feedback on the previous version.
This patchset adds architecture support to Linux for C-SKY's 32-bit embedded
CPU cores and the patches are based on linux-4.18.4
There are two ABI
Signed-off-by: Guo Ren
---
arch/csky/configs/defconfig | 61 +
1 file changed, 61 insertions(+)
create mode 100644 arch/csky/configs/defconfig
diff --git a/arch/csky/configs/defconfig b/arch/csky/configs/defconfig
new file mode 100644
index
This is the 3th version patchset to add the Linux kernel port for C-SKY(csky).
Thanks to everyone who provided feedback on the previous version.
This patchset adds architecture support to Linux for C-SKY's 32-bit embedded
CPU cores and the patches are based on linux-4.18.4
There are two ABI
Signed-off-by: Guo Ren
---
arch/csky/configs/defconfig | 61 +
1 file changed, 61 insertions(+)
create mode 100644 arch/csky/configs/defconfig
diff --git a/arch/csky/configs/defconfig b/arch/csky/configs/defconfig
new file mode 100644
index
Signed-off-by: Guo Ren
---
arch/csky/abiv1/bswapdi.c| 18 ++
arch/csky/abiv1/bswapsi.c| 14 ++
arch/csky/abiv1/inc/abi/string.h | 13 ++
arch/csky/abiv1/memcpy.S | 344 +++
arch/csky/abiv1/memset.c | 37 +
Signed-off-by: Guo Ren
---
arch/csky/abiv1/bswapdi.c| 18 ++
arch/csky/abiv1/bswapsi.c| 14 ++
arch/csky/abiv1/inc/abi/string.h | 13 ++
arch/csky/abiv1/memcpy.S | 344 +++
arch/csky/abiv1/memset.c | 37 +
On Wed, Sep 12, 2018 at 09:03:55AM -0400, Jerome Glisse wrote:
> On Wed, Sep 12, 2018 at 02:49:21PM +0800, Peter Xu wrote:
> > Add an extra check on page dirty bit in change_pte_range() since there
> > might be case where PTE dirty bit is unset but it's actually dirtied.
> > One example is when a
On Wed, Sep 12, 2018 at 09:03:55AM -0400, Jerome Glisse wrote:
> On Wed, Sep 12, 2018 at 02:49:21PM +0800, Peter Xu wrote:
> > Add an extra check on page dirty bit in change_pte_range() since there
> > might be case where PTE dirty bit is unset but it's actually dirtied.
> > One example is when a
Hello,
syzbot found the following crash on:
HEAD commit:7c1b097f27bf Add linux-next specific files for 20180912
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1333df0140
kernel config: https://syzkaller.appspot.com/x/.config?x=5980033172920ec0
Hello,
syzbot found the following crash on:
HEAD commit:7c1b097f27bf Add linux-next specific files for 20180912
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1333df0140
kernel config: https://syzkaller.appspot.com/x/.config?x=5980033172920ec0
Hello,
syzbot found the following crash on:
HEAD commit:7c1b097f27bf Add linux-next specific files for 20180912
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=175570c640
kernel config: https://syzkaller.appspot.com/x/.config?x=5980033172920ec0
Hello,
syzbot found the following crash on:
HEAD commit:7c1b097f27bf Add linux-next specific files for 20180912
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14e6101a40
kernel config: https://syzkaller.appspot.com/x/.config?x=5980033172920ec0
Hello,
syzbot found the following crash on:
HEAD commit:7c1b097f27bf Add linux-next specific files for 20180912
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=175570c640
kernel config: https://syzkaller.appspot.com/x/.config?x=5980033172920ec0
Hello,
syzbot found the following crash on:
HEAD commit:7c1b097f27bf Add linux-next specific files for 20180912
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14e6101a40
kernel config: https://syzkaller.appspot.com/x/.config?x=5980033172920ec0
On Wed 12-09-18 22:57:43, Balbir Singh wrote:
> On Wed, Sep 12, 2018 at 12:38:53PM +0200, Michal Hocko wrote:
> > On Wed 12-09-18 14:56:45, Arun KS wrote:
> > > When free pages are done with pageblock_order, time spend on
> > > coalescing pages by buddy allocator can be reduced. With
> > > section
On Wed 12-09-18 22:57:43, Balbir Singh wrote:
> On Wed, Sep 12, 2018 at 12:38:53PM +0200, Michal Hocko wrote:
> > On Wed 12-09-18 14:56:45, Arun KS wrote:
> > > When free pages are done with pageblock_order, time spend on
> > > coalescing pages by buddy allocator can be reduced. With
> > > section
On Wed, 12 Sep 2018, Alexandre Belloni wrote:
> On 12/09/2018 12:43:52+0100, Lee Jones wrote:
> > > > But ... we can't have it both ways. *Either* it's a true MFD, in
> > > > which case it can/should have 2 separate compatible strings which can
> > > > be specified directly from the DT. *Or*
On Wed, 12 Sep 2018, Alexandre Belloni wrote:
> On 12/09/2018 12:43:52+0100, Lee Jones wrote:
> > > > But ... we can't have it both ways. *Either* it's a true MFD, in
> > > > which case it can/should have 2 separate compatible strings which can
> > > > be specified directly from the DT. *Or*
Hi all,
[+ more people from get_maintainers.pl]
On Wed, Sep 05, 2018 at 03:34:41PM +0100, Will Deacon wrote:
> This is a resend of:
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2018-July/593559.html
>
> now based on 4.19-rc2.
>
> The Debian folks have observed a failure in the
Hi all,
[+ more people from get_maintainers.pl]
On Wed, Sep 05, 2018 at 03:34:41PM +0100, Will Deacon wrote:
> This is a resend of:
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2018-July/593559.html
>
> now based on 4.19-rc2.
>
> The Debian folks have observed a failure in the
Hello,
syzbot found the following crash on:
HEAD commit:7c1b097f27bf Add linux-next specific files for 20180912
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1667ea5640
kernel config: https://syzkaller.appspot.com/x/.config?x=5980033172920ec0
Hello,
syzbot found the following crash on:
HEAD commit:7c1b097f27bf Add linux-next specific files for 20180912
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1667ea5640
kernel config: https://syzkaller.appspot.com/x/.config?x=5980033172920ec0
Hello,
syzbot found the following crash on:
HEAD commit:7c1b097f27bf Add linux-next specific files for 20180912
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10ce508140
kernel config: https://syzkaller.appspot.com/x/.config?x=5980033172920ec0
Hello,
syzbot found the following crash on:
HEAD commit:7c1b097f27bf Add linux-next specific files for 20180912
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10ce508140
kernel config: https://syzkaller.appspot.com/x/.config?x=5980033172920ec0
Hi James,
On 12/09/18 11:31, James Morse wrote:
Hi Julien,
On 28/08/18 16:51, Julien Thierry wrote:
Masking daif flags is done very early before returning to EL0.
Only toggle the interrupt masking while in the vector entry and mask daif
once in kernel_exit.
I had an earlier version that
Hi James,
On 12/09/18 11:31, James Morse wrote:
Hi Julien,
On 28/08/18 16:51, Julien Thierry wrote:
Masking daif flags is done very early before returning to EL0.
Only toggle the interrupt masking while in the vector entry and mask daif
once in kernel_exit.
I had an earlier version that
> static int mvebu_pwm_request(struct pwm_chip *chip, struct pwm_device *pwm)
> {
> struct mvebu_pwm *mvpwm = to_mvebu_pwm(chip);
> struct mvebu_gpio_chip *mvchip = mvpwm->mvchip;
> struct gpio_desc *desc;
> + struct mvebu_pwm *counter;
> unsigned long flags;
>
> static int mvebu_pwm_request(struct pwm_chip *chip, struct pwm_device *pwm)
> {
> struct mvebu_pwm *mvpwm = to_mvebu_pwm(chip);
> struct mvebu_gpio_chip *mvchip = mvpwm->mvchip;
> struct gpio_desc *desc;
> + struct mvebu_pwm *counter;
> unsigned long flags;
>
On 09/09/2018 10:05 PM, Thomas Gleixner wrote:
See the patch below. It's integrating TAI without slowing down everything
and it definitely does not result in indirect calls.
On a HSW it slows down clock_gettime() by ~0.5ns. On a SKL I get a speedup
by ~0.5ns. On a AMD Epyc server it's 1.2ns
On 09/09/2018 10:05 PM, Thomas Gleixner wrote:
See the patch below. It's integrating TAI without slowing down everything
and it definitely does not result in indirect calls.
On a HSW it slows down clock_gettime() by ~0.5ns. On a SKL I get a speedup
by ~0.5ns. On a AMD Epyc server it's 1.2ns
On 12/09/18 13:28, James Morse wrote:
On 12/09/18 12:11, Julien Thierry wrote:
On 12/09/18 11:32, James Morse wrote:
On 28/08/18 16:51, Julien Thierry wrote:
For EL0 entries requiring bp_hardening, daif status is kept at
DAIF_PROCCTX_NOIRQ until after hardening has been done. Then
https://e24.no/nyheter/eu-vedtok-omstridt-direktiv-om-opphavsrett/24438959
Norwegian News today writes of EU, and a copyright directive that
ensures workmakers get their profits, from images, audio, art etc.
Indeed the Fair Pay project I started is resonating with this, and we
want a full
On Wed, Sep 12, 2018 at 02:49:21PM +0800, Peter Xu wrote:
> Add an extra check on page dirty bit in change_pte_range() since there
> might be case where PTE dirty bit is unset but it's actually dirtied.
> One example is when a huge PMD is splitted after written: the dirty bit
> will be set on the
On 12/09/18 13:28, James Morse wrote:
On 12/09/18 12:11, Julien Thierry wrote:
On 12/09/18 11:32, James Morse wrote:
On 28/08/18 16:51, Julien Thierry wrote:
For EL0 entries requiring bp_hardening, daif status is kept at
DAIF_PROCCTX_NOIRQ until after hardening has been done. Then
https://e24.no/nyheter/eu-vedtok-omstridt-direktiv-om-opphavsrett/24438959
Norwegian News today writes of EU, and a copyright directive that
ensures workmakers get their profits, from images, audio, art etc.
Indeed the Fair Pay project I started is resonating with this, and we
want a full
On Wed, Sep 12, 2018 at 02:49:21PM +0800, Peter Xu wrote:
> Add an extra check on page dirty bit in change_pte_range() since there
> might be case where PTE dirty bit is unset but it's actually dirtied.
> One example is when a huge PMD is splitted after written: the dirty bit
> will be set on the
On Mon, 10 Sep 2018 15:17:54 +0200
Michal Hocko wrote:
> [Cc Pavel]
>
> On Mon 10-09-18 14:35:27, Mikhail Zaslonko wrote:
> > If memory end is not aligned with the linux memory section boundary, such
> > a section is only partly initialized. This may lead to VM_BUG_ON due to
> > uninitialized
On Mon, 10 Sep 2018 15:17:54 +0200
Michal Hocko wrote:
> [Cc Pavel]
>
> On Mon 10-09-18 14:35:27, Mikhail Zaslonko wrote:
> > If memory end is not aligned with the linux memory section boundary, such
> > a section is only partly initialized. This may lead to VM_BUG_ON due to
> > uninitialized
On Wed, Sep 12, 2018 at 12:38:53PM +0200, Michal Hocko wrote:
> On Wed 12-09-18 14:56:45, Arun KS wrote:
> > When free pages are done with pageblock_order, time spend on
> > coalescing pages by buddy allocator can be reduced. With
> > section size of 256MB, hot add latency of a single section
> >
On Wed, Sep 12, 2018 at 12:38:53PM +0200, Michal Hocko wrote:
> On Wed 12-09-18 14:56:45, Arun KS wrote:
> > When free pages are done with pageblock_order, time spend on
> > coalescing pages by buddy allocator can be reduced. With
> > section size of 256MB, hot add latency of a single section
> >
On 08-Sep 20:02, Suren Baghdasaryan wrote:
> On Tue, Aug 28, 2018 at 6:53 AM, Patrick Bellasi
> wrote:
[...]
> > + cpu.util.min.effective
> > +A read-only single value file which exists on non-root cgroups and
> > +reports minimum utilization clamp value currently enforced on a
On 08-Sep 20:02, Suren Baghdasaryan wrote:
> On Tue, Aug 28, 2018 at 6:53 AM, Patrick Bellasi
> wrote:
[...]
> > + cpu.util.min.effective
> > +A read-only single value file which exists on non-root cgroups and
> > +reports minimum utilization clamp value currently enforced on a
CERTIFIED AND APPROVED THE PAYMENT OF ($10,500,000.00 )
Attention
This is to alert you that we received your fund worth the sum $10,500,000.00
from the Bank of USA ,we apologies for the delay of your payment and all the
inconveniences we might put you through, Meanwhile we were having
CERTIFIED AND APPROVED THE PAYMENT OF ($10,500,000.00 )
Attention
This is to alert you that we received your fund worth the sum $10,500,000.00
from the Bank of USA ,we apologies for the delay of your payment and all the
inconveniences we might put you through, Meanwhile we were having
Hi Leo,
On 12/09/18 11:47, leo@linaro.org wrote:
On Tue, Sep 11, 2018 at 11:17:03AM +0100, Suzuki K Poulose wrote:
Switch to updated coresight bindings for hw ports.
As Shawn suggested, please change subject as "arm64: dts: hi6220:
"
Sure, will do.
Cc: xuw...@hisilicon.com
Cc:
Subject: x86/tsc: Prevent result truncation on 32 bit
From: Chuanhua Lei
Date: Thu Sep 6 18:03:23 2018 +0800
From: Chuanhua Lei
Commit 17f6bac2249356c795339e03a0742cd79be3cab8 upstream.
Loops per jiffy is calculated by multiplying tsc_khz with 1e3 and then
dividing it by HZ.
Both tsc_khz
Subject: x86/tsc: Prevent result truncation on 32 bit
From: Chuanhua Lei
Date: Thu Sep 6 18:03:23 2018 +0800
From: Chuanhua Lei
Commit 17f6bac2249356c795339e03a0742cd79be3cab8 upstream.
Loops per jiffy is calculated by multiplying tsc_khz with 1e3 and then
dividing it by HZ.
Both tsc_khz
Hi Leo,
On 12/09/18 11:47, leo@linaro.org wrote:
On Tue, Sep 11, 2018 at 11:17:03AM +0100, Suzuki K Poulose wrote:
Switch to updated coresight bindings for hw ports.
As Shawn suggested, please change subject as "arm64: dts: hi6220:
"
Sure, will do.
Cc: xuw...@hisilicon.com
Cc:
On 12/09/18 11:28, James Morse wrote:
Hi Julien,
On 28/08/18 16:51, Julien Thierry wrote:
The cpu_enable callback for VHE feature requires all alternatives to have
been applied. This prevents applying VHE alternative separately from the
rest.
Use an alternative depending on VHE feature to
On 12/09/18 11:28, James Morse wrote:
Hi Julien,
On 28/08/18 16:51, Julien Thierry wrote:
The cpu_enable callback for VHE feature requires all alternatives to have
been applied. This prevents applying VHE alternative separately from the
rest.
Use an alternative depending on VHE feature to
On Tue 11-09-18 08:27:30, Roman Gushchin wrote:
> On Tue, Sep 11, 2018 at 02:11:41PM +0200, Michal Hocko wrote:
> > On Mon 10-09-18 14:56:22, Roman Gushchin wrote:
> > > The memcg OOM killer is never invoked due to a failed high-order
> > > allocation, however the MEMCG_OOM event can be easily
On Tue 11-09-18 08:27:30, Roman Gushchin wrote:
> On Tue, Sep 11, 2018 at 02:11:41PM +0200, Michal Hocko wrote:
> > On Mon 10-09-18 14:56:22, Roman Gushchin wrote:
> > > The memcg OOM killer is never invoked due to a failed high-order
> > > allocation, however the MEMCG_OOM event can be easily
Hi Julien,
On 12/09/18 12:11, Julien Thierry wrote:
> On 12/09/18 11:32, James Morse wrote:
>> On 28/08/18 16:51, Julien Thierry wrote:
>>> For EL0 entries requiring bp_hardening, daif status is kept at
>>> DAIF_PROCCTX_NOIRQ until after hardening has been done. Then interrupts
>>> are enabled
Hi Julien,
On 28/08/18 16:51, Julien Thierry wrote:
> Some of the work done in daifflags save/restore is already provided
> by irqflags functions. Daifflags should always be a superset of irqflags
> (it handles irq status + status of other flags). Modifying behaviour of
> irqflags should alter
Hi Julien,
On 12/09/18 12:11, Julien Thierry wrote:
> On 12/09/18 11:32, James Morse wrote:
>> On 28/08/18 16:51, Julien Thierry wrote:
>>> For EL0 entries requiring bp_hardening, daif status is kept at
>>> DAIF_PROCCTX_NOIRQ until after hardening has been done. Then interrupts
>>> are enabled
Hi Julien,
On 28/08/18 16:51, Julien Thierry wrote:
> Some of the work done in daifflags save/restore is already provided
> by irqflags functions. Daifflags should always be a superset of irqflags
> (it handles irq status + status of other flags). Modifying behaviour of
> irqflags should alter
On Wed, Sep 12, 2018 at 08:19:54PM +0800, Cheng-Yi Chiang wrote:
> max98927 codec driver will support reset-gpio binding so it can toggle
> reset line in its probe function.
All GPIO properties are supposed to end -gpios even if there can only
ever be a single GPIO.
signature.asc
Description:
On Wed, Sep 12, 2018 at 08:19:54PM +0800, Cheng-Yi Chiang wrote:
> max98927 codec driver will support reset-gpio binding so it can toggle
> reset line in its probe function.
All GPIO properties are supposed to end -gpios even if there can only
ever be a single GPIO.
signature.asc
Description:
On 09/11, Kees Cook wrote:
>
> Oh, I like this patch! This is much cleaner.
it's pity. cause this means I will have to actually test this change and
(worse) write the changelog ;)
> > @@ -410,11 +365,6 @@ static int bprm_mm_init(struct linux_binprm *bprm)
> > if (!mm)
> >
On 09/11, Kees Cook wrote:
>
> Oh, I like this patch! This is much cleaner.
it's pity. cause this means I will have to actually test this change and
(worse) write the changelog ;)
> > @@ -410,11 +365,6 @@ static int bprm_mm_init(struct linux_binprm *bprm)
> > if (!mm)
> >
On Tue 11-09-18 16:06:23, Zaslonko Mikhail wrote:
[...]
> > Well, I am afraid this is not the proper solution. We are relying on the
> > full pageblock worth of initialized struct pages at many other place. We
> > used to do that in the past because we have initialized the full
> > section but
On Tue 11-09-18 16:06:23, Zaslonko Mikhail wrote:
[...]
> > Well, I am afraid this is not the proper solution. We are relying on the
> > full pageblock worth of initialized struct pages at many other place. We
> > used to do that in the past because we have initialized the full
> > section but
Toggle reset line in max98927_i2c_probe.
Use a list to store max98927 instances so we do not toggle reset line
again if more than one instances share the same reset line.
Signed-off-by: Cheng-Yi Chiang
---
sound/soc/codecs/max98927.c | 78 +
On Wed, Sep 5, 2018 at 1:46 AM Jernej Škrabec wrote:
>
> Dne torek, 04. september 2018 ob 11:04:21 CEST je Chen-Yu Tsai napisal(a):
> > On Sun, Sep 2, 2018 at 3:27 PM Jernej Skrabec
> wrote:
> > > Support for mixer0, mixer1, writeback and rotation units is added.
> > >
> > > Signed-off-by:
Toggle reset line in max98927_i2c_probe.
Use a list to store max98927 instances so we do not toggle reset line
again if more than one instances share the same reset line.
Signed-off-by: Cheng-Yi Chiang
---
sound/soc/codecs/max98927.c | 78 +
On Wed, Sep 5, 2018 at 1:46 AM Jernej Škrabec wrote:
>
> Dne torek, 04. september 2018 ob 11:04:21 CEST je Chen-Yu Tsai napisal(a):
> > On Sun, Sep 2, 2018 at 3:27 PM Jernej Skrabec
> wrote:
> > > Support for mixer0, mixer1, writeback and rotation units is added.
> > >
> > > Signed-off-by:
max98927 codec driver will support reset-gpio binding so it can toggle
reset line in its probe function.
Signed-off-by: Cheng-Yi Chiang
---
Documentation/devicetree/bindings/sound/max9892x.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git
max98927 codec driver will support reset-gpio binding so it can toggle
reset line in its probe function.
Signed-off-by: Cheng-Yi Chiang
---
Documentation/devicetree/bindings/sound/max9892x.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git
Darren,
> -Original Message-
> From: Darren Hart [mailto:dvh...@infradead.org]
> Sent: Monday, September 10, 2018 3:52 PM
> To: Limonciello, Mario
> Cc: Andy Shevchenko; LKML; platform-driver-...@vger.kernel.org;
> sta...@vger.kernel.org
> Subject: Re: [PATCH 1/2] platform/x86:
Darren,
> -Original Message-
> From: Darren Hart [mailto:dvh...@infradead.org]
> Sent: Monday, September 10, 2018 3:52 PM
> To: Limonciello, Mario
> Cc: Andy Shevchenko; LKML; platform-driver-...@vger.kernel.org;
> sta...@vger.kernel.org
> Subject: Re: [PATCH 1/2] platform/x86:
On 12/09/2018 12:43:52+0100, Lee Jones wrote:
> > > But ... we can't have it both ways. *Either* it's a true MFD, in
> > > which case it can/should have 2 separate compatible strings which can
> > > be specified directly from the DT. *Or* it's not an MFD. In the
> > > latter case, which I think
On 12/09/2018 12:43:52+0100, Lee Jones wrote:
> > > But ... we can't have it both ways. *Either* it's a true MFD, in
> > > which case it can/should have 2 separate compatible strings which can
> > > be specified directly from the DT. *Or* it's not an MFD. In the
> > > latter case, which I think
On Tue, Sep 11, 2018 at 04:39:08PM -1000, Joshua Abraham wrote:
> This patch removes a set but unused variable in quirks.c.
>
> Fixes warning:
> variable ‘mmio_sys_info’ set but not used [-Wunused-but-set-variable]
>
> Signed-off-by: Joshua Abraham
Applied to pci/misc for v4.20, thanks!
> ---
On Tue, Sep 11, 2018 at 04:39:08PM -1000, Joshua Abraham wrote:
> This patch removes a set but unused variable in quirks.c.
>
> Fixes warning:
> variable ‘mmio_sys_info’ set but not used [-Wunused-but-set-variable]
>
> Signed-off-by: Joshua Abraham
Applied to pci/misc for v4.20, thanks!
> ---
On Tue 11-09-18 13:30:20, David Rientjes wrote:
> On Tue, 11 Sep 2018, Michal Hocko wrote:
[...]
> > hugepage specific MPOL flags sounds like yet another step into even more
> > cluttered API and semantic, I am afraid. Why should this be any
> > different from regular page allocations? You are
On Tue 11-09-18 13:30:20, David Rientjes wrote:
> On Tue, 11 Sep 2018, Michal Hocko wrote:
[...]
> > hugepage specific MPOL flags sounds like yet another step into even more
> > cluttered API and semantic, I am afraid. Why should this be any
> > different from regular page allocations? You are
Hi James,
On 12/09/18 11:28, James Morse wrote:
Hi Julien,
On 28/08/18 16:51, Julien Thierry wrote:
The cpu_enable callback for VHE feature requires all alternatives to have
been applied. This prevents applying VHE alternative separately from the
rest.
Use an alternative depending on VHE
Hi James,
On 12/09/18 11:28, James Morse wrote:
Hi Julien,
On 28/08/18 16:51, Julien Thierry wrote:
The cpu_enable callback for VHE feature requires all alternatives to have
been applied. This prevents applying VHE alternative separately from the
rest.
Use an alternative depending on VHE
1001 - 1100 of 1468 matches
Mail list logo
