All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: Sekhar Nori <nsekhar@ti.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
	Kevin Hilman <khilman@deeprootsystems.com>,
	Russell King <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel@savoirfairelinux.com
Subject: Re: [RFC] ARM: davinci: da850: add a few pinmux definitions
Date: Fri, 26 Jul 2013 16:59:19 -0400 (EDT)	[thread overview]
Message-ID: <55770703.973667.1374872359591.JavaMail.root@mail> (raw)
In-Reply-To: <51F0F377.1060204@ti.com>

Hi Sekhar,

You wrote:
> Why do you need to add these definitions? If it is for a new platform
> you are working on, then it should be supported using DT, in which
> case
> we use the pinctrl-single driver and define the muxing needed in
> .dts/.dtsi files.

Ok, good to know.

Thanks,
Vivien

WARNING: multiple messages have this Message-ID (diff)
From: vivien.didelot@savoirfairelinux.com (Vivien Didelot)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] ARM: davinci: da850: add a few pinmux definitions
Date: Fri, 26 Jul 2013 16:59:19 -0400 (EDT)	[thread overview]
Message-ID: <55770703.973667.1374872359591.JavaMail.root@mail> (raw)
In-Reply-To: <51F0F377.1060204@ti.com>

Hi Sekhar,

You wrote:
> Why do you need to add these definitions? If it is for a new platform
> you are working on, then it should be supported using DT, in which
> case
> we use the pinctrl-single driver and define the muxing needed in
> .dts/.dtsi files.

Ok, good to know.

Thanks,
Vivien

  reply	other threads:[~2013-07-26 20:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23 20:13 [RFC] ARM: davinci: da850: add a few pinmux definitions Vivien Didelot
2013-07-23 20:13 ` Vivien Didelot
2013-07-25  9:44 ` Sekhar Nori
2013-07-25  9:44   ` Sekhar Nori
2013-07-26 20:59   ` Vivien Didelot [this message]
2013-07-26 20:59     ` Vivien Didelot

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=55770703.973667.1374872359591.JavaMail.root@mail \
    --to=vivien.didelot@savoirfairelinux.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=kernel@savoirfairelinux.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nsekhar@ti.com \
    /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.