Hi, sorry for the late reply,
2017-12-14 17:36 GMT+00:00 Peter Zijlstra :
> On Thu, Dec 14, 2017 at 08:19:36AM -0800, Andy Lutomirski wrote:
>> On Thu, Dec 14, 2017 at 3:27 AM, Peter Zijlstra wrote:
>> > It makes no sense to ever prod at special
On 29/12/17 08:18, Christoph Hellwig wrote:
> So that they don't need to indirect through the operation vector.
>
> Signed-off-by: Christoph Hellwig
> ---
> arch/arm/mm/dma-mapping-nommu.c | 9 +++--
> include/linux/dma-direct.h | 5 +
> lib/dma-direct.c
Hi, sorry for the late reply,
2017-12-14 17:36 GMT+00:00 Peter Zijlstra :
> On Thu, Dec 14, 2017 at 08:19:36AM -0800, Andy Lutomirski wrote:
>> On Thu, Dec 14, 2017 at 3:27 AM, Peter Zijlstra wrote:
>> > It makes no sense to ever prod at special mappings with any of these
>> > syscalls.
>> >
>>
On 29/12/17 08:18, Christoph Hellwig wrote:
> So that they don't need to indirect through the operation vector.
>
> Signed-off-by: Christoph Hellwig
> ---
> arch/arm/mm/dma-mapping-nommu.c | 9 +++--
> include/linux/dma-direct.h | 5 +
> lib/dma-direct.c| 6 +++---
>
From: Bai Ping
On i.MX 6ULL, the pin MUX and CTRL register of BOOT_MODEx and TAMPERx
pins are available through IOMUXC_SNVS. Add additional pinfunc defines.
Signed-off-by: Bai Ping
Signed-off-by: Stefan Agner
---
From: Bai Ping
On i.MX 6ULL, the pin MUX and CTRL register of BOOT_MODEx and TAMPERx
pins are available through IOMUXC_SNVS. Add additional pinfunc defines.
Signed-off-by: Bai Ping
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6ull-pinfunc-snvs.h | 29 +
When the CPU is in ARM power off state the ARM architected
timers are stopped. The flag is already present in the higher
power WAIT mode.
This allows to use the ARM generic timer on i.MX 6UL/6ULL SoC.
Without the flag the kernel freezes when the timer enters the
first time ARM power off mode.
When the CPU is in ARM power off state the ARM architected
timers are stopped. The flag is already present in the higher
power WAIT mode.
This allows to use the ARM generic timer on i.MX 6UL/6ULL SoC.
Without the flag the kernel freezes when the timer enters the
first time ARM power off mode.
On 29/12/17 08:18, Christoph Hellwig wrote:
> If we got back an allocation that wasn't inside the support coherent mask,
> retry the allocation using GFP_DMA.
>
> Based on the x86 code.
>
> Signed-off-by: Christoph Hellwig
> ---
> lib/dma-direct.c | 25 -
>
Add per-core ARM architected timer. Unfortunately bootloaders (U-Boot)
currently do not make the necessary initialization. Also specifing the
clock manually using the clock-frequency property seems not to help.
Therefor leave the timer disabled by default for now.
Signed-off-by: Stefan Agner
On 29/12/17 08:18, Christoph Hellwig wrote:
> If we got back an allocation that wasn't inside the support coherent mask,
> retry the allocation using GFP_DMA.
>
> Based on the x86 code.
>
> Signed-off-by: Christoph Hellwig
> ---
> lib/dma-direct.c | 25 -
> 1 file
Add per-core ARM architected timer. Unfortunately bootloaders (U-Boot)
currently do not make the necessary initialization. Also specifing the
clock manually using the clock-frequency property seems not to help.
Therefor leave the timer disabled by default for now.
Signed-off-by: Stefan Agner
---
From: Fugang Duan
Update i.MX 6UltraLite IOMUXC pin defines.
Signed-off-by: Fugang Duan
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6ul-pinfunc.h | 169 +
1 file changed, 97 insertions(+),
From: Fugang Duan
Update i.MX 6UltraLite IOMUXC pin defines.
Signed-off-by: Fugang Duan
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6ul-pinfunc.h | 169 +
1 file changed, 97 insertions(+), 72 deletions(-)
diff --git
The Cortex-A7 and its GIC support virtualization extensions. To
make use of them the CPU private interrupt needs to be specified.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6ul.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/imx6ul.dtsi
The Cortex-A7 and its GIC support virtualization extensions. To
make use of them the CPU private interrupt needs to be specified.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6ul.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/imx6ul.dtsi
The i.MX 6ULL features another IOMUX Controller called IOMUXC
SNVS which allows to control BOOT_MODE and TAMPER pins. Add the
controller to the i.MX 6ULL specific imx6ull.dtsi device tree.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6ull.dtsi | 17 +
1
The i.MX 6ULL features another IOMUX Controller called IOMUXC
SNVS which allows to control BOOT_MODE and TAMPER pins. Add the
controller to the i.MX 6ULL specific imx6ull.dtsi device tree.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6ull.dtsi | 17 +
1 file changed, 17
In i.MX 6ULL UART8 is part of the AIPS-3 memory map instead of
AIPS-1. Clocks and interrupts remain the same.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6ull.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/imx6ull.dtsi
In i.MX 6ULL UART8 is part of the AIPS-3 memory map instead of
AIPS-1. Clocks and interrupts remain the same.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx6ull.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/imx6ull.dtsi
From: Bai Ping
On i.MX 6ULL, the BOOT_MODEx and TAMPERx pin MUX and CTRL registers
are available in a separate IOMUXC_SNVS module. Add support for the
IOMUXC_SNVS module to the i.MX 6UL pinctrl driver.
Signed-off-by: Bai Ping
Signed-off-by: Stefan Agner
From: Bai Ping
On i.MX 6ULL, the BOOT_MODEx and TAMPERx pin MUX and CTRL registers
are available in a separate IOMUXC_SNVS module. Add support for the
IOMUXC_SNVS module to the i.MX 6UL pinctrl driver.
Signed-off-by: Bai Ping
Signed-off-by: Stefan Agner
---
From: Colin Ian King
Currently a bool is being used to get and check for a -ve error
return from the call to ocfs2_get_clusters but the check for ret < 0 is
never true for a bool. Fix this by using an int type for an error return
instead.
Detected by CoverityScan,
From: Colin Ian King
Currently a bool is being used to get and check for a -ve error
return from the call to ocfs2_get_clusters but the check for ret < 0 is
never true for a bool. Fix this by using an int type for an error return
instead.
Detected by CoverityScan, CID#1463416 ("Operands don't
On Fri, Dec 22, 2017 at 11:43:08AM -0800, Florian Fainelli wrote:
> We are doing a blind write to SATA_TOP_CTRL_BUS_CTRL to set the system
> endian, but in doing so, we are also overwriting other bits, such as the
> SATA_SCB_BURST_SIZE and SATA_FIFO_SIZE bits, which impact performance.
> Do a
On Fri, Dec 22, 2017 at 11:43:08AM -0800, Florian Fainelli wrote:
> We are doing a blind write to SATA_TOP_CTRL_BUS_CTRL to set the system
> endian, but in doing so, we are also overwriting other bits, such as the
> SATA_SCB_BURST_SIZE and SATA_FIFO_SIZE bits, which impact performance.
> Do a
Hi Paul,
On 30 December 2017 at 19:21, Paul Cercueil wrote:
> Also remove the watchdog platform_device from platform.c, since it
> wasn't used anywhere anyway.
>
> Signed-off-by: Paul Cercueil
> ---
> arch/mips/boot/dts/ingenic/jz4740.dtsi | 8
Hi Paul,
On 30 December 2017 at 19:21, Paul Cercueil wrote:
> Also remove the watchdog platform_device from platform.c, since it
> wasn't used anywhere anyway.
>
> Signed-off-by: Paul Cercueil
> ---
> arch/mips/boot/dts/ingenic/jz4740.dtsi | 8
> arch/mips/jz4740/platform.c
On Tue, Jan 02, 2018 at 05:27:41PM +0100, Vladimir Rutsky wrote:
> Signed-off-by: Vladimir Rutsky
Applied to cgroup/for-4.16.
Thanks.
--
tejun
On Tue, Jan 02, 2018 at 05:27:41PM +0100, Vladimir Rutsky wrote:
> Signed-off-by: Vladimir Rutsky
Applied to cgroup/for-4.16.
Thanks.
--
tejun
On Wed, Dec 27, 2017 at 06:43:27PM +0900, Jaehoon Chung wrote:
> pci-exynos had updated to use the PHY framework.
> (drivers/phy/samsung/phy-exynos-pcie.c)
> Removed the depreccated codes relevant to phy in pci-exynos.c.
> Instead, use the phy-exynos-pcie.c file.
>
> Modified the binding
On Wed, Dec 27, 2017 at 06:43:27PM +0900, Jaehoon Chung wrote:
> pci-exynos had updated to use the PHY framework.
> (drivers/phy/samsung/phy-exynos-pcie.c)
> Removed the depreccated codes relevant to phy in pci-exynos.c.
> Instead, use the phy-exynos-pcie.c file.
>
> Modified the binding
Hi PrasannaKumar,
Le mar. 2 janv. 2018 à 17:02, PrasannaKumar Muralidharan
a écrit :
Hi Paul,
On 2 January 2018 at 20:38, Paul Cercueil
wrote:
This makes sure that 'mips_machtype' will be initialized to the SoC
version used on the board.
Hi PrasannaKumar,
Le mar. 2 janv. 2018 à 17:02, PrasannaKumar Muralidharan
a écrit :
Hi Paul,
On 2 January 2018 at 20:38, Paul Cercueil
wrote:
This makes sure that 'mips_machtype' will be initialized to the SoC
version used on the board.
Signed-off-by: Paul Cercueil
---
On Tue, 02 Jan 2018, Ryder Lee wrote:
> Add a common driver for the top block of the MediaTek audio subsystem.
> This is a wrapper which manages resources for audio components.
>
> Signed-off-by: Ryder Lee
> ---
> drivers/mfd/Kconfig | 9
>
sta...@suse.de>
---
Compile-tested only (with inspection of compiler output on x86_64).
Applicable to linux-next-20180102.
net/ipv4/raw.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/net/ipv4/raw.c b/net/ipv4/raw.c
index 5b9bd5c33d9d..e84290c28c0c 100644
---
On Tue, 02 Jan 2018, Ryder Lee wrote:
> Add a common driver for the top block of the MediaTek audio subsystem.
> This is a wrapper which manages resources for audio components.
>
> Signed-off-by: Ryder Lee
> ---
> drivers/mfd/Kconfig | 9
> drivers/mfd/Makefile | 2 +
>
Stange
---
Compile-tested only (with inspection of compiler output on x86_64).
Applicable to linux-next-20180102.
net/ipv4/raw.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/net/ipv4/raw.c b/net/ipv4/raw.c
index 5b9bd5c33d9d..e84290c28c0c 100644
--- a/net/ipv4/raw.c
+++ b/n
Signed-off-by: Vladimir Rutsky
---
Documentation/cgroup-v2.txt | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/cgroup-v2.txt b/Documentation/cgroup-v2.txt
index 2cddab7..eb0b679 100644
--- a/Documentation/cgroup-v2.txt
+++
Signed-off-by: Vladimir Rutsky
---
Documentation/cgroup-v2.txt | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/cgroup-v2.txt b/Documentation/cgroup-v2.txt
index 2cddab7..eb0b679 100644
--- a/Documentation/cgroup-v2.txt
+++ b/Documentation/cgroup-v2.txt
On 29/12/17 08:18, Christoph Hellwig wrote:
> This means it uses whatever linear remapping scheme that the architecture
> provides is used in the generic dma_direct ops.
>
> Signed-off-by: Christoph Hellwig
> ---
> lib/dma-direct.c | 18 +++---
> 1 file changed, 7
On 29/12/17 08:18, Christoph Hellwig wrote:
> This means it uses whatever linear remapping scheme that the architecture
> provides is used in the generic dma_direct ops.
>
> Signed-off-by: Christoph Hellwig
> ---
> lib/dma-direct.c | 18 +++---
> 1 file changed, 7 insertions(+), 11
On 29/12/17 08:18, Christoph Hellwig wrote:
> The trivial direct mapping implementation already does a virtual to
> physical translation which isn't strictly a noop, and will soon learn
> to do non-direct but linear physical to dma translations through the
> device offset and a few small tricks.
On 29/12/17 08:18, Christoph Hellwig wrote:
> The trivial direct mapping implementation already does a virtual to
> physical translation which isn't strictly a noop, and will soon learn
> to do non-direct but linear physical to dma translations through the
> device offset and a few small tricks.
On Tue, Jan 2, 2018 at 4:36 PM, Wang, Haiyue
wrote:
> On 2018-01-02 23:13, Arnd Bergmann wrote:
>>> On 2017-12-31 07:10, Arnd Bergmann wrote:
It also seems rather inflexible to have a single driver that is
responsible both
for the transport (eSPI
On Tue, Jan 2, 2018 at 4:36 PM, Wang, Haiyue
wrote:
> On 2018-01-02 23:13, Arnd Bergmann wrote:
>>> On 2017-12-31 07:10, Arnd Bergmann wrote:
It also seems rather inflexible to have a single driver that is
responsible both
for the transport (eSPI register level interface for
Hi Srini,
On 2 January 2018 at 17:32, Srinivas Kandagatla
wrote:
>
>
> On 28/12/17 21:29, Mathieu Malaterre wrote:
>>
>> From: PrasannaKumar Muralidharan
>>
>> This patch brings support for the JZ4780 efuse. Currently it only expose
>>
Hi Srini,
On 2 January 2018 at 17:32, Srinivas Kandagatla
wrote:
>
>
> On 28/12/17 21:29, Mathieu Malaterre wrote:
>>
>> From: PrasannaKumar Muralidharan
>>
>> This patch brings support for the JZ4780 efuse. Currently it only expose
>> a read only access to the entire 8K bits efuse memory.
>>
Hello,
On Fri, Dec 29, 2017 at 02:07:16AM +0530, Prateek Sood wrote:
> task T is waiting for cpuset_mutex acquired
> by kworker/2:1
>
> sh ==> cpuhp/2 ==> kworker/2:1 ==> sh
>
> kworker/2:3 ==> kthreadd ==> Task T ==> kworker/2:1
>
> It seems that my earlier patch set should fix this
Hello,
On Fri, Dec 29, 2017 at 02:07:16AM +0530, Prateek Sood wrote:
> task T is waiting for cpuset_mutex acquired
> by kworker/2:1
>
> sh ==> cpuhp/2 ==> kworker/2:1 ==> sh
>
> kworker/2:3 ==> kthreadd ==> Task T ==> kworker/2:1
>
> It seems that my earlier patch set should fix this
Hi Fabio,
thanks for testing my patch. Sorry for breaking suspend on your board.
Thus wrote Fabio Estevam (feste...@gmail.com):
> Which i.MX SoC did you use to test this patch?
I tested on an imx258.
> On a imx6q-cuboxi I am no longer able to enter in suspend with this
> path applied:
> #
Hi Fabio,
thanks for testing my patch. Sorry for breaking suspend on your board.
Thus wrote Fabio Estevam (feste...@gmail.com):
> Which i.MX SoC did you use to test this patch?
I tested on an imx258.
> On a imx6q-cuboxi I am no longer able to enter in suspend with this
> path applied:
> #
Hi Srinivas,
On 2 January 2018 at 17:31, Srinivas Kandagatla
wrote:
>
>
> On 28/12/17 21:29, Mathieu Malaterre wrote:
>>
>> This patchset bring support for read-only access to the JZ4780 efuse as
>> found
>> on MIPS Creator CI20.
>>
>> To keep the driver as simple
Hi Srinivas,
On 2 January 2018 at 17:31, Srinivas Kandagatla
wrote:
>
>
> On 28/12/17 21:29, Mathieu Malaterre wrote:
>>
>> This patchset bring support for read-only access to the JZ4780 efuse as
>> found
>> on MIPS Creator CI20.
>>
>> To keep the driver as simple as possible, it was not
On 12/22/2017 02:31 PM, Faiz Abbas wrote:
> From: Franklin S Cooper Jr
>
> Various CAN or CAN-FD IP may be able to run at a faster rate than
> what the transceiver the CAN node is connected to. This can lead to
> unexpected errors. However, CAN transceivers typically have fixed
>
On 12/22/2017 02:31 PM, Faiz Abbas wrote:
> From: Franklin S Cooper Jr
>
> Various CAN or CAN-FD IP may be able to run at a faster rate than
> what the transceiver the CAN node is connected to. This can lead to
> unexpected errors. However, CAN transceivers typically have fixed
> limitations and
Am 02.01.2018 um 16:39 schrieb Chris Wilson:
Quoting Christian König (2018-01-02 12:13:58)
TTM tries to allocate coherent memory in chunks of 2MB first to improve
TLB efficiency and falls back to allocating 4K pages if that fails.
Suppress the warning when the 2MB allocations fails since there
Am 02.01.2018 um 16:39 schrieb Chris Wilson:
Quoting Christian König (2018-01-02 12:13:58)
TTM tries to allocate coherent memory in chunks of 2MB first to improve
TLB efficiency and falls back to allocating 4K pages if that fails.
Suppress the warning when the 2MB allocations fails since there
Hi Paul,
On 2 January 2018 at 20:38, Paul Cercueil wrote:
> Provide just enough bits (clocks, clocksource, uart) to allow a kernel
> to boot on the JZ4770 SoC to a initramfs userspace.
>
> Signed-off-by: Paul Cercueil
> ---
>
Hi Paul,
On 2 January 2018 at 20:38, Paul Cercueil wrote:
> Provide just enough bits (clocks, clocksource, uart) to allow a kernel
> to boot on the JZ4770 SoC to a initramfs userspace.
>
> Signed-off-by: Paul Cercueil
> ---
> arch/mips/boot/dts/ingenic/jz4770.dtsi | 212
>
On 12/22/2017 02:31 PM, Faiz Abbas wrote:
> From: Franklin S Cooper Jr
>
> Add support for PM Runtime which is the new way to handle managing clocks.
> However, to avoid breaking SoCs not using PM_RUNTIME leave the old clk
> management approach in place.
There is no PM_RUNTIME
On 12/22/2017 02:31 PM, Faiz Abbas wrote:
> From: Franklin S Cooper Jr
>
> Add support for PM Runtime which is the new way to handle managing clocks.
> However, to avoid breaking SoCs not using PM_RUNTIME leave the old clk
> management approach in place.
There is no PM_RUNTIME anymore since
On Thu, Dec 28, 2017 at 11:49:12AM +0100, Bartosz Golaszewski wrote:
> Add other variants of at24 EEPROMs we support in the driver to the
> list of allowed compatible fallbacks.
>
> Signed-off-by: Bartosz Golaszewski
> Reviewed-by: Javier Martinez Canillas
>
On Thu, Dec 28, 2017 at 11:49:12AM +0100, Bartosz Golaszewski wrote:
> Add other variants of at24 EEPROMs we support in the driver to the
> list of allowed compatible fallbacks.
>
> Signed-off-by: Bartosz Golaszewski
> Reviewed-by: Javier Martinez Canillas
> ---
>
Hi Paul,
On 2 January 2018 at 20:38, Paul Cercueil wrote:
> This makes sure that 'mips_machtype' will be initialized to the SoC
> version used on the board.
>
> Signed-off-by: Paul Cercueil
> ---
> arch/mips/Kconfig | 1 +
>
Hi Paul,
On 2 January 2018 at 20:38, Paul Cercueil wrote:
> This makes sure that 'mips_machtype' will be initialized to the SoC
> version used on the board.
>
> Signed-off-by: Paul Cercueil
> ---
> arch/mips/Kconfig | 1 +
> arch/mips/jz4740/Makefile | 2 +-
>
On Thu, Dec 28, 2017 at 11:49:11AM +0100, Bartosz Golaszewski wrote:
> Make formatting and style consistent for the entire document.
>
> This patch doesn't change the content of the binding.
>
> Signed-off-by: Bartosz Golaszewski
> Reviewed-by: Javier Martinez Canillas
On Thu, Dec 28, 2017 at 11:49:11AM +0100, Bartosz Golaszewski wrote:
> Make formatting and style consistent for the entire document.
>
> This patch doesn't change the content of the binding.
>
> Signed-off-by: Bartosz Golaszewski
> Reviewed-by: Javier Martinez Canillas
> ---
>
On Thu, Dec 28, 2017 at 11:49:10AM +0100, Bartosz Golaszewski wrote:
> Current description of the compatible property for at24 is quite vague.
>
> State explicitly that any "," pair is accepted as
> long as a correct fallback is used for non-atmel chips.
>
> Signed-off-by: Bartosz Golaszewski
On Thu, Dec 28, 2017 at 11:49:10AM +0100, Bartosz Golaszewski wrote:
> Current description of the compatible property for at24 is quite vague.
>
> State explicitly that any "," pair is accepted as
> long as a correct fallback is used for non-atmel chips.
>
> Signed-off-by: Bartosz Golaszewski
>
On 2 January 2018 at 20:38, Paul Cercueil wrote:
> Add a machtype ID for the JZ4780 SoC, which was missing, and one for the
> newly supported JZ4770 SoC.
>
> Signed-off-by: Paul Cercueil
> ---
> arch/mips/include/asm/bootinfo.h | 2 ++
> 1 file
On 2 January 2018 at 20:38, Paul Cercueil wrote:
> Add a machtype ID for the JZ4780 SoC, which was missing, and one for the
> newly supported JZ4770 SoC.
>
> Signed-off-by: Paul Cercueil
> ---
> arch/mips/include/asm/bootinfo.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> v2: No change
> v3:
Hi Paul,
On 2 January 2018 at 20:38, Paul Cercueil wrote:
> From: Paul Burton
>
> jz4740_init_cmdline appends all arguments from argv (in fw_arg1) to
> arcs_cmdline, up to argc (in fw_arg0). The common code in
> fw_init_cmdline will do the exact
On Tue, Jan 02, 2018 at 07:34:30AM -0800, Joe Perches wrote:
> On Sat, 2017-12-23 at 15:19 +0100, Greg Kroah-Hartman wrote:
> > On Fri, Dec 22, 2017 at 12:02:47PM -0800, Joe Perches wrote:
> > > There are many uses of the DEVICE_ATTR(var, perms, show, store)
> > > declaration macro that could use
Hi Paul,
On 2 January 2018 at 20:38, Paul Cercueil wrote:
> From: Paul Burton
>
> jz4740_init_cmdline appends all arguments from argv (in fw_arg1) to
> arcs_cmdline, up to argc (in fw_arg0). The common code in
> fw_init_cmdline will do the exact same thing when run on a system where
> fw_arg0
On Tue, Jan 02, 2018 at 07:34:30AM -0800, Joe Perches wrote:
> On Sat, 2017-12-23 at 15:19 +0100, Greg Kroah-Hartman wrote:
> > On Fri, Dec 22, 2017 at 12:02:47PM -0800, Joe Perches wrote:
> > > There are many uses of the DEVICE_ATTR(var, perms, show, store)
> > > declaration macro that could use
On Tue, 2 Jan 2018, Ulf Hansson wrote:
> > While I acknowledge that Ulf doesn't appear to be convinced by my
> > arguments, I also see no technical reason why this cannot go in.
>
> Correct, I am not convinced this is the right path as a general
> optimization, at least in it's current form. The
On Tue, 2 Jan 2018, Ulf Hansson wrote:
> > While I acknowledge that Ulf doesn't appear to be convinced by my
> > arguments, I also see no technical reason why this cannot go in.
>
> Correct, I am not convinced this is the right path as a general
> optimization, at least in it's current form. The
On Fri, Dec 22, 2017 at 12:55:08AM +, Colin King wrote:
> From: Colin Ian King
>
> Label 'retry' is not used, remove it. Cleans up a clang build
> warning:
>
> warning: label ‘retry’ defined but not used [-Wunused-label]
>
> Fixes: b283738ab0ad ("Revert "btrfs:
On Fri, Dec 22, 2017 at 12:55:08AM +, Colin King wrote:
> From: Colin Ian King
>
> Label 'retry' is not used, remove it. Cleans up a clang build
> warning:
>
> warning: label ‘retry’ defined but not used [-Wunused-label]
>
> Fixes: b283738ab0ad ("Revert "btrfs: qgroups: Retry after commit
This commit adds definitions for PD Rev 3.0 messages, including
APDO PPS and extended message support for TCPM.
Signed-off-by: Adam Thomson
---
include/linux/usb/pd.h | 185 ++---
1 file changed, 174 insertions(+),
This commit adds definitions for PD Rev 3.0 messages, including
APDO PPS and extended message support for TCPM.
Signed-off-by: Adam Thomson
---
include/linux/usb/pd.h | 185 ++---
1 file changed, 174 insertions(+), 11 deletions(-)
diff --git
This commit adds a header providing definitions for handling
Status messages. Currently the header only focuses on handling
incoming Status messages.
Signed-off-by: Adam Thomson
---
include/linux/usb/pd_ext_sdb.h | 31 +++
1 file
This commit adds a header providing definitions for handling
Status messages. Currently the header only focuses on handling
incoming Status messages.
Signed-off-by: Adam Thomson
---
include/linux/usb/pd_ext_sdb.h | 31 +++
1 file changed, 31 insertions(+)
create
This commit adds code to handle requesting of PPS APDOs. Switching
between standard PDOs and APDOs, and re-requesting an APDO to
modify operating voltage/current will be triggered by an
external call into TCPM.
Signed-off-by: Adam Thomson
---
This commit adds code to handle requesting of PPS APDOs. Switching
between standard PDOs and APDOs, and re-requesting an APDO to
modify operating voltage/current will be triggered by an
external call into TCPM.
Signed-off-by: Adam Thomson
---
drivers/usb/typec/tcpm.c | 533
This patch set adds sink side support for the PPS feature introduced in the
USB PD 3.0 specification.
The source PPS supply is represented using the Power Supply framework to provide
access and control APIs for dealing with it's operating voltage and current,
and switching between a standard PDO
This patch set adds sink side support for the PPS feature introduced in the
USB PD 3.0 specification.
The source PPS supply is represented using the Power Supply framework to provide
access and control APIs for dealing with it's operating voltage and current,
and switching between a standard PDO
This commit adds the 'connected_type' property to represent supplies
which can report a number of different types of supply based on a
connection event.
Examples of this already exist in drivers whereby the existing 'type'
property is updated, based on an event, to represent what was
connected
On Mon, 01 Jan 2018, Paul Cercueil wrote:
> This header contains macros for the registers that are present in the
> regmap shared by all the drivers related to the TCU (Timer Counter Unit)
> of the Ingenic JZ47xx SoCs.
>
> Signed-off-by: Paul Cercueil
> ---
>
On Mon, 01 Jan 2018, Paul Cercueil wrote:
> This header contains macros for the registers that are present in the
> regmap shared by all the drivers related to the TCU (Timer Counter Unit)
> of the Ingenic JZ47xx SoCs.
>
> Signed-off-by: Paul Cercueil
> ---
>
This commit adds the 'connected_type' property to represent supplies
which can report a number of different types of supply based on a
connection event.
Examples of this already exist in drivers whereby the existing 'type'
property is updated, based on an event, to represent what was
connected
This commit adds a header providing definitions for handling Alert
messages. Currently the header only focuses on handling incoming
alerts.
Signed-off-by: Adam Thomson
---
include/linux/usb/pd_ado.h | 42 ++
1 file
This commit adds a header providing definitions for handling Alert
messages. Currently the header only focuses on handling incoming
alerts.
Signed-off-by: Adam Thomson
---
include/linux/usb/pd_ado.h | 42 ++
1 file changed, 42 insertions(+)
create mode
This commit adds a power_supply class instance to represent a
PD source's voltage and current properties. This provides an
interface for reading these properties from user-space or other
drivers.
For PPS enabled Sources, this also provides write access to set
the current and voltage and allows
This commit adds a power_supply class instance to represent a
PD source's voltage and current properties. This provides an
interface for reading these properties from user-space or other
drivers.
For PPS enabled Sources, this also provides write access to set
the current and voltage and allows
This commit adds sink side support for Get_Status, Status,
Get_PPS_Status and PPS_Status handling. As there's the
potential for a partner to respond with Not_Supported
handling of this message is also added. Sending of
Not_Supported is added is added to handle messages
received but not yet
This commit adds sink side support for Get_Status, Status,
Get_PPS_Status and PPS_Status handling. As there's the
potential for a partner to respond with Not_Supported
handling of this message is also added. Sending of
Not_Supported is added is added to handle messages
received but not yet
Hi Jacopo,
Thank you for the patch.
On Thursday, 28 December 2017 16:01:21 EET Jacopo Mondi wrote:
> Remove soc_camera framework dependencies from tw9910 sensor driver.
> - Handle clock and gpios
> - Register async subdevice
> - Remove soc_camera specific g/s_mbus_config operations
> - Add
Hi Jacopo,
Thank you for the patch.
On Thursday, 28 December 2017 16:01:21 EET Jacopo Mondi wrote:
> Remove soc_camera framework dependencies from tw9910 sensor driver.
> - Handle clock and gpios
> - Register async subdevice
> - Remove soc_camera specific g/s_mbus_config operations
> - Add
801 - 900 of 1720 matches
Mail list logo