The request reset function is not really used for any useful purpose
except for debugging. We can safely remove it.

Signed-off-by: Dinh Nguyen <dingu...@kernel.org>
---
 drivers/reset/ast2500-reset.c | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/drivers/reset/ast2500-reset.c b/drivers/reset/ast2500-reset.c
index b2c89e1..65708cf 100644
--- a/drivers/reset/ast2500-reset.c
+++ b/drivers/reset/ast2500-reset.c
@@ -68,14 +68,6 @@ static int ast2500_reset_assert(struct reset_ctl *reset_ctl)
        return ret;
 }
 
-static int ast2500_reset_request(struct reset_ctl *reset_ctl)
-{
-       debug("%s(reset_ctl=%p) (dev=%p, id=%lu)\n", __func__, reset_ctl,
-             reset_ctl->dev, reset_ctl->id);
-
-       return 0;
-}
-
 static int ast2500_reset_probe(struct udevice *dev)
 {
        struct ast2500_reset_priv *priv = dev_get_priv(dev);
@@ -92,7 +84,6 @@ static const struct udevice_id ast2500_reset_ids[] = {
 
 struct reset_ops ast2500_reset_ops = {
        .rst_assert = ast2500_reset_assert,
-       .request = ast2500_reset_request,
 };
 
 U_BOOT_DRIVER(ast2500_reset) = {
-- 
2.7.4

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Reply via email to