[linux-yocto][linux-yocto v5.10/standard/nxp-sdk-5.10/nxp-soc][PATCH] arm64: dts: imx8: Set usdhc's clock rate for imx8qm mmc for trim performance

2021-07-29 Thread Xiaolei Wang
Set usdhc's clock rate for imx8qm mmc, usdhc's clock rate is different according
to different devices connected, otherwise this will impact the trim performance.

Refer to the upstream commit: 3944b454f7fa
"(arm64: dts: imx8qxp: Move usdhc clocks assignment to board DT")

Signed-off-by: Xiaolei Wang 
Signed-off-by: Bruce Ashfield 
---
 arch/arm64/boot/dts/freescale/imx8qm-mek.dts | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/arch/arm64/boot/dts/freescale/imx8qm-mek.dts 
b/arch/arm64/boot/dts/freescale/imx8qm-mek.dts
index a3b01417638a..2928f336d497 100755
--- a/arch/arm64/boot/dts/freescale/imx8qm-mek.dts
+++ b/arch/arm64/boot/dts/freescale/imx8qm-mek.dts
@@ -1083,7 +1083,7 @@ usb3_drd_sw: endpoint {
 
  {
assigned-clocks = < IMX_SC_R_SDHC_0 IMX_SC_PM_CLK_PER>;
-   assigned-clock-rates = <4>;
+   assigned-clock-rates = <2>;
pinctrl-names = "default", "state_100mhz", "state_200mhz";
pinctrl-0 = <_usdhc1>;
pinctrl-1 = <_usdhc1>;
@@ -1096,6 +1096,8 @@  {
 };
 
  {
+   assigned-clocks = < IMX_SC_R_SDHC_0 IMX_SC_PM_CLK_PER>;
+   assigned-clock-rates = <2>;
pinctrl-names = "default", "state_100mhz", "state_200mhz";
pinctrl-0 = <_usdhc2>, <_usdhc2_gpio>;
pinctrl-1 = <_usdhc2>, <_usdhc2_gpio>;
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10215): 
https://lists.yoctoproject.org/g/linux-yocto/message/10215
Mute This Topic: https://lists.yoctoproject.org/mt/84544560/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto] [PATCH] Mailbox: Fix compile error caused by spell mistake of spin_lock_irqrestore

2021-07-29 Thread Ruiqiang Hao
From: Ruiqiang Hao 

Replace spin_lock_irqstore() with spin_lock_irqrestore().

Fixes: 4f52df83cd44("Mailbox: Replace mutex lock with spin lock")
Signed-off-by: Ruiqiang Hao 
---
 drivers/mailbox/mvl_mhu.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/mailbox/mvl_mhu.c b/drivers/mailbox/mvl_mhu.c
index 3caf04a2d557..e8639b570130 100644
--- a/drivers/mailbox/mvl_mhu.c
+++ b/drivers/mailbox/mvl_mhu.c
@@ -202,7 +202,7 @@ static bool mvl_mhu_last_tx_done(struct mbox_chan *chan)
 
spin_lock_irqsave(>link_lock, flags);
val = readq_relaxed(mhu->base + SCP_TO_AP0_MBOX_RINT);
-   spin_unlock_irqstore(>link_lock, flags);
+   spin_unlock_irqrestore(>link_lock, flags);
 
dev_dbg(mhu->dev, "%s\n", __func__);
 
@@ -216,7 +216,7 @@ static int mvl_mhu_send_data(struct mbox_chan *chan, void 
*data)
 
spin_lock_irqsave(>link_lock, flags);
writeq_relaxed(DONT_CARE_DATA, mhu->base + AP0_TO_SCP_MBOX);
-   spin_unlock_irqstore(>link_lock, flags);
+   spin_unlock_irqrestore(>link_lock, flags);
 
return 0;
 }
-- 
2.29.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10213): 
https://lists.yoctoproject.org/g/linux-yocto/message/10213
Mute This Topic: https://lists.yoctoproject.org/mt/84543384/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][linux-yocto v5.10] Fix compile error caused by spell mistake.

2021-07-29 Thread Ruiqiang Hao
Hi Bruce,

Please help to merge this patch into our linux-yocto repo.

patch:
0001-Mailbox-Fix-compile-error-caused-by-spell-mistake-of.patch

repo:
linux-yocto
   
branch:
v5.10/standard/cn-sdkv5.4/octeon
v5.10/standard/preempt-rt/cn-sdkv5.4/octeon

Thanks,
Ruiqiang

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10214): 
https://lists.yoctoproject.org/g/linux-yocto/message/10214
Mute This Topic: https://lists.yoctoproject.org/mt/84543385/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][yocto-kernel-cache yocto-5.10][PATCH 0/1] nxp-imx6: Enable Media Platform config to fix build warning

2021-07-29 Thread Bruce Ashfield
merged.

Bruce

In message: [linux-yocto][yocto-kernel-cache yocto-5.10][PATCH 0/1] nxp-imx6: 
Enable Media Platform config to fix build warning
on 28/07/2021 Jun Miao wrote:

> CONFIG V4L_MEM2MEM_DRIVERS and VIDEO_CODA are depended on
> MEDIA_PLATFORM_SUPPORT, so enable CONFIG_MEDIA_PLATFORM_SUPPORT to fix build
> warning.
> 
> Signed-off-by: Jun Miao 
> ---
>  bsp/nxp-imx6/nxp-imx6.cfg | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/bsp/nxp-imx6/nxp-imx6.cfg b/bsp/nxp-imx6/nxp-imx6.cfg
> index b47a89a0..76d7811b 100644
> --- a/bsp/nxp-imx6/nxp-imx6.cfg
> +++ b/bsp/nxp-imx6/nxp-imx6.cfg
> @@ -101,6 +101,7 @@ CONFIG_CPU_THERMAL=y
>  CONFIG_IMX_THERMAL=y
>  
>  CONFIG_MEDIA_SUPPORT=y
> +CONFIG_MEDIA_PLATFORM_SUPPORT=y
>  CONFIG_MEDIA_CAMERA_SUPPORT=y
>  CONFIG_V4L_MEM2MEM_DRIVERS=y
>  CONFIG_VIDEO_CODA=y
> -- 
> 2.25.1
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10212): 
https://lists.yoctoproject.org/g/linux-yocto/message/10212
Mute This Topic: https://lists.yoctoproject.org/mt/84500763/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [linux-yocto][linux-yocto v5.10] Fix sleep in atomic environment for marvell cn96xx

2021-07-29 Thread Bruce Ashfield

In message: [linux-yocto][linux-yocto v5.10] Fix sleep in atomic environment 
for marvell cn96xx
on 29/07/2021 Ruiqiang Hao wrote:

> Hi Bruce,
> 
> Please help to merge this patch into our linux-yocto repo.
> 
> patch:
>   0001-Mailbox-Replace-mutex-lock-with-spin-lock.patch
> 
> repo:
>   linux-yocto
> branch:
>   v5.10/standard/cn-sdkv5.4/octeon
>   v5.10/standard/preempt-rt/cn-sdkv5.4/octeon

merged.

Bruce

> 
> Thanks,
> Ruiqiang

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10211): 
https://lists.yoctoproject.org/g/linux-yocto/message/10211
Mute This Topic: https://lists.yoctoproject.org/mt/84521886/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [V2][linux-yocto][linux-yocto v5.10/standard/sdkv5.10/xlnx-soc][PATCH 1/2] net: xilinx: fix compile warning due to typecheck

2021-07-29 Thread Bruce Ashfield
merged.

Bruce

In message: [V2][linux-yocto][linux-yocto 
v5.10/standard/sdkv5.10/xlnx-soc][PATCH 1/2]  net: xilinx: fix compile warning 
due to typecheck
on 29/07/2021 quanyang.w...@windriver.com wrote:

> From: Quanyang Wang 
> 
> This warning is introduced by the SDK commit 1b5d1c43433b3 ("net: xilinx:
> axiethernet: Add check for transmit data FIFO vacancy").
> 
> Change the type of flags from "u32" to "unsigned long" to avoid the
> compile warning as below:
> 
> include/linux/spinlock.h:251:3: note: in expansion of macro ‘typecheck’
>   251 |   typecheck(unsigned long, flags); \
>   |   ^
> drivers/net/ethernet/xilinx/xilinx_axienet_main.c:1124:3: note: in expansion 
> of macro ‘spin_lock_irqsave’
>  1124 |   spin_lock_irqsave(>ptp_tx_lock, flags);
>   |   ^
> 
> Signed-off-by: Quanyang Wang 
> ---
> V1 ---> V2:
> Add the info of the commit which introduces this warning.
> 
> ---
>  drivers/net/ethernet/xilinx/xilinx_axienet_main.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/ethernet/xilinx/xilinx_axienet_main.c 
> b/drivers/net/ethernet/xilinx/xilinx_axienet_main.c
> index 5a52872ec1430..64de359e7697d 100644
> --- a/drivers/net/ethernet/xilinx/xilinx_axienet_main.c
> +++ b/drivers/net/ethernet/xilinx/xilinx_axienet_main.c
> @@ -1067,7 +1067,7 @@ static int axienet_create_tsheader(u8 *buf, u8 msg_type,
>  #endif
>   u64 val;
>   u32 tmp[MRMAC_TS_HEADER_WORDS];
> - u32 flags;
> + unsigned long flags;
>   int i;
>  
>  #ifdef CONFIG_AXIENET_HAS_MCDMA
> -- 
> 2.25.1
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10210): 
https://lists.yoctoproject.org/g/linux-yocto/message/10210
Mute This Topic: https://lists.yoctoproject.org/mt/84522327/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [V2][linux-yocto][linux-yocto v5.10/standard/sdkv5.10/xlnx-soc][PATCH 1/2] net: xilinx: fix compile warning due to typecheck

2021-07-29 Thread Michal Simek


On 7/29/21 6:48 AM, quanyang.w...@windriver.com wrote:
> From: Quanyang Wang 
> 
> This warning is introduced by the SDK commit 1b5d1c43433b3 ("net: xilinx:
> axiethernet: Add check for transmit data FIFO vacancy").
> 
> Change the type of flags from "u32" to "unsigned long" to avoid the
> compile warning as below:
> 
> include/linux/spinlock.h:251:3: note: in expansion of macro ‘typecheck’
>   251 |   typecheck(unsigned long, flags); \
>   |   ^
> drivers/net/ethernet/xilinx/xilinx_axienet_main.c:1124:3: note: in expansion 
> of macro ‘spin_lock_irqsave’
>  1124 |   spin_lock_irqsave(>ptp_tx_lock, flags);
>   |   ^
> 
> Signed-off-by: Quanyang Wang 
> ---
> V1 ---> V2:
> Add the info of the commit which introduces this warning.
> 
> ---
>  drivers/net/ethernet/xilinx/xilinx_axienet_main.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/ethernet/xilinx/xilinx_axienet_main.c 
> b/drivers/net/ethernet/xilinx/xilinx_axienet_main.c
> index 5a52872ec1430..64de359e7697d 100644
> --- a/drivers/net/ethernet/xilinx/xilinx_axienet_main.c
> +++ b/drivers/net/ethernet/xilinx/xilinx_axienet_main.c
> @@ -1067,7 +1067,7 @@ static int axienet_create_tsheader(u8 *buf, u8 msg_type,
>  #endif
>   u64 val;
>   u32 tmp[MRMAC_TS_HEADER_WORDS];
> - u32 flags;
> + unsigned long flags;
>   int i;
>  
>  #ifdef CONFIG_AXIENET_HAS_MCDMA
> 

This looks good. I have also added it to xilinx tree.

Thanks,
Michal

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10209): 
https://lists.yoctoproject.org/g/linux-yocto/message/10209
Mute This Topic: https://lists.yoctoproject.org/mt/84522327/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [V2][linux-yocto][linux-yocto v5.10/standard/sdkv5.10/xlnx-soc][PATCH 2/2] arm64: zynqmp: fix warning about lack of #address-cells

2021-07-29 Thread quanyang.wang

Hi Michal,

On 7/29/21 1:57 PM, Michal Simek wrote:

Hi,

On 7/29/21 6:48 AM, quanyang.w...@windriver.com wrote:

From: Quanyang Wang 

The interrupt controller nodes need #address-cells property. When
building device-tree files with "DTC_FLAGS='-@'", there is warning
as below:

arch/arm64/boot/dts/xilinx/zynqmp.dtsi:450.38-460.5: Warning 
(interrupt_provider): /axi/interrupt-controller@f901: Missing 
#address-cells in interrupt provider
arch/arm64/boot/dts/xilinx/zynqmp.dtsi:720.23-731.5: Warning 
(interrupt_provider): /axi/gpio@ff0a: Missing #address-cells in interrupt 
provider

Since they have no children in the device-tree hierarchy, assign '0'
to the "address-cells" property.

Signed-off-by: Quanyang Wang 
---
V1 ---> V2:
Fix the wrong description in commit message and short log since the
modfications are about "address-cells" but not the "interrupt-cells".

---
  arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 2 ++
  1 file changed, 2 insertions(+)

diff --git a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi 
b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
index 2e1ccd179d17d..8c2cad7816435 100644
--- a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
+++ b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
@@ -451,6 +451,7 @@ fpd_dma_chan8: dma@fd57 {
gic: interrupt-controller@f901 {
compatible = "arm,gic-400";
#interrupt-cells = <3>;
+   #address-cells = <0>;
reg = <0x0 0xf901 0x0 0x1>,
  <0x0 0xf902 0x0 0x2>,
  <0x0 0xf904 0x0 0x2>,
@@ -665,6 +666,7 @@ gpio: gpio@ff0a {
interrupts = <0 16 4>;
interrupt-controller;
#interrupt-cells = <2>;
+   #address-cells = <0>;
reg = <0x0 0xff0a 0x0 0x1000>;
power-domains = <_firmware PD_GPIO>;
};


I have added this change upstream by
commit c6badbd2d321c19d4f55ee56b0ef12bb3352feac
Author: Michal Simek 
AuthorDate: Wed Dec 2 15:14:57 2020 +0100
Commit: Michal Simek 
CommitDate: Thu Jan 21 11:17:16 2021 +0100

 arm64: dts: zynqmp: Add address-cells property to interrupt controllers

 The commit 3eb619b2f7d8 ("scripts/dtc: Update to upstream version
 v1.6.0-11-g9d7888cbf19c") updated dtc version which also contained DTC
 commit
 "81e0919a3e21 checks: Add interrupt provider test"
 where reasons for this checking are mentioned as
 "A missing #address-cells property is less critical, but creates
 ambiguities when used in interrupt-map properties, so warn about this as
 well now."

 That's why add address-cells property to gic and gpio nodes to get
rid of
 this warning.

 CC: Andre Przywara 
 Signed-off-by: Michal Simek 
 Link:
https://lore.kernel.org/r/e4f54ddce33b79a783aa7c76e0dc6e9787933610.1606918493.git.michal.si...@xilinx.com

But take a look at this thread
https://lore.kernel.org/linux-devicetree/cal_jsqjnu1m6ut8g_36ve-og22jfsyshbmvhogtdrhc-s37...@mail.gmail.com/
that we shouldn't add this and these warnings are not an issue.


Thank you for the info.  Please ignore this patch.

Thanks,

Quanyang



Thanks,
Michal

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10208): 
https://lists.yoctoproject.org/g/linux-yocto/message/10208
Mute This Topic: https://lists.yoctoproject.org/mt/84522328/21656
Mute 
#address-cells:https://lists.yoctoproject.org/g/linux-yocto/mutehashtag/address-cells
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-