From: Laxman Dewangan <ldewangan@nvidia.com>
To: <thierry.reding@gmail.com>, <swarren@wwwdotorg.org>
Cc: <gnurou@gmail.com>, <jonathanh@nvidia.com>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH V2 1/4] soc/tegra: pmc: Remove legacy Tegra I/O rail API
Date: Wed, 9 Nov 2016 18:39:19 +0530 [thread overview]
Message-ID: <1478696962-11831-2-git-send-email-ldewangan@nvidia.com> (raw)
In-Reply-To: <1478696962-11831-1-git-send-email-ldewangan@nvidia.com>
Remove tegra_io_rail_power_on() and tegra_io_rail_power_off()
from header as client has been moved to new APIs.
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
---
Changes from V1:
None
---
include/soc/tegra/pmc.h | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/include/soc/tegra/pmc.h b/include/soc/tegra/pmc.h
index 52780a77..9c314a6 100644
--- a/include/soc/tegra/pmc.h
+++ b/include/soc/tegra/pmc.h
@@ -203,16 +203,6 @@ static inline int tegra_io_pad_get_voltage(enum tegra_io_pad id)
{
return -ENOSYS;
}
-
-static inline int tegra_io_rail_power_on(unsigned int id)
-{
- return -ENOSYS;
-}
-
-static inline int tegra_io_rail_power_off(unsigned int id)
-{
- return -ENOSYS;
-}
#endif /* CONFIG_ARCH_TEGRA */
#endif /* __SOC_TEGRA_PMC_H__ */
--
2.1.4
next prev parent reply other threads:[~2016-11-09 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 13:09 [PATCH V2 0/4] soc/tegra: pmc: Add support for IO pad configuration and sub-driver Laxman Dewangan
2016-11-09 13:09 ` Laxman Dewangan [this message]
2016-11-09 13:09 ` [PATCH V2 2/4] soc/tegra: pmc: Add interface to get IO pad power status Laxman Dewangan
2016-11-09 13:09 ` [PATCH V2 3/4] soc/tegra: pmc: Register PMC child devices as platform device Laxman Dewangan
2016-11-09 13:09 ` [PATCH V2 4/4] soc/tegra: pmc: Make configuration of IO pads in atomic context Laxman Dewangan
2016-11-22 11:32 ` [PATCH V2 0/4] soc/tegra: pmc: Add support for IO pad configuration and sub-driver Laxman Dewangan
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=1478696962-11831-2-git-send-email-ldewangan@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=gnurou@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
/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®