linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: bjorn@kryo.se (Bjorn Andersson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: DT: apq8064: create qcom-apq8064-board-common.dtsi
Date: Fri, 26 Sep 2014 06:41:09 -0700	[thread overview]
Message-ID: <CAJAp7Ohdi2+M0LC+a3BT6++17b2DST8RgjJddKNEVwL9Ltqrdg@mail.gmail.com> (raw)
In-Reply-To: <1411718851-17436-2-git-send-email-mike.rapoport@gmail.com>

On Fri, Sep 26, 2014 at 1:07 AM, Mike Rapoport <mike.rapoport@gmail.com> wrote:

Cool to see the addition of dt for additional devices. I do however
not think it is correct to put all these things in common...

> diff --git a/arch/arm/boot/dts/qcom-apq8064-board-common.dtsi b/arch/arm/boot/dts/qcom-apq8064-board-common.dtsi
> new file mode 100644
> index 0000000..c92d3e9
> --- /dev/null
> +++ b/arch/arm/boot/dts/qcom-apq8064-board-common.dtsi
> @@ -0,0 +1,57 @@
> +#include "qcom-apq8064-v2.0.dtsi"
> +
> +/ {
> +
> +       soc {
> +               pinctrl at 800000 {
> +                       i2c1_pins: i2c1 {
> +                               mux {
> +                                       pins = "gpio20", "gpio21";
> +                                       function = "gsbi1";
> +                               };

The muxing is common, but you probably want to be able to set drive
strength and bias as well and handle active vs sleep mode and then I'm
not sure if it is common anymore...

> +                       };
> +               };
> +
> +               gsbi at 12440000 {
> +                       status = "okay";
> +                       qcom,mode = <GSBI_PROT_I2C>;
> +
> +                       i2c at 12460000 {
> +                               status = "okay";
> +                               clock-frequency = <200000>;
> +                               pinctrl-0 = <&i2c1_pins>;
> +                               pinctrl-names = "default";
> +
> +                               eeprom: eeprom at 52 {
> +                                       compatible = "atmel,24c128";
> +                                       reg = <0x52>;
> +                                       pagesize = <32>;
> +                               };

Not all apq8064 boards have this eeprom.

> +                       };
> +               };
> +
> +               gsbi at 16600000 {
> +                       status = "ok";
> +                       qcom,mode = <GSBI_PROT_I2C_UART>;
> +                       serial at 16640000 {
> +                               status = "ok";
> +                       };
> +               };
> +
> +               amba {
> +                       /* eMMC */
> +                       sdcc1: sdcc at 12400000 {
> +                               status = "okay";
> +                       };
> +
> +                       /* External micro SD card */
> +                       sdcc3: sdcc at 12180000 {
> +                               status = "okay";
> +                       };
> +                       /* WLAN */
> +                       sdcc4: sdcc at 121c0000 {
> +                               status = "okay";
> +                       };

I'm not sure if all boards are using sdcc4 for WiFi.

Regards,
Bjorn

  reply	other threads:[~2014-09-26 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26  8:07 [PATCH 0/2] qcom: add CM-QS600 board Mike Rapoport
2014-09-26  8:07 ` [PATCH 1/2] ARM: DT: apq8064: create qcom-apq8064-board-common.dtsi Mike Rapoport
2014-09-26 13:41   ` Bjorn Andersson [this message]
2014-09-26 13:53     ` Kumar Gala
2014-09-26  8:07 ` [PATCH 2/2] ARM: DT: apq8064: add CM-QS600 board Mike Rapoport

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=CAJAp7Ohdi2+M0LC+a3BT6++17b2DST8RgjJddKNEVwL9Ltqrdg@mail.gmail.com \
    --to=bjorn@kryo.se \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).