[<prev] [next>] [day] [month] [year] [list]
Message-ID: <3971c669-9095-9d18-d029-37f9663a54b2@cogentembedded.com>
Date: Thu, 18 Apr 2019 22:43:24 +0300
From: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To: masonccyang@...c.com.tw
Cc: bbrezillon@...nel.org, broonie@...nel.org,
devicetree@...r.kernel.org,
Geert Uytterhoeven <geert+renesas@...der.be>,
Simon Horman <horms@...ge.net.au>, juliensu@...c.com.tw,
lee.jones@...aro.org, linux-kernel@...r.kernel.org,
linux-renesas-soc@...r.kernel.org, linux-spi@...r.kernel.org,
marek.vasut@...il.com, mark.rutland@....com, robh+dt@...nel.org,
zhengxunli@...c.com.tw
Subject: Re: [PATCH v9 2/3] spi: Add Renesas R-Car Gen3 RPC-IF SPI controller
driver
On 04/18/2019 05:51 AM, masonccyang@...c.com.tw wrote:
>> >> >> Add a driver for Renesas R-Car Gen3 RPC-IF SPI controller.
>> >> >>
>> >> >> Signed-off-by: Mason Yang <masonccyang@...c.com.tw>
>> >> >> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
>> >> > [...]
>> >> >> diff --git a/drivers/spi/spi-renesas-rpc.c b/drivers/spi/spi-
>> renesas-rpc.c
>> >> >> new file mode 100644
>> >> >> index 0000000..037f273
>> >> >> --- /dev/null
>> >> >> +++ b/drivers/spi/spi-renesas-rpc.c
>> >> > [...]
>> >> >> +static int rpc_spi_probe(struct platform_device *pdev)
>> >> >> +{
>> >> >> + struct spi_controller *ctlr;
>> >> >> + struct rpc_mfd *rpc_mfd = dev_get_drvdata(pdev->dev.parent);
>> >> >> + struct rpc_spi *rpc;
>> >> >> + int ret;
>> >> >> +
>> >> >> + ctlr = spi_alloc_master(&pdev->dev, sizeof(*rpc));
>> >> >> + if (!ctlr)
>> >> >> + return -ENOMEM;
>> >> >> +
>> >> >> + platform_set_drvdata(pdev, ctlr);
>> >> >> +
>> >> >> + rpc = spi_controller_get_devdata(ctlr);
>> >> >> +
>> >> >> + ctlr->dev.of_node = pdev->dev.of_node;
>> >> > [...]
>> >> >> +
>> >> >> + pm_runtime_enable(&pdev->dev);
>> >> >> + ctlr->auto_runtime_pm = true;
>> >> >
>> >> > I think this line no longer works as expected with the new
>> >> probing scheme.
>>
>> That's because we added another (SPI) device under our MFD.
>
> Do you mean just to remove one line
> ctlr->auto_runtime_pm = true;
> ?
No, you should explicitly call RPM for the MFD (not the SPI device).
>> >> > Have you tested reading? v8 patch still works while v9 patches
>> >> > hang on doing:
>> >> >
>> >> > $ cat /dev/mtd<n>...
>> >>
>> >> Sorry, 'od -x', not 'cat'.
>> >
>> > root@...ak:/# cat /proc/mtd
>> > dev: size erasesize name
>> > mtd0: 00040000 00001000 "Bank 1 - Boot parameter"
>> > mtd1: 00140000 00001000 "Bank 1 - Loader-BL2"
>> > mtd2: 00040000 00001000 "Bank 1 - Certification"
>> > mtd3: 00080000 00001000 "Bank 1 - ARM Trusted FW"
>> > mtd4: 00400000 00001000 "Bank 1 - Reserved-1"
>> > mtd5: 00300000 00001000 "Bank 1 - U-Boot"
>> > mtd6: 00200000 00001000 "Bank 1 - Reserved-2"
>> > mtd7: 00480000 00001000 "Bank 1 - Splash"
>> > mtd8: 00040000 00001000 "Bank 1 - Device Tree"
>> > root@...ak:/# od -x /dev/mtd1
>> > 0000000 0000 d280 0001 d280 0002 d280 0003 d280
>> > 0000020 0004 d280 0005 d280 0006 d280 0007 d280
>> > 0000040 0008 d280 0009 d280 000a d280 000b d280
>> > 0000060 000c d280 000d d280 000e d280 000f d280
>> > 0000100 0010 d280 0011 d280 0012 d280 0013 d280
>> > 0000120 0014 d280 0015 d280 0016 d280 0017 d280
>> > 0000140 0018 d280 0019 d280 001a d280 001b d280
>> > 0000160 001c d280 001d d280 001e d280 1000 d53e
>> > 0000200 f800 9266 1000 d51e 3fdf d503 3ba0 1005
>>
>> Still hangs for me. After I patches spi-mem.c and the driver to
>> call RPM for the MFD, it started working again. Perhaps, that clock
>> is still enabled on your target. What does the following print (for
>> the RPC clocks)?
>>
>> $ mount none -t debugfs /sys/kernel/debug/
>> $ cat /sys/kernel/debug/clk/clk_summary
>>
>
> root@...ak:/# cat /sys/kernel/debug/clk/clk_summary
> enable prepare protect duty
> clock count count count rate accuracy phase cycle
> ---------------------------------------------------------------------------------------------
> audio_clkout1 0 0 0 11289600 0 0 50000
> x19_clk 0 0 0 24576000 0 0 50000
> dclkin-0 0 0 0 0 0 0 50000
> scif 1 1 0 0 0 0 50000
> audio_clkb 0 0 0 22579200 0 0 50000
> msiof-ref-clock 0 0 0 66666666 0 0 50000
> extal 2 3 0 48000000 0 0 50000
> r 0 2 0 31250 0 0 50000
> rpc-if 0 1 0 31250 0 0 50000
This looks wrong, the RPC-IF module clock should have RPC or RPCD2 (where ae they?)
as a source, not RLCK...
> rwdt 0 1 0 31250 0 0 50000
> cmt0 0 0 0 31250 0 0 50000
> cmt1 0 0 0 31250 0 0 50000
> cmt2 0 0 0 31250 0 0 50000
> cmt3 0 0 0 31250 0 0 50000
> osc 0 0 0 125000 0 0 50000
>
>
> thanks & best regards,
> Mason
MBR, Sergei
Powered by blists - more mailing lists