sam9x60 uart 中断列表

节选自邮件列表

All the mail mirrored from lore.kernel.org

help / color / mirror / Atom feed

  • [PATCHv3 0/2] update at91 usart compatible for sam9x60
    @ 2023-07-18 6:57 ` Durai Manickam KR
    0 siblings, 0 replies; 11+ messages in thread
    From: Durai Manickam KR @ 2023-07-18 6:57 UTC (permalink / raw)
    To: Hari.PrasathGE, balamanikandan.gunasundar, manikandan.m,
    varshini.rajendran, dharma.b, nayabbasha.sayed, balakrishnan.s,
    cristian.birsan, nicolas.ferre, krzysztof.kozlowski,
    alexandre.belloni, davem, arnd, olof, soc, devicetree,
    linux-arm-kernel, linux-kernel, Kavyasree.Kotagiri,
    Horatiu.Vultur, robh+dt, andrew, michael, jerry.ray, conor+dt,
    jesper.nilsson, andre.przywara, ada, radu_nicolae.pirea,
    richard.genoud, gregkh, linux-spi, linux-serial
    Cc: Durai Manickam KR

There is only one debug unit in the sam9x60 SOC and it has the chipid
register. So defining these dbgu compatible strings to the flexcom usart
is not correct and causes the SOC detection failure. So removing these
dbgu compatible strings defined under the flexcom usart and updating
the yaml file accordingly.

v2 changes:

  1. Updating the dt-bindings documentation and send one more patch for
    the yaml file.

v3 change:

  1. Explained the issue in the commit message rather than in the cover
    letter. Added the detailed commit message for the changes done.

Durai Manickam KR (2):
dt-bindings: serial: atmel,at91-usart: update compatible for sam9x60
ARM: dts: at91: sam9x60: fix the SOC detection

…/bindings/serial/atmel,at91-usart.yaml | 4 +±
arch/arm/boot/dts/microchip/sam9x60.dtsi | 26 ++++++++±---------
2 files changed, 16 insertions(+), 14 deletions(-)


2.25.1

^ permalink raw reply [flat|nested] 11+ messages in thread

  • [PATCHv3 0/2] update at91 usart compatible for sam9x60
    @ 2023-07-18 6:57 ` Durai Manickam KR
    0 siblings, 0 replies; 11+ messages in thread
    From: Durai Manickam KR @ 2023-07-18 6:57 UTC (permalink / raw)
    To: Hari.PrasathGE, balamanikandan.gunasundar, manikandan.m,
    varshini.rajendran, dharma.b, nayabbasha.sayed, balakrishnan.s,
    cristian.birsan, nicolas.ferre, krzysztof.kozlowski,
    alexandre.belloni, davem, arnd, olof, soc, devicetree,
    linux-arm-kernel, linux-kernel, Kavyasree.Kotagiri,
    Horatiu.Vultur, robh+dt, andrew, michael, jerry.ray, conor+dt,
    jesper.nilsson, andre.przywara, ada, radu_nicolae.pirea,
    richard.genoud, gregkh, linux-spi, linux-serial
    Cc: Durai Manickam KR

There is only one debug unit in the sam9x60 SOC and it has the chipid
register. So defining these dbgu compatible strings to the flexcom usart
is not correct and causes the SOC detection failure. So removing these
dbgu compatible strings defined under the flexcom usart and updating
the yaml file accordingly.

v2 changes:

  1. Updating the dt-bindings documentation and send one more patch for
    the yaml file.

v3 change:

  1. Explained the issue in the commit message rather than in the cover
    letter. Added the detailed commit message for the changes done.

Durai Manickam KR (2):
dt-bindings: serial: atmel,at91-usart: update compatible for sam9x60
ARM: dts: at91: sam9x60: fix the SOC detection

…/bindings/serial/atmel,at91-usart.yaml | 4 +±
arch/arm/boot/dts/microchip/sam9x60.dtsi | 26 ++++++++±---------
2 files changed, 16 insertions(+), 14 deletions(-)


2.25.1


linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply [flat|nested] 11+ messages in thread

  • [PATCHv3 1/2] dt-bindings: serial: atmel,at91-usart: update compatible for sam9x60
    2023-07-18 6:57 Durai Manickam KR @ 2023-07-18 6:57 Durai Manickam KR
    -1 siblings, 0 replies; 11+ messages in thread
    From: Durai Manickam KR @ 2023-07-18 6:57 UTC (permalink / raw)
    To: Hari.PrasathGE, balamanikandan.gunasundar, manikandan.m,
    varshini.rajendran, dharma.b, nayabbasha.sayed, balakrishnan.s,
    cristian.birsan, nicolas.ferre, krzysztof.kozlowski,
    alexandre.belloni, davem, arnd, olof, soc, devicetree,
    linux-arm-kernel, linux-kernel, Kavyasree.Kotagiri,
    Horatiu.Vultur, robh+dt, andrew, michael, jerry.ray, conor+dt,
    jesper.nilsson, andre.przywara, ada, radu_nicolae.pirea,
    richard.genoud, gregkh, linux-spi, linux-serial
    Cc: Durai Manickam KR

There is only one debug unit in the sam9x60 SOC and it has the chipid
register. So, the dbgu compatible strings are valid only for debug usart.
Defining these dbgu compatible strings are not valid for flexcom usart.
So adding the items which is valid only for flexcom usart and removing
the microchip,sam9x60-usart compatible string from the enum list as no
usart node defines only this specific compatible string.

Signed-off-by: Durai Manickam KR durai.manickamkr@microchip.com

…/devicetree/bindings/serial/atmel,at91-usart.yaml | 4 ++±
1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml b/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
index 30b2131b5860…65cb2e5c5eee 100644
— a/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
+++ b/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
@@ -16,13 +16,15 @@ properties:
- enum:
- atmel,at91rm9200-usart
- atmel,at91sam9260-usart

  •      - microchip,sam9x60-usart- items:- const: atmel,at91rm9200-dbgu- const: atmel,at91rm9200-usart- items:- const: atmel,at91sam9260-dbgu- const: atmel,at91sam9260-usart
    
  •  - items:
    
  •      - const: microchip,sam9x60-usart
    
  •      - const: atmel,at91sam9260-usart- items:- const: microchip,sam9x60-dbgu- const: microchip,sam9x60-usart
    


2.25.1

^ permalink raw reply related [flat|nested] 11+ messages in thread

  • [PATCHv3 1/2] dt-bindings: serial: atmel,at91-usart: update compatible for sam9x60
    @ 2023-07-18 6:57 ` Durai Manickam KR
    0 siblings, 0 replies; 11+ messages in thread
    From: Durai Manickam KR @ 2023-07-18 6:57 UTC (permalink / raw)
    To: Hari.PrasathGE, balamanikandan.gunasundar, manikandan.m,
    varshini.rajendran, dharma.b, nayabbasha.sayed, balakrishnan.s,
    cristian.birsan, nicolas.ferre, krzysztof.kozlowski,
    alexandre.belloni, davem, arnd, olof, soc, devicetree,
    linux-arm-kernel, linux-kernel, Kavyasree.Kotagiri,
    Horatiu.Vultur, robh+dt, andrew, michael, jerry.ray, conor+dt,
    jesper.nilsson, andre.przywara, ada, radu_nicolae.pirea,
    richard.genoud, gregkh, linux-spi, linux-serial
    Cc: Durai Manickam KR

There is only one debug unit in the sam9x60 SOC and it has the chipid
register. So, the dbgu compatible strings are valid only for debug usart.
Defining these dbgu compatible strings are not valid for flexcom usart.
So adding the items which is valid only for flexcom usart and removing
the microchip,sam9x60-usart compatible string from the enum list as no
usart node defines only this specific compatible string.

Signed-off-by: Durai Manickam KR durai.manickamkr@microchip.com

…/devicetree/bindings/serial/atmel,at91-usart.yaml | 4 ++±
1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml b/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
index 30b2131b5860…65cb2e5c5eee 100644
— a/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
+++ b/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
@@ -16,13 +16,15 @@ properties:
- enum:
- atmel,at91rm9200-usart
- atmel,at91sam9260-usart

  •      - microchip,sam9x60-usart- items:- const: atmel,at91rm9200-dbgu- const: atmel,at91rm9200-usart- items:- const: atmel,at91sam9260-dbgu- const: atmel,at91sam9260-usart
    
  •  - items:
    
  •      - const: microchip,sam9x60-usart
    
  •      - const: atmel,at91sam9260-usart- items:- const: microchip,sam9x60-dbgu- const: microchip,sam9x60-usart
    


2.25.1


linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply related [flat|nested] 11+ messages in thread

  • [PATCHv3 2/2] ARM: dts: at91: sam9x60: fix the SOC detection
    2023-07-18 6:57 Durai Manickam KR @ 2023-07-18 6:57 Durai Manickam KR
    -1 siblings, 0 replies; 11+ messages in thread
    From: Durai Manickam KR @ 2023-07-18 6:57 UTC (permalink / raw)
    To: Hari.PrasathGE, balamanikandan.gunasundar, manikandan.m,
    varshini.rajendran, dharma.b, nayabbasha.sayed, balakrishnan.s,
    cristian.birsan, nicolas.ferre, krzysztof.kozlowski,
    alexandre.belloni, davem, arnd, olof, soc, devicetree,
    linux-arm-kernel, linux-kernel, Kavyasree.Kotagiri,
    Horatiu.Vultur, robh+dt, andrew, michael, jerry.ray, conor+dt,
    jesper.nilsson, andre.przywara, ada, radu_nicolae.pirea,
    richard.genoud, gregkh, linux-spi, linux-serial
    Cc: Durai Manickam KR

Defining the dbgu compatible strings in the UART submodule of the
flexcom gives the below error log,
AT91: Could not find matching SoC description
This error arises due to defining the dbgu compatible strings to
the flexcom usart which is not valid because there is only one debug unit
in the sam9x60 SOC and it has the chipid register. The dbgu compatible
strings are valid only for debug usart and not valid for flexcom usart.
Thus removing the dbgu compatible strings in the UART submodule of the
flexcom for the proper SOC detection.

Fixes: 99c808335877 (ARM: dts: at91: sam9x60: Add missing flexcom definitions)
Signed-off-by: Durai Manickam KR durai.manickamkr@microchip.com

arch/arm/boot/dts/microchip/sam9x60.dtsi | 26 +++++++++++±-----------
1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/arch/arm/boot/dts/microchip/sam9x60.dtsi b/arch/arm/boot/dts/microchip/sam9x60.dtsi
index 8b53997675e7…73d570a17269 100644
— a/arch/arm/boot/dts/microchip/sam9x60.dtsi
+++ b/arch/arm/boot/dts/microchip/sam9x60.dtsi
@@ -172,7 +172,7 @@ flx4: flexcom@f0000000 {
status = “disabled”;

			uart4: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <13 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -240,7 +240,7 @@ flx5: flexcom@f0004000 {
status = “disabled”;

			uart5: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;atmel,usart-mode = <AT91_USART_MODE_SERIAL>;interrupts = <14 IRQ_TYPE_LEVEL_HIGH 7>;
    

@@ -370,7 +370,7 @@ flx11: flexcom@f0020000 {
status = “disabled”;

			uart11: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <32 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -419,7 +419,7 @@ flx12: flexcom@f0024000 {
status = “disabled”;

			uart12: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <33 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -576,7 +576,7 @@ flx6: flexcom@f8010000 {
status = “disabled”;

			uart6: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <9 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -625,7 +625,7 @@ flx7: flexcom@f8014000 {
status = “disabled”;

			uart7: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <10 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -674,7 +674,7 @@ flx8: flexcom@f8018000 {
status = “disabled”;

			uart8: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <11 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -723,7 +723,7 @@ flx0: flexcom@f801c000 {
status = “disabled”;

			uart0: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <5 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -791,7 +791,7 @@ flx1: flexcom@f8020000 {
status = “disabled”;

			uart1: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <6 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -859,7 +859,7 @@ flx2: flexcom@f8024000 {
status = “disabled”;

			uart2: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <7 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -927,7 +927,7 @@ flx3: flexcom@f8028000 {
status = “disabled”;

			uart3: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <8 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -1050,7 +1050,7 @@ flx9: flexcom@f8040000 {
status = “disabled”;

			uart9: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <15 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -1099,7 +1099,7 @@ flx10: flexcom@f8044000 {
status = “disabled”;

			uart10: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <16 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    


2.25.1

^ permalink raw reply related [flat|nested] 11+ messages in thread

  • [PATCHv3 2/2] ARM: dts: at91: sam9x60: fix the SOC detection
    @ 2023-07-18 6:57 ` Durai Manickam KR
    0 siblings, 0 replies; 11+ messages in thread
    From: Durai Manickam KR @ 2023-07-18 6:57 UTC (permalink / raw)
    To: Hari.PrasathGE, balamanikandan.gunasundar, manikandan.m,
    varshini.rajendran, dharma.b, nayabbasha.sayed, balakrishnan.s,
    cristian.birsan, nicolas.ferre, krzysztof.kozlowski,
    alexandre.belloni, davem, arnd, olof, soc, devicetree,
    linux-arm-kernel, linux-kernel, Kavyasree.Kotagiri,
    Horatiu.Vultur, robh+dt, andrew, michael, jerry.ray, conor+dt,
    jesper.nilsson, andre.przywara, ada, radu_nicolae.pirea,
    richard.genoud, gregkh, linux-spi, linux-serial
    Cc: Durai Manickam KR

Defining the dbgu compatible strings in the UART submodule of the
flexcom gives the below error log,
AT91: Could not find matching SoC description
This error arises due to defining the dbgu compatible strings to
the flexcom usart which is not valid because there is only one debug unit
in the sam9x60 SOC and it has the chipid register. The dbgu compatible
strings are valid only for debug usart and not valid for flexcom usart.
Thus removing the dbgu compatible strings in the UART submodule of the
flexcom for the proper SOC detection.

Fixes: 99c808335877 (ARM: dts: at91: sam9x60: Add missing flexcom definitions)
Signed-off-by: Durai Manickam KR durai.manickamkr@microchip.com

arch/arm/boot/dts/microchip/sam9x60.dtsi | 26 +++++++++++±-----------
1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/arch/arm/boot/dts/microchip/sam9x60.dtsi b/arch/arm/boot/dts/microchip/sam9x60.dtsi
index 8b53997675e7…73d570a17269 100644
— a/arch/arm/boot/dts/microchip/sam9x60.dtsi
+++ b/arch/arm/boot/dts/microchip/sam9x60.dtsi
@@ -172,7 +172,7 @@ flx4: flexcom@f0000000 {
status = “disabled”;

			uart4: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <13 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -240,7 +240,7 @@ flx5: flexcom@f0004000 {
status = “disabled”;

			uart5: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;atmel,usart-mode = <AT91_USART_MODE_SERIAL>;interrupts = <14 IRQ_TYPE_LEVEL_HIGH 7>;
    

@@ -370,7 +370,7 @@ flx11: flexcom@f0020000 {
status = “disabled”;

			uart11: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <32 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -419,7 +419,7 @@ flx12: flexcom@f0024000 {
status = “disabled”;

			uart12: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <33 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -576,7 +576,7 @@ flx6: flexcom@f8010000 {
status = “disabled”;

			uart6: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <9 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -625,7 +625,7 @@ flx7: flexcom@f8014000 {
status = “disabled”;

			uart7: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <10 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -674,7 +674,7 @@ flx8: flexcom@f8018000 {
status = “disabled”;

			uart8: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <11 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -723,7 +723,7 @@ flx0: flexcom@f801c000 {
status = “disabled”;

			uart0: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <5 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -791,7 +791,7 @@ flx1: flexcom@f8020000 {
status = “disabled”;

			uart1: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <6 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -859,7 +859,7 @@ flx2: flexcom@f8024000 {
status = “disabled”;

			uart2: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <7 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -927,7 +927,7 @@ flx3: flexcom@f8028000 {
status = “disabled”;

			uart3: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <8 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -1050,7 +1050,7 @@ flx9: flexcom@f8040000 {
status = “disabled”;

			uart9: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <15 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -1099,7 +1099,7 @@ flx10: flexcom@f8044000 {
status = “disabled”;

			uart10: serial@200 {
  •   			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  •   			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <16 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    


2.25.1


linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply related [flat|nested] 11+ messages in thread

  • Re: [PATCHv3 1/2] dt-bindings: serial: atmel,at91-usart: update compatible for sam9x60
    2023-07-18 6:57 Durai Manickam KR @ 2023-07-18 11:12 Conor Dooley
    -1 siblings, 0 replies; 11+ messages in thread
    From: Conor Dooley @ 2023-07-18 11:12 UTC (permalink / raw)
    To: Durai Manickam KR
    Cc: Hari.PrasathGE, balamanikandan.gunasundar, manikandan.m,
    varshini.rajendran, dharma.b, nayabbasha.sayed, balakrishnan.s,
    cristian.birsan, nicolas.ferre, krzysztof.kozlowski,
    alexandre.belloni, davem, arnd, olof, soc, devicetree,
    linux-arm-kernel, linux-kernel, Kavyasree.Kotagiri,
    Horatiu.Vultur, robh+dt, andrew, michael, jerry.ray, conor+dt,
    jesper.nilsson, andre.przywara, ada, radu_nicolae.pirea,
    richard.genoud, gregkh, linux-spi, linux-serial

[-- Attachment #1: Type: text/plain, Size: 1946 bytes --]

On Tue, Jul 18, 2023 at 12:27:34PM +0530, Durai Manickam KR wrote:

There is only one debug unit in the sam9x60 SOC and it has the chipid
register. So, the dbgu compatible strings are valid only for debug usart.
Defining these dbgu compatible strings are not valid for flexcom usart.
So adding the items which is valid only for flexcom usart and removing
the microchip,sam9x60-usart compatible string from the enum list as no
usart node defines only this specific compatible string.

It may have been worth pointing out that had any DTS used the compatible
that is being disallowed in isolation after this change, no driver in
Linux would have bound to it anyway.

Reviewed-by: Conor Dooley conor.dooley@microchip.com

Thanks,
Conor.

Signed-off-by: Durai Manickam KR durai.manickamkr@microchip.com

…/devicetree/bindings/serial/atmel,at91-usart.yaml | 4 ++±
1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml b/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
index 30b2131b5860…65cb2e5c5eee 100644
— a/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
+++ b/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
@@ -16,13 +16,15 @@ properties:
- enum:
- atmel,at91rm9200-usart
- atmel,at91sam9260-usart

  •      - microchip,sam9x60-usart- items:- const: atmel,at91rm9200-dbgu- const: atmel,at91rm9200-usart- items:- const: atmel,at91sam9260-dbgu- const: atmel,at91sam9260-usart
    
  •  - items:
    
  •      - const: microchip,sam9x60-usart
    
  •      - const: atmel,at91sam9260-usart- items:- const: microchip,sam9x60-dbgu- const: microchip,sam9x60-usart
    


2.25.1

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

^ permalink raw reply [flat|nested] 11+ messages in thread

  • Re: [PATCHv3 1/2] dt-bindings: serial: atmel,at91-usart: update compatible for sam9x60
    @ 2023-07-18 11:12 ` Conor Dooley
    0 siblings, 0 replies; 11+ messages in thread
    From: Conor Dooley @ 2023-07-18 11:12 UTC (permalink / raw)
    To: Durai Manickam KR
    Cc: andrew, alexandre.belloni, devicetree, jerry.ray, Hari.PrasathGE,
    varshini.rajendran, Horatiu.Vultur, manikandan.m, jesper.nilsson,
    balamanikandan.gunasundar, michael, dharma.b, linux-serial,
    cristian.birsan, nayabbasha.sayed, conor+dt, arnd,
    andre.przywara, radu_nicolae.pirea, soc, robh+dt,
    linux-arm-kernel, balakrishnan.s, ada, gregkh, linux-kernel,
    linux-spi, richard.genoud, krzysztof.kozlowski,
    Kavyasree.Kotagiri, olof, davem

[-- Attachment #1.1: Type: text/plain, Size: 1946 bytes --]

On Tue, Jul 18, 2023 at 12:27:34PM +0530, Durai Manickam KR wrote:

There is only one debug unit in the sam9x60 SOC and it has the chipid
register. So, the dbgu compatible strings are valid only for debug usart.
Defining these dbgu compatible strings are not valid for flexcom usart.
So adding the items which is valid only for flexcom usart and removing
the microchip,sam9x60-usart compatible string from the enum list as no
usart node defines only this specific compatible string.

It may have been worth pointing out that had any DTS used the compatible
that is being disallowed in isolation after this change, no driver in
Linux would have bound to it anyway.

Reviewed-by: Conor Dooley conor.dooley@microchip.com

Thanks,
Conor.

Signed-off-by: Durai Manickam KR durai.manickamkr@microchip.com

…/devicetree/bindings/serial/atmel,at91-usart.yaml | 4 ++±
1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml b/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
index 30b2131b5860…65cb2e5c5eee 100644
— a/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
+++ b/Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
@@ -16,13 +16,15 @@ properties:
- enum:
- atmel,at91rm9200-usart
- atmel,at91sam9260-usart

  •      - microchip,sam9x60-usart- items:- const: atmel,at91rm9200-dbgu- const: atmel,at91rm9200-usart- items:- const: atmel,at91sam9260-dbgu- const: atmel,at91sam9260-usart
    
  •  - items:
    
  •      - const: microchip,sam9x60-usart
    
  •      - const: atmel,at91sam9260-usart- items:- const: microchip,sam9x60-dbgu- const: microchip,sam9x60-usart
    


2.25.1

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]


linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply [flat|nested] 11+ messages in thread

  • Re: [PATCHv3 0/2] update at91 usart compatible for sam9x60
    2023-07-18 6:57 Durai Manickam KR (2 preceding siblings …)
    (?)
    @ 2023-07-24 14:05 ` patchwork-bot+linux-soc
    -1 siblings, 0 replies; 11+ messages in thread
    From: patchwork-bot+linux-soc @ 2023-07-24 14:05 UTC (permalink / raw)
    To: Durai Manickam KR; +Cc: soc

Hello:

This series was applied to soc/soc.git (arm/fixes)
by Arnd Bergmann arnd@arndb.de:

On Tue, 18 Jul 2023 12:27:33 +0530 you wrote:

There is only one debug unit in the sam9x60 SOC and it has the chipid
register. So defining these dbgu compatible strings to the flexcom usart
is not correct and causes the SOC detection failure. So removing these
dbgu compatible strings defined under the flexcom usart and updating
the yaml file accordingly.

v2 changes:

  1. Updating the dt-bindings documentation and send one more patch for
    the yaml file.

[…]

Here is the summary with links:

  • [PATCHv3,1/2] dt-bindings: serial: atmel,at91-usart: update compatible for sam9x60
    https://git.kernel.org/soc/soc/c/92d39d018347
  • [PATCHv3,2/2] ARM: dts: at91: sam9x60: fix the SOC detection
    https://git.kernel.org/soc/soc/c/f6ad3c13f1b8

You are awesome, thank you!

Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html

^ permalink raw reply [flat|nested] 11+ messages in thread

  • Re: [PATCHv3 2/2] ARM: dts: at91: sam9x60: fix the SOC detection
    2023-07-18 6:57 Durai Manickam KR @ 2023-07-31 13:35 Alexander Dahl
    -1 siblings, 0 replies; 11+ messages in thread
    From: Alexander Dahl @ 2023-07-31 13:35 UTC (permalink / raw)
    To: Durai Manickam KR
    Cc: andrew, alexandre.belloni, devicetree, jerry.ray, Hari.PrasathGE,
    varshini.rajendran, Horatiu.Vultur, manikandan.m, jesper.nilsson,
    balamanikandan.gunasundar, michael, dharma.b, linux-serial,
    cristian.birsan, nayabbasha.sayed, conor+dt, arnd,
    andre.przywara, radu_nicolae.pirea, soc, robh+dt,
    linux-arm-kernel, balakrishnan.s, ada, gregkh, linux-kernel,
    linux-spi, richard.genoud, krzysztof.kozlowski,
    Kavyasree.Kotagiri, olof, davem

Hello Durai,

Am Tue, Jul 18, 2023 at 12:27:35PM +0530 schrieb Durai Manickam KR:

Defining the dbgu compatible strings in the UART submodule of the
flexcom gives the below error log,
AT91: Could not find matching SoC description
This error arises due to defining the dbgu compatible strings to
the flexcom usart which is not valid because there is only one debug unit
in the sam9x60 SOC and it has the chipid register. The dbgu compatible
strings are valid only for debug usart and not valid for flexcom usart.
Thus removing the dbgu compatible strings in the UART submodule of the
flexcom for the proper SOC detection.

Fixes: 99c808335877 (ARM: dts: at91: sam9x60: Add missing flexcom definitions)
Signed-off-by: Durai Manickam KR durai.manickamkr@microchip.com

Acked-by: Alexander Dahl ada@thorsis.com

(The diff of the patch is identical to the diff of a quick hacked
patch I made weeks ago for my BSP which fixed the issue. SoC variant
was reported correctly on serial console on boot again. However I did
not actually test your patch on my hardware (sam9x60 curiosity),
thus Acked-by and not Tested-by.)

Greets
Alex


arch/arm/boot/dts/microchip/sam9x60.dtsi | 26 +++++++++++±-----------
1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/arch/arm/boot/dts/microchip/sam9x60.dtsi b/arch/arm/boot/dts/microchip/sam9x60.dtsi
index 8b53997675e7…73d570a17269 100644
— a/arch/arm/boot/dts/microchip/sam9x60.dtsi
+++ b/arch/arm/boot/dts/microchip/sam9x60.dtsi
@@ -172,7 +172,7 @@ flx4: flexcom@f0000000 {
status = “disabled”;

  		uart4: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <13 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -240,7 +240,7 @@ flx5: flexcom@f0004000 {
status = “disabled”;

  		uart5: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;atmel,usart-mode = <AT91_USART_MODE_SERIAL>;interrupts = <14 IRQ_TYPE_LEVEL_HIGH 7>;
    

@@ -370,7 +370,7 @@ flx11: flexcom@f0020000 {
status = “disabled”;

  		uart11: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <32 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -419,7 +419,7 @@ flx12: flexcom@f0024000 {
status = “disabled”;

  		uart12: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <33 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -576,7 +576,7 @@ flx6: flexcom@f8010000 {
status = “disabled”;

  		uart6: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <9 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -625,7 +625,7 @@ flx7: flexcom@f8014000 {
status = “disabled”;

  		uart7: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <10 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -674,7 +674,7 @@ flx8: flexcom@f8018000 {
status = “disabled”;

  		uart8: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <11 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -723,7 +723,7 @@ flx0: flexcom@f801c000 {
status = “disabled”;

  		uart0: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <5 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -791,7 +791,7 @@ flx1: flexcom@f8020000 {
status = “disabled”;

  		uart1: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <6 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -859,7 +859,7 @@ flx2: flexcom@f8024000 {
status = “disabled”;

  		uart2: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <7 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -927,7 +927,7 @@ flx3: flexcom@f8028000 {
status = “disabled”;

  		uart3: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <8 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -1050,7 +1050,7 @@ flx9: flexcom@f8040000 {
status = “disabled”;

  		uart9: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <15 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -1099,7 +1099,7 @@ flx10: flexcom@f8044000 {
status = “disabled”;

  		uart10: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <16 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    


2.25.1


linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply [flat|nested] 11+ messages in thread

  • Re: [PATCHv3 2/2] ARM: dts: at91: sam9x60: fix the SOC detection
    @ 2023-07-31 13:35 ` Alexander Dahl
    0 siblings, 0 replies; 11+ messages in thread
    From: Alexander Dahl @ 2023-07-31 13:35 UTC (permalink / raw)
    To: Durai Manickam KR
    Cc: Hari.PrasathGE, balamanikandan.gunasundar, manikandan.m,
    varshini.rajendran, dharma.b, nayabbasha.sayed, balakrishnan.s,
    cristian.birsan, nicolas.ferre, krzysztof.kozlowski,
    alexandre.belloni, davem, arnd, olof, soc, devicetree,
    linux-arm-kernel, linux-kernel, Kavyasree.Kotagiri,
    Horatiu.Vultur, robh+dt, andrew, michael, jerry.ray, conor+dt,
    jesper.nilsson, andre.przywara, ada, radu_nicolae.pirea,
    richard.genoud, gregkh, linux-spi, linux-serial

Hello Durai,

Am Tue, Jul 18, 2023 at 12:27:35PM +0530 schrieb Durai Manickam KR:

Defining the dbgu compatible strings in the UART submodule of the
flexcom gives the below error log,
AT91: Could not find matching SoC description
This error arises due to defining the dbgu compatible strings to
the flexcom usart which is not valid because there is only one debug unit
in the sam9x60 SOC and it has the chipid register. The dbgu compatible
strings are valid only for debug usart and not valid for flexcom usart.
Thus removing the dbgu compatible strings in the UART submodule of the
flexcom for the proper SOC detection.

Fixes: 99c808335877 (ARM: dts: at91: sam9x60: Add missing flexcom definitions)
Signed-off-by: Durai Manickam KR durai.manickamkr@microchip.com

Acked-by: Alexander Dahl ada@thorsis.com

(The diff of the patch is identical to the diff of a quick hacked
patch I made weeks ago for my BSP which fixed the issue. SoC variant
was reported correctly on serial console on boot again. However I did
not actually test your patch on my hardware (sam9x60 curiosity),
thus Acked-by and not Tested-by.)

Greets
Alex


arch/arm/boot/dts/microchip/sam9x60.dtsi | 26 +++++++++++±-----------
1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/arch/arm/boot/dts/microchip/sam9x60.dtsi b/arch/arm/boot/dts/microchip/sam9x60.dtsi
index 8b53997675e7…73d570a17269 100644
— a/arch/arm/boot/dts/microchip/sam9x60.dtsi
+++ b/arch/arm/boot/dts/microchip/sam9x60.dtsi
@@ -172,7 +172,7 @@ flx4: flexcom@f0000000 {
status = “disabled”;

  		uart4: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <13 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -240,7 +240,7 @@ flx5: flexcom@f0004000 {
status = “disabled”;

  		uart5: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;atmel,usart-mode = <AT91_USART_MODE_SERIAL>;interrupts = <14 IRQ_TYPE_LEVEL_HIGH 7>;
    

@@ -370,7 +370,7 @@ flx11: flexcom@f0020000 {
status = “disabled”;

  		uart11: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <32 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -419,7 +419,7 @@ flx12: flexcom@f0024000 {
status = “disabled”;

  		uart12: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <33 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -576,7 +576,7 @@ flx6: flexcom@f8010000 {
status = “disabled”;

  		uart6: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <9 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -625,7 +625,7 @@ flx7: flexcom@f8014000 {
status = “disabled”;

  		uart7: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <10 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -674,7 +674,7 @@ flx8: flexcom@f8018000 {
status = “disabled”;

  		uart8: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <11 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -723,7 +723,7 @@ flx0: flexcom@f801c000 {
status = “disabled”;

  		uart0: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <5 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -791,7 +791,7 @@ flx1: flexcom@f8020000 {
status = “disabled”;

  		uart1: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <6 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -859,7 +859,7 @@ flx2: flexcom@f8024000 {
status = “disabled”;

  		uart2: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <7 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -927,7 +927,7 @@ flx3: flexcom@f8028000 {
status = “disabled”;

  		uart3: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <8 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -1050,7 +1050,7 @@ flx9: flexcom@f8040000 {
status = “disabled”;

  		uart9: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <15 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    

@@ -1099,7 +1099,7 @@ flx10: flexcom@f8044000 {
status = “disabled”;

  		uart10: serial@200 {
  • 			compatible = "microchip,sam9x60-dbgu", "microchip,sam9x60-usart", "atmel,at91sam9260-dbgu", "atmel,at91sam9260-usart";
    
  • 			compatible = "microchip,sam9x60-usart", "atmel,at91sam9260-usart";reg = <0x200 0x200>;interrupts = <16 IRQ_TYPE_LEVEL_HIGH 7>;dmas = <&dma0
    


2.25.1

^ permalink raw reply [flat|nested] 11+ messages in thread

end of thread, other threads:[~2023-07-31 13:36 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
– links below jump to the message on this page –
2023-07-18 6:57 [PATCHv3 0/2] update at91 usart compatible for sam9x60 Durai Manickam KR
2023-07-18 6:57 Durai Manickam KR 2023-07-18 6:57 [PATCHv3 1/2] dt-bindings: serial: atmel,at91-usart: update " Durai Manickam KR
2023-07-18 6:57 Durai Manickam KR 2023-07-18 11:12 Conor Dooley
2023-07-18 11:12 Conor Dooley 2023-07-18 6:57 [PATCHv3 2/2] ARM: dts: at91: sam9x60: fix the SOC detection Durai Manickam KR
2023-07-18 6:57 Durai Manickam KR 2023-07-31 13:35 Alexander Dahl
2023-07-31 13:35 Alexander Dahl 2023-07-24 14:05 [PATCHv3 0/2] update at91 usart compatible for sam9x60 patchwork-bot+linux-soc

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.

sam9x60 所有的外设设备树请在最新的内核中寻找,官方的维护的可能不全

本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如若转载,请注明出处:http://www.mzph.cn/news/137185.shtml

如若内容造成侵权/违法违规/事实不符,请联系多彩编程网进行投诉反馈email:809451989@qq.com,一经查实,立即删除!

相关文章

Sentinel网关限流

背景 在微服务架构下&#xff0c;每个服务的性能都不同&#xff0c;为避免出现流量洪峰将服务冲垮&#xff0c;需要依赖限流工具来保护服务的稳定性。sentinel是阿里提供的限流工具&#xff0c;社区活跃&#xff0c;功能也很全面&#xff0c;包含实时监控、流控、熔断等功能。…

vue实战——登录过期【详解】

登录过期逻辑 现在普遍的登录权限校验方式是JWT &#xff08;json web token&#xff09;&#xff0c;当登录成功时&#xff0c;前端页面会获得一个 token &#xff0c;每个 token 都设置了过期时间&#xff0c;通过解析 token 即可判断出 token 是否过期。 token 过期&#x…

实现智慧工地的高效建筑管理,数据分析起着关键作用!

智慧工地是利用物联网、云计算、大数据等技术&#xff0c;实现对建筑工地实时监测、管理和控制的一种新型建筑管理方式。 智慧工地架构&#xff1a; 1、终端层&#xff1a;充分利用物联网技术、移动应用、智能硬件设备提高现场管控能力。通过RFID、传感器、摄像头、手机等终端…

很多个pdf怎么合并在一起?

很多个pdf怎么合并在一起&#xff1f;作为一个办公室的伙伴&#xff0c;对于PDF格式肯定不会陌生。它强大的功能为我们的工作提供了许多便利。由于PDF文件格式的稳定性和安全性较高&#xff0c;我们通常在工作或学习中使用它来传输文件&#xff0c;很多人都喜欢将办公文件都做成…

NVM安装node后提示没有对应npm包(即:无法将“npm”项识别为 cmdlet、函数、脚本文件)

背景 windows11 node版本降低到v12.22.12后&#xff0c;执行&#xff1a;nvm -v npm -v npm : 无法将“npm”项识别为 cmdlet、函数、脚本文件或可运行程序的名称。请检查名称的拼写&#xff0c;如果 包括路径&#xff0c;请确保路径正确&#xff0c;然后再试一次。 所在位置 …

java项目调用python进程

问题描述 某一功能是通过python项目实现的&#xff0c;但是主项目是java项目&#xff0c;此时希望在java项目中调用python进程。 方法 import lombok.extern.slf4j.Slf4j;import java.io.BufferedReader; import java.io.File; import java.io.IOException; import java.io.…

数据结构(C语言) 实验-栈与字符串

删除子串 字符串采用带头结点的链表存储&#xff0c;设计算法函数void delstring(linkstring s, int i,int len) 在字符串s中删除从第i个位置开始&#xff0c;长度为len的子串。 void delstring(linkstring s, int i, int len) {linkstring p,q,r;int cnt 1;p s->next;wh…

Python 解决tkinter的Menu菜单command参数与bind方法共用触发事件

用普通函数作为媒介&#xff0c;使用event_generate()方法模拟触发bind()事件来创建一个模拟的event对象&#xff0c;并将其传递给绑定的事件处理函数。 运行结果 示例代码 import tkinter as tk# 菜单事件 def menuEvent(event):print(event.x, event.y)label.config(textf鼠…

OC-编译错误

明明包含了头文件&#xff0c;但是还是显示未知的类型 可能这个头文件被某个宏包住了 #if defined(__cplusplus) 在 C 代码中包含了一个 C 的头文件会显示这个错误“the util lib only be used in c”&#xff0c;此时用 #if defined(__cplusplus) #endif 包一下就行了&…

IntelliJ IDEA 2023.2.1 (Ultimate Edition) 版本 Git 如何合并多次的本地提交进行 Push

本心、输入输出、结果 文章目录 IntelliJ IDEA 2023.2.1 (Ultimate Edition) 版本 Git 如何合并多次的本地提交进行 Push前言为什么需要把多次本地提交合并合并提交的 2 种形式:事中合并、事后合并事中合并事后合并:支持拆分为多组提交弘扬爱国精神IntelliJ IDEA 2023.2.1 (U…

在uniapp和微信小程序中onshow和onload的区别

在uni-app框架中&#xff0c;是两个页面级别的生命周期函数 onLoad&#xff1a;页面加载时调用&#xff0c;可以获取参数&#xff0c;通过options&#xff0c;但是只调用一次&#xff0c;onLoad"适合进行页面初始化操作” onshow&#xff1a; "onShow"生命周期…

Android Mvp案例解析

目录 后端数据接口数据格式 App客户端布局逻辑主界面布局 M&#xff08;Model&#xff09;V&#xff08;View&#xff09;P&#xff08;Presenter&#xff09;OkhttpRetrofitRxJava网络http请求 Mvp架构-初学者MVP架构的契约者 后端数据接口 接口地址&#xff1a;https://apis.…

flink1.18.0 自适应调度器 资源弹性缩放 flink帮你决定并行度

jobmanager.scheduler Elastic Scaling | Apache Flink 配置文件修改并重启flink后,webui上会显示调整并行度的按钮,他可以自己调整,你也可以通过webUI手动调整: 点击 之后: 调整完成后:

机器学习——朴素贝叶斯

目录 一、贝叶斯方法 背景知识 贝叶斯公式 二、朴素贝叶斯原理 判别模型和生成模型 1&#xff0e;朴素贝叶斯法是典型的生成学习方法 2&#xff0e;朴素贝叶斯法的基本假设是条件独立性 3&#xff0e;朴素贝叶斯法利用贝叶斯定理与学到的联合概率模型进行分类预测 用于文…

BERT和ChatGPT简单对比

OpenAI发布了第一个版本的GPT&#xff08;Generative Pretrained Transformer&#xff09;模型在2018年6月。 谷歌的BERT模型&#xff08;Bidirectional Encoder Representations from Transformers&#xff09;是在2018年10月发布的。 BERT和ChatGPT都是由人工智能研究实验室…

FindMy网络帮助您找到电动车

随着科技的发展&#xff0c;我们的生活变得越来越智能化。而现在&#xff0c;这项技术已经深入到了我们的出行方式中。如果你是一位电动车主&#xff0c;那么你可能会遇到一个常见的问题&#xff1a;忘记你的电动车停在了哪里。这种情况在日常生活中时有发生&#xff0c;而现在…

Python - 利用 OCR 技术提取视频台词、字幕

目录 一.引言 二.视频处理 1.视频样式 2.视频截取 ◆ 裁切降帧 ◆ 处理效果 3.视频分段 三.OCR 处理 1.视频帧处理 2.文本识别结果 3.后续工作与优化 ◆ 识别去重 ◆ 多线程提效 ◆ 片头片尾优化 四.总结 一.引言 视频经常会配套对应的台词或者字幕&#xff0c…

git 简单使用说明

git 是什么&#xff1f; 官方的说法自己去官网查&#xff0c;我只说说我浅薄的看法&#xff1a;git是一款用来协同敲代码的工具&#xff0c;方便一群人一起敲代码。 安装 自己去官网下载&#xff0c;b站也是一堆视频 使用前的准备 1.github新建仓库 当然码云也可以&#x…

CSS时间线样式

css实现时间线样式&#xff0c;效果如下图&#xff1a; 一、CSS代码 .timeline {padding-left: 5px} .timeline-item { position: relative;padding-bottom: 20px;} .timeline-axis {position: absolute;left: -5px;top: 0;z-index: 10;width: 20px;height: 20px;line-he…

火爆全网!用 Pyecharts 就能做出来“迁徙图“和“轮播图“

1.pyecharts知识点回顾 1&#xff09;知识回顾 前面我们已经讲述了&#xff0c;如何使用pyecharts进行图形的绘制&#xff0c;一共涉及到如下四步。我们今天就是按照下面这几步来进行迁徙图和轮播图的绘制。 ① 选择图表类型&#xff1b; ② 声明图形类并添加数据&#xff1…