public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
	Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Nuno Sa <nuno.sa@analog.com>,
	David Lechner <dlechner@baylibre.com>,
	Javier Carrasco <javier.carrasco.cruz@gmail.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] dt-bindings: ROHM BD79104 ADC
Date: Mon, 31 Mar 2025 16:47:29 +0100	[thread overview]
Message-ID: <20250331-chooser-superbowl-2dfa754e8d05@spud> (raw)
In-Reply-To: <4ccc6d33ffb0fd29f02afcb9124a0f72f571a0cd.1742474322.git.mazziesaccount@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3659 bytes --]

On Mon, Mar 31, 2025 at 11:02:20AM +0300, Matti Vaittinen wrote:
> The ROHM BD79104 is a 12-bit, 8-channel ADC with two power supply pins,
> connected to SPI. It's worth noting the IC requires SPI MODE 3, (CPHA =
> 1, CPOL = 1).
> 
> I used an evaluation board "BD79104FV-EVK-001" from ROHM. With this
> board I had problems to have things working correctly with higher SPI
> clock frequencies. I didn't do thorough testing for maximum frequency
> though. First attempt was 40M, then 20M and finally 4M. With 20M it
> seemed as if the read values were shifted by 1 bit. With 4M it worked
> fine.
> 
> The component data-sheet is not exact what comes to the maximum SPI
> frequency. It says SPI frequency is 20M - "unless othervice specified".
> Additionally, it says that maximum sampling rate is 1Mhz, and since
> reading a sample requires writing the channel (16 bits) and reading
> data (16 bits) - we get some upper limit from this.
> 
> From the "frequency is 20M, unless othervice specified" I picked the
> maximum frequency 20M - and did assumption that my problems with 20M
> weren't related to the BD79104 - but to the evaluation board
> "BD79104FV-EVK-001".
> 
> Add bindings for the ROHM BD79104 ADC.
> 
> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>

Reviewed-by: Conor Dooley <conor.dooley@microchip.com>

> ---
>  .../bindings/iio/adc/rohm,bd79104.yaml        | 69 +++++++++++++++++++
>  1 file changed, 69 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/iio/adc/rohm,bd79104.yaml
> 
> diff --git a/Documentation/devicetree/bindings/iio/adc/rohm,bd79104.yaml b/Documentation/devicetree/bindings/iio/adc/rohm,bd79104.yaml
> new file mode 100644
> index 000000000000..2a8ad4fdfc6b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/rohm,bd79104.yaml
> @@ -0,0 +1,69 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/adc/rohm,bd79104.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: ROHM Semiconductor BD79104 ADC
> +
> +maintainers:
> +  - Matti Vaittinen <mazziesaccount@gmail.com>
> +
> +description: |
> +  12 bit SPI ADC with 8 channels.
> +
> +properties:
> +  compatible:
> +    const: rohm,bd79104
> +
> +  reg:
> +    maxItems: 1
> +
> +  vdd-supply: true
> +  iovdd-supply: true
> +
> +# The component data-sheet says the frequency is 20M. I, however, found
> +# that the ROHM evaluation board BD79104FV-EVK-001 had problems with 20M.
> +# I have successfully used it with 4M. My _assumption_ is that this is not
> +# the limitation of the component itself, but a limitation of the EVK.
> +  spi-max-frequency:
> +    maximum: 20000000
> +
> +  "#io-channel-cells":
> +    const: 1
> +
> +  spi-cpha: true
> +  spi-cpol: true
> +
> +required:
> +  - compatible
> +  - reg
> +  - vdd-supply
> +  - iovdd-supply
> +  - spi-cpha
> +  - spi-cpol
> +
> +allOf:
> +  - $ref: /schemas/spi/spi-peripheral-props.yaml#
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    #include <dt-bindings/interrupt-controller/irq.h>
> +    spi {
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        adc@0 {
> +            compatible = "rohm,bd79104";
> +            reg = <0>;
> +            vdd-supply = <&vdd_supply>;
> +            iovdd-supply = <&iovdd_supply>;
> +            spi-max-frequency = <4000000>;
> +            spi-cpha;
> +            spi-cpol;
> +            #io-channel-cells = <1>;
> +        };
> +    };
> +...
> -- 
> 2.48.1
> 



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-03-31 15:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-31  8:01 [PATCH 0/6] Support ROHM BD79104 ADC Matti Vaittinen
2025-03-31  8:02 ` [PATCH 1/6] dt-bindings: " Matti Vaittinen
2025-03-31 15:47   ` Conor Dooley [this message]
2025-03-31  8:02 ` [PATCH 2/6] iio: adc: ti-adc128s052: Fix ADC value on BE systems Matti Vaittinen
2025-03-31 11:11   ` Jonathan Cameron
2025-03-31 12:07     ` Matti Vaittinen
2025-03-31  8:03 ` [PATCH 3/6] iio: adc: ti-adc128s052: Be consistent with arrays Matti Vaittinen
2025-03-31 11:13   ` Jonathan Cameron
2025-03-31  8:03 ` [PATCH 4/6] iio: adc: ti-adc128s052: Use devm_mutex_init() Matti Vaittinen
2025-03-31 11:13   ` Jonathan Cameron
2025-03-31  8:03 ` [PATCH 5/6] iio: adc: ti-adc128s052: Simplify using guard(mutex) Matti Vaittinen
2025-03-31 11:14   ` Jonathan Cameron
2025-03-31  8:03 ` [PATCH 6/6] iio: adc: ti-adc128s052: Support ROHM BD79104 Matti Vaittinen
2025-03-31 11:22   ` Jonathan Cameron
2025-04-01 12:33     ` Matti Vaittinen
2025-04-05 17:43       ` Jonathan Cameron
2025-04-07  6:10         ` Matti Vaittinen
2025-04-07 18:44           ` Jonathan Cameron

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=20250331-chooser-superbowl-2dfa754e8d05@spud \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=javier.carrasco.cruz@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=mazziesaccount@gmail.com \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.org \
    /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