From: Sekhar Nori <nsekhar@ti.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Kevin Hilman <khilman@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
David Lechner <david@lechnology.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Ohad Ben-Cohen <ohad@wizery.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
linux-remoteproc@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v7 1/4] remoteproc/davinci: use the reset framework
Date: Tue, 31 Jul 2018 15:34:33 +0530 [thread overview]
Message-ID: <c3484965-1efe-2425-86e0-ecb78ea189dd@ti.com> (raw)
In-Reply-To: <CAMRc=MdwCruRZ_EQ3Pzq-=HdhiA6pfSZczRKMa5i9Rju0JgHig@mail.gmail.com>
Bjorn,
On Tuesday 31 July 2018 01:25 PM, Bartosz Golaszewski wrote:
> 2018-07-31 6:25 GMT+02:00 Bjorn Andersson <bjorn.andersson@linaro.org>:
>> On Thu 21 Jun 00:37 PDT 2018, Bartosz Golaszewski wrote:
>>
>>> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>>
>>> Switch to using the reset framework instead of handcoded reset routines
>>> we used so far.
>>>
>>> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>> Reviewed-by: Sekhar Nori <nsekhar@ti.com>
>>> Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
>>
>> Acked-by: Bjorn Andersson <bjorn.andersson@linaro.org>
>>
>
> Sekhar,
>
> can you take this through your tree or is it already too late?
The last -rc is already tagged and I am not sure ARM-SoC will be open to
new stuff now (there is also a bit of lag after I send my pull request).
Is this something you can take in your tree along with Suman's patch?
There are no build dependencies with my tree, so it will be safe to
queue from your tree. It will be great if this can be merged late in the
cycle though to avoid breaking remoteproc even for short while during
the merge window.
Or if you okay with it, it will be safest to send it soon after
v4.19-rc1 is tagged.
Let me know.
Thanks,
Sekhar
next prev parent reply other threads:[~2018-07-31 10:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 7:37 [PATCH v7 0/4] ARM: davinci: complete the conversion to using the reset framework Bartosz Golaszewski
2018-06-21 7:37 ` [PATCH v7 1/4] remoteproc/davinci: use " Bartosz Golaszewski
2018-07-23 8:03 ` Bartosz Golaszewski
2018-07-31 4:25 ` Bjorn Andersson
2018-07-31 7:55 ` Bartosz Golaszewski
2018-07-31 10:04 ` Sekhar Nori [this message]
2018-06-21 7:37 ` [PATCH v7 2/4] clk: davinci: kill davinci_clk_reset_assert/deassert() Bartosz Golaszewski
2018-07-06 17:54 ` David Lechner
2018-10-02 15:08 ` Bartosz Golaszewski
2018-10-02 15:28 ` David Lechner
2018-10-02 15:54 ` Stephen Boyd
2018-06-21 7:37 ` [PATCH v7 3/4] ARM: davinci: dts: make psc0 a reset provider Bartosz Golaszewski
2018-07-02 11:57 ` Sekhar Nori
2018-06-21 7:37 ` [PATCH v7 4/4] ARM: davinci: dts: add a reset control to the dsp node Bartosz Golaszewski
2018-07-02 12:02 ` Sekhar Nori
2018-06-21 10:52 ` [PATCH v7 0/4] ARM: davinci: complete the conversion to using the reset framework Sekhar Nori
2018-06-21 11:41 ` Bartosz Golaszewski
2018-07-02 12:08 ` Sekhar Nori
2018-07-02 15:27 ` David Lechner
2018-07-03 4:42 ` Sekhar Nori
2018-07-31 4:34 ` Bjorn Andersson
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=c3484965-1efe-2425-86e0-ecb78ea189dd@ti.com \
--to=nsekhar@ti.com \
--cc=bgolaszewski@baylibre.com \
--cc=bjorn.andersson@linaro.org \
--cc=brgl@bgdev.pl \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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