[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1415004100.3060.1.camel@pengutronix.de>
Date: Mon, 03 Nov 2014 09:41:40 +0100
From: Philipp Zabel <p.zabel@...gutronix.de>
To: dinguyen@...nsource.altera.com
Cc: dinh.linux@...il.com, s.trumtrar@...gutronix.de,
atull@...nsource.altera.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] reset: add socfpga_reset_status
Hi Dinh,
Am Freitag, den 24.10.2014, 10:53 -0500 schrieb
dinguyen@...nsource.altera.com:
> From: Dinh Nguyen <dinguyen@...nsource.altera.com>
>
> Populate the reset_status callback for SOCFPGA.
>
> Signed-off-by: Alan Tull <atull@...nsource.altera.com>
> Signed-off-by: Dinh Nguyen <dinguyen@...nsource.altera.com>
> ---
> drivers/reset/reset-socfpga.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/drivers/reset/reset-socfpga.c b/drivers/reset/reset-socfpga.c
> index 79c32ca..cd37849 100644
> --- a/drivers/reset/reset-socfpga.c
> +++ b/drivers/reset/reset-socfpga.c
> @@ -76,9 +76,27 @@ static int socfpga_reset_deassert(struct reset_controller_dev *rcdev,
> return 0;
> }
>
> +static int socfpga_reset_status(struct reset_controller_dev *rcdev,
> + unsigned long id)
> +{
> + struct socfpga_reset_data *data = container_of(rcdev,
> + struct socfpga_reset_data, rcdev);
> + int bank = id / BITS_PER_LONG;
> + int offset = id % BITS_PER_LONG;
> + unsigned long flags;
> + u32 reg;
> +
> + spin_lock_irqsave(&data->lock, flags);
> + reg = readl(data->membase + OFFSET_MODRST + (bank * NR_BANKS));
> + spin_unlock_irqrestore(&data->lock, flags);
For the register read access, you don't need the lock.
> + return !(reg & BIT(offset));
> +}
> +
> static struct reset_control_ops socfpga_reset_ops = {
> .assert = socfpga_reset_assert,
> .deassert = socfpga_reset_deassert,
> + .status = socfpga_reset_status,
> };
>
> static int socfpga_reset_probe(struct platform_device *pdev)
regards
Philipp
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists