From: "Huang, Tao" <huangtao@rock-chips.com>
To: Mark Brown <broonie@kernel.org>
Cc: Huibin Hong <huibin.hong@rock-chips.com>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
"shawn.lin" <shawn.lin@kernel-upstream.org>,
linux-rockchip@lists.infradead.org,
Addy Ke <addy.ke@rockchip.com>
Subject: Re: [PATCH] spi/rockchip: Make sure spi clk is on in rockchip_spi_set_cs
Date: Wed, 24 Feb 2016 19:09:57 +0800 [thread overview]
Message-ID: <56CD8F85.2090204@rock-chips.com> (raw)
In-Reply-To: <1456308004-29102-1-git-send-email-huibin.hong@rock-chips.com>
Hi, Mark:
Another way to solve this bug is add runtime PM support while spi setup.
Some other chips may have some problem, for example mt65xx and orion,
which access hardware register too.
On 2016年02月24日 18:00, Huibin Hong wrote:
> Rockchip_spi_set_cs could be called by spi_setup, but
> spi_setup may be called by device driver after runtime suspend.
> Then the spi clock is closed, rockchip_spi_set_cs may access the
> spi registers, which causes cpu block in some socs.
>
> Fixes: 64e36824b32 ("spi/rockchip: add driver for Rockchip RK3xxx")
> Cc: Addy Ke <addy.ke@rockchip.com>
> Cc: shawn.lin <shawn.lin@kernel-upstream.org>
> Signed-off-by: Huibin Hong <huibin.hong@rock-chips.com>
> ---
>
> drivers/spi/spi-rockchip.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/spi/spi-rockchip.c b/drivers/spi/spi-rockchip.c
> index 79a8bc4..035767c 100644
> --- a/drivers/spi/spi-rockchip.c
> +++ b/drivers/spi/spi-rockchip.c
> @@ -265,7 +265,10 @@ static inline u32 rx_max(struct rockchip_spi *rs)
> static void rockchip_spi_set_cs(struct spi_device *spi, bool enable)
> {
> u32 ser;
> - struct rockchip_spi *rs = spi_master_get_devdata(spi->master);
> + struct spi_master *master = spi->master;
> + struct rockchip_spi *rs = spi_master_get_devdata(master);
> +
> + pm_runtime_get_sync(rs->dev);
>
> ser = readl_relaxed(rs->regs + ROCKCHIP_SPI_SER) & SER_MASK;
>
> @@ -290,6 +293,8 @@ static void rockchip_spi_set_cs(struct spi_device *spi, bool enable)
> ser &= ~(1 << spi->chip_select);
>
> writel_relaxed(ser, rs->regs + ROCKCHIP_SPI_SER);
> +
> + pm_runtime_put_sync(rs->dev);
> }
>
> static int rockchip_spi_prepare_message(struct spi_master *master,
> --
> 1.9.1
>
>
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
>
>
>
next prev parent reply other threads:[~2016-02-24 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 10:00 [PATCH] spi/rockchip: Make sure spi clk is on in rockchip_spi_set_cs Huibin Hong
2016-02-24 11:09 ` Huang, Tao [this message]
[not found] ` <56CD8F85.2090204-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-02-26 1:58 ` Mark Brown
[not found] ` <20160226015829.GC18327-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-02-26 2:31 ` Huang, Tao
[not found] ` <56CFB916.5010403-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-03-05 4:45 ` Mark Brown
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=56CD8F85.2090204@rock-chips.com \
--to=huangtao@rock-chips.com \
--cc=addy.ke@rockchip.com \
--cc=broonie@kernel.org \
--cc=huibin.hong@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=shawn.lin@kernel-upstream.org \
/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;
as well as URLs for NNTP newsgroup(s).