linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhou Yanjie <zhouyanjie@zoho.com>
To: linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	robh+dt@kernel.org, paul.burton@mips.com, paulburton@kernel.org,
	jhogan@kernel.org, mripard@kernel.org, shawnguo@kernel.org,
	mark.rutland@arm.com, syq@debian.org, ralf@linux-mips.org,
	heiko@sntech.de, icenowy@aosc.io,
	laurent.pinchart@ideasonboard.com, krzk@kernel.org,
	geert+renesas@glider.be, paul@crapouillou.net,
	prasannatsmkumar@gmail.com, sernia.zhou@foxmail.com,
	zhenwenjin@gmail.com
Subject: [PATCH v5 10/10] MIPS: CU1000: Update defconfig for rtc.
Date: Thu, 28 Nov 2019 18:37:47 +0800	[thread overview]
Message-ID: <1574937467-101907-11-git-send-email-zhouyanjie@zoho.com> (raw)
In-Reply-To: <1574937467-101907-1-git-send-email-zhouyanjie@zoho.com>

Selected rtc support by default.

Signed-off-by: Zhou Yanjie <zhouyanjie@zoho.com>
---

Notes:
    v5:
    New patch.

 arch/mips/configs/cu1000-neo_defconfig | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/mips/configs/cu1000-neo_defconfig b/arch/mips/configs/cu1000-neo_defconfig
index 565e9a0..b48a1cb 100644
--- a/arch/mips/configs/cu1000-neo_defconfig
+++ b/arch/mips/configs/cu1000-neo_defconfig
@@ -63,6 +63,8 @@ CONFIG_GPIO_SYSFS=y
 # CONFIG_USB_SUPPORT is not set
 CONFIG_MMC=y
 CONFIG_MMC_JZ4740=y
+CONFIG_RTC_CLASS=y
+CONFIG_RTC_DRV_JZ4740=y
 CONFIG_DMADEVICES=y
 CONFIG_DMA_JZ4780=y
 # CONFIG_IOMMU_SUPPORT is not set
-- 
2.7.4



      parent reply	other threads:[~2019-11-28 10:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28 10:37 Add initial support for Ingenic X1000 SoC and Y&A CU Neo board v5 Zhou Yanjie
2019-11-28 10:37 ` [PATCH v5 01/10] MIPS: Ingenic: Initial X1000 support Zhou Yanjie
2019-11-28 10:37 ` [PATCH v5 02/10] dt-bindings: Document yna vendor-prefix Zhou Yanjie
2019-11-28 10:37 ` [PATCH v5 03/10] dt-bindings: MIPS: Add Ingenic XBurst based boards Zhou Yanjie
2019-11-28 10:37 ` [PATCH v5 04/10] MIPS: Ingenic: Initial YSH & ATIL CU Neo board support Zhou Yanjie
2019-11-28 10:37 ` [PATCH v5 05/10] MIPS: X1000: Add pdma controller DT node Zhou Yanjie
2019-11-28 10:37 ` [PATCH v5 06/10] MIPS: CU1000: Update defconfig for pdma controller Zhou Yanjie
2019-11-28 10:37 ` [PATCH v5 07/10] MIPS: X1000: Add msc controller DT node Zhou Yanjie
2019-11-28 10:37 ` [PATCH v5 08/10] MIPS: CU1000: Update defconfig for msc controller Zhou Yanjie
2019-11-28 10:37 ` [PATCH v5 09/10] MIPS: X1000: Add rtc DT node Zhou Yanjie
2019-11-28 10:37 ` Zhou Yanjie [this message]

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=1574937467-101907-11-git-send-email-zhouyanjie@zoho.com \
    --to=zhouyanjie@zoho.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=heiko@sntech.de \
    --cc=icenowy@aosc.io \
    --cc=jhogan@kernel.org \
    --cc=krzk@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mripard@kernel.org \
    --cc=paul.burton@mips.com \
    --cc=paul@crapouillou.net \
    --cc=paulburton@kernel.org \
    --cc=prasannatsmkumar@gmail.com \
    --cc=ralf@linux-mips.org \
    --cc=robh+dt@kernel.org \
    --cc=sernia.zhou@foxmail.com \
    --cc=shawnguo@kernel.org \
    --cc=syq@debian.org \
    --cc=zhenwenjin@gmail.com \
    --subject='Re: [PATCH v5 10/10] MIPS: CU1000: Update defconfig for rtc.' \
    /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

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).