[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230401165723.19762-1-quic_sartgarg@quicinc.com>
Date: Sat, 1 Apr 2023 22:27:21 +0530
From: Sarthak Garg <quic_sartgarg@...cinc.com>
To: adrian.hunter@...el.com, ulf.hansson@...aro.org
Cc: linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, quic_rampraka@...cinc.com,
quic_bhaskarv@...cinc.com, quic_sachgupt@...cinc.com,
quic_pragalla@...cinc.com, quic_sayalil@...cinc.com,
Sarthak Garg <quic_sartgarg@...cinc.com>
Subject: [PATCH V1 0/2] Introduce new vendor op and export few symbols
For our earlier discussions on clock scaling and partial init features
we have come up with a new design where we have moved the entire logic
for both the features in our vendor related files.
But to support this new design we need a vendor op in
_mmc_suspend/_mmc_resume functions to control our feature functionality
in suspend/resume paths.
Moreover export of few symbols is also needed to make core layer
functions accessible to our vendor module.
Old discussion for Clock scaling feature :
https://patchwork.kernel.org/project/linux-mmc/cover/1571668177-3766-1-git-send-email-rampraka@codeaurora.org/
Old discussion for Partial init feature :
https://patchwork.kernel.org/project/linux-mmc/patch/1650963852-4173-1-git-send-email-quic_spathi@quicinc.com/
Hence introduce new vendor op in suspend/resume and export few symbols
nedeed for our feature.
Sarthak Garg (2):
mmc: core: Define new vendor ops to enable internal features
mmc: core: Export core functions to let vendors use for their features
drivers/mmc/core/core.c | 6 ++++++
drivers/mmc/core/host.c | 1 +
drivers/mmc/core/mmc.c | 31 ++++++++++++++++++++++---------
drivers/mmc/core/mmc_ops.c | 1 +
drivers/mmc/core/queue.c | 1 +
include/linux/mmc/host.h | 4 ++++
6 files changed, 35 insertions(+), 9 deletions(-)
--
2.17.1
Powered by blists - more mailing lists