Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1335213 > unrolled thread

[PATCH] spi/rockchip: Add dt-binding for Rockchip rk3399 spi

Back to article view | Back to linux.kernel

Contents

  [PATCH] spi/rockchip: Add dt-binding for Rockchip rk3399 spi "jianqun.xu" <jay.xu@rock-chips.com> - 2016-02-16 10:30 +0100
    Re: [PATCH] spi/rockchip: Add dt-binding for Rockchip rk3399 spi Mark Brown <broonie@kernel.org> - 2016-02-16 14:40 +0100
      Re: [PATCH] spi/rockchip: Add dt-binding for Rockchip rk3399 spi Heiko Stuebner <heiko@sntech.de> - 2016-02-16 15:40 +0100
        Re: [PATCH] spi/rockchip: Add dt-binding for Rockchip rk3399 spi Jianqun Xu <jay.xu@rock-chips.com> - 2016-02-17 01:30 +0100
          Re: [PATCH] spi/rockchip: Add dt-binding for Rockchip rk3399 spi Heiko Stuebner <heiko@sntech.de> - 2016-02-17 07:50 +0100
            Re: [PATCH] spi/rockchip: Add dt-binding for Rockchip rk3399 spi Mark Brown <broonie@kernel.org> - 2016-02-17 12:00 +0100

#1335213 — [PATCH] spi/rockchip: Add dt-binding for Rockchip rk3399 spi

From: Xu Jianqun <jay.xu@rock-chips.com>

Add compatible support for Rockchip rk3399 spi.

Signed-off-by: Xu Jianqun <jay.xu@rock-chips.com>
---
 Documentation/devicetree/bindings/spi/spi-rockchip.txt | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/spi/spi-rockchip.txt b/Documentation/devicetree/bindings/spi/spi-rockchip.txt
index 0c491bd..1b14d69 100644
--- a/Documentation/devicetree/bindings/spi/spi-rockchip.txt
+++ b/Documentation/devicetree/bindings/spi/spi-rockchip.txt
@@ -9,6 +9,7 @@ Required Properties:
     "rockchip,rk3066-spi" for rk3066.
     "rockchip,rk3188-spi", "rockchip,rk3066-spi" for rk3188.
     "rockchip,rk3288-spi", "rockchip,rk3066-spi" for rk3288.
+    "rockchip,rk3399-spi", "rockchip,rk3066-spi" for rk3399.
 - reg: physical base address of the controller and length of memory mapped
        region.
 - interrupts: The interrupt number to the cpu. The interrupt specifier format
-- 
1.9.1

[toc] | [next] | [standalone]

#1335383

[Multipart message — attachments visible in raw view] — view raw

On Tue, Feb 16, 2016 at 05:22:18PM +0800, jianqun.xu wrote:

>  Documentation/devicetree/bindings/spi/spi-rockchip.txt | 1 +
>  1 file changed, 1 insertion(+)

I'd expect this to be added to both the driver and the binding document
not just the document.

[toc] | [prev] | [next] | [standalone]

#1335463

Am Dienstag, 16. Februar 2016, 13:22:23 schrieb Mark Brown:
> On Tue, Feb 16, 2016 at 05:22:18PM +0800, jianqun.xu wrote:
> >  Documentation/devicetree/bindings/spi/spi-rockchip.txt | 1 +
> >  1 file changed, 1 insertion(+)
> 
> I'd expect this to be added to both the driver and the binding document
> not just the document.

It seems the driver can still use the rk3066-variant - aka nobody has found 
specific issues in the rk3399 IP implementation.

Having the more specific IP names already in the dts before actually using 
them was suggested by devicetree people to not have to exchange everything 
once specific issues were found. 

So right now it's using the fallback-mechanism of binding to the rk3066 
name, but if some obstacle appears it will only take adding the binding in 
the driver to make it work (even with old devicetrees).

[toc] | [prev] | [next] | [standalone]

#1335953

Hi Heiko

在 16/02/2016 22:37, Heiko Stuebner 写道:
> Am Dienstag, 16. Februar 2016, 13:22:23 schrieb Mark Brown:
>> On Tue, Feb 16, 2016 at 05:22:18PM +0800, jianqun.xu wrote:
>>>   Documentation/devicetree/bindings/spi/spi-rockchip.txt | 1 +
>>>   1 file changed, 1 insertion(+)
>>
>> I'd expect this to be added to both the driver and the binding document
>> not just the document.
>
> It seems the driver can still use the rk3066-variant - aka nobody has found
> specific issues in the rk3399 IP implementation.
>
> Having the more specific IP names already in the dts before actually using
> them was suggested by devicetree people to not have to exchange everything
> once specific issues were found.
>
> So right now it's using the fallback-mechanism of binding to the rk3066
> name, but if some obstacle appears it will only take adding the binding in
> the driver to make it work (even with old devicetrees).
>
>
Thank you, got it, and I will re-send this patch with the driver patch.
>

[toc] | [prev] | [next] | [standalone]

#1336082

Hi Jianqun,

Am Mittwoch, 17. Februar 2016, 08:21:58 schrieb Jianqun Xu:
> 在 16/02/2016 22:37, Heiko Stuebner 写道:
> > Am Dienstag, 16. Februar 2016, 13:22:23 schrieb Mark Brown:
> >> On Tue, Feb 16, 2016 at 05:22:18PM +0800, jianqun.xu wrote:
> >>>   Documentation/devicetree/bindings/spi/spi-rockchip.txt | 1 +
> >>>   1 file changed, 1 insertion(+)
> >> 
> >> I'd expect this to be added to both the driver and the binding document
> >> not just the document.
> > 
> > It seems the driver can still use the rk3066-variant - aka nobody has
> > found specific issues in the rk3399 IP implementation.
> > 
> > Having the more specific IP names already in the dts before actually
> > using them was suggested by devicetree people to not have to exchange
> > everything once specific issues were found.
> > 
> > So right now it's using the fallback-mechanism of binding to the rk3066
> > name, but if some obstacle appears it will only take adding the binding
> > in the driver to make it work (even with old devicetrees).
> 
> Thank you, got it, and I will re-send this patch with the driver patch.

you have me confused now :-) .

That was meant as a reply to Mark's comment, explaining why the double 
compatible and the driver only binding to the rk3066-one right now.


Heiko

[toc] | [prev] | [next] | [standalone]

#1336251

[Multipart message — attachments visible in raw view] — view raw

On Wed, Feb 17, 2016 at 07:45:09AM +0100, Heiko Stuebner wrote:

> That was meant as a reply to Mark's comment, explaining why the double 
> compatible and the driver only binding to the rk3066-one right now.

It's still better to have the compatible explicitly listed in the
driver even if it doesn't change the configuration at all at this time.
That way we've at least got a record that the handling is currently
identical to whatever other devices it is the same as.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web