linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Claudiu Beznea <claudiu.beznea@microchip.com>
To: <linux@armlinux.org.uk>, <nicolas.ferre@microchip.com>,
	<alexandre.belloni@bootlin.com>,
	<ludovic.desroches@microchip.com>, <sre@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>,
	Claudiu Beznea <claudiu.beznea@microchip.com>
Subject: [PATCH v3 7/9] ARM: debug-ll: select DEBUG_AT91_RM9200_DBGU for sam9x60
Date: Fri, 29 Nov 2019 15:51:43 +0200	[thread overview]
Message-ID: <1575035505-6310-8-git-send-email-claudiu.beznea@microchip.com> (raw)
In-Reply-To: <1575035505-6310-1-git-send-email-claudiu.beznea@microchip.com>

Select DEBUG_AT91_RM9200_DBGU for SAM9X60 SoC.

Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
---
 arch/arm/Kconfig.debug | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
index 8bcbd0cd739b..b70d7debf5ca 100644
--- a/arch/arm/Kconfig.debug
+++ b/arch/arm/Kconfig.debug
@@ -147,14 +147,14 @@ choice
 		    0x80024000      | 0xf0024000     | UART9
 
 	config DEBUG_AT91_RM9200_DBGU
-		bool "Kernel low-level debugging on AT91RM9200, AT91SAM9 DBGU"
+		bool "Kernel low-level debugging on AT91RM9200, AT91SAM9, SAM9X60 DBGU"
 		select DEBUG_AT91_UART
-		depends on SOC_AT91RM9200 || SOC_AT91SAM9
+		depends on SOC_AT91RM9200 || SOC_AT91SAM9 || SOC_SAM9X60
 		help
 		  Say Y here if you want kernel low-level debugging support
 		  on the DBGU port of:
 		    at91rm9200, at91sam9260, at91sam9g20, at91sam9261,
-		    at91sam9g10, at91sam9n12, at91sam9rl64, at91sam9x5
+		    at91sam9g10, at91sam9n12, at91sam9rl64, at91sam9x5, sam9x60
 
 	config DEBUG_AT91_SAM9263_DBGU
 		bool "Kernel low-level debugging on AT91SAM{9263,9G45,A5D3} DBGU"
-- 
2.7.4


  parent reply	other threads:[~2019-11-29 13:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 13:51 [PATCH v3 0/9] SoC and defconfig support for SAM9X60 Claudiu Beznea
2019-11-29 13:51 ` [PATCH v3 1/9] ARM: at91: Kconfig: add sam9x60 pll config flag Claudiu Beznea
2019-11-29 13:51 ` [PATCH v3 2/9] ARM: at91: Kconfig: add config flag for SAM9X60 SoC Claudiu Beznea
2019-11-29 13:51 ` [PATCH v3 3/9] ARM: at91: pm: move SAM9X60's PM under its own SoC config flag Claudiu Beznea
2019-11-29 13:51 ` [PATCH v3 4/9] drivers: soc: atmel: move sam9x60 under its own " Claudiu Beznea
2019-11-29 13:51 ` [PATCH v3 5/9] power: reset: Kconfig: select POWER_RESET_AT91_RESET for sam9x60 Claudiu Beznea
2019-11-29 13:51 ` [PATCH v3 6/9] drivers: soc: atmel: select POWER_RESET_AT91_SAMA5D2_SHDWC " Claudiu Beznea
2019-11-29 13:51 ` Claudiu Beznea [this message]
2019-11-29 13:51 ` [PATCH v3 8/9] ARM: at91/defconfig: use savedefconfig Claudiu Beznea
2019-11-29 13:51 ` [PATCH v3 9/9] ARM: at91/defconfig: enable config flags for sam9x60 SoC Claudiu Beznea
2019-12-09 23:45 ` [PATCH v3 0/9] SoC and defconfig support for SAM9X60 Alexandre Belloni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1575035505-6310-8-git-send-email-claudiu.beznea@microchip.com \
    --to=claudiu.beznea@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=ludovic.desroches@microchip.com \
    --cc=nicolas.ferre@microchip.com \
    --cc=sre@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).