Re: [PATCH v2 1/3] usb: roles: intel_xhci: Always allow user control

On Wed, May 23, 2018 at 08:03:43PM +0200, Hans de Goede wrote: > Hi, > > On 23-05-18 16:37, Heikki Krogerus wrote: > > Trying to determine the USB port type with this mux is very > > difficult. To simplify the situation, always allowing user > > control, even if the port is USB Type-C port. > >

Re: [PATCH v2 1/5] PCI/AER: Define and allocate aer_stats structure for AER capable devices

On Wed, May 23, 2018 at 10:58:04AM -0700, Rajat Jain wrote: > --- > v2: Fix the license header as per Greg's suggestions > (Since there is disagreement with using "//" vs "/* */" for license > I decided to keep the one preferred by Linus, also used by others > in this directory) The

[PATCH 9/9] regulator: bd71837: Build BD71837 regulator driver

Configurations and Makefile for BD71837 regulator driver Signed-off-by: Matti Vaittinen --- drivers/regulator/Kconfig | 11 +++ drivers/regulator/Makefile | 1 + 2 files changed, 12 insertions(+) diff --git a/drivers/regulator/Kconfig

[PATCH 7/9] clk: bd71837: Build ROHM BD71837 PMIC clock driver

Configuration options and Makefile for BD71837 clock driver Signed-off-by: Matti Vaittinen --- drivers/clk/Kconfig | 9 + drivers/clk/Makefile | 1 + 2 files changed, 10 insertions(+) diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig index

Re: [PATCH v2 1/3] usb: roles: intel_xhci: Always allow user control

On Wed, May 23, 2018 at 07:10:58PM +0300, Sergei Shtylyov wrote: > On 05/23/2018 05:37 PM, Heikki Krogerus wrote: > > > Trying to determine the USB port type with this mux is very > > difficult. To simplify the situation, always allowing user > >s/allowing/allow/? Else the statement doesn't

Re: [PATCH v2 11/29] venus: venc,vdec: adds clocks needed for venus 4xx

Hi Stanimir, On Tue, May 15, 2018 at 5:10 PM Stanimir Varbanov < stanimir.varba...@linaro.org> wrote: > This extends the clocks number to support suspend and resume > on Venus version 4xx. > Signed-off-by: Stanimir Varbanov > --- >

[PATCH 8/9] regulator: bd71837: BD71837 PMIC regulator driver

Support for controlling the 8 bucks and 7 LDOs the PMIC contains. Signed-off-by: Matti Vaittinen --- drivers/regulator/bd71837-regulator.c | 683 ++ 1 file changed, 683 insertions(+) create mode 100644

[PATCH 6/9] clk: bd71837: Add driver for BD71837 PMIC clock

Support BD71837 gateable 32768 Hz clock. Signed-off-by: Matti Vaittinen --- drivers/clk/clk-bd71837.c | 155 ++ 1 file changed, 155 insertions(+) create mode 100644 drivers/clk/clk-bd71837.c diff --git

Re: [PATCH 0/5] mm: rework hmm to use devm_memremap_pages

On Wed, May 23, 2018 at 08:18:11PM -0700, Dan Williams wrote: > On Wed, May 23, 2018 at 5:10 PM, Jerome Glisse wrote: > > On Mon, May 21, 2018 at 03:35:14PM -0700, Dan Williams wrote: > >> Hi Andrew, please consider this series for 4.18. > >> > >> For maintainability, as

[PATCH v7 1/4] ARM: dts: tegra: Remove usage of deprecated skeleton.dtsi

Remove the usage of skeleton.dtsi because it was deprecated since commit 9c0da3cc61f1 ("ARM: dts: explicitly mark skeleton.dtsi as deprecated"). It also allows later to fix DTC warnings for missing unit name in /memory nodes. The /chosen and /aliases nodes are added only when dependent DTSes do

Re: [PATCH] cpuidle/powernv : init all present cpus for deep states

On Wed, May 16, 2018 at 05:32:14PM +0530, Akshay Adiga wrote: > Init all present cpus for deep states instead of "all possible" cpus. > Init fails if the possible cpu is gaurded. Resulting in making only > non-deep states available for cpuidle/hotplug. > > Signed-off-by: Akshay Adiga

[PATCH v7 3/4] ARM: dts: tegra: Fix unit_address_vs_reg and avoid_unnecessary_addr_size DTC warnings

Remove unneeded address/size cells properties and unit addresses to fix DTC warnings like: arch/arm/boot/dts/tegra30-apalis-eval.dtb: Warning (unit_address_vs_reg): /i2c@7000d000/stmpe811@41/stmpe_touchscreen@0: node has a unit name, but no reg property

[PATCH] cpufreq: reinitialize new policy min/max when writing scaling_(max|min)_freq

consider such situation, current user_policy.min is 100, current user_policy.max is 120, in cpufreq_set_policy, other driver may update policy.min to 120, policy.max to 130. After that, If we input "echo 130 > scaling_min_freq", then user_policy.min will be 130, and

Re: [PATCH 8/9] PM / Domains: Add support for multi PM domains per device to genpd

On 23 May 2018 at 11:07, Jon Hunter wrote: > > On 23/05/18 07:12, Ulf Hansson wrote: > > ... > > >> Thanks for sending this. Believe it or not this has still been on my >> to-do list >> and so we definitely need a solution for Tegra. >> >> Looking at the

Re: [PATCH 1/5] dt-bindings: pinctrl: document the STMFX pinctrl bindings

On Fri, May 18, 2018 at 9:29 AM, Amelie DELAUNAY wrote: > On 05/17/2018 08:36 AM, Lee Jones wrote: >> On Wed, 16 May 2018, Amelie DELAUNAY wrote: >>> On 05/16/2018 04:20 PM, Linus Walleij wrote: On Wed, May 9, 2018 at 9:56 AM, Amelie DELAUNAY

Re: [PATCH 3/3] sched/fair: add tracepoints for cfs throttle

On Wed, May 23, 2018 at 09:40:47PM -0700, Cong Wang wrote: > On Wed, May 23, 2018 at 2:09 AM, Peter Zijlstra wrote: > > Yeah, don't worry. I hate tracepoints, I regret the existing ones, no > > new ones will happen. > > No matter you hate them or not, they are useful: No

Re: [PATCH 3/8] md: raid5: use refcount_t for reference counting instead atomic_t

On Wed, May 23, 2018 at 12:22:39PM -0700, Shaohua Li wrote: > I don't know what is changed in the refcount, such raid5 change has attempted > before and didn't work. 0 for the stripe count is a valid usage and we do > inc-from-zero in several places. Nothing much has changed with refcount; and

[PATCH V2] thermal: qcom-spmi-temp-alarm: add support for GEN2 PMIC peripherals

From: David Collins Add support for the TEMP_ALARM GEN2 PMIC peripheral subtype. The GEN2 subtype defines an over temperature state with hysteresis instead of stage in the status register. There are two GEN2 states corresponding to stages 1 and 2. Signed-off-by: David

Re: [PATCH V4] mlx4_core: allocate ICM memory in page size chunks

On Thu, May 24, 2018 at 1:22 AM, Qing Huang wrote: > When a system is under memory presure (high usage with fragments), > the original 256KB ICM chunk allocations will likely trigger kernel > memory management to enter slow path doing memory compact/migration > ops in order

Re: [PATCH v3] dma-debug: Check scatterlist segments

Thanks Robin, applied to the dma-mapping tree.

Re: [PATCH v9 3/4] arm64: Implement page table free interfaces

On 5/23/2018 7:31 PM, Will Deacon wrote: Hi Chintan, Hi Will, [as a side note: I'm confused on the status of this patch series, as part of it was reposted separately by Toshi. Please can you work together?] I will share all 4 patches once again as v10 and take latest version of 1/4 as

Re: [PATCH v3] usbip: dynamically allocate idev by nports found in sysfs

On Wed, May 23, 2018 at 10:44:57AM -0600, Shuah Khan wrote: > On 05/23/2018 03:22 AM, Michael Grzeschik wrote: > > As the amount of available ports varies by the kernels build > > configuration. To remove the limitation of the fixed 128 ports > > we allocate the amount of idevs by using the number

Re: [PATCH v1 6/7] MAINTAINERS: update entry for PIN CONTROLLER - MEDIATEK

On Sun, May 20, 2018 at 7:01 PM, wrote: > From: Sean Wang > > Add new files for the entry > > Signed-off-by: Sean Wang Patch applied. Yours, Linus Walleij

Re: [PATCH v1 7/7] arm64: dts: mt7622: add EINT support to pinctrl

On Sun, May 20, 2018 at 7:01 PM, wrote: > From: Sean Wang > > Add EINT support to pinctrl and set those GPIO keys as interrupt-driven > keys. > > Signed-off-by: Sean Wang Acked-by: Linus Walleij

Re: [PATCH] cpufreq: reinitialize new policy min/max when writing scaling_(max|min)_freq

On Thu, May 24, 2018 at 8:43 AM, Kevin Wangtao wrote: > consider such situation, current user_policy.min is 100, > current user_policy.max is 120, in cpufreq_set_policy, > other driver may update policy.min to 120, policy.max to > 130. After that, If

Re: [RESEND PATCH 2/5] mtd: rawnand: add NVIDIA Tegra NAND Flash controller driver

Hi Stefan (and all), First off, I apoloigize in advance if I'm deviating from common kernel mailing list courtesy -- this is my first time responding. I just have a comment on the NAND driver that I'd like to bring to the public. > + switch (mtd->oobsize) { > ... > + case 224: > +

Re: [PATCH v2 4/7] Bluetooth: Add new quirk for non-persistent setup settings

Hi Sean, [ ... ] >> -if (hci_dev_test_flag(hdev, HCI_SETUP)) { >> +if (hci_dev_test_flag(hdev, HCI_SETUP) || >> +test_bit(HCI_QUIRK_NON_PERSISTENT_SETUP, >quirks)) { >> hci_sock_dev_event(hdev, HCI_DEV_SETUP); > > I am

Re: [PATCH v1 00/10] mm: online/offline 4MB chunks controlled by device driver

I've had some questions before and I am not sure they are fully covered. At least not in the cover letter (I didn't get much further yet) which should give us a highlevel overview of the feature. On Wed 23-05-18 17:11:41, David Hildenbrand wrote: > This is now the !RFC version. I did some

Re: [PATCH v2 2/4] drm/mediatek: Add support for mediatek SOC MT2712

Hi CK, On Thu, 2018-05-24 at 09:26 +0800, CK Hu wrote: > Hi, Stu: > > On Wed, 2018-05-23 at 17:28 +0800, Stu Hsieh wrote: > > On Wed, 2018-05-23 at 13:23 +0800, CK Hu wrote: > > > Hi, Stu: > > > > > > I've some inline comment. > > > > > > On Wed, 2018-05-23 at 10:25 +0800, Stu Hsieh wrote: > >

Re: WARNING in ip_recv_error

On Wed, 2018-05-23 at 11:40 -0400, Willem de Bruijn wrote: > On Sun, May 20, 2018 at 7:13 PM, Willem de Bruijn > wrote: > > On Fri, May 18, 2018 at 2:59 PM, Willem de Bruijn > > wrote: > > > On Fri, May 18, 2018 at 2:46 PM, Willem

Re: [PATCH 3/6] block: Create scsi_sense.h for SCSI and ATAPI

On Wed, May 23, 2018 at 03:14:19PM -0600, Jens Axboe wrote: > Ugh, so that would necessitate a change there too. As I said before, > I don't really care where it lives. I know the SCSI folks seem bothered > by moving it, but in reality, it's not like this stuff will likely ever > really change. Of

Re: [PATCH 1/5] pinctrl: at91-pio4: add missing of_node_put

On Wed, May 23, 2018 at 09:07:12PM +0200, Julia Lawall wrote: > The device node iterators perform an of_node_get on each iteration, so a > jump out of the loop requires an of_node_put. > > The semantic patch that fixes this problem is as follows > (http://coccinelle.lip6.fr): > > // > @@ >

[PATCH v3 4/4] usb: roles: intel_xhci: Enable runtime PM

This fixes an issue where the mux does not get configured when the parent device is suspended. The registers for this mux are mapped to the parent device MMIO (usually xHCI PCI device), so in order for the driver to be able to program the registers, the parent device must be resumed. Reported-by:

[PATCH v3 1/4] usb: roles: intel_xhci: Always allow user control

Trying to determine the USB port type with this mux is very difficult. To simplify the situation, always allow user control, even if the port is USB Type-C port. Reviewed-by: Hans de Goede Signed-off-by: Heikki Krogerus ---

[PATCH v3 2/4] platform: x86: intel_cht_int33fe: Fix dependencies

The driver will not probe unless bq24190 is loaded, so making it a dependency. Signed-off-by: Heikki Krogerus Cc: Wolfram Sang Cc: Darren Hart Cc: Andy Shevchenko ---

[PATCH v3 0/4] usb: typec: fixes for Cherry Trails

Hi, This is third version of patches that fix various problems I encountered while testing my USB Type-C Alternate Mode patches with GPD Win board (Intel Cherry Trail based). I added one more patch to this series. Sathyanarayanan reported an issue where the mux does not get configured when xHCI

Re: [PATCH v2] pinctrl: cherryview: limit Strago DMI workarounds to version 1.0

On Tue, May 22, 2018 at 10:47 PM, Dmitry Torokhov wrote: > As Google/Intel will fix the BIOS/Coreboot issues with hardcoding > virtual interrupt numbers for keyboard/touchpad/touchscreen controllers > in ACPI tables, they will also update BOARD version number from 1.0

[PATCH v3 3/4] usb: typec: fusb302: Fix debugfs issue

Removing the "fusb302" debugfs directory when unloading the driver. That allows the driver to be loaded more then one time. The directory will not get actually removed until it is empty, so only after the last instance has been removed. This fixes an issue where the driver can't be re-loaded if

Re: [PATCH v3] gpio: Remove VLA from stmpe driver

On Wed, Mar 28, 2018 at 7:59 PM, Laura Abbott wrote: > The new challenge is to remove VLAs from the kernel > (see https://lkml.org/lkml/2018/3/7/621) > > The number of GPIOs on the supported chips is fairly small > so stack allocate to a known upper bound and spit out a

[GIT PULL 0/2] stm class/intel_th: Fixes for v4.17

-0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm.git tags/stm-intel_th-fixes-for-greg-20180524 for you to fetch changes up to 3ce35db3ff05400e5676d0155cf261cc6bd3d351: intel_th: Use correct device when freeing buffers (2018-05-24 10:55:03

[GIT PULL 2/2] intel_th: Use correct device when freeing buffers

Commit d5c435df4a890 ("intel_th: msu: Use the real device in case of IOMMU domain allocation") changes dma buffer allocation to use the actual underlying device, but forgets to change the deallocation path, which leads to (if you've got CAP_SYS_RAWIO): > # echo 0,0 >

[GIT PULL 1/2] stm class: Use vmalloc for the master map

Fengguang is running into a warning from the buddy allocator: > swapper/0: page allocation failure: order:9, > mode:0x14040c0(GFP_KERNEL|__GFP_COMP), nodemask=(null) > CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.17.0-rc1 #262 > Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1

Re: [PATCH v2 0/7] mm: pages for hugetlb's overcommit may be able to charge to memcg

On Thu 24-05-18 13:26:12, TSUKADA Koutaro wrote: [...] > I do not know if it is really a strong use case, but I will explain my > motive in detail. English is not my native language, so please pardon > my poor English. > > I am one of the developers for software that managing the resource used >

Re: [PATCH v2 2/5] gpio: syscon: Add gpio-syscon for rockchip

On Wed, May 23, 2018 at 5:12 PM, Heiko Stübner wrote: > So the gpio controller should definitly also be a subnode. > > The gpio in question is called "mute", so I'd think the gpio-syscon driver > should just define a "rockchip,rk3328-gpio-mute" compatible and contain > all the

Re: [PATCH v3] powerpc: Implement csum_ipv6_magic in assembly

Le 23/05/2018 à 20:34, Segher Boessenkool a écrit : On Tue, May 22, 2018 at 08:57:01AM +0200, Christophe Leroy wrote: The generic csum_ipv6_magic() generates a pretty bad result Please try with a more recent compiler, what you used is pretty ancient. It's not like recent compilers do

[PATCH v2 00/13] ARM: pxa: switch to DMA slave maps

This v1 cover letter is quoted in [1]. For maintainers the table below should help you focus on the patches targetted at you, and ignore the other noise. The differences since v1 is by maintainers / topic / patch : - Arnd and Daniel / PXA topic / 0002 devices.c split into pxa25x.c, pxa27x.c

[PATCH v2 04/13] media: pxa_camera: remove the dmaengine compat need

As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more generic function dma_request_slave_channel().

Re: [PATCH v2] platform/x86: dell-wmi: Ignore new rfkill and fn-lock events

at 10:30 PM, mario.limoncie...@dell.com wrote: -Original Message- From: Pali Rohár [mailto:pali.ro...@gmail.com] Sent: Friday, April 20, 2018 2:29 AM To: Kai-Heng Feng Cc: mj...@srcf.ucam.org; dvh...@infradead.org; a...@infradead.org; Limonciello, Mario;

[PATCH v2 02/13] ARM: pxa: add dma slave map

In order to remove the specific knowledge of the dma mapping from PXA drivers, add a default slave map for pxa architectures. This is the first step, and once all drivers are converted, pxad_filter_fn() will be made static, and the DMA resources removed from device.c. Signed-off-by: Robert

[PATCH v2 08/13] ASoC: pxa: remove the dmaengine compat need

As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more generic function dma_request_slave_channel().

[PATCH v2 06/13] net: smc911x: remove the dmaengine compat need

As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more generic function dma_request_slave_channel().

Re: [RFC V2] virtio: Add platform specific DMA API translation for virito devices

On Wed, May 23, 2018 at 09:50:02PM +0300, Michael S. Tsirkin wrote: > subj: s/virito/virtio/ > ..snip.. > > machine_subsys_initcall_sync(pseries, tce_iommu_bus_notifier_init); > > + > > +bool platform_forces_virtio_dma(struct virtio_device *vdev) > > +{ > > + /* > > +* On protected guest

Re: [PATCH] kdump: add default crashkernel reserve kernel config options

On 05/24/18 at 08:57am, Petr Tesarik wrote: > On Thu, 24 May 2018 09:49:05 +0800 > Dave Young wrote: > > > Hi Petr, > > > > On 05/23/18 at 10:22pm, Petr Tesarik wrote: > >[...] > > > In short, if one size fits none, what good is it to hardcode that "one > > > size" into the

Re: [PATCH] kdump: add default crashkernel reserve kernel config options

On 05/24/18 at 08:57am, Petr Tesarik wrote: > On Thu, 24 May 2018 09:49:05 +0800 > Dave Young wrote: > > > Hi Petr, > > > > On 05/23/18 at 10:22pm, Petr Tesarik wrote: > >[...] > > > In short, if one size fits none, what good is it to hardcode that "one > > > size" into the

Re: [PATCH v1 1/7] dt-bindings: pinctrl: add external interrupt support to MT7622 pinctrl

On Sun, May 20, 2018 at 7:01 PM, wrote: > From: Sean Wang > > Extend the capability of MT7622 pinctrl with adding EINT so that each > GPIO can be used to notify CPU when a signal state is changing on the > line as an external interrupt. > >

Re: [PATCH v1 4/7] pinctrl: mediatek: use generic EINT register maps for each SoC

On Sun, May 20, 2018 at 7:01 PM, wrote: > From: Sean Wang > > So far, EINT on each SoC all used exactly identical register map and thus > it's better that we apply generic register map already supported in EINT > library and stop copy-n-pasting

Re: [PATCH bpf-next v2 0/3] bpf: add boot parameters for sysctl knobs

On Wed, 23 May 2018 15:02:45 -0700 Alexei Starovoitov wrote: > On Wed, May 23, 2018 at 02:18:19PM +0200, Eugene Syromiatnikov wrote: > > Some BPF sysctl knobs affect the loading of BPF programs, and during > > system boot/init stages these sysctls are not yet

[PATCH v12 6/8] clk: qcom: cpu-8996: Add support to switch to alternate PLL

From: Rajendra Nayak Each of the CPU clusters on msm8996 are powered via a primary PLL and a secondary PLL. The primary PLL is what drives the CPU clk, except for times when we are reprogramming the PLL itself, when we temporarily switch to an alternate PLL. Use clock rate

[PATCH v12 5/8] dt-bindings: clk: qcom: Add bindings for CPU clock for msm8996

Each of the CPU clusters (Power and Perf) on msm8996 are clocked via 2 PLLs, a primary and alternate. There are also 2 Mux'es, a primary and secondary all connected together as shown below +---+ XO | |

[PATCH v12 4/8] clk: qcom: Add CPU clock driver for msm8996

Each of the CPU clusters (Power and Perf) on msm8996 are clocked via 2 PLLs, a primary and alternate. There are also 2 Mux'es, a primary and secondary all connected together as shown below +---+ XO | |

Re: omapdrm regression in v4.17-rc series

On 24/05/18 01:03, Tony Lindgren wrote: > Hi all, > > I bisected the n900 LCD issue to commit 24aac6011f70 ("drm: omapdrm: > sdi: Allocate the sdi private data structure dynamically"). Reverting > this patch makes LCD work for me again on n900. > > Any ideas? This should help to get the SDI

Re: [PATCH V3] gpio: mxc: add clock operation

On Tue, May 22, 2018 at 5:05 AM, Anson Huang wrote: > Some i.MX SoCs have GPIO clock gates in CCM CCGR, such as > i.MX6SLL, need to enable clocks before accessing GPIO > registers, add optional clock operation for GPIO driver. > > Signed-off-by: Anson Huang

[RFD] Add debugfs for cpuidle ?

Hi all, would it be interesting to add debugfs metrics for cpuidle in order to read some statistics from there and investigate the behavior ? -- Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook |

Re: [PATCH v5 1/3] phy: Power on PHY before start Serdes configuration

Hi Can, On 5/23/2018 9:17 AM, Can Guo wrote: PHYs should be powered on before register configuration starts. Signed-off-by: Can Guo --- Thanks for fixing this. drivers/phy/qualcomm/phy-qcom-qmp.c | 6 ++ 1 file changed, 6 insertions(+) diff --git

Re: [PATCH v1 00/10] mm: online/offline 4MB chunks controlled by device driver

On 24.05.2018 09:53, Michal Hocko wrote: > I've had some questions before and I am not sure they are fully covered. > At least not in the cover letter (I didn't get much further yet) which > should give us a highlevel overview of the feature. Sure, I can give you more details. Adding all details

Re: [PATCH] kdump: add default crashkernel reserve kernel config options

On 05/24/18 at 03:56pm, Dave Young wrote: > > > > Instead of setting aside a significant chunk of memory nobody can use, > > > > [...] reserve a significant chunk of memory that the kernel is prevented > > > > from using [...], but applications are free to use it. > > > > > > That works great,

Re: v4.17-rc1: regressions on N900, N950

On 24/05/18 01:02, Aaro Koskinen wrote: But turns out that omapdrm tree is unbisectable, as I get build failures such as (commit 28d79f3e56b2c1d5ff0fd363da3229be0962cc85): /home/aaro/git/devel/linux/drivers/gpu/drm/omapdrm/dss/dss.c:1473:52: error: undefined identifier 'dss_debug_dump_clocks'

Re: [PATCH net-next v2 0/3] net: sfp: small improvements

Hi Florian, On Wed, May 23, 2018 at 11:40:50AM -0700, Florian Fainelli wrote: > > Antoine, can you please do CC the people who worked on that code before, > arguably, send an update to MAINTAINERS file to create a specific > section for PHYLINK. My bad, sorry for that, I'll make sure to Cc

Re: [PATCH] kdump: add default crashkernel reserve kernel config options

On Thu, 24 May 2018 09:49:05 +0800 Dave Young wrote: > Hi Petr, > > On 05/23/18 at 10:22pm, Petr Tesarik wrote: >[...] > > In short, if one size fits none, what good is it to hardcode that "one > > size" into the kernel image? > > I agreed with all the things that we can

[PATCH v2 13/13] ARM: pxa: change SSP DMA channels allocation

Now the dma_slave_map is available for PXA architecture, switch the SSP device to it. This specifically means that : - for platform data based machines, the DMA requestor channels are extracted from the slave map, where pxa-ssp-dai. is a 1-1 match to ssp., and the channels are either "rx" or

[PATCH v2 11/13] dmaengine: pxa: make the filter function internal

As the pxa architecture and all its related drivers do not rely anymore on the filter function, thanks to the slave map conversion, make pxad_filter_fn() static, and remove it from the global namespace. Signed-off-by: Robert Jarzmik --- drivers/dma/pxa_dma.c | 5

[PATCH v2 07/13] net: smc91x: remove the dmaengine compat need

As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more generic function dma_request_slave_channel().

Re: [GIT PULL] pinctrl: samsung: Stuff for v4.18 (second version)

On Wed, May 23, 2018 at 9:27 PM, Krzysztof Kozlowski wrote: > This is updated pull request with one additional patch from Marek. > I saw you did not pull my previous pull request for v4.18 so I hope > this update should not be a problem. Thanks Krzysztof, pulled this into

[PATCH v2 03/13] mmc: pxamci: remove the dmaengine compat need

As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more generic function dma_request_slave_channel().

[PATCH v2 01/13] dmaengine: pxa: use a dma slave map

In order to remove the specific knowledge of the dma mapping from PXA drivers, add a default slave map for pxa architectures. This won't impact MMP architecture, but is aimed only at all PXA boards. This is the first step, and once all drivers are converted, pxad_filter_fn() will be made static,

[PATCH v2 05/13] mtd: rawnand: marvell: remove the dmaengine compat need

As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more generic function dma_request_slave_channel().

[PATCH v2 09/13] ata: pata_pxa: remove the dmaengine compat need

As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more generic function dma_request_slave_channel().

Re: [RFC V2] virtio: Add platform specific DMA API translation for virito devices

On Thu, May 24, 2018 at 08:27:04AM +1000, Benjamin Herrenschmidt wrote: > - First qemu doesn't know that the guest will switch to "secure mode" > in advance. There is no difference between a normal and a secure > partition until the partition does the magic UV call to "enter secure > mode" and

[PATCH 1/2] rtmutex: allow specifying a subclass for nested locking

Needed for annotating rt_mutex locks. Signed-off-by: Peter Rosin --- include/linux/rtmutex.h | 6 ++ kernel/locking/rtmutex.c | 29 + 2 files changed, 31 insertions(+), 4 deletions(-) diff --git a/include/linux/rtmutex.h

[PATCH 2/2] i2c: mux: annotate the nested rt_mutex usage

If an i2c topology has instances of nested muxes, then a lockdep splat is produced when when i2c_parent_lock_bus() is called. Here is an example: WARNING: possible recursive locking detected insmod/68159 is

Re: Problem: lockdep warning with nested instances of i2c-mux

On 2018-05-24 04:25, John Sperbeck wrote: > If an i2c topology has instances of nested muxes, then a lockdep splat > is produced when when i2c_parent_lock_bus() is called. Here is an > example: > > > WARNING: possible recursive locking detected >

Re: [PATCH] kdump: add default crashkernel reserve kernel config options

On 05/24/18 at 03:26pm, Dave Young wrote: > On 05/24/18 at 08:57am, Petr Tesarik wrote: > > On Thu, 24 May 2018 09:49:05 +0800 > > Dave Young wrote: > > > > > Hi Petr, > > > > > > On 05/23/18 at 10:22pm, Petr Tesarik wrote: > > >[...] > > > > In short, if one size fits none,

Re: [PATCH v1 5/7] pinctrl: mediatek: remove unused fields in struct mtk_eint_hw

On Sun, May 20, 2018 at 7:01 PM, wrote: > From: Sean Wang > > The .name field has been not being used in existent code logic, so > it's better that we remove them all. > > Signed-off-by: Sean Wang Patch applied. Yours,

Re: [PATCH v1 3/7] pinctrl: mediatek: add EINT support to MT7622 SoC

On Sun, May 20, 2018 at 7:01 PM, wrote: > From: Sean Wang > > Add EINT support to MT7622 SoC and the support is made as just an option > to MT7622 pinctrl. > > Signed-off-by: Sean Wang Patch applied. Yours, Linus

Re: [PATCH v5 06/13] KVM: s390: interfaces to manage guest's AP matrix

On 23/05/2018 16:29, Tony Krowiak wrote: On 05/18/2018 04:55 AM, Pierre Morel wrote: On 16/05/2018 15:48, Tony Krowiak wrote: On 05/16/2018 09:15 AM, Pierre Morel wrote: On 16/05/2018 15:12, Tony Krowiak wrote: On 05/16/2018 03:48 AM, Pierre Morel wrote: On 15/05/2018 18:07, Tony Krowiak

[PATCH v12 7/8] clk: qcom: cpu-8996: Add support to switch below 600Mhz

The CPU clock controller's primary PLL operates on a single VCO range, between 600MHz and 3GHz. However the CPUs do support OPPs with frequencies between 300MHz and 600MHz. In order to support running the CPUs at those frequencies we end up having to lock the PLL at twice the rate and drive the

[PATCH v12 3/8] clk: Use devm_ in the register fixed factor clock

Use devm_clk_hw_register instead of clk_hw_register to simplify the usage of this API. This way drivers that call the clk_hw_register_fixed_factor won't need to maintain a data structure for further cleanup. Signed-off-by: Ilia Lin --- drivers/clk/clk-fixed-factor.c | 2

[PATCH v12 0/8] Clock for CPU scaling support for msm8996

[v12] * Addressed the kbuild fail on arm architecture [v11] * Split the series into domains [v9] * Addressed comments from Viresh and Russel about the error handling [v8] * Reordered the patch series into 4 groups * Addressed comments from Amit about the comments and commit messages *

Re: [PATCH v2 0/7] mm: pages for hugetlb's overcommit may be able to charge to memcg

On Thu 24-05-18 13:39:59, TSUKADA Koutaro wrote: > On 2018/05/23 3:54, Michal Hocko wrote: [...] > > I am also quite confused why you keep distinguishing surplus hugetlb > > pages from regular preallocated ones. Being a surplus page is an > > implementation detail that we use for an internal

Re: [PATCH 02/13] atomics/treewide: remove redundant atomic_inc_not_zero() definitions

On Wed, May 23, 2018 at 02:35:22PM +0100, Mark Rutland wrote: > vWhen atomic_inc_not_zero(v) isn't defined, will define > it as falling back to atomic_add_unless((v), 1, 0), so there's no need > for arch code to do so. Typo: s/vWhen/When/ I've fixed that up in the git branch. Mark.

Re: [RFD] Add debugfs for cpuidle ?

On Thursday, May 24, 2018 10:14:31 AM CEST Daniel Lezcano wrote: > > Hi all, Hi, > would it be interesting to add debugfs metrics for cpuidle in order to > read some statistics from there and investigate the behavior ? What exactly would you like to see in there?

Re: B53 DSA switch problem on Banana Pi-R1 on Fedora 26

On 24.05.2018 07:29, Gerhard Wiesinger wrote: After some analysis with Florian (thnx) we found out that the current implementation is broken: https://patchwork.ozlabs.org/patch/836538/

[PATCH v7 2/4] ARM: dts: tegra: Fix unit_address_vs_reg DTC warnings for /memory

Add a generic /memory node in each Tegra DTSI (with empty reg property, to be overidden by each DTS) and set proper unit address for /memory nodes to fix the DTC warnings: arch/arm/boot/dts/tegra20-harmony.dtb: Warning (unit_address_vs_reg): /memory: node has a reg or ranges property,

[PATCH v7 4/4] ARM: dts: tegra: Work safely with 256 MB Colibri-T20 modules

Colibri-T20 can come in 256 MB RAM (with 512 MB NAND) or 512 MB RAM (with 1024 MB NAND) flavors. Both of them will use the same DTSI expecting the bootloader to do the fixup of /memory node. However in case it does not happen, let's stay on safe side by limiting the memory to 256 MB for both

Re: [PATCH v9 3/4] arm64: Implement page table free interfaces

On 5/23/2018 8:04 PM, Kani, Toshi wrote: On Wed, 2018-05-23 at 15:01 +0100, Will Deacon wrote: Hi Chintan, [as a side note: I'm confused on the status of this patch series, as part of it was reposted separately by Toshi. Please can you work together?] I do not know the status of my patch

[PATCH v2 12/13] ARM: pxa: remove the DMA IO resources

As the last driver using the former mechanism to acquire the DMA requestor line has be converted to the dma_slave_map, remove all these resources from the PXA devices. Signed-off-by: Robert Jarzmik --- arch/arm/mach-pxa/devices.c | 136

Re: [PATCH v1 2/7] pinctrl: mediatek: refactor EINT related code for all MediaTek pinctrl can fit

On Sun, May 20, 2018 at 7:01 PM, wrote: > From: Sean Wang > > This patch is in preparation for adding EINT support to MT7622 pinctrl, > and the refactoring doesn't alter any existent logic. > > A reason we have to refactor EINT code pieces into a

[PATCH v2 10/13] dmaengine: pxa: document pxad_param

Add some documentation for the pxad_param structure, and describe the contract behind the minimal required priority of a DMA channel. Signed-off-by: Robert Jarzmik --- include/linux/dma/pxa-dma.h | 9 + 1 file changed, 9 insertions(+) diff --git

Re: [PATCH 3/6] block: Create scsi_sense.h for SCSI and ATAPI

On Wed, May 23, 2018 at 02:17:14PM -0700, Kees Cook wrote: > > True, though I'm finding other robustness issues in the CDROM code. > They're probably all insane corner cases, but it seems like it'd be > nice to just fix them: > > diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c > index

Re: [PATCH] sched,tracing: Correct trace_sched_pi_setprio() for deboosting

On 2018-05-23 19:28:19 [+0200], Peter Zijlstra wrote: > On Wed, May 23, 2018 at 04:11:07PM +0200, Sebastian Andrzej Siewior wrote: > > > Since that commit I see during a deboost a task this: > > |futex sched_pi_setprio: comm=futex_requeue_p pid=2234 oldprio=98 newprio=98 > > |futex sched_switch:

  1   2   3   4   5   6   7   8   9   10   >