public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: ariel@vanguardiasur.com.ar (Ariel D'Alessandro)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/4] ARM: configs: lpc18xx: enable EEPROM NVMEM driver
Date: Mon, 16 Nov 2015 13:19:58 -0300	[thread overview]
Message-ID: <1447690798-14641-5-git-send-email-ariel@vanguardiasur.com.ar> (raw)
In-Reply-To: <1447690798-14641-1-git-send-email-ariel@vanguardiasur.com.ar>

Enable NVMEM driver for NXP LPC18xx EEPROM, which can be found in
NXP LPC185x/3x and LPC435x/3x/2x/1x devices.

Signed-off-by: Ariel D'Alessandro <ariel@vanguardiasur.com.ar>
---
 arch/arm/configs/lpc18xx_defconfig | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/arm/configs/lpc18xx_defconfig b/arch/arm/configs/lpc18xx_defconfig
index 03c155f..6d6d504 100644
--- a/arch/arm/configs/lpc18xx_defconfig
+++ b/arch/arm/configs/lpc18xx_defconfig
@@ -148,6 +148,8 @@ CONFIG_ARM_PL172_MPMC=y
 CONFIG_PWM=y
 CONFIG_PWM_LPC18XX_SCT=y
 CONFIG_PHY_LPC18XX_USB_OTG=y
+CONFIG_NVMEM=y
+CONFIG_NVMEM_LPC18XX_EEPROM=y
 CONFIG_EXT2_FS=y
 # CONFIG_FILE_LOCKING is not set
 # CONFIG_DNOTIFY is not set
-- 
2.6.2

  parent reply	other threads:[~2015-11-16 16:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16 16:19 [PATCH v3 0/4] Add support for NXP LPC18xx EEPROM using nvmem Ariel D'Alessandro
2015-11-16 16:19 ` [PATCH v3 1/4] DT: nvmem: Add NXP LPC18xx EEPROM memory binding documentation Ariel D'Alessandro
2015-11-17  0:11   ` Rob Herring
2015-11-16 16:19 ` [PATCH v3 2/4] nvmem: NXP LPC18xx EEPROM memory NVMEM driver Ariel D'Alessandro
2015-11-16 16:19 ` [PATCH v3 3/4] ARM: dts: lpc18xx: add EEPROM memory node Ariel D'Alessandro
2015-11-16 16:19 ` Ariel D'Alessandro [this message]
2015-11-16 17:11 ` [PATCH v3 0/4] Add support for NXP LPC18xx EEPROM using nvmem Ariel D'Alessandro

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=1447690798-14641-5-git-send-email-ariel@vanguardiasur.com.ar \
    --to=ariel@vanguardiasur.com.ar \
    --cc=linux-arm-kernel@lists.infradead.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