From: Laxman Dewangan <ldewangan@nvidia.com>
To: <thierry.reding@gmail.com>, <swarren@wwwdotorg.org>
Cc: <gnurou@gmail.com>, <jonathanh@nvidia.com>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 0/4] soc/tegra: pmc: Add support for IO pad configuration and sub-driver
Date: Tue, 22 Nov 2016 17:02:09 +0530 [thread overview]
Message-ID: <58342CB9.6040203@nvidia.com> (raw)
In-Reply-To: <1478696962-11831-1-git-send-email-ldewangan@nvidia.com>
Thierry,
On Wednesday 09 November 2016 06:39 PM, Laxman Dewangan wrote:
> Tegra SoC support the configutaion of IO pads to multi-level voltage
> and low power state. The conifguration is done via pictrl framework
> and the io pad driver in pinctrl frameowrk uses the APIs from pmc to
> access PMC registers.
>
> his series add the API to get the IO pad power status and register
> the pmc child devices like IO pad drvier.
>
> The patches were send earlier part of different series but applied
> partially in the Thierry's t186 branch
> https://github.com/thierryreding/linux/tree/tegra186.
>
> Resending the patches as the new start to avoid any confusion.
> This need to be applied in
> https://github.com/thierryreding/linux/tree/tegra186
>
Any comment on this?
I saw that your patches are available from t186 branch to linux-next.
Do I need to re-send the patches on top of linux-next?
prev parent reply other threads:[~2016-11-22 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 13:09 Laxman Dewangan
2016-11-09 13:09 ` [PATCH V2 1/4] soc/tegra: pmc: Remove legacy Tegra I/O rail API Laxman Dewangan
2016-11-09 13:09 ` [PATCH V2 2/4] soc/tegra: pmc: Add interface to get IO pad power status Laxman Dewangan
2016-11-09 13:09 ` [PATCH V2 3/4] soc/tegra: pmc: Register PMC child devices as platform device Laxman Dewangan
2016-11-09 13:09 ` [PATCH V2 4/4] soc/tegra: pmc: Make configuration of IO pads in atomic context Laxman Dewangan
2016-11-22 11:32 ` Laxman Dewangan [this message]
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=58342CB9.6040203@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=gnurou@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome