Devicetree
 help / color / mirror / Atom feed
From: <ludovic.desroches@atmel.com>
To: linux-can@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	devicetree-discuss@lists.ozlabs.org
Cc: nicolas.ferre@atmel.com, plagnioj@jcrosoft.com,
	mkl@pengutronix.de,
	Ludovic Desroches <ludovic.desroches@atmel.com>
Subject: [PATCH v2 2/2] can: Kconfig: CAN_AT91 depends on ARM
Date: Mon, 11 Mar 2013 18:26:04 +0100	[thread overview]
Message-ID: <1363022764-7647-2-git-send-email-ludovic.desroches@atmel.com> (raw)
In-Reply-To: <1363022764-7647-1-git-send-email-ludovic.desroches@atmel.com>

From: Ludovic Desroches <ludovic.desroches@atmel.com>

SAMA5D3 devices also embed CAN feature. Moreover if we want to produce a single
kernel image it is not useful to be too restrictive.

Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
---
Changes in v2:
- depends on ARM instead of ARCH_AT91 (compilation tested with
exynos4_defconfig and imx_v6_v7_defconfig)

 driver/net/can/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/can/Kconfig b/drivers/net/can/Kconfig
index 9862b2e..e456b70 100644
--- a/drivers/net/can/Kconfig
+++ b/drivers/net/can/Kconfig
@@ -65,7 +65,7 @@ config CAN_LEDS
 
 config CAN_AT91
 	tristate "Atmel AT91 onchip CAN controller"
-	depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9X5
+	depends on ARM
 	---help---
 	  This is a driver for the SoC CAN controller in Atmel's AT91SAM9263
 	  and AT91SAM9X5 processors.
-- 
1.7.11.3


  reply	other threads:[~2013-03-11 17:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 17:26 [PATCH v2 1/2] can: at91_can: add dt support ludovic.desroches
2013-03-11 17:26 ` ludovic.desroches [this message]
2013-03-11 17:32 ` Marc Kleine-Budde
     [not found]   ` <513E1523.4010803-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-03-12  7:45     ` Ludovic Desroches
2013-03-12  7:45   ` Ludovic Desroches

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=1363022764-7647-2-git-send-email-ludovic.desroches@atmel.com \
    --to=ludovic.desroches@atmel.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=nicolas.ferre@atmel.com \
    --cc=plagnioj@jcrosoft.com \
    /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