linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: Mark Brown <broonie@linaro.org>,
	linux-spi@vger.kernel.org, linux-sh@vger.kernel.org,
	Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH] spi: sh-hspi: Do not specifically request shyway_clk clock
Date: Thu, 13 Mar 2014 11:10:25 +0100	[thread overview]
Message-ID: <2144304.qo37EGpAOW@avalon> (raw)
In-Reply-To: <1394699450-31286-1-git-send-email-horms+renesas@verge.net.au>

Hi Simon,

Thank you for the patch.

On Thursday 13 March 2014 17:30:50 Simon Horman wrote:
> Rather than requesting the shyway_clk call clk_get with
> the device and a NULL con_id.
> 
> This is in keeping with the way that clk_get() is called
> on other drivers used by Renesas Gen 1 SoCs. And I believe
> it is compatible with supplying clocks via DT, unlike the current code.
> 
> It appears to me that the two uses of this driver are
> the r8a7778 and r8a7779 SoCs. Both of which have already clocks setup
> to allow this driver to continue to work with this change applied.

If I'm not mistaken the hspi clocks on r8a7778 are children of clkp, while the 
shyway clock is a alias to clks. The only r8a7778 documentation I have access 
to is in Japanese so I'm not 100% sure, but I believe the MSTP007 parent clock 
should be clks.

The problem is not present in our r8a7779 code, the MSTP007 parent is clks 
there.

> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> ---
>  drivers/spi/spi-sh-hspi.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/spi/spi-sh-hspi.c b/drivers/spi/spi-sh-hspi.c
> index 82d2f92..e975892 100644
> --- a/drivers/spi/spi-sh-hspi.c
> +++ b/drivers/spi/spi-sh-hspi.c
> @@ -274,9 +274,9 @@ static int hspi_probe(struct platform_device *pdev)
>  		return -ENOMEM;
>  	}
> 
> -	clk = clk_get(NULL, "shyway_clk");
> +	clk = clk_get(&pdev->dev, NULL);
>  	if (IS_ERR(clk)) {
> -		dev_err(&pdev->dev, "shyway_clk is required\n");
> +		dev_err(&pdev->dev, "couldn't get clock\n");
>  		ret = -EINVAL;
>  		goto error0;
>  	}

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2014-03-13 10:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13  8:30 [PATCH] spi: sh-hspi: Do not specifically request shyway_clk clock Simon Horman
2014-03-13 10:10 ` Laurent Pinchart [this message]
2014-03-13 23:50   ` Simon Horman

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=2144304.qo37EGpAOW@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=broonie@linaro.org \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=magnus.damm@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;
as well as URLs for NNTP newsgroup(s).