From: Roland Stigge <stigge@antcom.de>
To: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
thierry.reding@avionic-design.de, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org, dmitry.torokhov@gmail.com,
axel.lin@gmail.com, broonie@opensource.wolfsonmicro.com,
marek.vasut@gmail.com, devel@driverdev.osuosl.org,
kevin.wells@nxp.com, srinivas.bakki@nxp.com,
dan.carpenter@oracle.com
Cc: Roland Stigge <stigge@antcom.de>
Subject: [PATCH v3 5/10] ARM: LPC32xx: Remove obsolete platform Kconfig
Date: Wed, 18 Apr 2012 15:36:10 +0200 [thread overview]
Message-ID: <1334756176-25144-6-git-send-email-stigge@antcom.de> (raw)
In-Reply-To: <1334756176-25144-1-git-send-email-stigge@antcom.de>
This patch removes two Kconfig options now unused (the network driver is
configured via DT now).
Signed-off-by: Roland Stigge <stigge@antcom.de>
---
Applies to v3.4-rc3
--- linux-2.6.orig/arch/arm/mach-lpc32xx/Kconfig
+++ linux-2.6/arch/arm/mach-lpc32xx/Kconfig
@@ -29,30 +29,4 @@ config ARCH_LPC32XX_UART6_SELECT
endmenu
-menu "LPC32XX chip components"
-
-config ARCH_LPC32XX_IRAM_FOR_NET
- bool "Use IRAM for network buffers"
- default y
- help
- Say Y here to use the LPC internal fast IRAM (i.e. 256KB SRAM) as
- network buffer. If the total combined required buffer sizes is
- larger than the size of IRAM, then SDRAM will be used instead.
-
- This can be enabled safely if the IRAM is not intended for other
- uses.
-
-config ARCH_LPC32XX_MII_SUPPORT
- bool "Check to enable MII support or leave disabled for RMII support"
- help
- Say Y here to enable MII support, or N for RMII support. Regardless of
- which support is selected, the ethernet interface driver needs to be
- selected in the device driver networking section.
-
- The PHY3250 reference board uses RMII, so users of this board should
- say N.
-
-endmenu
-
endif
-
next prev parent reply other threads:[~2012-04-18 13:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 13:36 [PATCH v3 0/10] Second patchset for LPC32xx device tree conversion Roland Stigge
2012-04-18 13:36 ` [PATCH v3 1/10] ohci-nxp: Driver cleanup Roland Stigge
2012-04-18 13:36 ` [PATCH v3 2/10] ohci-nxp: Device tree support Roland Stigge
2012-04-18 13:36 ` [PATCH v3 3/10] ARM: LPC32xx: clock.c cleanup Roland Stigge
2012-04-18 13:36 ` [PATCH v3 4/10] ARM: LPC32xx: clock.c dma adjustment Roland Stigge
2012-04-18 13:36 ` Roland Stigge [this message]
2012-04-18 13:36 ` [PATCH v3 6/10] input: Device tree support for LPC32xx touchscreen Roland Stigge
2012-04-18 13:36 ` [PATCH v3 7/10] iio: lpc32xx-adc: Remove driver conflict due to device tree Roland Stigge
2012-04-18 22:02 ` Greg KH
2012-04-18 13:36 ` [PATCH v3 8/10] ARM: LPC32xx: DTS files for device tree conversion Roland Stigge
2012-04-18 13:36 ` [PATCH v3 9/10] ARM: LPC32xx: Device tree support Roland Stigge
2012-04-18 13:36 ` [PATCH v3 10/10] ARM: LPC32xx: Move common code to common.c Roland Stigge
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=1334756176-25144-6-git-send-email-stigge@antcom.de \
--to=stigge@antcom.de \
--cc=arm@kernel.org \
--cc=axel.lin@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kevin.wells@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=srinivas.bakki@nxp.com \
--cc=thierry.reding@avionic-design.de \
/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).