* [PATCH v2 0/2] arm64: dts: renesas: Remove renesas, no-ether-link property
From: Vladimir Zapolskiy @ 2017-12-21 15:18 UTC (permalink / raw)
To: linux-arm-kernel
The present change is a bug fix for AVB link iteratively up/down.
Steps to reproduce:
- start AVB TX stream (Using aplay via MSE),
- disconnect+reconnect the eth cable,
- after a reconnection the eth connection goes iteratively up/down
without user interaction,
- this may heal after some seconds or even stay for minutes.
As the documentation specifies, the "renesas,no-ether-link" option
should be used when a board does not provide a proper AVB_LINK signal.
There is no need for this option enabled on RCAR H3/M3 Salvator-X/XS
and ULCB starter kits since the AVB_LINK is correctly handled by HW.
Choosing to keep or remove the "renesas,no-ether-link" option will
have impact on the code flow in the following ways:
- keeping this option enabled may lead to unexpected behavior since
the RX & TX are enabled/disabled directly from adjust_link function
without any HW interrogation,
- removing this option, the RX & TX will only be enabled/disabled after
HW interrogation. The HW check is made through the LMON pin in PSR
register which specifies AVB_LINK signal value (0 - at low level;
1 - at high level).
In conclusion, the change is also a safety improvement because it
removes the "renesas,no-ether-link" option leading to a proper way
of detecting the link state based on HW interrogation and not on
software heuristic.
Note that DTS files for V3M Starter Kit, Draak and Eagle boards
contain the same property, the files are untouched due to unavailable
schematics to verify if the fix applies to these boards as well.
Changes from v1 to v2:
* per a request from Simon added Fixes tags to both changes,
the specified commits generalize Salvator-X and ULCB dtsi files
and the fixes should be applicable without a conflict, however
similar but virtually different fixes can be spread into Salvator-X
and ULCB board DTS files of older kernel revisions as well.
Bogdan Mirea (2):
arm64: dts: renesas: salvator-x: Remove renesas,no-ether-link property
arm64: dts: renesas: ulcb: Remove renesas,no-ether-link property
arch/arm64/boot/dts/renesas/salvator-common.dtsi | 1 -
arch/arm64/boot/dts/renesas/ulcb.dtsi | 1 -
2 files changed, 2 deletions(-)
--
2.8.1
^ permalink raw reply
* [PATCH 1/3] ARM: dts: am335x-boneblue: fix wl1835 IRQ pin
From: Tony Lindgren @ 2017-12-21 15:18 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171219223242.21386-1-robertcnelson@gmail.com>
* Robert Nelson <robertcnelson@gmail.com> [171219 14:35]:
> Use the correct IRQ gpio pin on the BeagleBone Blue to allow the
> wl1835 wireless module to actually work.
Thanks applying all three into omap-for-v4.16/dt.
Tony
^ permalink raw reply
* [GIT PULL] Renesas ARM Based SoC DT Bindings Updates for v4.16
From: Arnd Bergmann @ 2017-12-21 15:17 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <cover.1512553735.git.horms+renesas@verge.net.au>
On Wed, Dec 6, 2017 at 11:21 AM, Simon Horman
<horms+renesas@verge.net.au> wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these Renesas ARM based SoC DT bindings updates for v4.16.
>
>
> The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
>
> Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-dt-bindings-for-v4.16
>
> for you to fetch changes up to eebd0732136fd293c8f15a435978c1c34cd7f32f:
>
> arm64: renesas: document V3MSK board bindings (2017-11-29 09:18:24 +0100)
>
> ----------------------------------------------------------------
> Renesas ARM Based SoC DT Bindings Updates for v4.16
>
> * Document V3MSK board bindings
>
> These are the bindings for the R-Car V3M Starter Kit
>
> * Document M3-W-based Salvator-XS board bingigns
>
> Geert Uytterhoeven says "The Renesas Salvator-XS (Salvator-X 2nd version)
> development board can be equipped with either an R-Car H3 ES2.0 or M3-W
> ES1.x SiP, which are pin-compatible."
Pulled into next/dt, thanks!
Arnd
^ permalink raw reply
* [PATCH v2 0/4] arm64: defconfig: enable additional led triggers
From: Arnd Bergmann @ 2017-12-21 15:16 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <CAHLCerN4sYpU7PJG7JLhAy644s3jz9KD_myKWfOoOkEResPu-Q@mail.gmail.com>
On Wed, Dec 6, 2017 at 9:57 AM, Amit Kucheria <amit.kucheria@linaro.org> wrote:
> (Adding Arnd)
>
> Now that the merge window rush has abated, can you please apply this
> trivial series?
>
> On Mon, Nov 6, 2017 at 12:38 PM, Amit Kucheria <amit.kucheria@linaro.org> wrote:
>> This patchset enables the kernel panic and disk-activity trigger for LEDs
>> and then enables the panic trigger for three 96Boards - DB410c, Hikey and
>> Hikey960.
>>
>> DB410c and Hikey panic behaviour has been tested by triggering a panic
>> through /proc/sysrq-trigger, while Hikey960 is only compile-tested.
I applied all four now, but it would have been easier for me if you had either
sent them to the platform maintainers, or to arm at kernel.org.
Arnd
^ permalink raw reply
* [PATCH 1/2] ARM: sun8i: v3s: add EHCI/OHCI0 device nodes
From: Maxime Ripard @ 2017-12-21 15:16 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171221150537.20304-2-icenowy@aosc.io>
Hi,
On Thu, Dec 21, 2017 at 11:05:36PM +0800, Icenowy Zheng wrote:
> The USB PHY 0 on V3s SoC can also be routed to a pair of EHCI/OHCI
> controllers.
>
> Add the device nodes for the controllers.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
> ---
> arch/arm/boot/dts/sun8i-v3s.dtsi | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/arch/arm/boot/dts/sun8i-v3s.dtsi b/arch/arm/boot/dts/sun8i-v3s.dtsi
> index 443b083c6adc..cc315dc742d2 100644
> --- a/arch/arm/boot/dts/sun8i-v3s.dtsi
> +++ b/arch/arm/boot/dts/sun8i-v3s.dtsi
> @@ -264,6 +264,25 @@
> #phy-cells = <1>;
> };
>
> + ehci0: usb at 01c1a000 {
> + compatible = "allwinner,sun8i-v3s-ehci", "generic-ehci";
> + reg = <0x01c1a000 0x100>;
> + interrupts = <GIC_SPI 72 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&ccu CLK_BUS_EHCI0>, <&ccu CLK_BUS_OHCI0>;
> + resets = <&ccu RST_BUS_EHCI0>, <&ccu RST_BUS_OHCI0>;
Why are you taking the OHCI clocks and resets in the OHCI node..
> + status = "disabled";
> + };
> +
> + ohci0: usb at 01c1a400 {
> + compatible = "allwinner,sun8i-v3s-ohci", "generic-ohci";
> + reg = <0x01c1a400 0x100>;
> + interrupts = <GIC_SPI 73 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&ccu CLK_BUS_EHCI0>, <&ccu CLK_BUS_OHCI0>,
> + <&ccu CLK_USB_OHCI0>;
> + resets = <&ccu RST_BUS_EHCI0>, <&ccu RST_BUS_OHCI0>;
... And the EHCI clocks and resets in the OHCI node?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20171221/96d46b00/attachment.sig>
^ permalink raw reply
* [PATCH 1/8] ARM: dts: dra7: Add vbb-supply to cpu and additional voltages
From: Tony Lindgren @ 2017-12-21 15:15 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1513697066-27732-2-git-send-email-d-gerlach@ti.com>
* Dave Gerlach <d-gerlach@ti.com> [171219 15:27]:
> Add a vbb-supply phandle to the cpus node and also add an additional
> triplet of voltages for each OPP in the operating-points-v2 table to
> make use of the multi regulator support in the OPP core and provide the
> vbb regulator for use by the ti-opp-supply driver.
Sounds like these depend on the ti-opp-supply being available first?
Regards,
Tony
^ permalink raw reply
* [PATCH 0/7] ARM: dts: dra7: Enable x2 lane mode support
From: Tony Lindgren @ 2017-12-21 15:13 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171219093133.16565-1-kishon@ti.com>
* Kishon Vijay Abraham I <kishon@ti.com> [171219 01:34]:
> Add properties to enable PCIe x2 lane mode since all dra7
> based SoCs support x2 lane mode.
>
> However only dra76-evm has a slot which can support x2 lane
> cards. Hence only enable x2 lane mode in dra76-evm.
> (am571x-idk can support x2 lane mode but that makes usb port
> not functional so not including the patch to enable
> x2 mode in am571x-idk)
>
> Also included in this series is patch to enable PCIe configs
> (both host and device) in omap2plus_defconfig and
> multi_v7_defconfig
>
> In order to get x2 mode working [1] is required.
>
> However by keeping the older compatible, this series won't
> break functionality if this series is merged before [1]
OK applying into omap-for-v4.16/dt and omap-for-v4.16/defconfig.
Thanks,
Tony
^ permalink raw reply
* [PATCH] ARM: make ARCH_S3C24XX select USE_OF and clean-up boot/dts/Makefile
From: Arnd Bergmann @ 2017-12-21 15:11 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1511749163-11057-1-git-send-email-yamada.masahiro@socionext.com>
On Mon, Nov 27, 2017 at 3:19 AM, Masahiro Yamada
<yamada.masahiro@socionext.com> wrote:
> ARCH_S3C24XX is a very exceptional platform that some DT files in
> arch/arm/boot/dts/, but does not select USE_OF.
>
> All the other platforms with DT files correctly select USE_OF
> directly or indirectly (Most of them are either ARCH_MULTIPLATFORM
> or ARM_SINGLE_ARMV7M).
>
> With ARCH_S3C24XX fixed, "ifeq ($(CONFIG_OF),y)" in DT Makefile
> can be deleted.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Applied to next/dt, thanks!
Arnd
^ permalink raw reply
* [RESEND PATCH 4/4] ARM: dts: socfpga: Add generic compatible string for I2C EEPROM
From: Arnd Bergmann @ 2017-12-21 15:08 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171124162750.18756-4-javierm@redhat.com>
On Fri, Nov 24, 2017 at 5:27 PM, Javier Martinez Canillas
<javierm@redhat.com> wrote:
> The at24 driver allows to register I2C EEPROM chips using different vendor
> and devices, but the I2C subsystem does not take the vendor into account
> when matching using the I2C table since it only has device entries.
>
> But when matching using an OF table, both the vendor and device has to be
> taken into account so the driver defines only a set of compatible strings
> using the "atmel" vendor as a generic fallback for compatible I2C devices.
>
> So add this generic fallback to the device node compatible string to make
> the device to match the driver using the OF device ID table.
>
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
Applied, thanks!
Arnd
^ permalink raw reply
* [RESEND PATCH 3/4] ARM: dts: lpc18xx: Add generic compatible string for I2C EEPROM
From: Arnd Bergmann @ 2017-12-21 15:08 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171124162750.18756-3-javierm@redhat.com>
On Fri, Nov 24, 2017 at 5:27 PM, Javier Martinez Canillas
<javierm@redhat.com> wrote:
> The at24 driver allows to register I2C EEPROM chips using different vendor
> and devices, but the I2C subsystem does not take the vendor into account
> when matching using the I2C table since it only has device entries.
>
> But when matching using an OF table, both the vendor and device has to be
> taken into account so the driver defines only a set of compatible strings
> using the "atmel" vendor as a generic fallback for compatible I2C devices.
>
> So add this generic fallback to the device node compatible string to make
> the device to match the driver using the OF device ID table.
>
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
Applied, thanks
Arnd
^ permalink raw reply
* [PATCH v2] ARM: dts: sunxi: Add sid for a83t
From: Icenowy Zheng @ 2017-12-21 15:07 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171221145512.llxvzkcrjpquhczi@flea.lan>
? 2017?12?21???? CST ??10:55:12?Maxime Ripard ???
> Hi Kyle,
>
> On Tue, Dec 19, 2017 at 03:05:23PM -0600, kevans91 at ksu.edu wrote:
> > Allwinner a83t has a 1 KB sid block with efuse for security rootkey and
> > thermal calibration data, add node to describe it.
> >
> > a83t-sid is not currently supported by nvmem/sunxi-sid, but it is
> > supported in an external driver for FreeBSD.
> >
> > Signed-off-by: Kyle Evans <kevans91@ksu.edu>
>
> The patch looks fine in itself, but we've had a number of issues with
> the register layout (and access patterns) in the past, so I'd rather
> have something that works in Linux too if possible.
I think for A83T it can just refer H3.
>
> Maxime
^ permalink raw reply
* [RESEND PATCH 1/4] ARM: dts: efm32: Add generic compatible string for I2C EEPROM
From: Arnd Bergmann @ 2017-12-21 15:06 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171124162750.18756-1-javierm@redhat.com>
On Fri, Nov 24, 2017 at 5:27 PM, Javier Martinez Canillas
<javierm@redhat.com> wrote:
> The at24 driver allows to register I2C EEPROM chips using different vendor
> and devices, but the I2C subsystem does not take the vendor into account
> when matching using the I2C table since it only has device entries.
>
> But when matching using an OF table, both the vendor and device has to be
> taken into account so the driver defines only a set of compatible strings
> using the "atmel" vendor as a generic fallback for compatible I2C devices.
>
> So add this generic fallback to the device node compatible string to make
> the device to match the driver using the OF device ID table.
>
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
Applied to next/dt, thanks
Arnd
^ permalink raw reply
* [PATCH 2/2] ARM: sun8i: v3s: enable EHCI/OHCI for Lichee Pi Zero
From: Icenowy Zheng @ 2017-12-21 15:05 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171221150537.20304-1-icenowy@aosc.io>
As the USB port on Lichee Pi Zero works in the OTG mode, enable the
EHCI/OHCI controllers for it.
Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
---
arch/arm/boot/dts/sun8i-v3s-licheepi-zero.dts | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-v3s-licheepi-zero.dts b/arch/arm/boot/dts/sun8i-v3s-licheepi-zero.dts
index 387fc2aa546d..cf2d9fe3bbb7 100644
--- a/arch/arm/boot/dts/sun8i-v3s-licheepi-zero.dts
+++ b/arch/arm/boot/dts/sun8i-v3s-licheepi-zero.dts
@@ -77,6 +77,10 @@
};
};
+&ehci0 {
+ status = "okay";
+};
+
&mmc0 {
pinctrl-0 = <&mmc0_pins_a>;
pinctrl-names = "default";
@@ -86,6 +90,10 @@
status = "okay";
};
+&ohci0 {
+ status = "okay";
+};
+
&uart0 {
pinctrl-0 = <&uart0_pins_a>;
pinctrl-names = "default";
--
2.14.2
^ permalink raw reply related
* [PATCH 1/2] ARM: sun8i: v3s: add EHCI/OHCI0 device nodes
From: Icenowy Zheng @ 2017-12-21 15:05 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171221150537.20304-1-icenowy@aosc.io>
The USB PHY 0 on V3s SoC can also be routed to a pair of EHCI/OHCI
controllers.
Add the device nodes for the controllers.
Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
---
arch/arm/boot/dts/sun8i-v3s.dtsi | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-v3s.dtsi b/arch/arm/boot/dts/sun8i-v3s.dtsi
index 443b083c6adc..cc315dc742d2 100644
--- a/arch/arm/boot/dts/sun8i-v3s.dtsi
+++ b/arch/arm/boot/dts/sun8i-v3s.dtsi
@@ -264,6 +264,25 @@
#phy-cells = <1>;
};
+ ehci0: usb at 01c1a000 {
+ compatible = "allwinner,sun8i-v3s-ehci", "generic-ehci";
+ reg = <0x01c1a000 0x100>;
+ interrupts = <GIC_SPI 72 IRQ_TYPE_LEVEL_HIGH>;
+ clocks = <&ccu CLK_BUS_EHCI0>, <&ccu CLK_BUS_OHCI0>;
+ resets = <&ccu RST_BUS_EHCI0>, <&ccu RST_BUS_OHCI0>;
+ status = "disabled";
+ };
+
+ ohci0: usb at 01c1a400 {
+ compatible = "allwinner,sun8i-v3s-ohci", "generic-ohci";
+ reg = <0x01c1a400 0x100>;
+ interrupts = <GIC_SPI 73 IRQ_TYPE_LEVEL_HIGH>;
+ clocks = <&ccu CLK_BUS_EHCI0>, <&ccu CLK_BUS_OHCI0>,
+ <&ccu CLK_USB_OHCI0>;
+ resets = <&ccu RST_BUS_EHCI0>, <&ccu RST_BUS_OHCI0>;
+ status = "disabled";
+ };
+
ccu: clock at 1c20000 {
compatible = "allwinner,sun8i-v3s-ccu";
reg = <0x01c20000 0x400>;
--
2.14.2
^ permalink raw reply related
* [PATCH 0/2] Add EHCI/OHCI nodes for V3s and Lichee Pi Zero
From: Icenowy Zheng @ 2017-12-21 15:05 UTC (permalink / raw)
To: linux-arm-kernel
As the PHY dual-route property is added to 4.15-rc, the EHCI/OHCI nodes
are now necessary.
Please apply these patches to 4.15, Thanks!
Icenowy Zheng (2):
ARM: sun8i: v3s: add EHCI/OHCI0 device nodes
ARM: sun8i: v3s: enable EHCI/OHCI for Lichee Pi Zero
arch/arm/boot/dts/sun8i-v3s-licheepi-zero.dts | 8 ++++++++
arch/arm/boot/dts/sun8i-v3s.dtsi | 19 +++++++++++++++++++
2 files changed, 27 insertions(+)
--
2.14.2
^ permalink raw reply
* [GIT PULL] tee async tee supplicant communication for v4.16
From: Arnd Bergmann @ 2017-12-21 15:03 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171129102715.dsxcsq6s5tvnep2s@jax>
On Wed, Nov 29, 2017 at 11:27 AM, Jens Wiklander
<jens.wiklander@linaro.org> wrote:
> ----------------------------------------------------------------
> Enable async communication with tee supplicant
>
> This pull request enables asynchronous communication with TEE supplicant
> by introducing meta parameters in the user space API. The meta
> parameters can be used to tag requests with an id that can be matched
> against an asynchronous response as is done here in the OP-TEE driver.
>
> Asynchronous supplicant communication is needed by OP-TEE to implement
> GlobalPlatforms TEE Sockets API Specification v1.0.1. The specification
> is available at https://www.globalplatform.org/specificationsdevice.asp.
>
> This change is backwards compatible allowing older supplicants to work
> with newer kernels and vice versa.
>
Pulled into next/drivers, thanks!
Arnd
^ permalink raw reply
* [PATCH 0/2] ARM: dts: Some am43x fixes
From: Tony Lindgren @ 2017-12-21 14:58 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171215171643.8345-1-d-gerlach@ti.com>
* Dave Gerlach <d-gerlach@ti.com> [171215 09:19]:
> Hi,
> This series has two fixes for am43x based platforms. First patch disables OPP50
> on am437x-idk-evm which the board supply does not support. Second patch is for
> am43x-epos-evm and adds dcdc2 regulator as the missing cpu0-supply which
> enables CPUFreq on this platform.
Applying both into omap-for-v4.16/dt thanks.
Tony
^ permalink raw reply
* [PATCH 0/2] arm64: dts: renesas: Remove renesas,no-ether-link property
From: Vladimir Zapolskiy @ 2017-12-21 14:57 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171221112830.4ehdp237zsddfvrv@verge.net.au>
Hi Simon,
On 12/21/2017 01:28 PM, Simon Horman wrote:
> On Wed, Dec 20, 2017 at 03:22:10PM +0200, Vladimir Zapolskiy wrote:
>> The present change is a bug fix for AVB link iteratively up/down.
>
> If this is a bug please consider including Fixes tags in the patches.
>
would you prefer to get v2 with the Fixes tags added or short replies
to v1 with the requested information?
--
With best wishes,
Vladimir
^ permalink raw reply
* [PATCH v2] ARM: dts: sunxi: Add sid for a83t
From: Maxime Ripard @ 2017-12-21 14:55 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171219210523.10428-1-kevans91@ksu.edu>
Hi Kyle,
On Tue, Dec 19, 2017 at 03:05:23PM -0600, kevans91 at ksu.edu wrote:
> Allwinner a83t has a 1 KB sid block with efuse for security rootkey and
> thermal calibration data, add node to describe it.
>
> a83t-sid is not currently supported by nvmem/sunxi-sid, but it is
> supported in an external driver for FreeBSD.
>
> Signed-off-by: Kyle Evans <kevans91@ksu.edu>
The patch looks fine in itself, but we've had a number of issues with
the register layout (and access patterns) in the past, so I'd rather
have something that works in Linux too if possible.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20171221/cf6e2c93/attachment.sig>
^ permalink raw reply
* [PATCH v5 4/5] DTS: gta04: add uart2 child node for w2sg00x4
From: Tony Lindgren @ 2017-12-21 14:53 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1b1c7a8319eaf61a46eebd7a366ea745b7a54634.1512114577.git.hns@goldelico.com>
* H. Nikolaus Schaller <hns@goldelico.com> [171130 23:52]:
> GTA04 has a W2SG0004/84 connected to UART2 of the OMAP3
> processor. A GPIO can pulse the on/off toggle switch.
>
> The VSIM regulator is used to power on/off the LNA of an external
> active GPS antenna so that a driver can turn the LNA off if GPS is
> not needed to save battery energy.
>
> Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com>
Sounds like Greg's going to take the whole series, so for this
patch:
Acked-by: Tony Lindgren <tony@atomide.com>
> ---
> arch/arm/boot/dts/omap3-gta04.dtsi | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi b/arch/arm/boot/dts/omap3-gta04.dtsi
> index 4504908c23fe..1ad744a25c36 100644
> --- a/arch/arm/boot/dts/omap3-gta04.dtsi
> +++ b/arch/arm/boot/dts/omap3-gta04.dtsi
> @@ -477,6 +477,13 @@
> &uart2 {
> pinctrl-names = "default";
> pinctrl-0 = <&uart2_pins>;
> +
> + gps: gps {
> + compatible = "wi2wi,w2sg0004";
> + lna-supply = <&vsim>; /* LNA regulator */
> + /* GPIO_145: trigger for on/off-impulse for w2sg0004 */
> + enable-gpios = <&gpio5 17 GPIO_ACTIVE_HIGH>;
> + };
> };
>
> &uart3 {
> --
> 2.12.2
>
^ permalink raw reply
* [PATCH] ARM: dts: imx: Add memory node unit name
From: Marco Franchi @ 2017-12-21 14:26 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171221090736.3ac9d5db@karo-electronics.de>
Hi Lothar,
2017-12-21 6:07 GMT-02:00 Lothar Wa?mann <LW@karo-electronics.de>:
> Hi,
>
> On Wed, 6 Dec 2017 13:59:49 -0200 Marco Franchi wrote:
>> Fix the following warnings from dtc by adding the unit name to memory
>> nodes:
>>
>> Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but no unit name
>>
>> Converted using the following command:
>>
>> perl -p0777i -e 's/memory \{\n\t\treg = \<0x+([0-9a-f])/memory\@$1$\0000000 \{\n\t\treg = <0x$1/m' `find ./arch/arm/boot/dts -name "imx*"`
>>
>> The files below were manually fixed:
>> -imx1-ads.dts
>> -imx1-apf9328.dts
>>
> The imx*.dtsi files all have this:
> | memory { device_type = "memory"; reg = <0 0>; };
> Thus you will end up with a 'memory' node with a reg = <0 0> entry and
> an additional 'memory at ...' node with the correct 'reg' values.
You are right. The .dtb files were composed by two different memory nodes.
Do you have some recommendation to take off this specific warning?
>
>
> Lothar Wa?mann
Marco Franchi
^ permalink raw reply
* [PATCH 4/4] ARM: dts: vf610-zii-dev-rev-b: add interrupts for 88e1545 PHY
From: Andrew Lunn @ 2017-12-21 13:40 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <CACRpkdas5JJ4KHE4g=sPXag=3vQt4TS5EcZBsy=LRfw8tqcgOw@mail.gmail.com>
On Thu, Dec 21, 2017 at 01:32:21PM +0100, Linus Walleij wrote:
> On Thu, Dec 21, 2017 at 12:12 AM, Russell King
> <rmk+kernel@armlinux.org.uk> wrote:
>
> > The 88e1545 PHY has its interrupts wired to the VF610, so we might as
> > well use them.
> >
> > Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
> > ---
> > This is certainly not correct, as all PHYs on this device share the
> > same interrupt line, but we can't specify the pinmux settings
> > individually on each PHY. How should this be handled?
>
> I do not know the details of the Marvell switch.
Hi Linus
The 88e1545 is a discreet quad PHY. It is connected to the switch, but
not integrated into the switch. All its interrupt handling is done
with a GPIO onto the Freescale processor, via a GPIO. There is nothing
DSA related here at all with respect to the interrupt. It is just a
normal GPIO interrupt. What is a bit odd is that it one shared
interrupt for all four PHYs.
What you described with an irqchip inside the switch is what we
actually do for the internal PHYs on Marvell devices. And it is what i
recommend for all DSA drivers. Expose standard IRQs, and let phylib
use them in its normal way.
Andrew
^ permalink raw reply
* [PATCH 1/2] thermal: mtk: Cleanup unused defines
From: Zhang Rui @ 2017-12-21 13:40 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <feb1e2bd-bee8-0950-7ecf-8e8c0e157f57@gmail.com>
On Thu, 2017-12-21 at 11:01 +0100, Matthias Brugger wrote:
>
> On 12/01/2017 11:43 AM, Matthias Brugger wrote:
> >
> > The mtk_thermal has some defiens which are never used within the
> > driver.
> > This patch delets them.
> >
> > Signed-off-by: Matthias Brugger <mbrugger@suse.com>
> > ---
> Rui, Eduardo, do you have any comments on this patch?
>
No, I don't have any.
I suppose Eduardo will review them soon as I need the thermal soc
material for next merge window.
thanks,
rui
> Regards,
> Matthias
>
> >
> > ?drivers/thermal/mtk_thermal.c | 9 +--------
> > ?1 file changed, 1 insertion(+), 8 deletions(-)
> >
> > diff --git a/drivers/thermal/mtk_thermal.c
> > b/drivers/thermal/mtk_thermal.c
> > index 1e61c09153c9..c75661a3801a 100644
> > --- a/drivers/thermal/mtk_thermal.c
> > +++ b/drivers/thermal/mtk_thermal.c
> > @@ -32,15 +32,10 @@
> > ?#include <linux/types.h>
> > ?
> > ?/* AUXADC Registers */
> > -#define AUXADC_CON0_V 0x000
> > -#define AUXADC_CON1_V 0x004
> > ?#define AUXADC_CON1_SET_V 0x008
> > ?#define AUXADC_CON1_CLR_V 0x00c
> > ?#define AUXADC_CON2_V 0x010
> > ?#define AUXADC_DATA(channel) (0x14 + (channel) * 4)
> > -#define AUXADC_MISC_V 0x094
> > -
> > -#define AUXADC_CON1_CHANNEL(x) BIT(x)
> > ?
> > ?#define APMIXED_SYS_TS_CON1 0x604
> > ?
> > @@ -158,8 +153,6 @@
> > ?/* The number of sensing points per bank */
> > ?#define MT2712_NUM_SENSORS_PER_ZONE 4
> > ?
> > -#define THERMAL_NAME????"mtk-thermal"
> > -
> > ?struct mtk_thermal;
> > ?
> > ?struct thermal_bank_cfg {
> > @@ -765,7 +758,7 @@ static struct platform_driver
> > mtk_thermal_driver = {
> > ? .probe = mtk_thermal_probe,
> > ? .remove = mtk_thermal_remove,
> > ? .driver = {
> > - .name = THERMAL_NAME,
> > + .name = "mtk-thermal",
> > ? .of_match_table = mtk_thermal_of_match,
> > ? },
> > ?};
> >
^ permalink raw reply
* [PATCH RESEND 1/1] cpufreq: imx6q: switch to Use clk_bulk_get to refine clk operations
From: Dong Aisheng @ 2017-12-21 13:18 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20170914214032.GE11836@ubuntu>
Hi Rafael,
On Thu, Sep 14, 2017 at 02:40:32PM -0700, Viresh Kumar wrote:
> On 31-08-17, 19:43, Dong Aisheng wrote:
> > Use clk_bulk_get to ease the driver clocks handling.
> >
> > Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
> > Cc: Viresh Kumar <viresh.kumar@linaro.org>
> > Cc: Shawn Guo <shawnguo@kernel.org>
> > Cc: Anson Huang <anson.huang@nxp.com>
> > Cc: Leonard Crestez <leonard.crestez@nxp.com>
> > Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com>
> > --
> > The original one is here which depends on clk_bulk APIs.
> > https://patchwork.kernel.org/patch/9737337/
> > Now the clk_bulk APIs are already in kernel, so resend the patch.
> > (Patch title changed a bit to be more specific.)
> > ---
> > drivers/cpufreq/imx6q-cpufreq.c | 125 ++++++++++++++++++----------------------
> > 1 file changed, 56 insertions(+), 69 deletions(-)
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>
Would you help pick it?
I did not see it in latest kernel.
It still applies.
Regards
Dong Aisheng
^ permalink raw reply
* [PATCH] drm/sun4i: hdmi: Fix sun4i_tmds_determine_rate
From: Maxime Ripard @ 2017-12-21 12:48 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171221112411.21550-1-net147@gmail.com>
Hi,
On Thu, Dec 21, 2017 at 10:24:11PM +1100, Jonathan Liu wrote:
> There are several issues in sun4i_tmds_determine_rate:
> - doesn't check if the best match was already set before comparing it
> with the enumerated parameters which could result in integer divide
> by zero
> - doesn't consider rate halving when determining closest match if it
> can't match the requested rate exactly
> - sets best_div to i which corresponds to rate halving when it should be
> set to j which corresponds to the divider
>
> Fix these issues.
>
> Fixes: 9c5681011a0c ("drm/sun4i: Add HDMI support")
> Signed-off-by: Jonathan Liu <net147@gmail.com>
Please make separate patches for each of these issues, if possible
detailing how do you reproduce them.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20171221/555a6fd4/attachment.sig>
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox