From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Hemant Kumar <hemantk@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
jhugo@codeaurora.org, bbhatt@codeaurora.org
Subject: Re: [PATCH v1] bus: mhi: core: Add const qualifier to MHI config information
Date: Tue, 15 Sep 2020 13:50:36 +0530 [thread overview]
Message-ID: <20200915082036.GC12395@mani> (raw)
In-Reply-To: <010101747c3a6fdd-33efa632-e20c-476d-9e39-01cb1f2d1cea-000000@us-west-2.amazonses.com>
On Fri, Sep 11, 2020 at 08:13:58AM +0000, Hemant Kumar wrote:
> MHI channel, event and controller config data needs to be
> treated read only information. Add const qualifier to make
> sure config information passed by MHI controller is not
> modified by MHI core driver.
>
> Suggested-by: Kalle Valo <kvalo@codeaurora.org>
> Signed-off-by: Hemant Kumar <hemantk@codeaurora.org>
Applied to mhi-next!
Thanks,
Mani
> ---
> drivers/bus/mhi/core/init.c | 12 ++++++------
> include/linux/mhi.h | 6 +++---
> 2 files changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/bus/mhi/core/init.c b/drivers/bus/mhi/core/init.c
> index f69a2f3..d232938 100644
> --- a/drivers/bus/mhi/core/init.c
> +++ b/drivers/bus/mhi/core/init.c
> @@ -562,10 +562,10 @@ int mhi_init_chan_ctxt(struct mhi_controller *mhi_cntrl,
> }
>
> static int parse_ev_cfg(struct mhi_controller *mhi_cntrl,
> - struct mhi_controller_config *config)
> + const struct mhi_controller_config *config)
> {
> struct mhi_event *mhi_event;
> - struct mhi_event_config *event_cfg;
> + const struct mhi_event_config *event_cfg;
> struct device *dev = &mhi_cntrl->mhi_dev->dev;
> int i, num;
>
> @@ -648,9 +648,9 @@ static int parse_ev_cfg(struct mhi_controller *mhi_cntrl,
> }
>
> static int parse_ch_cfg(struct mhi_controller *mhi_cntrl,
> - struct mhi_controller_config *config)
> + const struct mhi_controller_config *config)
> {
> - struct mhi_channel_config *ch_cfg;
> + const struct mhi_channel_config *ch_cfg;
> struct device *dev = &mhi_cntrl->mhi_dev->dev;
> int i;
> u32 chan;
> @@ -766,7 +766,7 @@ static int parse_ch_cfg(struct mhi_controller *mhi_cntrl,
> }
>
> static int parse_config(struct mhi_controller *mhi_cntrl,
> - struct mhi_controller_config *config)
> + const struct mhi_controller_config *config)
> {
> int ret;
>
> @@ -803,7 +803,7 @@ static int parse_config(struct mhi_controller *mhi_cntrl,
> }
>
> int mhi_register_controller(struct mhi_controller *mhi_cntrl,
> - struct mhi_controller_config *config)
> + const struct mhi_controller_config *config)
> {
> struct mhi_event *mhi_event;
> struct mhi_chan *mhi_chan;
> diff --git a/include/linux/mhi.h b/include/linux/mhi.h
> index 6b987e8..b2c0214 100644
> --- a/include/linux/mhi.h
> +++ b/include/linux/mhi.h
> @@ -280,9 +280,9 @@ struct mhi_controller_config {
> u32 timeout_ms;
> u32 buf_len;
> u32 num_channels;
> - struct mhi_channel_config *ch_cfg;
> + const struct mhi_channel_config *ch_cfg;
> u32 num_events;
> - struct mhi_event_config *event_cfg;
> + const struct mhi_event_config *event_cfg;
> bool use_bounce_buf;
> bool m2_no_db;
> };
> @@ -545,7 +545,7 @@ struct mhi_driver {
> * @config: Configuration to use for the controller
> */
> int mhi_register_controller(struct mhi_controller *mhi_cntrl,
> - struct mhi_controller_config *config);
> + const struct mhi_controller_config *config);
>
> /**
> * mhi_unregister_controller - Unregister MHI controller
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
>
prev parent reply other threads:[~2020-09-15 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1599812017-32680-1-git-send-email-hemantk@codeaurora.org>
2020-09-11 8:13 ` [PATCH v1] bus: mhi: core: Add const qualifier to MHI config information Hemant Kumar
2020-09-15 8:19 ` Manivannan Sadhasivam
2020-09-15 8:20 ` Manivannan Sadhasivam [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=20200915082036.GC12395@mani \
--to=manivannan.sadhasivam@linaro.org \
--cc=bbhatt@codeaurora.org \
--cc=hemantk@codeaurora.org \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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