All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@sonymobile.com>
To: Andy Gross <agross@codeaurora.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: [Patch v2] pinctrl: msm: Add more MSM8X74 pin definitions
Date: Fri, 9 May 2014 14:45:42 -0700	[thread overview]
Message-ID: <20140509214541.GB25733@sonymobile.com> (raw)
In-Reply-To: <1399657974-32695-1-git-send-email-agross@codeaurora.org>

On Fri 09 May 10:52 PDT 2014, Andy Gross wrote:

> This patch adds pin definitiones for the MSM8x74 TLMM.  New definitions
> include:
> 
> BLSP devices (I2C, UART, UART flow control, SPI, and UIM), mi2s, gp clk, pdm,
> gcc clk, cci_timer, cci_i2c, cam_clk, hsic, tsif, sdc3, sdc4, and other assorted
> pins.
> 
> Signed-off-by: Andy Gross <agross@codeaurora.org>

Awesome stuff, only have some minor comments.

> +       MSM_MUX_blsp_uart1,
> +       MSM_MUX_blsp_uart1_flow,
[...]
> +static const char * const blsp_uim1_groups[] = { "gpio0", "gpio1" };
> +static const char * const blsp_uart1_flow_groups[] = { "gpio2", "gpio3" };

You don't need to separate uart and flow control into two different functions
here.  If you have gpio0-gpio3 in a group named uart1 both of the following
snippets are valid:

uart1 {
	pins = "gpio0", "gpio1";
	function = "uart1";
};

uart1 {
	pins = "gpio0", "gpio1", "gpio2", "gpio3";
	function = "uart1";
};

This is how I had to handle gsbis in family a, where a gsbi is pairs of pins
with different configurations.

[...]
> +static const char * const hdmi_cec_groups[] = { "gpio31" };
> +static const char * const hdmi_ddc_groups[] = { "gpio32", "gpio33" };
> +static const char * const hdmi_hpd_groups[] = { "gpio34" };

As with the uart vs uart_flow you could group these as "hdmi", but maybe not as
useful.

[...]
> +       PINGROUP(35,  NA, sdc3, NA, NA, NA, NA, NA),
> +       PINGROUP(36,  NA, sdc3, NA, NA, NA, NA, NA),
> +       PINGROUP(37,  NA, sdc3, NA, NA, NA, NA, NA),
> +       PINGROUP(38,  NA, sdc3, NA, NA, NA, NA, NA),
> +       PINGROUP(39,  NA, sdc3, NA, NA, NA, NA, NA),
> +       PINGROUP(40,  NA, sdc3, NA, NA, NA, NA, NA),
> +       PINGROUP(41,  NA, blsp_spi7, blsp_uart7, blsp_uim7, NA, NA, NA),
> +       PINGROUP(42,  NA, blsp_spi7, blsp_uart7, blsp_uim7, NA, NA, NA),
> +       PINGROUP(43,  NA, blsp_spi7, blsp_uart7_flow, blsp_i2c7, NA, NA, NA),
> +       PINGROUP(44,  NA, blsp_spi7, blsp_uart7_flow, blsp_i2c7, NA, NA, NA),

I was expecting wcnss, bt and fm as function 1 for pins 35-44. Adding those and
I think we have everything we use in our devices.

[...]
> +       PINGROUP(72,  NA, spkr_mi2s, NA, NA, NA, NA, NA),

spkr_mi2s is function 1 for pin 72.

Regards,
Bjorn

WARNING: multiple messages have this Message-ID (diff)
From: bjorn.andersson@sonymobile.com (Bjorn Andersson)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch v2] pinctrl: msm: Add more MSM8X74 pin definitions
Date: Fri, 9 May 2014 14:45:42 -0700	[thread overview]
Message-ID: <20140509214541.GB25733@sonymobile.com> (raw)
In-Reply-To: <1399657974-32695-1-git-send-email-agross@codeaurora.org>

On Fri 09 May 10:52 PDT 2014, Andy Gross wrote:

> This patch adds pin definitiones for the MSM8x74 TLMM.  New definitions
> include:
> 
> BLSP devices (I2C, UART, UART flow control, SPI, and UIM), mi2s, gp clk, pdm,
> gcc clk, cci_timer, cci_i2c, cam_clk, hsic, tsif, sdc3, sdc4, and other assorted
> pins.
> 
> Signed-off-by: Andy Gross <agross@codeaurora.org>

Awesome stuff, only have some minor comments.

> +       MSM_MUX_blsp_uart1,
> +       MSM_MUX_blsp_uart1_flow,
[...]
> +static const char * const blsp_uim1_groups[] = { "gpio0", "gpio1" };
> +static const char * const blsp_uart1_flow_groups[] = { "gpio2", "gpio3" };

You don't need to separate uart and flow control into two different functions
here.  If you have gpio0-gpio3 in a group named uart1 both of the following
snippets are valid:

uart1 {
	pins = "gpio0", "gpio1";
	function = "uart1";
};

uart1 {
	pins = "gpio0", "gpio1", "gpio2", "gpio3";
	function = "uart1";
};

This is how I had to handle gsbis in family a, where a gsbi is pairs of pins
with different configurations.

[...]
> +static const char * const hdmi_cec_groups[] = { "gpio31" };
> +static const char * const hdmi_ddc_groups[] = { "gpio32", "gpio33" };
> +static const char * const hdmi_hpd_groups[] = { "gpio34" };

As with the uart vs uart_flow you could group these as "hdmi", but maybe not as
useful.

[...]
> +       PINGROUP(35,  NA, sdc3, NA, NA, NA, NA, NA),
> +       PINGROUP(36,  NA, sdc3, NA, NA, NA, NA, NA),
> +       PINGROUP(37,  NA, sdc3, NA, NA, NA, NA, NA),
> +       PINGROUP(38,  NA, sdc3, NA, NA, NA, NA, NA),
> +       PINGROUP(39,  NA, sdc3, NA, NA, NA, NA, NA),
> +       PINGROUP(40,  NA, sdc3, NA, NA, NA, NA, NA),
> +       PINGROUP(41,  NA, blsp_spi7, blsp_uart7, blsp_uim7, NA, NA, NA),
> +       PINGROUP(42,  NA, blsp_spi7, blsp_uart7, blsp_uim7, NA, NA, NA),
> +       PINGROUP(43,  NA, blsp_spi7, blsp_uart7_flow, blsp_i2c7, NA, NA, NA),
> +       PINGROUP(44,  NA, blsp_spi7, blsp_uart7_flow, blsp_i2c7, NA, NA, NA),

I was expecting wcnss, bt and fm as function 1 for pins 35-44. Adding those and
I think we have everything we use in our devices.

[...]
> +       PINGROUP(72,  NA, spkr_mi2s, NA, NA, NA, NA, NA),

spkr_mi2s is function 1 for pin 72.

Regards,
Bjorn

  reply	other threads:[~2014-05-09 21:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 17:52 [Patch v2] pinctrl: msm: Add more MSM8X74 pin definitions Andy Gross
2014-05-09 17:52 ` Andy Gross
2014-05-09 21:45 ` Bjorn Andersson [this message]
2014-05-09 21:45   ` Bjorn Andersson

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=20140509214541.GB25733@sonymobile.com \
    --to=bjorn.andersson@sonymobile.com \
    --cc=agross@codeaurora.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.