| Message ID | 9813bf559ad89ca6fecc438d9176d634bbc122a0.1469686300.git.dalias@libc.org (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On Tue, May 17, 2016 at 11:19:25PM +0000, Rich Felker wrote: > Signed-off-by: Rich Felker <dalias@libc.org> > --- > .../devicetree/bindings/spi/jcore,spi.txt | 30 ++++++++++++++++++++++ > 1 file changed, 30 insertions(+) > create mode 100644 Documentation/devicetree/bindings/spi/jcore,spi.txt Acked-by: Rob Herring <robh@kernel.org> -- To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, Jul 29, 2016 at 03:58:38PM -0500, Rob Herring wrote: > On Tue, May 17, 2016 at 11:19:25PM +0000, Rich Felker wrote: > > Signed-off-by: Rich Felker <dalias@libc.org> > > --- > > .../devicetree/bindings/spi/jcore,spi.txt | 30 ++++++++++++++++++++++ > > 1 file changed, 30 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/spi/jcore,spi.txt > > Acked-by: Rob Herring <robh@kernel.org> Thanks. Since I switched to to using the clk framework rather than a clock-frequency property (at Mark Brown's suggestion/request), I'll be submitting one more version for your review. After that, who should be responsible for upstreaming this and the other binding patches? You, me, or the subsystem maintainers that the drivers are going through? Rich -- To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Aug 2, 2016 at 5:00 PM, Rich Felker <dalias@libc.org> wrote: > On Fri, Jul 29, 2016 at 03:58:38PM -0500, Rob Herring wrote: >> On Tue, May 17, 2016 at 11:19:25PM +0000, Rich Felker wrote: >> > Signed-off-by: Rich Felker <dalias@libc.org> >> > --- >> > .../devicetree/bindings/spi/jcore,spi.txt | 30 ++++++++++++++++++++++ >> > 1 file changed, 30 insertions(+) >> > create mode 100644 Documentation/devicetree/bindings/spi/jcore,spi.txt >> >> Acked-by: Rob Herring <robh@kernel.org> > > Thanks. Since I switched to to using the clk framework rather than a > clock-frequency property (at Mark Brown's suggestion/request), I'll be > submitting one more version for your review. > > After that, who should be responsible for upstreaming this and the > other binding patches? You, me, or the subsystem maintainers that the > drivers are going through? Mark will take the SPI changes. I generally only take standalone binding patches thru the DT tree. Rob -- To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/devicetree/bindings/spi/jcore,spi.txt b/Documentation/devicetree/bindings/spi/jcore,spi.txt new file mode 100644 index 0000000..815106d --- /dev/null +++ b/Documentation/devicetree/bindings/spi/jcore,spi.txt @@ -0,0 +1,30 @@ +J-Core SPI master + +Required properties: + +- compatible: Must be "jcore,spi2". + +- reg: Memory region for registers. + +- #address-cells: Must be 1. + +- #size-cells: Must be 0. + +Optional properties: + +- clock-frequency: Specifies an input clock frequency relative to + which the SPI clock speed must be programmed. Necessary only if + the input clock rate is something other than 50 MHz. + +See spi-bus.txt for additional properties not specific to this device. + +Example: + +spi@40 { + compatible = "jcore,spi2"; + #address-cells = <1>; + #size-cells = <0>; + reg = <0x40 0x8>; + spi-max-frequency = <25000000>; + clock-frequency = <50000000>; +}
Signed-off-by: Rich Felker <dalias@libc.org> --- .../devicetree/bindings/spi/jcore,spi.txt | 30 ++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 Documentation/devicetree/bindings/spi/jcore,spi.txt