From: Mukesh Ojha <quic_mojha@quicinc.com>
To: Komal Bajaj <quic_kbajaj@quicinc.com>, <agross@kernel.org>,
<andersson@kernel.org>, <konrad.dybcio@linaro.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <srinivas.kandagatla@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 3/6] nvmem: core: Add stub for nvmem_cell_read_u8
Date: Mon, 24 Jul 2023 18:06:15 +0530 [thread overview]
Message-ID: <3e193791-613f-b500-75a1-5f36cefe0ddc@quicinc.com> (raw)
In-Reply-To: <20230724084155.8682-4-quic_kbajaj@quicinc.com>
On 7/24/2023 2:11 PM, Komal Bajaj wrote:
> This change add the stub function for nvmem_cell_read_u8.
"Add the stub nvmem_cell_read_u8() function for drivers running with
CONFIG_NVMEM disabled"
-Mukesh
> This will be helpful when a driver uses this function and
-Mukesh
> CONFIG_NVMEM is not enabled.
>
> Signed-off-by: Komal Bajaj <quic_kbajaj@quicinc.com>
> ---
> include/linux/nvmem-consumer.h | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/include/linux/nvmem-consumer.h b/include/linux/nvmem-consumer.h
> index fa030d93b768..5c88635d4c2b 100644
> --- a/include/linux/nvmem-consumer.h
> +++ b/include/linux/nvmem-consumer.h
> @@ -125,6 +125,12 @@ static inline int nvmem_cell_write(struct nvmem_cell *cell,
> return -EOPNOTSUPP;
> }
>
> +static inline int nvmem_cell_read_u8(struct device *dev,
> + const char *cell_id, u8 *val)
> +{
> + return -EOPNOTSUPP;
> +}
> +
> static inline int nvmem_cell_read_u16(struct device *dev,
> const char *cell_id, u16 *val)
> {
next prev parent reply other threads:[~2023-07-24 12:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 8:41 [PATCH v5 0/6] soc: qcom: llcc: Add support for QDU1000/QRU1000 Komal Bajaj
2023-07-24 8:41 ` [PATCH v5 1/6] dt-bindings: cache: qcom,llcc: Add LLCC compatible " Komal Bajaj
2023-07-24 9:51 ` Krzysztof Kozlowski
2023-07-24 8:41 ` [PATCH v5 2/6] soc: qcom: llcc: Refactor llcc driver to support multiple configuration Komal Bajaj
2023-07-24 12:28 ` Mukesh Ojha
2023-07-24 13:26 ` Krzysztof Kozlowski
2023-07-24 16:14 ` Mukesh Ojha
2023-07-24 16:11 ` Mukesh Ojha
2023-08-02 8:53 ` Komal Bajaj
2023-07-24 8:41 ` [PATCH v5 3/6] nvmem: core: Add stub for nvmem_cell_read_u8 Komal Bajaj
2023-07-24 12:36 ` Mukesh Ojha [this message]
2023-08-02 8:53 ` Komal Bajaj
2023-07-24 8:41 ` [PATCH v5 4/6] soc: qcom: Add LLCC support for multi channel DDR Komal Bajaj
2023-07-24 12:40 ` Mukesh Ojha
2023-08-02 8:54 ` Komal Bajaj
2023-07-24 8:41 ` [PATCH v5 5/6] soc: qcom: llcc: Updating the macro name Komal Bajaj
2023-07-24 12:41 ` Mukesh Ojha
2023-07-24 12:48 ` Konrad Dybcio
2023-08-02 8:55 ` Komal Bajaj
2023-07-24 8:41 ` [PATCH v5 6/6] soc: qcom: llcc: Add QDU1000 and QRU1000 LLCC support Komal Bajaj
2023-07-24 12:45 ` Mukesh Ojha
2023-07-24 12:55 ` Konrad Dybcio
2023-08-02 9:00 ` Komal Bajaj
2023-08-02 8:57 ` Komal Bajaj
2023-07-24 12:54 ` Konrad Dybcio
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=3e193791-613f-b500-75a1-5f36cefe0ddc@quicinc.com \
--to=quic_mojha@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kbajaj@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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
all inboxes | Powered by JetHome®