mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gregory Bean <gbean@codeaurora.org>
To: Janakiram Sistla <janakiram.sistla@gmail.com>
Cc: Gregory Bean <gbean@codeaurora.org>,
	dwalker@codeaurora.org, linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] msm: gpio: Add irq support to v2 gpiolib.
Date: Fri, 19 Nov 2010 10:37:45 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1011191035210.10052@gbean-linux.qualcomm.com> (raw)
In-Reply-To: <AANLkTiknYmWOmiFXGp6h2dT==aMuGs3BtXi82b6Vdq5i@mail.gmail.com>

On Thu, 18 Nov 2010, Janakiram Sistla wrote:

>> Targets with the v2 block define CONFIG_MSM_V2_TLMM.
>
> So in that case we can name  it as gpio-tlmm.c ??

No, not and have things be any clearer.

All MSM chips have a TLMM block.  The older chips have
version 1 (v1) of the TLMM block.  The newer chips have v2.

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2010-11-19 18:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 19:52 [PATCH v4 1/2] msm: gpio: Add v2 gpio support to MSM SoCs Gregory Bean
2010-11-18 19:52 ` [PATCH v4 2/2] msm: gpio: Add irq support to v2 gpiolib Gregory Bean
2010-11-18 19:59   ` Janakiram Sistla
2010-11-18 20:30     ` Gregory Bean
2010-11-18 20:39       ` Janakiram Sistla
2010-11-18 20:59         ` Gregory Bean
2010-11-18 22:02           ` Janakiram Sistla
2010-11-19 18:37             ` Gregory Bean [this message]
2010-11-19 18:49               ` Janakiram Sistla
2010-11-19 19:00                 ` Gregory Bean
2010-11-19 19:09                   ` Janakiram Sistla
2010-11-19 20:27                     ` Gregory Bean
2010-11-23 17:51   ` Daniel Walker
2010-11-23 23:08     ` Gregory Bean
2010-11-24  0:44       ` Daniel Walker
2010-11-18 19:56 ` [PATCH v4 1/2] msm: gpio: Add v2 gpio support to MSM SoCs Janakiram Sistla

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=alpine.DEB.2.00.1011191035210.10052@gbean-linux.qualcomm.com \
    --to=gbean@codeaurora.org \
    --cc=dwalker@codeaurora.org \
    --cc=janakiram.sistla@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®