[tip:sched/urgent] mm, sched/numa: Remove remaining traces of NUMA rate-limiting

Commit-ID: e054637597ba36d3729ba6a3a3dd7aad8e2a3003 Gitweb: https://git.kernel.org/tip/e054637597ba36d3729ba6a3a3dd7aad8e2a3003 Author: Srikar Dronamraju AuthorDate: Sat, 6 Oct 2018 16:53:19 +0530 Committer: Ingo Molnar CommitDate: Tue, 9 Oct 2018 08:30:51 +0200 mm, sched/numa: Remove

[tip:x86/cache] x86/intel_rdt: Fix out-of-bounds memory access in CBM tests

Commit-ID: 49e00eee00612b1357596fed8a88b621a7648c14 Gitweb: https://git.kernel.org/tip/49e00eee00612b1357596fed8a88b621a7648c14 Author: Reinette Chatre AuthorDate: Thu, 4 Oct 2018 14:05:23 -0700 Committer: Ingo Molnar CommitDate: Tue, 9 Oct 2018 08:02:15 +0200 x86/intel_rdt: Fix out-of

[tip:x86/cache] x86/intel_rdt: CBM overlap should also check for overlap with CDP peer

Commit-ID: e5f3530c391105fdd6174852e3ea6136d073b45a Gitweb: https://git.kernel.org/tip/e5f3530c391105fdd6174852e3ea6136d073b45a Author: Reinette Chatre AuthorDate: Wed, 3 Oct 2018 15:17:02 -0700 Committer: Ingo Molnar CommitDate: Tue, 9 Oct 2018 08:50:43 +0200 x86/intel_rdt: CBM overla

[tip:x86/cache] x86/intel_rdt: Introduce utility to obtain CDP peer

Commit-ID: 521348b011d64cf3febb10b64ba5b472681bef94 Gitweb: https://git.kernel.org/tip/521348b011d64cf3febb10b64ba5b472681bef94 Author: Reinette Chatre AuthorDate: Wed, 3 Oct 2018 15:17:01 -0700 Committer: Ingo Molnar CommitDate: Tue, 9 Oct 2018 08:50:40 +0200 x86/intel_rdt: Introduce

[PATCH v3 0/3] namei: implement various lookup restriction AT_* flags

The need for some sort of control over VFS's path resolution (to avoid malicious paths resulting in inadvertent breakouts) has been a very long-standing desire of many userspace applications. This patchset is a revival of Al Viro's old AT_NO_JUMPS[1,2] patchset (which was a variant of David Drysdal

[PATCH v3 1/3] namei: implement O_BENEATH-style AT_* flags

Add the following flags to allow various restrictions on path resolution (these affect the *entire* resolution, rather than just the final path component -- as is the case with most other AT_* flags). The primary justification for these flags is to allow for programs to be far more strict about ho

[PATCH v3 2/3] namei: implement AT_THIS_ROOT chroot-like path resolution

The primary motivation for the need for this flag is container runtimes which have to interact with malicious root filesystems in the host namespaces. One of the first requirements for a container runtime to be secure against a malicious rootfs is that they correctly scope symlinks (that is, they s

[PATCH v3 3/3] namei: aggressively check for nd->root escape on ".." resolution

This patch allows for AT_BENEATH and AT_THIS_ROOT to safely permit ".." resolution (in the case of AT_BENEATH the resolution will still fail if ".." resolution would resolve a path outside of the root -- while AT_THIS_ROOT will chroot(2)-style scope it). "proclink" jumps are still disallowed entire

[tip:x86/cache] x86/intel_rdt: Fix initial allocation to consider CDP

Commit-ID: 2a7adf6ce643fdeec051dc88e5250b08c83bbb67 Gitweb: https://git.kernel.org/tip/2a7adf6ce643fdeec051dc88e5250b08c83bbb67 Author: Reinette Chatre AuthorDate: Wed, 3 Oct 2018 15:17:03 -0700 Committer: Ingo Molnar CommitDate: Tue, 9 Oct 2018 08:50:47 +0200 x86/intel_rdt: Fix initia

[tip:x86/urgent] x86/mm: Avoid VLA in pgd_alloc()

Commit-ID: 184d47f0fd365108bd06ab26cdb3450b716269fd Gitweb: https://git.kernel.org/tip/184d47f0fd365108bd06ab26cdb3450b716269fd Author: Kees Cook AuthorDate: Mon, 8 Oct 2018 16:54:34 -0700 Committer: Ingo Molnar CommitDate: Tue, 9 Oct 2018 08:55:07 +0200 x86/mm: Avoid VLA in pgd_alloc(

Re: [alsa-devel] [PATCH linux-next v2 9/9] ASoC: rsnd: add busif property to dai stream

Hi Morimoto-san Thanks for your comment On 2018/10/09 9:44, Kuninori Morimoto wrote: Hi Jiada SSI can work in following modes 1. Basic Mode: (channel 1, 2, 4, 6, 8, 16) 2. TDM Extended Mode: (channel 6, 8) 3. TDM Split Mode: (channel 1, 2) 4. TDM Ex-Split mode: (Channel 2, 4, 6, 8, 10) (snip

Re: [PATCH 4.18 000/168] 4.18.13-stable review

On Mon, Oct 08, 2018 at 05:13:51PM -0600, Shuah Khan wrote: > On 10/08/2018 12:29 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.18.13 release. > > There are 168 patches in this series, all will be posted as a response > > to this one. If anyone has any is

Re: Linux 4.19-rc7

On Mon, Oct 08, 2018 at 12:43:05PM -0600, Shuah Khan wrote: > On Sun, Oct 7, 2018 at 9:48 AM Greg KH wrote: > > > > Hi all, > > > > Yet again, it's time for a kernel -rc release. This one is bigger than > > -rc6 was, for a variety of unrelated reasons it seems. Lots of > > different trees being

Re: [PATCH v3 1/7] dt-bindings: stm32-dma: Add DMA/MDMA chaining support bindings

Hi Vinod On 10/07/2018 04:57 PM, Vinod wrote: > On 28-09-18, 15:01, Pierre-Yves MORDRET wrote: >> From: M'boumba Cedric Madianga >> >> This patch adds dma bindings to support DMA/MDMA chaining transfer. >> 1 bit is to manage both DMA FIFO Threshold >> 1 bit is to manage DMA/MDMA Chaining features

Re: [PATCH] of: base: Change logic in of_alias_get_alias_list()

On 8.10.2018 17:07, Rob Herring wrote: > On Mon, Oct 8, 2018 at 7:19 AM Michal Simek wrote: >> >> Check compatible string first before setting up bit in bitmap to also >> cover cases that allocated bitfield is not big enough. >> Show warning about it but let driver to continue to work with allocat

Re: [PATCH v3 2/7] dt-bindings: stm32-dmamux: Add one cell to support DMA/MDMA chain

On 10/07/2018 04:58 PM, Vinod wrote: > On 28-09-18, 15:01, Pierre-Yves MORDRET wrote: >> From: M'boumba Cedric Madianga >> >> Add one cell to support DMA/MDMA chaining. >> >> Signed-off-by: Pierre-Yves MORDRET >> --- >> Version history: >> v3: >> v2: >>* rework content >>

Re: [PATCH 1/2] dt-bindings: phy: Update SERDES_MAX to be SERDES_MAX + 1

Hi Gustavo, On Tue, Oct 09, 2018 at 12:21:36AM +0200, Gustavo A. R. Silva wrote: > SERDES_MAX is a valid value to index ctrl->phys in > drivers/phy/mscc/phy-ocelot-serdes.c. But, currently, > there is an out-of-bounds bug in the mentioned driver > when reading from ctrl->phys, because the size of

Re: [PATCH 2/2] phy: ocelot-serdes: fix out-of-bounds read

Hi Gustavo, On Tue, Oct 09, 2018 at 12:22:33AM +0200, Gustavo A. R. Silva wrote: > Currently, there is an out-of-bounds read on array ctrl->phys, > once variable i reaches the maximum array size of SERDES_MAX > in the for loop. > > Fix this by changing the condition in the for loop from > i <= SE

Re: [PATCH v2] sysctl: kselftests: fix test_modprobe issue

On Thu, 6 Sep 2018 at 12:20, Lei Yang wrote: > > when CONFIG_TEST_SYSCTL=y, there is no "/sys/module/test_sysctl/" > when CONFIG_TEST_SYSCTL=m, checking /sys/module/test_sysctl/ is > before kernel module loading > > you'll get below error message > root@intel-x86-64:/tmp/sysctl# ./sysctl.sh > Chec

Re: [PATCH 0/2] phy: ocelot-serdes: fix out-of-bounds bug

Hi Gustavo, On Tue, Oct 09, 2018 at 12:20:28AM +0200, Gustavo A. R. Silva wrote: > This patchset aims to fix an out-of-bounds bug in > the phy-ocelot-serdes driver. > > Currently, there is an out-of-bounds read on array ctrl->phys, > once variable i reaches the maximum array size of SERDES_MAX >

Re: [PATCH 4/6] mmc: sdhci-of-arasan: Add a single data structure to incorporate pdata and soc_ctl_map

On 4 October 2018 at 13:14, Faiz Abbas wrote: > Currently, the driver passes platform data as a global structure > and uses the .data of of_device_id to pass the soc_ctl_map. To > make the implementation more flexible add a single data structure > that incorporates both of the above and pass it in

Re: [PATCH V6 00/23] mmc: mmci: add sdmmc variant for stm32

On 8 October 2018 at 14:08, Ludovic Barre wrote: > From: Ludovic Barre > > The goal of this serie is to add support of sdmmc for stm32. > Be to able to add this new variant it is needed to do some changes in > mmci core: > -Internalize specific needs of legacy dmaengine. > -Create and setup dma_p

Re: [PATCH 5/6] mmc: sdhci-of-arasan: Add Support for AM654 MMC and PHY

On 4 October 2018 at 13:14, Faiz Abbas wrote: > The current arasan sdhci PHY configuration isn't compatible > with the PHY on TI's AM654 devices. > > Therefore, add a new compatible, AM654 specific quirks > and a new AM654 specific set_clock function which > configures the PHY in a sane way. > > S

Re: [PATCH 3/6] dt-bindings: mmc: sdhci-of-arasan: Add new compatible for AM654 MMC PHY

On 4 October 2018 at 13:14, Faiz Abbas wrote: > Add a new compatible to use the host controller driver with the > MMC PHY on TI's AM654 SOCs > > Signed-off-by: Faiz Abbas > Signed-off-by: Sekhar Nori Applied for next, thanks! Kind regards Uffe > --- > Documentation/devicetree/bindings/mmc/ar

Re: [PATCH 2/6] phy: am654-mmc-phy: Add Support for MMC PHY on AM654 Devices

On 9 October 2018 at 07:18, Kishon Vijay Abraham I wrote: > Hi Uffe, > > On Monday 08 October 2018 05:02 PM, Ulf Hansson wrote: >> On 4 October 2018 at 13:14, Faiz Abbas wrote: >>> Add driver support for the MMC physical layer present >>> on TI's AM654 devices. >>> >>> Signed-off-by: Faiz Abbas

Re: [PATCH 5/6] mmc: sdhci-of-arasan: Add Support for AM654 MMC and PHY

Hi Uffe, On Tuesday 09 October 2018 01:00 PM, Ulf Hansson wrote: > On 4 October 2018 at 13:14, Faiz Abbas wrote: >> The current arasan sdhci PHY configuration isn't compatible >> with the PHY on TI's AM654 devices. >> >> Therefore, add a new compatible, AM654 specific quirks >> and a new AM654 sp

Re: [tip:x86/urgent] x86/mm: Avoid VLA in pgd_alloc()

On Tue, Oct 9, 2018 at 1:28 AM Kees Cook wrote: > On Mon, Oct 8, 2018 at 1:22 PM, Borislav Petkov wrote: > > On Fri, Oct 05, 2018 at 09:24:53AM -0700, tip-bot for Arnd Bergmann wrote: > > > > For whatever reason - probably because it forced > > MAX_PREALLOCATED_USER_PMDS be KERNEL_PGD_PTRS and n

Re: [RESEND][PATCH] ACPI / CPPC: Add support for guaranteed performance

On Mon, Oct 8, 2018 at 6:55 PM Srinivas Pandruvada wrote: > > The Continuous Performance Control Package can have guaranteed performance > field. Add support to read guaranteed performance. The spec says that it is optional, but you seem to assume that it always will be there. What happens if it

Re: [PATCH 5/6] mmc: sdhci-of-arasan: Add Support for AM654 MMC and PHY

On 9 October 2018 at 09:35, Faiz Abbas wrote: > Hi Uffe, > > On Tuesday 09 October 2018 01:00 PM, Ulf Hansson wrote: >> On 4 October 2018 at 13:14, Faiz Abbas wrote: >>> The current arasan sdhci PHY configuration isn't compatible >>> with the PHY on TI's AM654 devices. >>> >>> Therefore, add a ne

Re: [tip:x86/urgent] x86/mm: Avoid VLA in pgd_alloc()

Hi Arnd, On Tue, Oct 09, 2018 at 09:33:56AM +0200, Arnd Bergmann wrote: > Ah, cool, thanks for the analysis. Is the patch already reverted? > I.e. should I send a replacement patch, or a relative fix, or is > someone else already on it? Kees sent a fix which is already in tip-tree: https

Re: [alsa-devel] [PATCH linux-next v2 9/9] ASoC: rsnd: add busif property to dai stream

Hi Jiada Thanks for your feedback > 1ch:  (tdm_slots < 4) Basic mode, (tdm_slots >= 4) TDM Split mode > 2ch: (2 <= tdm_slots < 8) Basic mode, (tdm_slots >= 8) TDM Ex-Split mode > 4ch: (4 <= tdm_slots < 8) Basic mode, (tdm_slots >= 8) TDM Ex-Split mode > 6ch: (6 <= tdm_slots < 8) Basic mode, (td

Re: [PATCH] cpufreq: conservative: Fix requested_freq handling

On Mon, Oct 8, 2018 at 5:11 PM Waldemar Rymarkiewicz wrote: > > From: Waldemar Rymarkiewicz > > The governor updates dbs_info->requested_freq only after increasing or > decreasing frequency. There is, however, an use case when this is not > sufficient. > > Imagine, external module constraining cp

Re: [PATCH v4 2/2] phy: zynqmp: Add phy driver for xilinx zynqmp phy core

Hi Anurag, On Wednesday 12 September 2018 09:52 PM, Anurag Kumar Vulisha wrote: > ZynqMP SoC has a Gigabit Transceiver with four lanes. All the high speed > peripherals such as USB, SATA, PCIE, Display Port and Ethernet SGMII can > rely on any of the four GT lanes for PHY layer. This patch adds dr

Re: [tip:x86/urgent] x86/mm: Avoid VLA in pgd_alloc()

* Joerg Roedel wrote: > Hi Arnd, > > On Tue, Oct 09, 2018 at 09:33:56AM +0200, Arnd Bergmann wrote: > > Ah, cool, thanks for the analysis. Is the patch already reverted? > > I.e. should I send a replacement patch, or a relative fix, or is > > someone else already on it? > > Kees sent a fix wh

Re: [PATCH] mm, oom_adj: avoid meaningless loop to find processes sharing mm

On Tue 09-10-18 08:35:41, Michal Hocko wrote: > [I have only now noticed that the patch has been reposted] > > On Mon 08-10-18 18:27:39, Tetsuo Handa wrote: > > On 2018/10/08 17:38, Yong-Taek Lee wrote: [...] > > > Thank you for your suggestion. But i think it would be better to seperate > > > to

Re: [RESEND PATCH v2 3/3] ARM: dts: imx28-cfa10036: Fix the reset gpio signal polarity

On 10/09/2018 02:20 AM, Shawn Guo wrote: > On Mon, Oct 08, 2018 at 11:45:36AM +, Vokáč Michal wrote: >> On 27.9.2018 11:24, Michal Vokáč wrote: >>> The reset signal of the SSD1306 OLED display is actually active-low. >>> Adapt the DT to reflect the real world. >>> >>> Signed-off-by: Michal Vo

Re: [PATCH 2/2] mmc: Add mmc_force_detect_change_begin / _end functions

Hi Frieder, On Mon, Oct 08, 2018 at 11:53:21AM +0200, Frieder Schrempf wrote: > Hi, > > On 27.09.2018 10:14, Maxime Ripard wrote: > > On Wed, Sep 26, 2018 at 10:19:22PM +0200, Hans de Goede wrote: > > > On 26-09-18 16:44, Frieder Schrempf wrote: > > > > Hi, > > > > > > > > On Fri, Feb 09, 2018 a

Re: [PATCH V6 00/23] mmc: mmci: add sdmmc variant for stm32

hi Ulf On 10/09/2018 09:30 AM, Ulf Hansson wrote: Applied for next, thanks! FYI, I made little fixup of the help text in the Kconfig for the last patch. Thanks for your review. Did you had a feedback on Qcom platform tests? Kind regards Uffe

Re: [RESEND PATCH v3 0/3] sh: make early_platform code SuperH-specific

czw., 20 wrz 2018 o 18:48 Daniel Lezcano napisał(a): > > On 20/09/2018 18:19, Bartosz Golaszewski wrote: > > 2018-09-20 18:09 GMT+02:00 Daniel Lezcano : > >> On 20/09/2018 15:00, Bartosz Golaszewski wrote: > >> > >> [ ... ] > >> > >>> Ping for 4.20. This is the third release cycle I'm trying to ge

Re: [tip:x86/urgent] x86/mm: Avoid VLA in pgd_alloc()

On Tue, Oct 9, 2018 at 9:03 AM tip-bot for Kees Cook wrote: > > Commit-ID: 184d47f0fd365108bd06ab26cdb3450b716269fd > Gitweb: > https://git.kernel.org/tip/184d47f0fd365108bd06ab26cdb3450b716269fd > Author: Kees Cook > AuthorDate: Mon, 8 Oct 2018 16:54:34 -0700 > Committer: Ingo Molnar

[PATCH] media: venus: amend buffer size for bitstream plane

For lower resolutions, incase of encoder, the compressed frame size is more than half of the corresponding input YUV. Keep the size as same as YUV considering worst case. Signed-off-by: Malathi Gottam --- drivers/media/platform/qcom/venus/helpers.c | 2 +- 1 file changed, 1 insertion(+), 1 delet

[PATCH] media: venus: add support for USERPTR to queue

Add USERPTR to queue access methods by adding this support to io_modes on both the planes. Signed-off-by: Malathi Gottam --- drivers/media/platform/qcom/venus/venc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/media/platform/qcom/venus/venc.c b/drivers/media/

Re: Re: [PATCH] mm, oom_adj: avoid meaningless loop to find processes sharing mm

On Mon 08-10-18 17:38:55, Yong-Taek Lee wrote: > Do you have any other idea to avoid meaningless loop ? I have already asked in the earlier posting but let's follow up here. Could you please expand on why this actually matters and what are the consequences please? -- Michal Hocko SUSE Labs

linux-next: Tree for Oct 9

Hi all, Changes since 20181008: The s390 tree gained a conflict against the compiler-attributes tree. The ext4 tree gained a build failure for which I reverted a commit. The nfsd tree lost its build failure. The crypto tree lost its build failure. The net-next tree gained a conflict against t

Re: [PATCH] mm, oom_adj: avoid meaningless loop to find processes sharing mm

On Tue 09-10-18 08:23:30, Michal Hocko wrote: > [Cc Oleg] JFYI there was new submission http://lkml.kernel.org/r/20181008011931epcms1p82dd01b7e5c067ea99946418bc97de46a@epcms1p8 > > On Fri 05-10-18 15:32:08, Yong-Taek Lee wrote: > > It is introduced by commit 44a70adec910 ("mm, oom_adj: make sure

Re: [PATCH 1/7] clocksource: exynos_mct: Remove dead code

On Mon, 8 Oct 2018 at 14:50, Marek Szyprowski wrote: > > Exynos Multi-Core Timer driver is used only on device-tree based > systems, so remove non-dt related code. You can also mention that in case of !CONFIG_OF the code is anyway equal because of_irq_count() has a stub returning 0. Reviewed-by:

Re: [PATCH v2 2/2] HID: google: add support tablet mode switch for Whiskers

On Fri, Oct 5, 2018 at 8:41 PM Dmitry Torokhov wrote: > > Whiskers is a foldable base, and thus requires combining "base presence" > signal coming from EC with base state signal (folded/unfolded) coming > from USB/HID interface to produce proper SW_TABLET_MODE event. > > Signed-off-by: Nicolas Boi

Re: [RFC][PATCH 1/3] printk: keep kernel cont support always enabled

On Tue 2018-10-02 11:38:34, Sergey Senozhatsky wrote: > Since 5c2992ee7fd8a29 ("printk: remove console flushing special > cases for partial buffered lines") we don't print cont fragments > to the consoles; cont lines are now proper log_buf entries and > there is no "consecutive continuation flag" a

Re: [PATCH V10 1/8] irqchip: add C-SKY SMP interrupt controller

On 09/10/18 03:24, Guo Ren wrote: Hi Marc, On Mon, Oct 08, 2018 at 05:35:19PM +0100, Marc Zyngier wrote: Hi Guo, On 04/10/18 18:22, Guo Ren wrote: - Irq-csky-mpintc is C-SKY smp system interrupt controller and it could support 16 soft irqs, 16 private irqs, and 992 max common irqs.

Re: [PATCH v3 3/7] dt-bindings: stm32-mdma: Add DMA/MDMA chaining support bindings

On 10/07/2018 04:59 PM, Vinod wrote: > On 28-09-18, 15:01, Pierre-Yves MORDRET wrote: >> From: M'boumba Cedric Madianga >> >> This patch adds the description of the 2 properties needed to support M2M >> transfer triggered by STM32 DMA when his transfer is complete. >> >> Signed-off-by: Pierre-Y

Re: [PATCH 2/7] clocksource: exynos_mct: Add arch_timer cooperation mode for ARM64

On Mon, 8 Oct 2018 at 14:50, Marek Szyprowski wrote: > > To get ARM Architected Timers working on Samsung Exynos SoCs, one has to > first configure and enable Exynos Multi-Core Timer, because they both > share some common hardware blocks. This patch adds a mode of cooperation > with arch_timer dri

Re: [PATCH 3/7] clocksource: Change CPU hotplug priority of exynos_mct driver

On Mon, 8 Oct 2018 at 14:50, Marek Szyprowski wrote: > > Exynos Multi-Core Timer driver (exynos_mct) must be started before > ARM Architected Timers (arch_timer), because both timers share common > hardware block and turning on MCT is needed to get ARM Architected > Timer working properly. > > Sig

Re: [RESEND PATCH v2 3/3] ARM: dts: imx28-cfa10036: Fix the reset gpio signal polarity

On 9.10.2018 09:51, Bartlomiej Zolnierkiewicz wrote: > > On 10/09/2018 02:20 AM, Shawn Guo wrote: >> On Mon, Oct 08, 2018 at 11:45:36AM +, Vokáč Michal wrote: >>> On 27.9.2018 11:24, Michal Vokáč wrote: The reset signal of the SSD1306 OLED display is actually active-low. Adapt the DT

Re: [PATCH 0/2] arm64: dts: meson: s400: emmc updates

Jerome Brunet writes: > This patchset adds the emmc pwrseq to the emmc node and disable the device > by default, since eMMC is not the default option for this board. > > Jerome Brunet (2): > arm64: dts: meson-axg: s400: add missing emmc pwrseq > arm64: dts: meson-axg: s400: disable emmc Appl

Re: [PATCH v4 2/3] mm: introduce put_user_page*(), placeholder versions

On Mon 08-10-18 17:14:42, Andrew Morton wrote: > On Mon, 8 Oct 2018 14:16:22 -0700 john.hubb...@gmail.com wrote: > > + put_user_page(pages[index]); > > + } > > +} > > + > > +static inline void put_user_pages(struct page **pages, > > + unsigned long npages) >

Re: [Patch] sched/fair: Avoid throttle_list starvation with low cfs quota

I've Cc:-ed a handful of gents who worked on CFS bandwidth details to widen the discussion. Patch quoted below. Looks like a real bug that needs to be fixed - and at first sight the quota of 1000 looks very low - could we improve the arithmetics perhaps? A low quota of 1000 is used because

Re: [RFC PATCH] mm, proc: report PR_SET_THP_DISABLE in proc

On Thu 04-10-18 11:34:11, David Rientjes wrote: > On Thu, 4 Oct 2018, Michal Hocko wrote: > > > > And prior to the offending commit, there were three ways to control thp > > > but two ways to determine if a mapping was eligible for thp based on the > > > implementation detail of one of those way

[PATCH v10 4/5] clk: imx: add imx composite clock

Since a lot of clocks on imx8m are formed by a mux, gate, predivider and divider, the idea here is to combine all of those into one composite clock, but we need to deal with both predivider and divider at the same time and therefore we add the imx_clk_composite_8m_divider_ops and register the compo

[PATCH v10 0/5] Add i.MX8MQ clock driver

Changes since v9: * Replaced DIV_ROUND_UP_ULL with DIV_ROUND_UP * Renamed the entire composite to composite-8m Abel Vesa (1): clk: imx: add imx composite clock Lucas Stach (4): dt-bindings: add binding for i.MX8MQ CCM clk: imx: add fractional PLL output clock clk: imx: add SCCG PLL type

[PATCH v10 2/5] clk: imx: add fractional PLL output clock

From: Lucas Stach This is a new clock type introduced on i.MX8. Signed-off-by: Lucas Stach Signed-off-by: Abel Vesa Reviewed-by: Sascha Hauer --- drivers/clk/imx/Makefile | 1 + drivers/clk/imx/clk-frac-pll.c | 215 + drivers/clk/imx/clk.h

[PATCH v10 3/5] clk: imx: add SCCG PLL type

From: Lucas Stach The SCCG is a new PLL type introduced on i.MX8. Add support for this. The driver currently misses the PLL lock check, as the preliminary documentation mentions lock configurations, but is quiet about where to find the actual lock status signal. Signed-off-by: Lucas Stach Signe

[PATCH v10 1/5] dt-bindings: add binding for i.MX8MQ CCM

From: Lucas Stach This adds the binding for the i.MX8MQ Clock Controller Module. Signed-off-by: Lucas Stach Signed-off-by: Abel Vesa Reviewed-by: Rob Herring --- .../devicetree/bindings/clock/imx8mq-clock.txt | 20 ++ include/dt-bindings/clock/imx8mq-clock.h | 395

[PATCH v10 5/5] clk: imx: add clock driver for i.MX8MQ CCM

From: Lucas Stach Add driver for the Clock Control Module found on i.MX8MQ. This is largely based on the downstream driver from Anson Huang and Bai Ping at NXP, plus the imx composite clock from Abel Vesa at NXP, with only some small adaptions to mainline from me. Signed-off-by: Lucas Stach Si

Re: [RFC][PATCH 2/3] printk: lock/unlock console only for new logbuf entries

On Tue 2018-10-02 11:38:35, Sergey Senozhatsky wrote: > From: Sergey Senozhatsky > > Prior to 5c2992ee7fd8a29 ("printk: remove console flushing special > cases for partial buffered lines") we would do console_cont_flush() > for each pr_cont() to print cont fragments, so console_unlock() would > a

Re: [PATCH v2 1/2] mfd: cros: add "base attached" MKBP switch definition

On Mon, 8 Oct 2018, Lee Jones wrote: > > This adds a "base attached" switch definition to the MKBP protocol that > > is used by Whiskers driver to properly determine device state (clamshell > > vs tablet mode). > > > > Signed-off-by: Dmitry Torokhov > > --- > > > > v2 changes: None > > > > Lee

Re: [RFC][PATCH 3/3] printk: do not preliminary split up cont buffer

On Tue 2018-10-02 11:38:36, Sergey Senozhatsky wrote: > We have a proper 'overflow' check which tells us that we need to > split up existing cont buffer in separate records: > > if (cont.len + len > sizeof(cont.buf)) > cont_flush(); > > At the same time we also have one extra

Re: [PATCH v3 4/7] dmaengine: stm32-dma: Add DMA/MDMA chaining support

On 10/07/2018 06:00 PM, Vinod wrote: > On 28-09-18, 15:01, Pierre-Yves MORDRET wrote: >> This patch adds support of DMA/MDMA chaining support. >> It introduces an intermediate transfer between peripherals and STM32 DMA. >> This intermediate transfer is triggered by SW for single M2D transfer and

Re: [PATCH 02/12] perf auxtrace: Include missing asm/bitsperlong.h to get BITS_PER_LONG

Hi! On 09/10/2018 02:54, Arnaldo Carvalho de Melo wrote: > From: Arnaldo Carvalho de Melo > > The auxtrace.h header references BITS_PER_LONG without including the > header where it is defined, getting it by luck from some other header, > fix it. > > Cc: Adrian Hunter > Cc: Alexander Sverdlin

[PATCH v12 0/3]: perf: reduce data loss when profiling highly parallel CPU bound workloads

Currently in record mode the tool implements trace writing serially. The algorithm loops over mapped per-cpu data buffers and stores ready data chunks into a trace file using write() system call. At some circumstances the kernel may lack free space in a buffer because the other buffer's half

[PATCH] HID: google: drop superfluous const before SIMPLE_DEV_PM_OPS()

From: Jiri Kosina SIMPLE_DEV_PM_OPS() already implies const for the type; drop the extra modifier. Fixes: eb1aac4c8744f75460c34d71b0c73bebf3e8ee5c ("HID: google: add support tablet mode switch for Whiskers") Signed-off-by: Jiri Kosina --- In hid.git#for-4.20/google drivers/hid/hid-google-h

Re: [PATCH 01/12] tools include: Adopt linux/bits.h

Hello Arnaldo, On 09/10/2018 02:54, Arnaldo Carvalho de Melo wrote: > From: Arnaldo Carvalho de Melo > > So that we reduce the difference of tools/include/linux/bitops.h to the > original kernel file, include/linux/bitops.h, trying to remove the need > to define BITS_PER_LONG, to avoid clashes w

Re: [PATCH v1 00/11] Continuing the work on coupled regulators

On 10/8/18 8:58 PM, Tony Lindgren wrote: > * Dmitry Osipenko [181005 15:43]: >> 1. Re-worked the original "Add voltage balancing mechanism" patch from >>Maciej by: >> 1) Fixing infinite loop within regulator_balance_voltage(). >> 2) Handling suspend_state_t properly. >>

[PATCH] regulator: stpmic1: Return REGULATOR_MODE_INVALID for invalid mode

-EINVAL is not a valid return value for .of_map_mode, return REGULATOR_MODE_INVALID instead. Signed-off-by: Axel Lin --- drivers/regulator/stpmic1_regulator.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/regulator/stpmic1_regulator.c b/drivers/regulator/stpmic1_re

Re: general protection fault in __handle_mm_fault

Willem de Bruijn writes: > On Mon, Oct 8, 2018 at 12:10 PM Willem de Bruijn > wrote: >> >> On Fri, Oct 5, 2018 at 6:27 PM syzbot >> wrote: >> > >> > Hello, >> > >> > syzbot found the following crash on: >> > >> > HEAD commit:25bcda3e8b9f Add linux-next specific files for 20181004 >> > git t

Re: [PATCH 1/3] mfd: ti-lmu: switch to gpiod

On Tue, 11 Sep 2018, Pavel Machek wrote: > Use new descriptor based API instead of the legacy one. > > Signed-off-by: Sebastian Reichel > Signed-off-by: Pavel Machek Applied, thanks. -- Lee Jones [李琼斯] Linaro Services Technical Lead Linaro.org │ Open source software for ARM SoCs Follow L

Re: [PATCH 2/3] mfd: ti-lmu: use managed resource for everything

On Tue, 11 Sep 2018, Pavel Machek wrote: > This replaces all remaining unmanaged resources with device > managed ones, so that the remove function is no longer needed. > This makes the code slightly shorter and fixes two problems: > > 1. The hardware is disabled after the child devices have

Re: [PATCH 3/3] mfd: ti-lmu: use of_device_get_match_data() helper

On Tue, 11 Sep 2018, Pavel Machek wrote: > Replace of_match_device() with of_device_get_match_data(), which > slightly decreases lines of code and allows to move the DT table > next to the I2C table. > > Signed-off-by: Sebastian Reichel > Signed-off-by: Pavel Machek Not sure how you're sen

[PATCH v12 1/3] perf util: map data buffer for preserving collected data

The map->data buffer is used to preserve map->base profiling data for writing to disk. AIO map->cblock is used to queue corresponding map->data buffer for asynchronous writing. Signed-off-by: Alexey Budankov --- Changes in v12: - applied stub functions design for the whole patch kit - group

Re: [PATCH v3 1/7] dt-bindings: stm32-dma: Add DMA/MDMA chaining support bindings

Hi Pierre, On 09-10-18, 09:18, Pierre Yves MORDRET wrote: > >> * DMA client > >> @@ -68,7 +84,16 @@ channel: a phandle to the DMA controller plus the > >> following four integer cells: > >>0x1: 1/2 full FIFO > >>0x2: 3/4 full FIFO > >>0x3: full FIFO > >> - > >> + -bit 2: Intermediat

[PATCH v12 2/3]: perf record: enable asynchronous trace writing

Trace file offset is read once before mmaps iterating loop and written back after all performance data enqueued for aio writing. Trace file offset is incremented linearly after every successful aio write operation. record__aio_sync() blocks till completion of started AIO operation and then pr

[PATCH v12 3/3]: perf record: extend trace writing to multi AIO

Multi AIO trace writing allows caching more kernel data into userspace memory postponing trace writing for the sake of overall profiling data thruput increase. It could be seen as kernel data buffer extension into userspace memory. With aio-cblocks option value different from 0, current defaul

RE: [POC][RFC][PATCH 1/2] jump_function: Addition of new feature "jump_function"

From: Masami Hiramatsu > Sent: 09 October 2018 04:44 ... > I think we can replace the first 5 bytes of the default function > to jmp instruction (to alternative function) instead of making > this trampoline. Or have a trampoline that is just a jump instruction and overwrite the target address at r

Re: [PATCH v12 0/6] Driver for at91 usart in spi mode

On Wed, 12 Sep 2018, Radu Pirea wrote: > On Wed, 2018-09-12 at 14:12 +0100, Lee Jones wrote: > > 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 > > > >

Re: [BUG] mfd: ezx-pcap: Possible sleep-in-atomic-context bugs in pcap_adc_irq()

On Mon, 17 Sep 2018, Jia-Ju Bai wrote: > > > On 2018/9/17 9:03, Lee Jones wrote: > > On Sat, 15 Sep 2018, Jia-Ju Bai wrote: > > > > > The driver may sleep in an interrupt handler. > > > The function call paths (from bottom to top) in Linux-4.17 are: > > > > > > [FUNC] mutex_lock_nested > > > d

Re: linux-next: manual merge of the staging tree with the vfs tree

On Tue, Oct 09, 2018 at 03:59:45PM +1100, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the staging tree got a conflict in: > > drivers/staging/dgnc/dgnc_tty.c > > between commits: > > b68166ef8fd9 ("dgnc: leave TIOC[GS]SOFTCAR to ldisc") > e002c6f1ccb9 ("dgnc: don't b

Re: [PATCH 4.18 000/168] 4.18.13-stable review

On Tue, Oct 09, 2018 at 05:21:31AM +0200, Andre Tomt wrote: > On 08. okt. 2018 20:29, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.18.13 release. > > There are 168 patches in this series, all will be posted as a response > > to this one. If anyone has any is

Re: [PATCH 4.4 093/113] pinctrl: msm: Really mask level interrupts to prevent latching

On Mon, Oct 08, 2018 at 11:33:38PM -0700, Nathan Chancellor wrote: > On Mon, Oct 08, 2018 at 08:31:34PM +0200, Greg Kroah-Hartman wrote: > > 4.4-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Stephen Boyd > > > > [ Upstream commi

Re: 4.19-rcX: WARN_ON() arch/arm64/kernel/setup.c:271 reserve_memblock_reserved_regions

On Mon, Oct 08, 2018 at 05:03:27PM +0100, James Morse wrote: > But! DT's that have this reserved-but-not-memory are already out there, so we > should work around this in the kernel. Ack, thanks for the explanation. -- bye, p.

[RFD/RFC PATCH 1/8] locking/mutex: Convert mutex::wait_lock to raw_spinlock_t

From: Peter Zijlstra In preparation to nest mutex::wait_lock under rq::lock it needs to be raw_spinlock_t. Signed-off-by: Peter Zijlstra --- include/linux/mutex.h| 4 ++-- kernel/locking/mutex-debug.c | 4 ++-- kernel/locking/mutex.c | 22 +++--- 3 files changed

[RFD/RFC PATCH 0/8] Towards implementing proxy execution

Hi all, Proxy Execution (also goes under several other names) isn't a new concept, it has been mentioned already in the past to this community (both in email discussions and at conferences [1, 2]), but no actual implementation that applies to a fairly recent kernel exists as of today (of which I'm

[RFD/RFC PATCH 3/8] locking/mutex: Rework task_struct::blocked_on

From: Peter Zijlstra Track the blocked-on relation for mutexes, this allows following this relation at schedule time. Add blocked_task to track the inverse relation. ,-> task | | blocked-on | v blocked-task | mutex |

[RFD/RFC PATCH 6/8] locking/mutex: make mutex::wait_lock irq safe

mutex::wait_lock might be nested under rq->lock. Make it irq safe then. Signed-off-by: Juri Lelli --- kernel/locking/mutex.c | 23 +-- 1 file changed, 13 insertions(+), 10 deletions(-) diff --git a/kernel/locking/mutex.c b/kernel/locking/mutex.c index 23312afa7fca..c16cb844

[RFD/RFC PATCH 4/8] sched: Split scheduler execution context

From: Peter Zijlstra Lets define the scheduling context as all the scheduler state in task_struct and the execution context as all state required to run the task. Currently both are intertwined in task_struct. We want to logically split these such that we can run the execution context of one tas

[RFD/RFC PATCH 2/8] locking/mutex: Removes wakeups from under mutex::wait_lock

From: Peter Zijlstra In preparation to nest mutex::wait_lock under rq::lock we need to remove wakeups from under it. Signed-off-by: Peter Zijlstra (Intel) [Heavily changed after 55f036ca7e74 ("locking: WW mutex cleanup") and 08295b3b5bee ("locking: Implement an algorithm choice for Wound-Wait m

[RFD/RFC PATCH 7/8] sched: Ensure blocked_on is always guarded by blocked_lock

blocked_on pointer might be concurrently modified by schedule() (when proxy() is called) and by wakeup path, so we need to guard changes. Ensure blocked_lock is always held before updating blocked_on pointer. Signed-off-by: Juri Lelli --- kernel/locking/mutex-debug.c | 1 + kernel/locking/mute

[RFD/RFC PATCH 5/8] sched: Add proxy execution

From: Peter Zijlstra A task currently holding a mutex (executing a critical section) might find benefit in using scheduling contexts of other tasks blocked on the same mutex if they happen to have higher priority of the current owner (e.g., to prevent priority inversions). Proxy execution lets a

[RFD/RFC PATCH 8/8] sched: Fixup task CPUs for potential proxies.

When a mutex owner with potential proxies wakes up those proxies are activated as well, on the same CPU of the owner. They might have been sleeping on a different CPU however. Fixup potential proxies CPU at wakeup time before activating them (or they get woken up with a wrong CPU reference). Sign

Re: [PATCH 4.9 00/59] 4.9.132-stable review

On Mon, Oct 08, 2018 at 06:30:07PM -0700, Nathan Chancellor wrote: > On Mon, Oct 08, 2018 at 08:31:07PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.132 release. > > There are 59 patches in this series, all will be posted as a response > > to this on

Re: [PATCH 4.14 66/94] dm thin metadata: try to avoid ever aborting transactions

On Mon, Oct 08, 2018 at 08:45:57PM +0100, Sudip Mukherjee wrote: > HI Greg, > > On Mon, Oct 8, 2018 at 8:06 PM Greg Kroah-Hartman > wrote: > > > > 4.14-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Joe Thornber > > > > [ Upstream

[tip:x86/hyperv] x86/hyperv: Enable PV qspinlock for Hyper-V

Commit-ID: b36bcb7ce0b353bd4889e06b61e036744b02ca51 Gitweb: https://git.kernel.org/tip/b36bcb7ce0b353bd4889e06b61e036744b02ca51 Author: Yi Sun AuthorDate: Mon, 8 Oct 2018 16:29:34 +0800 Committer: Thomas Gleixner CommitDate: Tue, 9 Oct 2018 11:26:31 +0200 x86/hyperv: Enable PV qspinloc

  1   2   3   4   5   6   7   8   >