From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v6 2/2] nvmem: Add Vybrid OCOTP and OCROM support
Date: Wed, 24 Jun 2015 10:37:43 +0100 [thread overview]
Message-ID: <558A7A67.806@linaro.org> (raw)
In-Reply-To: <20150624051903.GA11753@Sanchayan-Arch.toradex.int>
On 24/06/15 06:19, maitysanchayan at gmail.com wrote:
> I just tested it without the "select REGMAP_MMIO" and it works just fine.
You just got lucky in this case, as REGMAP_MMIO is getting selected
somewhere else.
Drivers should directly select the dependecies. In this case this driver
actually is going to use REGMAP_MMIO, so keeping it selected is the
right thing.
--srini
WARNING: multiple messages have this Message-ID (diff)
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: maitysanchayan@gmail.com, Stefan Wahren <stefan.wahren@i2se.com>
Cc: maxime.ripard@free-electrons.com,
linux-arm-kernel@lists.infradead.org, stefan@agner.ch,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
shawn.guo@linaro.org, arnd@arndb.de
Subject: Re: [RFC PATCH v6 2/2] nvmem: Add Vybrid OCOTP and OCROM support
Date: Wed, 24 Jun 2015 10:37:43 +0100 [thread overview]
Message-ID: <558A7A67.806@linaro.org> (raw)
In-Reply-To: <20150624051903.GA11753@Sanchayan-Arch.toradex.int>
On 24/06/15 06:19, maitysanchayan@gmail.com wrote:
> I just tested it without the "select REGMAP_MMIO" and it works just fine.
You just got lucky in this case, as REGMAP_MMIO is getting selected
somewhere else.
Drivers should directly select the dependecies. In this case this driver
actually is going to use REGMAP_MMIO, so keeping it selected is the
right thing.
--srini
next prev parent reply other threads:[~2015-06-24 9:37 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 13:44 [RFC PATCH v6 0/2] Implement NVMEM/SoC bus support for Vybrid Sanchayan Maity
2015-06-23 13:44 ` Sanchayan Maity
2015-06-23 13:44 ` [RFC PATCH v6 1/2] ARM: dts: vfxxx: Add OCOTP and OCROM nodes Sanchayan Maity
2015-06-23 13:44 ` Sanchayan Maity
2015-06-23 13:44 ` [RFC PATCH v6 2/2] nvmem: Add Vybrid OCOTP and OCROM support Sanchayan Maity
2015-06-23 13:44 ` Sanchayan Maity
2015-06-23 19:03 ` Srinivas Kandagatla
2015-06-23 19:03 ` Srinivas Kandagatla
2015-06-24 5:25 ` maitysanchayan at gmail.com
2015-06-24 5:25 ` maitysanchayan
2015-06-23 19:31 ` Stefan Wahren
2015-06-23 19:31 ` Stefan Wahren
2015-06-24 5:19 ` maitysanchayan at gmail.com
2015-06-24 5:19 ` maitysanchayan
2015-06-24 9:37 ` Srinivas Kandagatla [this message]
2015-06-24 9:37 ` Srinivas Kandagatla
2015-06-24 9:44 ` Sanchayan Maity
2015-06-24 9:44 ` Sanchayan Maity
2015-06-24 9:56 ` Stefan Wahren
2015-06-24 9:56 ` Stefan Wahren
2015-06-24 10:45 ` maitysanchayan at gmail.com
2015-06-24 10:45 ` maitysanchayan
2015-06-24 11:52 ` Stefan Wahren
2015-06-24 11:52 ` Stefan Wahren
2015-06-24 12:05 ` maitysanchayan at gmail.com
2015-06-24 12:05 ` maitysanchayan
2015-06-29 11:22 ` [RFC PATCH v6 0/3] Implement NVMEM/SoC bus support for Vybrid Sanchayan Maity
2015-06-29 11:22 ` Sanchayan Maity
2015-06-29 11:22 ` [RFC PATCH v6 1/3] clk: clk-vf610: Add clock for Vybrid OCOTP controller Sanchayan Maity
2015-06-29 11:22 ` Sanchayan Maity
2015-06-29 11:22 ` [RFC PATCH v6 2/3] ARM: dts: vfxxx: Add OCOTP node Sanchayan Maity
2015-06-29 11:22 ` Sanchayan Maity
2015-06-29 11:22 ` [RFC PATCH v6 3/3] drivers: nvmem: Add Vybrid OCOTP support Sanchayan Maity
2015-06-29 11:22 ` Sanchayan Maity
2015-07-06 10:16 ` Stefan Wahren
2015-07-06 10:16 ` Stefan Wahren
2015-07-07 5:19 ` maitysanchayan at gmail.com
2015-07-07 5:19 ` maitysanchayan
2015-07-07 12:49 ` Stefan Wahren
2015-07-07 12:49 ` Stefan Wahren
2015-07-08 5:39 ` maitysanchayan at gmail.com
2015-07-08 5:39 ` maitysanchayan
2015-07-08 20:55 ` Stefan Wahren
2015-07-08 20:55 ` Stefan Wahren
2015-07-10 18:09 ` maitysanchayan at gmail.com
2015-07-10 18:09 ` maitysanchayan
2015-06-24 11:20 ` [RFC PATCH v6 2/2] nvmem: Add Vybrid OCOTP and OCROM support Stefan Agner
2015-06-24 11:20 ` Stefan Agner
2015-06-24 8:35 ` Maxime Ripard
2015-06-24 8:35 ` Maxime Ripard
2015-06-24 9:34 ` Srinivas Kandagatla
2015-06-24 9:34 ` Srinivas Kandagatla
2015-06-25 17:49 ` Maxime Ripard
2015-06-25 17:49 ` Maxime Ripard
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=558A7A67.806@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.