* [PATCH v2 1/4] dt-bindings: thermal/armada: describe AP806 and CP110
From: Baruch Siach @ 2017-12-03 11:11 UTC (permalink / raw)
To: linux-arm-kernel
Add compatible strings for AP806 and CP110 that are part of the Armada 8k/7k
line of SoCs.
Add a note on the difference in the size of the control area in different
bindings. This is an existing difference between the Armada 375 binding and
the rest. The new AP806 and CP110 bindings are similar to the existing Armada
375 in this regard.
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
---
v2: No change
---
Documentation/devicetree/bindings/thermal/armada-thermal.txt | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/thermal/armada-thermal.txt b/Documentation/devicetree/bindings/thermal/armada-thermal.txt
index 24aacf8948c5..eec57f509166 100644
--- a/Documentation/devicetree/bindings/thermal/armada-thermal.txt
+++ b/Documentation/devicetree/bindings/thermal/armada-thermal.txt
@@ -7,12 +7,19 @@ Required properties:
marvell,armada375-thermal
marvell,armada380-thermal
marvell,armadaxp-thermal
+ marvell,armada-ap806-thermal
+ marvell,armada-cp110-thermal
- reg: Device's register space.
Two entries are expected, see the examples below.
The first one is required for the sensor register;
- the second one is required for the control register
+ the second one is required for the control area
to be used for sensor initialization (a.k.a. calibration).
+ The size of the control area must be 4 for
+ marvell,armada370-thermal, marvell,armada380-thermal, and
+ marvell,armadaxp-thermal. The size must be 8 for
+ marvell,armada375-thermal, marvell,armada-ap806-thermal, and
+ marvell,armada-cp110-thermal.
Example:
--
2.15.0
^ permalink raw reply related
* [PATCH net-next v4 2/2] net: ethernet: socionext: add AVE ethernet driver
From: kbuild test robot @ 2017-12-03 9:38 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1512090230-27594-3-git-send-email-hayashi.kunihiko@socionext.com>
Hi Kunihiko,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Kunihiko-Hayashi/dt-bindings-net-add-DT-bindings-for-Socionext-UniPhier-AVE/20171203-095248
config: ia64-allyesconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 6.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=ia64
All warnings (new ones prefixed by >>):
In file included from arch/ia64/include/asm/smp.h:21:0,
from include/linux/smp.h:64,
from include/linux/percpu.h:7,
from include/linux/percpu-rwsem.h:7,
from include/linux/fs.h:33,
from include/linux/net.h:27,
from include/linux/skbuff.h:29,
from include/linux/if_ether.h:23,
from include/linux/etherdevice.h:25,
from drivers/net/ethernet/socionext/sni_ave.c:19:
drivers/net/ethernet/socionext/sni_ave.c: In function 'ave_pfsel_set_promisc':
arch/ia64/include/asm/io.h:396:30: warning: large integer implicitly truncated to unsigned type [-Woverflow]
#define writel(v,a) __writel((v), (a))
^
>> drivers/net/ethernet/socionext/sni_ave.c:1046:2: note: in expansion of macro 'writel'
writel(AVE_PFMBYTE_MASK0, priv->base + AVE_PFMBYTE(entry));
^~~~~~
vim +/writel +1046 drivers/net/ethernet/socionext/sni_ave.c
1034
1035 static void ave_pfsel_set_promisc(struct net_device *ndev,
1036 unsigned int entry, u32 rxring)
1037 {
1038 struct ave_private *priv = netdev_priv(ndev);
1039
1040 if (WARN_ON(entry > AVE_PF_SIZE))
1041 return;
1042
1043 ave_pfsel_stop(ndev, entry);
1044
1045 /* set byte mask */
> 1046 writel(AVE_PFMBYTE_MASK0, priv->base + AVE_PFMBYTE(entry));
1047 writel(AVE_PFMBYTE_MASK1, priv->base + AVE_PFMBYTE(entry) + 4);
1048
1049 /* set bit mask filter */
1050 writel(AVE_PFMBIT_MASK, priv->base + AVE_PFMBIT(entry));
1051
1052 /* set selector to rxring */
1053 writel(rxring, priv->base + AVE_PFSEL(entry));
1054
1055 ave_pfsel_start(ndev, entry);
1056 }
1057
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/gzip
Size: 52905 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20171203/ff5e2b51/attachment-0001.gz>
^ permalink raw reply
* [PATCH 1/2] dt-bindings: trivial: add tfa9879 device
From: Peter Rosin @ 2017-12-03 6:59 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <CAOMZO5BA2ZbBnPVORALkEGV21j7H9GJW_2uVvtEEU=8qM599-w@mail.gmail.com>
On 2017-12-02 22:17, Fabio Estevam wrote:
> On Fri, Dec 1, 2017 at 8:44 PM, Peter Rosin <peda@axentia.se> wrote:
>> Add record for NXP TFA9879 Mono BTL Class D audio amplifier.
>>
>> Signed-off-by: Peter Rosin <peda@axentia.se>
>> ---
>> Documentation/devicetree/bindings/trivial-devices.txt | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/devicetree/bindings/trivial-devices.txt b/Documentation/devicetree/bindings/trivial-devices.txt
>> index af284fbd4d23..4cf30ce4e71f 100644
>> --- a/Documentation/devicetree/bindings/trivial-devices.txt
>> +++ b/Documentation/devicetree/bindings/trivial-devices.txt
>> @@ -157,6 +157,7 @@ nxp,pcf2127 Real-time clock
>> nxp,pcf2129 Real-time clock
>> nxp,pcf8563 Real-time clock/calendar
>> nxp,pcf85063 Tiny Real-Time Clock
>> +nxp,tfa9879 Mono BTL Class D audio amplifier
>
> This is already described at Documentation/devicetree/bindings/sound/tfa9879.txt
Right. However, the patch adding that should have been sent to me, the
maintainer of the driver. That is carefully recorded in MAINTAINERS. So,
forgive me for assuming that nothing had changed in the driver behind my
back.
Had that patch been sent my way as it should have been, I would have
insisted that maintenance of the bindings had been kept together with
the maintenance of the driver.
Cheers,
Peter
^ permalink raw reply
* [PATCH] ARM: dts: qcom: msm8974: Add Sony Xperia Z1 Compact
From: Attila Szöllősi @ 2017-12-03 4:09 UTC (permalink / raw)
To: linux-arm-kernel
This patch adds a DTS file for Sony Xperia Z1 Compact with support for
regulators, serial UART, eMMC/SD-card, USB, charger, backlight,
coincell and buttons.
Work based on arch/arm/boot/dts/qcom-msm8974-sony-xperia-honami.dts.
Signed-off-by: Attila Sz?ll?si <ata2001@airmail.cc>
---
arch/arm/boot/dts/Makefile | 1 +
.../boot/dts/qcom-msm8974-sony-xperia-amami.dts | 436 +++++++++++++++++++++
2 files changed, 437 insertions(+)
create mode 100644 arch/arm/boot/dts/qcom-msm8974-sony-xperia-amami.dts
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 043d7c720..06a50f646 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -738,6 +738,7 @@ dtb-$(CONFIG_ARCH_QCOM) += \
qcom-msm8960-cdp.dtb \
qcom-msm8974-fairphone-fp2.dtb \
qcom-msm8974-lge-nexus5-hammerhead.dtb \
+ qcom-msm8974-sony-xperia-amami.dtb \
qcom-msm8974-sony-xperia-castor.dtb \
qcom-msm8974-sony-xperia-honami.dtb \
qcom-mdm9615-wp8548-mangoh-green.dtb
diff --git a/arch/arm/boot/dts/qcom-msm8974-sony-xperia-amami.dts b/arch/arm/boot/dts/qcom-msm8974-sony-xperia-amami.dts
new file mode 100644
index 000000000..5669f5f58
--- /dev/null
+++ b/arch/arm/boot/dts/qcom-msm8974-sony-xperia-amami.dts
@@ -0,0 +1,436 @@
+// SPDX-License-Identifier: GPL-2.0
+#include "qcom-msm8974.dtsi"
+#include "qcom-pm8841.dtsi"
+#include "qcom-pm8941.dtsi"
+#include <dt-bindings/gpio/gpio.h>
+#include <dt-bindings/input/input.h>
+#include <dt-bindings/pinctrl/qcom,pmic-gpio.h>
+
+/ {
+ model = "Sony Xperia Z1 Compact";
+ compatible = "sony,xperia-amami", "qcom,msm8974";
+
+ aliases {
+ serial0 = &blsp1_uart2;
+ };
+
+ chosen {
+ stdout-path = "serial0:115200n8";
+ };
+
+ gpio-keys {
+ compatible = "gpio-keys";
+ input-name = "gpio-keys";
+
+ pinctrl-names = "default";
+ pinctrl-0 = <&gpio_keys_pin_a>;
+
+ volume-down {
+ label = "volume_down";
+ gpios = <&pm8941_gpios 2 GPIO_ACTIVE_LOW>;
+ linux,input-type = <1>;
+ linux,code = <KEY_VOLUMEDOWN>;
+ };
+
+ camera-snapshot {
+ label = "camera_snapshot";
+ gpios = <&pm8941_gpios 3 GPIO_ACTIVE_LOW>;
+ linux,input-type = <1>;
+ linux,code = <KEY_CAMERA>;
+ };
+
+ camera-focus {
+ label = "camera_focus";
+ gpios = <&pm8941_gpios 4 GPIO_ACTIVE_LOW>;
+ linux,input-type = <1>;
+ linux,code = <KEY_CAMERA_FOCUS>;
+ };
+
+ volume-up {
+ label = "volume_up";
+ gpios = <&pm8941_gpios 5 GPIO_ACTIVE_LOW>;
+ linux,input-type = <1>;
+ linux,code = <KEY_VOLUMEUP>;
+ };
+ };
+
+ memory at 0 {
+ reg = <0 0x40000000>, <0x40000000 0x40000000>;
+ device_type = "memory";
+ };
+
+ smd {
+ rpm {
+ rpm_requests {
+ pm8841-regulators {
+ s1 {
+ regulator-min-microvolt = <675000>;
+ regulator-max-microvolt = <1050000>;
+ };
+
+ s2 {
+ regulator-min-microvolt = <500000>;
+ regulator-max-microvolt = <1050000>;
+ };
+
+ s3 {
+ regulator-min-microvolt = <500000>;
+ regulator-max-microvolt = <1050000>;
+ };
+
+ s4 {
+ regulator-min-microvolt = <500000>;
+ regulator-max-microvolt = <1050000>;
+ };
+ };
+
+ pm8941-regulators {
+ vdd_l1_l3-supply = <&pm8941_s1>;
+ vdd_l2_lvs1_2_3-supply = <&pm8941_s3>;
+ vdd_l4_l11-supply = <&pm8941_s1>;
+ vdd_l5_l7-supply = <&pm8941_s2>;
+ vdd_l6_l12_l14_l15-supply = <&pm8941_s2>;
+ vdd_l9_l10_l17_l22-supply = <&vreg_boost>;
+ vdd_l13_l20_l23_l24-supply = <&vreg_boost>;
+ vdd_l21-supply = <&vreg_boost>;
+
+ s1 {
+ regulator-min-microvolt = <1300000>;
+ regulator-max-microvolt = <1300000>;
+ regulator-always-on;
+ regulator-boot-on;
+ };
+
+ s2 {
+ regulator-min-microvolt = <2150000>;
+ regulator-max-microvolt = <2150000>;
+ regulator-boot-on;
+ };
+
+ s3 {
+ regulator-min-microvolt = <1800000>;
+ regulator-max-microvolt = <1800000>;
+ regulator-always-on;
+ regulator-boot-on;
+ };
+
+ s4 {
+ regulator-min-microvolt = <5000000>;
+ regulator-max-microvolt = <5000000>;
+ };
+
+ l1 {
+ regulator-min-microvolt = <1225000>;
+ regulator-max-microvolt = <1225000>;
+
+ regulator-always-on;
+ regulator-boot-on;
+ };
+
+ l2 {
+ regulator-min-microvolt = <1200000>;
+ regulator-max-microvolt = <1200000>;
+ };
+
+ l3 {
+ regulator-min-microvolt = <1200000>;
+ regulator-max-microvolt = <1200000>;
+ };
+
+ l4 {
+ regulator-min-microvolt = <1225000>;
+ regulator-max-microvolt = <1225000>;
+ };
+
+ l5 {
+ regulator-min-microvolt = <1800000>;
+ regulator-max-microvolt = <1800000>;
+ };
+
+ l6 {
+ regulator-min-microvolt = <1800000>;
+ regulator-max-microvolt = <1800000>;
+
+ regulator-boot-on;
+ };
+
+ l7 {
+ regulator-min-microvolt = <1800000>;
+ regulator-max-microvolt = <1800000>;
+
+ regulator-boot-on;
+ };
+
+ l8 {
+ regulator-min-microvolt = <1800000>;
+ regulator-max-microvolt = <1800000>;
+ };
+
+ l9 {
+ regulator-min-microvolt = <1800000>;
+ regulator-max-microvolt = <2950000>;
+ };
+
+ l11 {
+ regulator-min-microvolt = <1300000>;
+ regulator-max-microvolt = <1350000>;
+ };
+
+ l12 {
+ regulator-min-microvolt = <1800000>;
+ regulator-max-microvolt = <1800000>;
+
+ regulator-always-on;
+ regulator-boot-on;
+ };
+
+ l13 {
+ regulator-min-microvolt = <1800000>;
+ regulator-max-microvolt = <2950000>;
+
+ regulator-boot-on;
+ };
+
+ l14 {
+ regulator-min-microvolt = <1800000>;
+ regulator-max-microvolt = <1800000>;
+ };
+
+ l15 {
+ regulator-min-microvolt = <2050000>;
+ regulator-max-microvolt = <2050000>;
+ };
+
+ l16 {
+ regulator-min-microvolt = <2700000>;
+ regulator-max-microvolt = <2700000>;
+ };
+
+ l17 {
+ regulator-min-microvolt = <2700000>;
+ regulator-max-microvolt = <2700000>;
+ };
+
+ l18 {
+ regulator-min-microvolt = <2850000>;
+ regulator-max-microvolt = <2850000>;
+ };
+
+ l19 {
+ regulator-min-microvolt = <3300000>;
+ regulator-max-microvolt = <3300000>;
+ };
+
+ l20 {
+ regulator-min-microvolt = <2950000>;
+ regulator-max-microvolt = <2950000>;
+
+ regulator-allow-set-load;
+ regulator-boot-on;
+ regulator-system-load = <200000>;
+ };
+
+ l21 {
+ regulator-min-microvolt = <2950000>;
+ regulator-max-microvolt = <2950000>;
+
+ regulator-boot-on;
+ };
+
+ l22 {
+ regulator-min-microvolt = <3000000>;
+ regulator-max-microvolt = <3000000>;
+ };
+
+ l23 {
+ regulator-min-microvolt = <2800000>;
+ regulator-max-microvolt = <2800000>;
+ };
+
+ l24 {
+ regulator-min-microvolt = <3075000>;
+ regulator-max-microvolt = <3075000>;
+
+ regulator-boot-on;
+ };
+ };
+ };
+ };
+ };
+};
+
+&soc {
+ sdhci at f9824900 {
+ status = "ok";
+
+ vmmc-supply = <&pm8941_l20>;
+ vqmmc-supply = <&pm8941_s3>;
+
+ bus-width = <8>;
+ non-removable;
+
+ pinctrl-names = "default";
+ pinctrl-0 = <&sdhc1_pin_a>;
+ };
+
+ sdhci at f98a4900 {
+ status = "ok";
+
+ bus-width = <4>;
+
+ vmmc-supply = <&pm8941_l21>;
+ vqmmc-supply = <&pm8941_l13>;
+
+ cd-gpios = <&msmgpio 62 GPIO_ACTIVE_LOW>;
+
+ pinctrl-names = "default";
+ pinctrl-0 = <&sdhc2_pin_a>, <&sdhc2_cd_pin_a>;
+ };
+
+ serial at f991e000 {
+ status = "ok";
+
+ pinctrl-names = "default";
+ pinctrl-0 = <&blsp1_uart2_pin_a>;
+ };
+
+
+ pinctrl at fd510000 {
+ blsp1_uart2_pin_a: blsp1-uart2-pin-active {
+ rx {
+ pins = "gpio5";
+ function = "blsp_uart2";
+
+ drive-strength = <2>;
+ bias-pull-up;
+ };
+
+ tx {
+ pins = "gpio4";
+ function = "blsp_uart2";
+
+ drive-strength = <4>;
+ bias-disable;
+ };
+ };
+
+ i2c2_pins: i2c2 {
+ mux {
+ pins = "gpio6", "gpio7";
+ function = "blsp_i2c2";
+
+ drive-strength = <2>;
+ bias-disable;
+ };
+ };
+
+ sdhc1_pin_a: sdhc1-pin-active {
+ clk {
+ pins = "sdc1_clk";
+ drive-strength = <16>;
+ bias-disable;
+ };
+
+ cmd-data {
+ pins = "sdc1_cmd", "sdc1_data";
+ drive-strength = <10>;
+ bias-pull-up;
+ };
+ };
+
+ sdhc2_cd_pin_a: sdhc2-cd-pin-active {
+ pins = "gpio62";
+ function = "gpio";
+
+ drive-strength = <2>;
+ bias-disable;
+ };
+
+ sdhc2_pin_a: sdhc2-pin-active {
+ clk {
+ pins = "sdc2_clk";
+ drive-strength = <10>;
+ bias-disable;
+ };
+
+ cmd-data {
+ pins = "sdc2_cmd", "sdc2_data";
+ drive-strength = <6>;
+ bias-pull-up;
+ };
+ };
+ };
+
+ dma-controller at f9944000 {
+ qcom,controlled-remotely;
+ };
+
+ usb at f9a55000 {
+ status = "ok";
+
+ phys = <&usb_hs1_phy>;
+ phy-select = <&tcsr 0xb000 0>;
+ extcon = <&smbb>, <&usb_id>;
+ vbus-supply = <&chg_otg>;
+
+ hnp-disable;
+ srp-disable;
+ adp-disable;
+
+ ulpi {
+ phy at a {
+ status = "ok";
+
+ v1p8-supply = <&pm8941_l6>;
+ v3p3-supply = <&pm8941_l24>;
+
+ extcon = <&smbb>;
+ qcom,init-seq = /bits/ 8 <0x1 0x64>;
+ };
+ };
+ };
+};
+
+&spmi_bus {
+ pm8941 at 0 {
+ charger at 1000 {
+ qcom,fast-charge-safe-current = <1300000>;
+ qcom,fast-charge-current-limit = <1300000>;
+ qcom,dc-current-limit = <1300000>;
+ qcom,fast-charge-safe-voltage = <4400000>;
+ qcom,fast-charge-high-threshold-voltage = <4350000>;
+ qcom,fast-charge-low-threshold-voltage = <3400000>;
+ qcom,auto-recharge-threshold-voltage = <4200000>;
+ qcom,minimum-input-voltage = <4300000>;
+ };
+
+ gpios at c000 {
+ gpio_keys_pin_a: gpio-keys-active {
+ pins = "gpio2", "gpio3", "gpio4", "gpio5";
+ function = "normal";
+
+ bias-pull-up;
+ power-source = <PM8941_GPIO_S3>;
+ };
+ };
+
+ coincell at 2800 {
+ status = "ok";
+ qcom,rset-ohms = <2100>;
+ qcom,vset-millivolts = <3000>;
+ };
+ };
+
+ pm8941 at 1 {
+ wled at d800 {
+ status = "ok";
+
+ qcom,cs-out;
+ qcom,current-limit = <20>;
+ qcom,current-boost-limit = <805>;
+ qcom,switching-freq = <1600>;
+ qcom,ovp = <29>;
+ qcom,num-strings = <2>;
+ };
+ };
+};
--
2.15.0
^ permalink raw reply related
* [PATCH 0/6] 66AK2G: Add DT nodes for few peripherals
From: santosh.shilimkar at oracle.com @ 2017-12-03 4:01 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171123075154.3938-1-vigneshr@ti.com>
On 11/22/17 11:51 PM, Vignesh R wrote:
> This patch series adds DT nodes for bunch of peripherials on 66AK2G EVM and
> 66AK2G ICE boards.
>
> Tested on 66AK2G EVM and ICE boards
>
>
> Vignesh R (6):
> ARM: dts: keystone-k2g: Add QSPI DT entry
> ARM: dts: keystone-k2g-evm: Fix botched up merge
> ARM: dts: keystone-k2g: Move ti,non-removable property to board dts
> ARM: dts: keystone-k2g-evm: Add QSPI DT node.
> ARM: dts: keystone-k2g-ice: Add DT nodes for few peripherals
> ARM: configs: keystone_defconfig: Enable few peripheral drivers
>
Series applied. Please submit the follow up patch for
multi-v7 config.
Regards,
Santosh
^ permalink raw reply
* [PATCH v6 0/2] memory: Introduce ti-emif-sram driver
From: santosh.shilimkar at oracle.com @ 2017-12-03 4:00 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1512082568-5012-1-git-send-email-d-gerlach@ti.com>
On 11/30/17 2:56 PM, Dave Gerlach wrote:
> This is a resend of v5 of this series found here [1]. It introduces
> relocatable PM handlers for the emif that are copied to sram and
> run from there during low power mode entry.
>
> The patches still have the previous ACKs but have a small change to
> accomodate a change made by Tony in commit cd57dc5a2099 ("ARM: dts:
> Add missing hwmod related nodes for am33xx"). If there are objections
> to this let me know ASAP.
>
> Now that a hwmod is present for the am335x EMIF, on probe fail the call to
> pm_runtime_put_sync causes the board to hang. In fact, this emif driver should
> never alter the PM state of the hardware at all through normal kernel calls, it
> is the job of the suspend handlers that are added, that is the whole point of
> this driver. Because of this, I have dropped all runtime pm calls, as any
> change to the PM state while the kernel is running is dangerous as we may shut
> of the memory controller. It makes the most sense just to drop runtime PM from
> the driver entirely. Besides that patch is unchanged.
>
> This code is required for low-power modes to work on AM335x and AM437x and a
> forthcoming PM series for those platforms will depend on this series. After
> both this and the PM series are reviewed I will send the necessary device tree
> changes for both, but in the meantime all remaining patches for am335x and
> am437x PM can be found here [2].
>
Applied
^ permalink raw reply
* [PATCH] ARM: dts: keystone-k2l: Add the second gpio bank node
From: santosh.shilimkar at oracle.com @ 2017-12-03 4:00 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <61c80992-92bd-a401-457c-267c64a3400d@oracle.com>
On 11/13/17 9:12 AM, Santosh Shilimkar wrote:
> On 11/9/2017 3:42 AM, Keerthy wrote:
>> In case of k2l there are 2 more banks with 16 pins each.
>> Adding the node as the da-vinci driver now supports multiple
>> banks.
>>
>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>> ---
>>
>> This is based on linux-next branch. Boot tested on keystone-k2l-evm.
>>
> Will pick this up Keerthy !!
>
Applied
^ permalink raw reply
* [PATCH 6/6] ARM: configs: keystone_defconfig: Enable few peripheral drivers
From: santosh.shilimkar at oracle.com @ 2017-12-03 4:00 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171123075154.3938-7-vigneshr@ti.com>
On 11/22/17 11:51 PM, Vignesh R wrote:
> Enable drivers for QSPI, LEDS, gpio-decoder that are present on 66AK2G EVM
> and 66AK2G ICE boards.
>
> Signed-off-by: Vignesh R <vigneshr@ti.com>
> ---
Please submit a patch also to enable all these peripherals
in multi-v7 config. Just enable all remainder
options enabled in keystone config also in multi-v7.
Am pushing this series to next now.
Regards,
Santosh
^ permalink raw reply
* [RESEND PATCH 2/4] ARM: dts: keystone: Add generic compatible string for I2C EEPROM
From: santosh.shilimkar at oracle.com @ 2017-12-03 3:57 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171124162750.18756-2-javierm@redhat.com>
On 11/24/17 8:27 AM, Javier Martinez Canillas 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
^ permalink raw reply
* [PATCH v3] usb: xhci: allow imod-interval to be configurable
From: Chunfeng Yun @ 2017-12-03 3:51 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1512143059-25674-1-git-send-email-awallis@codeaurora.org>
On Fri, 2017-12-01 at 10:44 -0500, Adam Wallis wrote:
> The xHCI driver currently has the IMOD set to 160, which
> translates to an IMOD interval of 40,000ns (160 * 250)ns
>
> Commit 0cbd4b34cda9 ("xhci: mediatek: support MTK xHCI host controller")
> introduced a QUIRK for the MTK platform to adjust this interval to 20,
> which translates to an IMOD interval of 5,000ns (20 * 250)ns. This is
> due to the fact that the MTK controller IMOD interval is 8 times
> as much as defined in xHCI spec.
>
> Instead of adding more quirk bits for additional platforms, this patch
> introduces the ability for vendors to set the IMOD_INTERVAL as is
> optimal for their platform. By using device_property_read_u32() on
> "imod-interval", the IMOD INTERVAL can be specified in nano seconds. If
> no interval is specified, the default of 40,000ns (IMOD=160) will be
> used.
>
> No bounds checking has been implemented due to the fact that a vendor
> may have violated the spec and would need to specify a value outside of
> the max 8,000 IRQs/second limit specified in the xHCI spec.
>
> Signed-off-by: Adam Wallis <awallis@codeaurora.org>
> ---
> changes from v2:
> * Added PCI default value [Mathias]
> * Removed xhci-mtk.h from xhci-plat.c [Chunfeng Yun]
> * Removed MTK quirk from xhci-plat and moved logic to xhci-mtk [Chunfeng]
> * Updated bindings Documentation to use proper units [Rob Herring]
> * Added imod-interval description and example to MTK binding documentation
> changes from v1:
> * Removed device_property_read_u32() per suggestion from greg k-h
> * Used ER_IRQ_INTERVAL_MASK in place of (u16) cast
>
> Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.txt | 2 ++
> Documentation/devicetree/bindings/usb/usb-xhci.txt | 1 +
> drivers/usb/host/xhci-mtk.c | 9 +++++++++
> drivers/usb/host/xhci-pci.c | 3 +++
> drivers/usb/host/xhci-plat.c | 4 ++++
> drivers/usb/host/xhci.c | 7 ++-----
> drivers/usb/host/xhci.h | 2 ++
> 7 files changed, 23 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.txt b/Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.txt
> index 3059596..45bbf18 100644
> --- a/Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.txt
> +++ b/Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.txt
> @@ -46,6 +46,7 @@ Optional properties:
> - pinctrl-names : a pinctrl state named "default" must be defined
> - pinctrl-0 : pin control group
> See: Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
> + - imod-interval: Default interval is 5000ns
>
> Example:
> usb30: usb at 11270000 {
> @@ -66,6 +67,7 @@ usb30: usb at 11270000 {
> usb3-lpm-capable;
> mediatek,syscon-wakeup = <&pericfg>;
> mediatek,wakeup-src = <1>;
> + imod-interval = <10000>;
> };
>
> 2nd: dual-role mode with xHCI driver
> diff --git a/Documentation/devicetree/bindings/usb/usb-xhci.txt b/Documentation/devicetree/bindings/usb/usb-xhci.txt
> index ae6e484..89b68f1 100644
> --- a/Documentation/devicetree/bindings/usb/usb-xhci.txt
> +++ b/Documentation/devicetree/bindings/usb/usb-xhci.txt
> @@ -29,6 +29,7 @@ Optional properties:
> - usb2-lpm-disable: indicate if we don't want to enable USB2 HW LPM
> - usb3-lpm-capable: determines if platform is USB3 LPM capable
> - quirk-broken-port-ped: set if the controller has broken port disable mechanism
> + - imod-interval: Default interval is 40000ns
>
> Example:
> usb at f0931000 {
> diff --git a/drivers/usb/host/xhci-mtk.c b/drivers/usb/host/xhci-mtk.c
> index b62a1d2..278ea3b 100644
> --- a/drivers/usb/host/xhci-mtk.c
> +++ b/drivers/usb/host/xhci-mtk.c
> @@ -674,6 +674,15 @@ static int xhci_mtk_probe(struct platform_device *pdev)
>
> xhci = hcd_to_xhci(hcd);
> xhci->main_hcd = hcd;
> +
> + /*
> + * imod_interval is the interrupt modulation value in nanoseconds.
> + * The increment interval is 8 times as much as that defined in
> + * the xHCI spec on MTK's controller.
> + */
> + xhci->imod_interval = 5000;
> + device_property_read_u32(dev, "imod-interval", &xhci->imod_interval);
> +
> xhci->shared_hcd = usb_create_shared_hcd(driver, dev,
> dev_name(dev), hcd);
> if (!xhci->shared_hcd) {
> diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
> index 7ef1274..efbe57b 100644
> --- a/drivers/usb/host/xhci-pci.c
> +++ b/drivers/usb/host/xhci-pci.c
> @@ -234,6 +234,9 @@ static int xhci_pci_setup(struct usb_hcd *hcd)
> if (!xhci->sbrn)
> pci_read_config_byte(pdev, XHCI_SBRN_OFFSET, &xhci->sbrn);
>
> + /* imod_interval is the interrupt modulation value in nanoseconds. */
> + xhci->imod_interval = 40000;
> +
> retval = xhci_gen_setup(hcd, xhci_pci_quirks);
> if (retval)
> return retval;
> diff --git a/drivers/usb/host/xhci-plat.c b/drivers/usb/host/xhci-plat.c
> index 09f164f..b78be87 100644
> --- a/drivers/usb/host/xhci-plat.c
> +++ b/drivers/usb/host/xhci-plat.c
> @@ -269,6 +269,10 @@ static int xhci_plat_probe(struct platform_device *pdev)
> if (device_property_read_bool(&pdev->dev, "quirk-broken-port-ped"))
> xhci->quirks |= XHCI_BROKEN_PORT_PED;
>
> + /* imod_interval is the interrupt modulation value in nanoseconds. */
> + xhci->imod_interval = 40000;
> + device_property_read_u32(sysdev, "imod-interval", &xhci->imod_interval);
> +
> hcd->usb_phy = devm_usb_get_phy_by_phandle(sysdev, "usb-phy", 0);
> if (IS_ERR(hcd->usb_phy)) {
> ret = PTR_ERR(hcd->usb_phy);
> diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
> index 2424d30..0b7755b 100644
> --- a/drivers/usb/host/xhci.c
> +++ b/drivers/usb/host/xhci.c
> @@ -586,11 +586,8 @@ int xhci_run(struct usb_hcd *hcd)
> "// Set the interrupt modulation register");
> temp = readl(&xhci->ir_set->irq_control);
> temp &= ~ER_IRQ_INTERVAL_MASK;
> - /*
> - * the increment interval is 8 times as much as that defined
> - * in xHCI spec on MTK's controller
> - */
> - temp |= (u32) ((xhci->quirks & XHCI_MTK_HOST) ? 20 : 160);
> + temp |= (xhci->imod_interval / 250) & ER_IRQ_INTERVAL_MASK;
> +
> writel(temp, &xhci->ir_set->irq_control);
>
> /* Set the HCD state before we enable the irqs */
> diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhci.h
> index 99a014a..2a4177b 100644
> --- a/drivers/usb/host/xhci.h
> +++ b/drivers/usb/host/xhci.h
> @@ -1717,6 +1717,8 @@ struct xhci_hcd {
> u8 max_interrupters;
> u8 max_ports;
> u8 isoc_threshold;
> + /* imod_interval in ns (I * 250ns) */
> + u32 imod_interval;
> int event_ring_max;
> /* 4KB min, 128MB max */
> int page_size;
Tested-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
Thanks
^ permalink raw reply
* [PATCH net-next v4 2/2] net: ethernet: socionext: add AVE ethernet driver
From: kbuild test robot @ 2017-12-03 3:37 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1512090230-27594-3-git-send-email-hayashi.kunihiko@socionext.com>
Hi Kunihiko,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Kunihiko-Hayashi/dt-bindings-net-add-DT-bindings-for-Socionext-UniPhier-AVE/20171203-095248
config: alpha-allyesconfig (attached as .config)
compiler: alpha-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=alpha
All warnings (new ones prefixed by >>):
drivers/net/ethernet/socionext/sni_ave.c: In function 'ave_pfsel_set_promisc':
>> drivers/net/ethernet/socionext/sni_ave.c:172:27: warning: large integer implicitly truncated to unsigned type [-Woverflow]
#define AVE_PFMBYTE_MASK0 (~GENMASK(7, 6))
^
>> drivers/net/ethernet/socionext/sni_ave.c:1046:9: note: in expansion of macro 'AVE_PFMBYTE_MASK0'
writel(AVE_PFMBYTE_MASK0, priv->base + AVE_PFMBYTE(entry));
^~~~~~~~~~~~~~~~~
vim +172 drivers/net/ethernet/socionext/sni_ave.c
170
171 /* Packet filter */
> 172 #define AVE_PFMBYTE_MASK0 (~GENMASK(7, 6))
173 #define AVE_PFMBYTE_MASK1 GENMASK(25, 0)
174 #define AVE_PFMBIT_MASK GENMASK(15, 0)
175
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/gzip
Size: 52634 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20171203/a3988e62/attachment-0001.gz>
^ permalink raw reply
* [PATCH v3] usb: xhci: allow imod-interval to be configurable
From: Chunfeng Yun @ 2017-12-03 3:22 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1512143059-25674-1-git-send-email-awallis@codeaurora.org>
On Fri, 2017-12-01 at 10:44 -0500, Adam Wallis wrote:
> The xHCI driver currently has the IMOD set to 160, which
> translates to an IMOD interval of 40,000ns (160 * 250)ns
>
> Commit 0cbd4b34cda9 ("xhci: mediatek: support MTK xHCI host controller")
> introduced a QUIRK for the MTK platform to adjust this interval to 20,
> which translates to an IMOD interval of 5,000ns (20 * 250)ns. This is
> due to the fact that the MTK controller IMOD interval is 8 times
> as much as defined in xHCI spec.
>
> Instead of adding more quirk bits for additional platforms, this patch
> introduces the ability for vendors to set the IMOD_INTERVAL as is
> optimal for their platform. By using device_property_read_u32() on
> "imod-interval", the IMOD INTERVAL can be specified in nano seconds. If
> no interval is specified, the default of 40,000ns (IMOD=160) will be
> used.
>
> No bounds checking has been implemented due to the fact that a vendor
> may have violated the spec and would need to specify a value outside of
> the max 8,000 IRQs/second limit specified in the xHCI spec.
>
> Signed-off-by: Adam Wallis <awallis@codeaurora.org>
> ---
> changes from v2:
> * Added PCI default value [Mathias]
> * Removed xhci-mtk.h from xhci-plat.c [Chunfeng Yun]
> * Removed MTK quirk from xhci-plat and moved logic to xhci-mtk [Chunfeng]
> * Updated bindings Documentation to use proper units [Rob Herring]
> * Added imod-interval description and example to MTK binding documentation
> changes from v1:
> * Removed device_property_read_u32() per suggestion from greg k-h
> * Used ER_IRQ_INTERVAL_MASK in place of (u16) cast
>
> Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.txt | 2 ++
> Documentation/devicetree/bindings/usb/usb-xhci.txt | 1 +
> drivers/usb/host/xhci-mtk.c | 9 +++++++++
> drivers/usb/host/xhci-pci.c | 3 +++
> drivers/usb/host/xhci-plat.c | 4 ++++
> drivers/usb/host/xhci.c | 7 ++-----
> drivers/usb/host/xhci.h | 2 ++
> 7 files changed, 23 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.txt b/Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.txt
> index 3059596..45bbf18 100644
> --- a/Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.txt
> +++ b/Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.txt
> @@ -46,6 +46,7 @@ Optional properties:
> - pinctrl-names : a pinctrl state named "default" must be defined
> - pinctrl-0 : pin control group
> See: Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
> + - imod-interval: Default interval is 5000ns
I think, as Rob suggested before, recommend to have a unit suffix
appended to the property name.
s/imod-interval/imod-interval-ns
>
> Example:
> usb30: usb at 11270000 {
> @@ -66,6 +67,7 @@ usb30: usb at 11270000 {
> usb3-lpm-capable;
> mediatek,syscon-wakeup = <&pericfg>;
> mediatek,wakeup-src = <1>;
> + imod-interval = <10000>;
> };
>
> 2nd: dual-role mode with xHCI driver
> diff --git a/Documentation/devicetree/bindings/usb/usb-xhci.txt b/Documentation/devicetree/bindings/usb/usb-xhci.txt
> index ae6e484..89b68f1 100644
> --- a/Documentation/devicetree/bindings/usb/usb-xhci.txt
> +++ b/Documentation/devicetree/bindings/usb/usb-xhci.txt
> @@ -29,6 +29,7 @@ Optional properties:
> - usb2-lpm-disable: indicate if we don't want to enable USB2 HW LPM
> - usb3-lpm-capable: determines if platform is USB3 LPM capable
> - quirk-broken-port-ped: set if the controller has broken port disable mechanism
> + - imod-interval: Default interval is 40000ns
>
> Example:
> usb at f0931000 {
> diff --git a/drivers/usb/host/xhci-mtk.c b/drivers/usb/host/xhci-mtk.c
> index b62a1d2..278ea3b 100644
> --- a/drivers/usb/host/xhci-mtk.c
> +++ b/drivers/usb/host/xhci-mtk.c
> @@ -674,6 +674,15 @@ static int xhci_mtk_probe(struct platform_device *pdev)
>
> xhci = hcd_to_xhci(hcd);
> xhci->main_hcd = hcd;
> +
> + /*
> + * imod_interval is the interrupt modulation value in nanoseconds.
> + * The increment interval is 8 times as much as that defined in
> + * the xHCI spec on MTK's controller.
> + */
> + xhci->imod_interval = 5000;
> + device_property_read_u32(dev, "imod-interval", &xhci->imod_interval);
> +
> xhci->shared_hcd = usb_create_shared_hcd(driver, dev,
> dev_name(dev), hcd);
> if (!xhci->shared_hcd) {
> diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
> index 7ef1274..efbe57b 100644
> --- a/drivers/usb/host/xhci-pci.c
> +++ b/drivers/usb/host/xhci-pci.c
> @@ -234,6 +234,9 @@ static int xhci_pci_setup(struct usb_hcd *hcd)
> if (!xhci->sbrn)
> pci_read_config_byte(pdev, XHCI_SBRN_OFFSET, &xhci->sbrn);
>
> + /* imod_interval is the interrupt modulation value in nanoseconds. */
> + xhci->imod_interval = 40000;
> +
> retval = xhci_gen_setup(hcd, xhci_pci_quirks);
> if (retval)
> return retval;
> diff --git a/drivers/usb/host/xhci-plat.c b/drivers/usb/host/xhci-plat.c
> index 09f164f..b78be87 100644
> --- a/drivers/usb/host/xhci-plat.c
> +++ b/drivers/usb/host/xhci-plat.c
> @@ -269,6 +269,10 @@ static int xhci_plat_probe(struct platform_device *pdev)
> if (device_property_read_bool(&pdev->dev, "quirk-broken-port-ped"))
> xhci->quirks |= XHCI_BROKEN_PORT_PED;
>
> + /* imod_interval is the interrupt modulation value in nanoseconds. */
> + xhci->imod_interval = 40000;
> + device_property_read_u32(sysdev, "imod-interval", &xhci->imod_interval);
> +
> hcd->usb_phy = devm_usb_get_phy_by_phandle(sysdev, "usb-phy", 0);
> if (IS_ERR(hcd->usb_phy)) {
> ret = PTR_ERR(hcd->usb_phy);
> diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
> index 2424d30..0b7755b 100644
> --- a/drivers/usb/host/xhci.c
> +++ b/drivers/usb/host/xhci.c
> @@ -586,11 +586,8 @@ int xhci_run(struct usb_hcd *hcd)
> "// Set the interrupt modulation register");
> temp = readl(&xhci->ir_set->irq_control);
> temp &= ~ER_IRQ_INTERVAL_MASK;
> - /*
> - * the increment interval is 8 times as much as that defined
> - * in xHCI spec on MTK's controller
> - */
> - temp |= (u32) ((xhci->quirks & XHCI_MTK_HOST) ? 20 : 160);
> + temp |= (xhci->imod_interval / 250) & ER_IRQ_INTERVAL_MASK;
> +
> writel(temp, &xhci->ir_set->irq_control);
>
> /* Set the HCD state before we enable the irqs */
> diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhci.h
> index 99a014a..2a4177b 100644
> --- a/drivers/usb/host/xhci.h
> +++ b/drivers/usb/host/xhci.h
> @@ -1717,6 +1717,8 @@ struct xhci_hcd {
> u8 max_interrupters;
> u8 max_ports;
> u8 isoc_threshold;
> + /* imod_interval in ns (I * 250ns) */
> + u32 imod_interval;
> int event_ring_max;
> /* 4KB min, 128MB max */
> int page_size;
^ permalink raw reply
* [kernel-hardening][PATCH v2 3/3] arm: mm: dump: add checking for writable and executable pages
From: park jinbum @ 2017-12-03 2:32 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <23def981-3f61-8421-b46d-94f75b293003@redhat.com>
I agree with your opinion, Laura.
I'll make a new version to take advantage of the existing pg_level and
bits arrays.
Thanks,
Jinbum Park.
2017-12-02 6:59 GMT+09:00 Laura Abbott <labbott@redhat.com>:
> On 12/01/2017 03:34 AM, Jinbum Park wrote:
>>
>> +static inline bool is_prot_ro(struct pg_state *st)
>> +{
>> + if (st->level < 4) {
>> + #ifdef CONFIG_ARM_LPAE
>> + if ((st->current_prot &
>> + (L_PMD_SECT_RDONLY | PMD_SECT_AP2)) ==
>> + (L_PMD_SECT_RDONLY | PMD_SECT_AP2))
>> + return true;
>> + #elif __LINUX_ARM_ARCH__ >= 6
>> + if ((st->current_prot &
>> + (PMD_SECT_APX | PMD_SECT_AP_READ | PMD_SECT_AP_WRITE)) ==
>> + (PMD_SECT_APX | PMD_SECT_AP_WRITE))
>> + return true;
>> + #else
>> + if ((st->current_prot &
>> + (PMD_SECT_AP_READ | PMD_SECT_AP_WRITE)) == 0)
>> + return true;
>> + #endif
>> + } else {
>> + if ((st->current_prot & L_PTE_RDONLY) == L_PTE_RDONLY)
>> + return true;
>> + }
>> +
>> + return false;
>> +}
>> +
>> +static inline bool is_prot_nx(struct pg_state *st)
>> +{
>> + if (st->level < 4) {
>> + if ((st->current_prot & PMD_SECT_XN) == PMD_SECT_XN)
>> + return true;
>> + } else {
>> + if ((st->current_prot & L_PTE_XN) == L_PTE_XN)
>> + return true;
>> + }
>> +
>> + return false;
>> +}
>
>
> I know arm64 checks the bits directly, but the arm32 code is a bit
> more fiddly and I have mixed feelings about copying and pasting
> the checks. It would be cleaner if we could take advantage of
> the existing pg_level and bits arrays. I also don't have my heart
> set on this so if nobody else objects, the code can stay as is.
>
> Thanks,
> Laura
^ permalink raw reply
* [GIT PULL] fixes for omaps for v4.15-rc cycle
From: Olof Johansson @ 2017-12-03 1:17 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <pull-1512056553-465925@atomide.com>
Hi,
On Thu, Nov 30, 2017 at 08:19:27AM -0800, Tony Lindgren wrote:
> From: "Tony Lindgren" <tony@atomide.com>
>
> The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
>
> Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.15/fixes-v2-signed
>
> for you to fetch changes up to 7cd4a5eb64b638a71564f62175f6c7ad3f27044e:
>
> Merge branch 'omap-for-v4.15/fixes-dt' into omap-for-v4.15/fixes-v2 (2017-11-28 08:23:05 -0800)
>
> ----------------------------------------------------------------
> Fixes for omaps for v4.15-rc cycle with two fixes for hangs with the
> rest being compiler warning fixes and fixes for power states and devices
> on various boards:
Merged, thanks.
-Olof
^ permalink raw reply
* [GIT PULL] Amlogic fixes for v4.15-rc (redo)
From: Olof Johansson @ 2017-12-03 1:08 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <7h7eu7p95w.fsf@baylibre.com>
Hi,
On Thu, Nov 30, 2017 at 04:46:19PM -0800, Kevin Hilman wrote:
> Arnd, Olof,
>
> A handful of minor v4.15 fixes for Amlogic family SoCs. They're mostly
> DT, but some trivial non-DT stuff mixed in. Let me know if you prefer
> those in separate pulls, and I will do so.
>
> Thanks,
>
> Kevin
>
>
> The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
>
> Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git amlogic-fixes
>
> for you to fetch changes up to 9f8e06ca1d0e3ef1167a2f43a8b1e63763b283b8:
>
> ARM64: dts: odroid-c2: Add HDMI and CEC Nodes (2017-11-30 15:30:09 -0800)
>
> ----------------------------------------------------------------
> Amlogic fixes for v4.15-rc
> - GPIO interrupt fixes
> - new nodes for drivers merged late (VPU domains)
The VPU power domain and HDMI regulator changes look more like new hardware
support than bugfixes to me, is that a correct assessment? I.e. is something
breaking by not having these new DT nodes in the tree one existing hardware?
If it isn't a bugfix, I think I'd rather see it queued up for next merge
window
-Olof
^ permalink raw reply
* [GIT PULL] revert ARM SCPI changes for v4.15-rc1
From: Olof Johansson @ 2017-12-03 1:04 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <7hlgimns2m.fsf@baylibre.com>
On Fri, Dec 01, 2017 at 11:53:05AM -0800, Kevin Hilman wrote:
> Arnd, Olof,
>
> These ARM SCPI changes caused SCPI regressions resulting in CPUfreq
> failures on most Amlogic SoCs (found by kernelci.org.)
>
> Unfortunately, this was not caught in linux-next due to other
> bugs/panics on these platforms masking this problem so we've only found
> it since we've fixed the other issues.
>
> Since we're already in the -rc cycle, I'd prefer to revert to a known
> working state (that of v4.14) rather than finding/reverting a subset,
> which would just lead to another untested state.
>
> These changes can then have some time to be better reviewed and tested
> and resubmitted for v4.16.
>
> I've tested this revert on the affect Amlogic SoCs and verified that
> we're back to the previous (working) condition.
>
> Also, I'm sending the pull directly to arm-soc instead of Sudeeep
> because I understand that Sudeep is currently out-of-office and unlikely
> to be able to address this himself during the -rc cycle.
>
Sounds like the right approach here. I've merged this and added the above text
to the merge commit as well.
-Olof
^ permalink raw reply
* [PATCH] pinctrl: pxa2xx: add MODULE_LICENSE
From: Daniel Axtens @ 2017-12-03 1:03 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <CACRpkdYWTNEJZ3TUCsgEdDMRytGiOiMV6YhRKgciO1Qwgbeorg@mail.gmail.com>
Linus Walleij <linus.walleij@linaro.org> writes:
> On Sat, Dec 2, 2017 at 10:40 AM, Daniel Axtens <dja@axtens.net> wrote:
>
>> This fixes the following warning on an allmodconfig build:
>> WARNING: modpost: missing MODULE_LICENSE() in drivers/pinctrl/pxa/pinctrl-pxa2xx.o
>>
>> This matches the license in the header.
>>
>> Signed-off-by: Daniel Axtens <dja@axtens.net>
>
> Somebody patches this too. Sorry!
No worries, apologies for the noise!
Regards,
Daniel
>
> Thanks anyway!
>
> Yours,
> Linus Walleij
^ permalink raw reply
* [GIT PULL] i.MX fixes for 4.15
From: Olof Johansson @ 2017-12-03 1:01 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171130013439.GH22908@dragon>
On Thu, Nov 30, 2017 at 09:34:40AM +0800, Shawn Guo wrote:
> The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
>
> Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-fixes-4.15
>
> for you to fetch changes up to e501506d3ea00eefa64463ebd9e5c13ee70990bd:
>
> Revert "ARM: dts: imx53: add srtc node" (2017-11-29 10:34:45 +0800)
>
> ----------------------------------------------------------------
> i.MX fixes for 4.15:
> - A fix for vf610-zii-dev-rev-c board which correct the unit-address
> of I2C EEPROM node to match the 'reg' property.
> - We thought the RTC block on i.MX53 is compatible with the one found
> on i.MX25, and added the device for i.MX53 device tree. But it turns
> out that's not the case, and we have to revert the change.
Great tag description. Merged, thanks.
-Olof
^ permalink raw reply
* [GIT PULL] ARM: uniphier: fixes for v4.15
From: Olof Johansson @ 2017-12-03 1:01 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <CAK7LNARMXg-3Xfz2Mxq47Suys4kPSWuPYKY1o8HkVRBd4fHfSA@mail.gmail.com>
On Wed, Nov 29, 2017 at 11:01:57PM +0900, Masahiro Yamada wrote:
> Hi Arnd, Olof,
>
> Here are some fixes of ARM UniPhier SoC family.
> There is a mistake in the IRQ number. Otherwise, I wouldn't have done
> this early pull request. One more trivial patch to avoid conflict.
> Also, MAINTAINERS update, which is always safe.
> Please pull!
>
>
> The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
>
> Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-uniphier.git
> tags/uniphier-fixes-v4.15
>
> for you to fetch changes up to 0308cadcec379e510f498c48c34aafe582f1af88:
>
> MAINTAINERS: exclude other Socionext SoC DT files from ARM/UNIPHIER
> entry (2017-11-29 22:22:10 +0900)
>
> ----------------------------------------------------------------
> UniPhier ARM SoC fixes for v4.15
>
> - Fix IRQ number of PXs3 SoC
> - Remove redundant interrupt-parent properties
> - Fix arm64 DT path in MAINTAINERS
Merged, thanks.
-Olof
^ permalink raw reply
* [GIT PULL] tee fix for v4.15
From: Olof Johansson @ 2017-12-03 0:59 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171129101649.3vrhocn65gzbhvkp@jax>
On Wed, Nov 29, 2017 at 11:16:50AM +0100, Jens Wiklander wrote:
> Hi arm-soc maiantainers,
>
> Please pull this OP-TEE driver init fix for v4.15
>
> Thanks,
> Jens
>
> 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.linaro.org/people/jens.wiklander/linux-tee.git tags/tee-drv-fix-for-4.15
>
> for you to fetch changes up to f044113113dd95ba73916bde10e804d3cdfa2662:
>
> optee: fix invalid of_node_put() in optee_driver_init() (2017-11-29 10:24:57 +0100)
Merged, thanks.
-Olof
^ permalink raw reply
* [GIT PULL 1/1] Broadcom devicetree fixes for 4.15
From: Olof Johansson @ 2017-12-03 0:57 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171127200817.32647-1-f.fainelli@gmail.com>
On Mon, Nov 27, 2017 at 12:08:17PM -0800, Florian Fainelli wrote:
> The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
>
> Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
>
> are available in the git repository at:
>
> http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.15/devicetree-fixes-1
>
> for you to fetch changes up to babd8a3e31fbb0abb4c37ee3548974732080b996:
>
> Merge tag 'bcm2835-dt-next-fixes-2017-11-15' into devicetree/fixes (2017-11-27 11:28:23 -0800)
>
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM-based SoCs Device Tree fixes for 4.15,
> please pull the following:
>
> - Stefan provides a fix for the BCM2835 (Raspberry Pi) to fix warnings about
> missing "#phy-cells" properties
>
> - Florian provides two fixes for Nortsthar Plus, one that uses the correct
> interrupt specifiers for the timer/watchdog and one that disables SATA
> on BCM9582**HR boards since that leads to unidentified hangs right now
Merged, thanks.
-Olof
^ permalink raw reply
* [GIT PULL] Renesas ARM Based SoC DT Fixes for v4.15
From: Olof Johansson @ 2017-12-03 0:56 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <cover.1511781272.git.horms+renesas@verge.net.au>
On Mon, Nov 27, 2017 at 12:17:41PM +0100, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider this Renesas ARM based SoC DT fix for v4.15.
>
> It is from Arnd adding missing '#reset-cells' property to cpg nodes.
> This flagged by recent dtc.
>
> This pull request is based on
> "[GIT PULL] Second Round of Renesas ARM Based SoC DT Updates for v4.15"
> which is tagged as renesas-dt2-for-v4.15 and you have already pulled.
>
>
> The following changes since commit b6d3b649441936621c87b79bff8dd436e2397e3c:
>
> ARM: dts: r8a7743: Add xhci support to SoC dtsi (2017-10-18 07:21:36 +0200)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-dt-fixes-for-v4.15
>
> for you to fetch changes up to 098f53050154498876ef3febde706ff5c8b25cf4:
>
> ARM: dts: r8a779x: Add '#reset-cells' in cpg-mssr (2017-11-20 11:35:41 +0100)
Merged, thanks.
-Olof
^ permalink raw reply
* [PATCH 3/6] arm: dts: marvell: Add missing #phy-cells to usb-nop-xceiv
From: Olof Johansson @ 2017-12-03 0:49 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171121205622.GE30040@lunn.ch>
On Tue, Nov 21, 2017 at 09:56:22PM +0100, Andrew Lunn wrote:
> On Thu, Nov 09, 2017 at 04:26:11PM -0600, Rob Herring wrote:
> > "usb-nop-xceiv" is using the phy binding, but is missing #phy-cells
> > property. This is probably because the binding was the precursor to the phy
> > binding.
> >
> > Fixes the following warning in Marvell dts files:
> >
> > Warning (phys_property): Missing property '#phy-cells' in node ...
> >
> > Signed-off-by: Rob Herring <robh@kernel.org>
>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
I didn't see this come in before -rc1 and in current fixes, so given the acks
I've applied it directly now.
-Olof
^ permalink raw reply
* [PATCH] arm64: dts: sort vendor subdirectories in Makefile alphabetically
From: Olof Johansson @ 2017-12-03 0:28 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1510974603-7463-1-git-send-email-yamada.masahiro@socionext.com>
On Sat, Nov 18, 2017 at 12:10:03PM +0900, Masahiro Yamada wrote:
> The list is almost sorted. Move "lg" up to complete it.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Applied to fixes, thanks.
-Olof
^ permalink raw reply
* [PATCH v2 11/18] drm/sun4i: Add A83T support
From: Jernej Škrabec @ 2017-12-02 21:58 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171130153312.plmh2wr4n5njhlvb@flea.lan>
Dne ?etrtek, 30. november 2017 ob 16:33:12 CET je Maxime Ripard napisal(a):
> On Tue, Nov 28, 2017 at 11:33:44PM +0100, Jernej ?krabec wrote:
> > Hi!
> >
> > Dne torek, 28. november 2017 ob 23:00:14 CET je Maxime Ripard napisal(a):
> > > On Tue, Nov 28, 2017 at 04:48:55PM +0100, Jernej ?krabec wrote:
> > > > > On Mon, Nov 27, 2017 at 05:01:49PM +0100, Jernej ?krabec wrote:
> > > > > > Dne ponedeljek, 27. november 2017 ob 16:41:35 CET je Maxime Ripard
> > > >
> > > > napisal(a):
> > > > > > > Add support for the A83T display pipeline.
> > > > > > >
> > > > > > > Reviewed-by: Chen-Yu Tsai <wens@csie.org>
> > > > > > > Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> > > > > > > ---
> > > > > > >
> > > > > > > Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt |
> > > > > > > 3
> > > > > > > +++
> > > > > > > drivers/gpu/drm/sun4i/sun4i_drv.c |
> > > > > > > 2
> > > > > > > ++
> > > > > > > drivers/gpu/drm/sun4i/sun4i_tcon.c |
> > > > > > > 5
> > > > > > > +++++
> > > > > > > drivers/gpu/drm/sun4i/sun8i_mixer.c |
> > > > > > > 4
> > > > > > > ++++
> > > > > > > 4 files changed, 14 insertions(+)
> > > > > > >
> > > > > > > diff --git
> > > > > > > a/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt
> > > > > > > b/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt
> > > > > > > index
> > > > > > > d4259a4f5171..d6b52e5c48c0 100644
> > > > > > > ---
> > > > > > > a/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt
> > > > > > > +++
> > > > > > > b/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt
> > > > > > >
> > > > > > > @@ -93,6 +93,7 @@ Required properties:
> > > > > > > * allwinner,sun6i-a31s-tcon
> > > > > > > * allwinner,sun7i-a20-tcon
> > > > > > > * allwinner,sun8i-a33-tcon
> > > > > > >
> > > > > > > + * allwinner,sun8i-a83t-tcon-lcd
> > > > > > >
> > > > > > > * allwinner,sun8i-v3s-tcon
> > > > > > >
> > > > > > > - reg: base address and size of memory-mapped region
> > > > > > > - interrupts: interrupt associated to this IP
> > > > > > >
> > > > > > > @@ -224,6 +225,7 @@ supported.
> > > > > > >
> > > > > > > Required properties:
> > > > > > > - compatible: value must be one of:
> > > > > > > + * allwinner,sun8i-a83t-de2-mixer
> > > > > >
> > > > > > What will be the name of the second mixer, once support for HDMI
> > > > > > is
> > > > > > added?
> > > > > > Should we start directly with 0 and 1 postfix ?
> > > > >
> > > > > What are the differences exactly without the two mixers?
> > > >
> > > > Mixer properties:
> > > > - mixer index (0 or 1), important for determining CCSC base (see my
> > > > patches)
> > >
> > > Is that the only thing we need to determine?
> >
> > For now, mixer index is important only for determining CCSC base in
> > conjuction with VEP capability. Obviously, I can't exclude that there is
> > some other case where that mixer index is needed.
>
> That's unfortunate...
I take a deeper look today about that issue and it seems that mixer index is
really needed only here. I did only regex search and not line by line check,
so take this with grain of salt.
Additionally, it seems that this comparison is kind of a hack for V3s. Channel
output CSC is done through VEP (video enhancement processor, maybe?) unit.
Those units are only on VI channels. But every SoC with DE2 I checked except
V3s have 1 VI channel and VEP enabled on first mixer. V3s on the other hand
have 2 VI channels and no VEP, but same addresses should work for channel
output CSC according to the code. Of course, that is only a theory, but if you
want, we can go with quirks structure. Or better yet, with quirk property,
since there may be some (future?) SoC with two mixers and no VEP unit
supported.
BTW, how should be DE3 on H6 handled in the future? Registers offsets seems to
be same within same DE2 and DE3 units, just extended. However, some base
addresses are different, for example, those connected to VEP. I don't think
new driver is needed, just some quirks structure which would tell DE version.
Best regards,
Jernej
>
> > Can't we just add reg property for that?
>
> No, reg is here specifically for the bus address, not for an index,
> and in general, indices are poorly perceived and have been subject to
> a lot of debate in the past. Hence why I'd really like to avoid any
> solution looking like this. But I guess we don't really have the
> choice either.
>
> Maxime
>
> --
> Maxime Ripard, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
^ 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;
as well as URLs for NNTP newsgroup(s).