Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758610Ab3IBOPx (ORCPT ); Mon, 2 Sep 2013 10:15:53 -0400 Received: from bear.ext.ti.com ([192.94.94.41]:43882 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758350Ab3IBOPv (ORCPT ); Mon, 2 Sep 2013 10:15:51 -0400 From: Afzal Mohammed To: , , CC: Stephen Warren , Pavel Machek , Philipp Zabel , Dan Carpenter , Shawn Guo Subject: [PATCH RFC 1/6] reset: is_reset and clear_reset api's Date: Mon, 2 Sep 2013 19:45:14 +0530 Message-ID: <5dcf227d360f748ddc965f6c13ff0b31c3e90dab.1378129416.git.afzal@ti.com> X-Mailer: git-send-email 1.8.3.4 In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3395 Lines: 94 Enhance reset framework with "is_reset" and "clear_reset" api's. is_reset - used by client driver to know reset status clear_reset - used by client driver to clear reset status These functionalities may sometimes be achieved by using existing api like deassert. But in some scenarios, steps to achieve reset requires clearing reset, deassert reset, enabling clock to module and then checking reset status. Here enabling clock module is coming in between reset procedure, hence enhance framework with additional api's. Signed-off-by: Afzal Mohammed --- drivers/reset/core.c | 32 ++++++++++++++++++++++++++++++++ include/linux/reset-controller.h | 2 ++ include/linux/reset.h | 2 ++ 3 files changed, 36 insertions(+) diff --git a/drivers/reset/core.c b/drivers/reset/core.c index d1b6089..ba12171 100644 --- a/drivers/reset/core.c +++ b/drivers/reset/core.c @@ -127,6 +127,38 @@ int reset_control_deassert(struct reset_control *rstc) EXPORT_SYMBOL_GPL(reset_control_deassert); /** + * reset_control_is_reset - check reset status + * @rstc: reset controller + * + * Returns a boolean or negative error code + * + */ +int reset_control_is_reset(struct reset_control *rstc) +{ + if (rstc->rcdev->ops->is_reset) + return rstc->rcdev->ops->is_reset(rstc->rcdev, rstc->id); + + return -ENOSYS; +} +EXPORT_SYMBOL_GPL(reset_control_is_reset); + +/** + * reset_control_clear_reset - clear the reset + * @rstc: reset controller + * + * Returns zero on success or negative error code + * + */ +int reset_control_clear_reset(struct reset_control *rstc) +{ + if (rstc->rcdev->ops->clear_reset) + return rstc->rcdev->ops->clear_reset(rstc->rcdev, rstc->id); + + return -ENOSYS; +} +EXPORT_SYMBOL_GPL(reset_control_clear_reset); + +/** * reset_control_get - Lookup and obtain a reference to a reset controller. * @dev: device to be reset by the controller * @id: reset line name diff --git a/include/linux/reset-controller.h b/include/linux/reset-controller.h index 2f61311..c9bbadb 100644 --- a/include/linux/reset-controller.h +++ b/include/linux/reset-controller.h @@ -17,6 +17,8 @@ struct reset_control_ops { int (*reset)(struct reset_controller_dev *rcdev, unsigned long id); int (*assert)(struct reset_controller_dev *rcdev, unsigned long id); int (*deassert)(struct reset_controller_dev *rcdev, unsigned long id); + int (*is_reset)(struct reset_controller_dev *rcdev, unsigned long id); + int (*clear_reset)(struct reset_controller_dev *rcdev, unsigned long i); }; struct module; diff --git a/include/linux/reset.h b/include/linux/reset.h index 6082247..da59f9f 100644 --- a/include/linux/reset.h +++ b/include/linux/reset.h @@ -7,6 +7,8 @@ struct reset_control; int reset_control_reset(struct reset_control *rstc); int reset_control_assert(struct reset_control *rstc); int reset_control_deassert(struct reset_control *rstc); +int reset_control_is_reset(struct reset_control *rstc); +int reset_control_clear_reset(struct reset_control *rstc); struct reset_control *reset_control_get(struct device *dev, const char *id); void reset_control_put(struct reset_control *rstc); -- 1.8.3.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/