lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 14 Mar 2014 16:14:03 +0000
From:	Mark Rutland <mark.rutland@....com>
To:	Steffen Trumtrar <s.trumtrar@...gutronix.de>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	Mark Brown <broonie@...nel.org>, Rob Landley <rob@...dley.net>,
	Rob Herring <robh+dt@...nel.org>,
	Pawel Moll <Pawel.Moll@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>
Subject: Re: [PATCH] spi: dw-mmio: add oftree support

On Fri, Mar 14, 2014 at 08:55:26AM +0000, Steffen Trumtrar wrote:
> Allow probing the dw-mmio from devicetree.
> 
> Signed-off-by: Steffen Trumtrar <s.trumtrar@...gutronix.de>
> ---
> This was tested on Socfpga and v3.14-rc6
> 
>  .../devicetree/bindings/spi/spi-dw-mmio.txt        | 25 ++++++++++++++++++++++
>  drivers/spi/spi-dw-mmio.c                          | 19 +++++++++++++++-
>  2 files changed, 43 insertions(+), 1 deletion(-)
>  create mode 100644 Documentation/devicetree/bindings/spi/spi-dw-mmio.txt
> 
> diff --git a/Documentation/devicetree/bindings/spi/spi-dw-mmio.txt b/Documentation/devicetree/bindings/spi/spi-dw-mmio.txt
> new file mode 100644
> index 0000000..2b9bb90
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/spi/spi-dw-mmio.txt
> @@ -0,0 +1,25 @@
> +Synopsys DesignWare SPI master controller.
> +
> +Required properties:
> +- compatible : "snps,dw-spi-mmio"

Is there not a better name than "dw-spi-mmio"?

What's the full name of the device, as on a datasheet? Is there no model
number?

Otherwise this looks ok.

> +- reg : The register base for the controller.
> +- interrupts : One interrupt, used by the controller.
> +- #address-cells : <1>, as required by generic SPI binding.
> +- #size-cells : <0>, also as required by generic SPI binding.
> +
> +Optional properties:
> +- num-chipselects : The number of chipselects.

If this is optional, when wuold I need to set this? What's the default
assumption?

Mark: I see some bindings have "num-chipselects", and some have
"num-cs". Do you have a preferred form that people could align on?

Cheers,
Mark.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ