public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: ldewangan@nvidia•com (Laxman Dewangan)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/3] ARM: dt: tegra: seaboard: add regulators
Date: Tue, 10 Jul 2012 19:14:53 +0530	[thread overview]
Message-ID: <4FFC31D5.7090600@nvidia.com> (raw)
In-Reply-To: <20120710134436.GD9409@opensource.wolfsonmicro.com>

On Tuesday 10 July 2012 07:14 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Tue, Jul 10, 2012 at 05:29:06PM +0530, Laxman Dewangan wrote:
>
>> Looked tps6586x-regulator driver and it has the platform data which
>> is regulator_init_data.
>> So for adding the vin-supply similar to what we have in fixed or
>> tps6591x regulator to pass through the desc.supply_name, we are not
>> having option here in platform data which can work for DT and non-DT
>> case.
>> So if still want to have the DT and non-DT case similar, we can add
>> one tps6586x_regulator_platform_data as
> The supply names are not supposed to be conditional (I realise they are
> for your current DT patch, I let that in because I just want to see an
> end to all this DT stuff).
>

Sorry, I did not get it fully. I had two patches, one for fixed one and 
other for tps65910. On which patch, you are seeing issue and which part 
of code?
I like to fix it if it does not conform the DT or your expectation or 
any future enhancement which you are planning.
Little bit more details will help so that I will not repeat the same and 
fix it in my future patches.

Thanks,
Laxman

  reply	other threads:[~2012-07-10 13:44 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 23:14 [PATCH 1/3] ARM: dt: tegra: seaboard: add regulators Stephen Warren
2012-06-22 23:14 ` [PATCH 2/3] ARM: dt: tegra: ventana: " Stephen Warren
2012-06-22 23:14 ` [PATCH 3/3] ARM: dt: tegra: paz00: " Stephen Warren
2012-06-23 16:35   ` Marc Dietrich
2012-06-24 11:03     ` Mark Brown
2012-06-24 12:01       ` Marc Dietrich
2012-06-24 12:31         ` Mark Brown
2012-06-24 13:27           ` Marc Dietrich
2012-06-25  8:46             ` Mark Brown
2012-06-25 10:45               ` Marc Dietrich
2012-06-25 11:07             ` Thierry Reding
2012-06-26 22:35       ` Stephen Warren
2012-06-26 23:02         ` Mark Brown
2012-06-26 23:16           ` Stephen Warren
2012-06-29 17:32           ` Stephen Warren
2012-06-30 11:45             ` Mark Brown
2012-06-25  6:24 ` [PATCH 1/3] ARM: dt: tegra: seaboard: " Laxman Dewangan
2012-06-25 15:12   ` Stephen Warren
2012-06-25 15:24     ` Laxman Dewangan
2012-06-25 15:36       ` Stephen Warren
2012-06-25 22:26       ` Mark Brown
2012-06-25 23:09         ` Stephen Warren
2012-06-26  6:38           ` Laxman Dewangan
2012-06-26  8:52           ` Mark Brown
2012-07-10 11:59           ` Laxman Dewangan
2012-07-10 13:44             ` Mark Brown
2012-07-10 13:44               ` Laxman Dewangan [this message]
2012-07-10 13:53                 ` Mark Brown
2012-07-10 15:04                   ` Laxman Dewangan
2012-07-10 15:42                     ` Mark Brown
2012-07-10 16:39                       ` Laxman Dewangan
2012-07-10 16:52                         ` Mark Brown
2012-07-10 16:53                           ` Laxman Dewangan
2012-07-10 17:01                             ` Mark Brown
2012-07-11 10:02                               ` Laxman Dewangan

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=4FFC31D5.7090600@nvidia.com \
    --to=ldewangan@nvidia$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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