public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Gautam <vivek.gautam@codeaurora.org>
To: Jon Hunter <jonathanh@nvidia.com>,
	p.zabel@pengutronix.de, swarren@wwwdotorg.org, balbi@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-usb@vger.kernel.org, thierry.reding@gmail.com,
	gregkh@linuxfoundation.org, linux-arm-msm@vger.kernel.org,
	Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH V3 4/4] soc/tegra: pmc: Use the new reset APIs to manage reset controllers
Date: Tue, 25 Apr 2017 09:45:48 +0530	[thread overview]
Message-ID: <afcddcbe-7086-2739-6de2-84f5c1d34374@codeaurora.org> (raw)
In-Reply-To: <e87a846b-4bbf-03cf-f3a6-99d5e468425c@nvidia.com>



On 04/24/2017 06:15 PM, Jon Hunter wrote:
> On 18/04/17 12:21, Vivek Gautam wrote:
>> Make use of reset_control_array_*() set of APIs to manage
>> an array of reset controllers available with the device.
> Before we apply this patch, I need to check to see if the order of the
> resets managed by the PMC driver matter. Today the order of the resets
> is determined by the order they appear in the DT node and although the
> new APIs work in the same way they do not guarantee this. So let me
> check to see if we can any concerns about ordering here. Otherwise would
> be nice to use these APIs.

Right, that will be perfect.

Best regards
Vivek

>
> Cheers
> Jon
>

-- 
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2017-04-25  4:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 11:21 [PATCH V3 0/4] reset: APIs to manage a list of resets Vivek Gautam
2017-04-18 11:21 ` [PATCH V3 1/4] reset: Add API to count number of reset available with device Vivek Gautam
     [not found]   ` <1492514488-27385-2-git-send-email-vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-04-19 10:25     ` Philipp Zabel
     [not found]       ` <1492597532.2970.61.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-04-19 11:49         ` Vivek Gautam
2017-04-18 11:21 ` [PATCH V3 2/4] reset: Add APIs to manage array of resets Vivek Gautam
2017-04-19 10:31   ` Philipp Zabel
     [not found]     ` <1492597912.2970.65.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-04-19 11:55       ` Vivek Gautam
2017-04-18 11:21 ` [PATCH V3 3/4] usb: dwc3: of-simple: Add support to get resets for the device Vivek Gautam
     [not found]   ` <1492514488-27385-4-git-send-email-vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-04-19 10:32     ` Philipp Zabel
2017-04-19 12:02       ` Vivek Gautam
2017-04-18 11:21 ` [PATCH V3 4/4] soc/tegra: pmc: Use the new reset APIs to manage reset controllers Vivek Gautam
2017-04-19 10:40   ` Philipp Zabel
     [not found]   ` <1492514488-27385-5-git-send-email-vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-04-24 12:45     ` Jon Hunter
2017-04-25  4:15       ` Vivek Gautam [this message]
     [not found]         ` <afcddcbe-7086-2739-6de2-84f5c1d34374-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-04-25 10:05           ` Jon Hunter
     [not found]             ` <b3f2cbe5-4a1a-2f7b-2e4a-6a06eeadc890-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-04-25 10:33               ` Philipp Zabel
2017-04-25 10:54                 ` Jon Hunter
     [not found]                   ` <afdb02e5-9299-fec9-9451-8271c220744b-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-04-25 11:06                     ` Vivek Gautam
     [not found]                       ` <5e0c2030-ad96-15fc-1dc4-db6cd11d52c3-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-04-25 11:11                         ` Jon Hunter
     [not found]                           ` <ff663727-dcdf-b3e7-616d-5e770d32d782-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-04-25 17:50                             ` Vivek Gautam

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=afcddcbe-7086-2739-6de2-84f5c1d34374@codeaurora.org \
    --to=vivek.gautam@codeaurora.org \
    --cc=balbi@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@gmail.com \
    --cc=treding@nvidia.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