From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
David Lechner <david@lechnology.com>,
Kevin Hilman <khilman@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Sekhar Nori <nsekhar@ti.com>,
devicetree <devicetree@vger.kernel.org>,
linux-remoteproc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
linux-clk@vger.kernel.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 0/8] ARM: davinci: complete the conversion to using the reset framework
Date: Fri, 23 Mar 2018 17:55:47 +0100 [thread overview]
Message-ID: <CAMRc=MfEebDk4D=t-ybRgbn+HaY7RUfOFCDAf9H8F3cZRchJmA@mail.gmail.com> (raw)
In-Reply-To: <152182378792.178046.3747112581117251857@swboyd.mtv.corp.google.com>
2018-03-23 17:49 GMT+01:00 Stephen Boyd <sboyd@kernel.org>:
> Quoting Bartosz Golaszewski (2018-03-23 06:04:47)
>> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>
>> This series converts the only user of the handcoded, mach-specific reset
>> routines in the davinci platform to using the reset framework.
>>
>> Patch 1 modifies the way lookup entries are registered with the reset
>> framework.
>>
>> Patches 2-4 add necessary lookups/DT-properties.
>>
>> Patches 5-7 convert the davinci-rproc driver to the reset framework.
>>
>> Patch 8 removes now dead code.
>>
>> Philipp: it turned out that it's indeed better to use the reset
>> controller's device name for the entry lookup.
>>
>> Tested both in DT and legacy modes by booting the examples from
>> ti-ipc-rtos recipe in meta-ti.
>>
>> This series applies on top of David Lechner's common-clk-v9 branch[1]
>> with Philipp Zabel's reset/next branch[2] pulled in.
>>
>> It can be found in my github tree as well[3].
>>
>
> What's the merge strategy for the rest of the patches? I should apply
> the clk ones after the next -rc1?
Or maybe Philipp can provide us with an immutable branch with the reset patches?
The you could apply the driver patches and let Sekhar take all the
platform code?
Best regards,
Bartosz Golaszewski
WARNING: multiple messages have this Message-ID (diff)
From: brgl@bgdev.pl (Bartosz Golaszewski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/8] ARM: davinci: complete the conversion to using the reset framework
Date: Fri, 23 Mar 2018 17:55:47 +0100 [thread overview]
Message-ID: <CAMRc=MfEebDk4D=t-ybRgbn+HaY7RUfOFCDAf9H8F3cZRchJmA@mail.gmail.com> (raw)
In-Reply-To: <152182378792.178046.3747112581117251857@swboyd.mtv.corp.google.com>
2018-03-23 17:49 GMT+01:00 Stephen Boyd <sboyd@kernel.org>:
> Quoting Bartosz Golaszewski (2018-03-23 06:04:47)
>> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>
>> This series converts the only user of the handcoded, mach-specific reset
>> routines in the davinci platform to using the reset framework.
>>
>> Patch 1 modifies the way lookup entries are registered with the reset
>> framework.
>>
>> Patches 2-4 add necessary lookups/DT-properties.
>>
>> Patches 5-7 convert the davinci-rproc driver to the reset framework.
>>
>> Patch 8 removes now dead code.
>>
>> Philipp: it turned out that it's indeed better to use the reset
>> controller's device name for the entry lookup.
>>
>> Tested both in DT and legacy modes by booting the examples from
>> ti-ipc-rtos recipe in meta-ti.
>>
>> This series applies on top of David Lechner's common-clk-v9 branch[1]
>> with Philipp Zabel's reset/next branch[2] pulled in.
>>
>> It can be found in my github tree as well[3].
>>
>
> What's the merge strategy for the rest of the patches? I should apply
> the clk ones after the next -rc1?
Or maybe Philipp can provide us with an immutable branch with the reset patches?
The you could apply the driver patches and let Sekhar take all the
platform code?
Best regards,
Bartosz Golaszewski
next prev parent reply other threads:[~2018-03-23 16:55 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 13:04 [PATCH v4 0/8] ARM: davinci: complete the conversion to using the reset framework Bartosz Golaszewski
2018-03-23 13:04 ` Bartosz Golaszewski
2018-03-23 13:04 ` [PATCH v4 1/8] reset: modify the way reset lookup works for board files Bartosz Golaszewski
2018-03-23 13:04 ` Bartosz Golaszewski
2018-03-23 13:43 ` Philipp Zabel
2018-03-23 13:43 ` Philipp Zabel
2018-03-23 13:43 ` Philipp Zabel
2018-03-23 13:46 ` Bartosz Golaszewski
2018-03-23 13:46 ` Bartosz Golaszewski
2018-03-23 13:04 ` [PATCH v4 2/8] ARM: davinci: dts: make psc0 a reset provider Bartosz Golaszewski
2018-03-23 13:04 ` Bartosz Golaszewski
2018-03-23 13:04 ` [PATCH v4 3/8] ARM: davinci: dts: add a reset control to the dsp node Bartosz Golaszewski
2018-03-23 13:04 ` Bartosz Golaszewski
2018-03-23 13:04 ` [PATCH v4 4/8] clk: davinci: add a reset lookup table for psc0 Bartosz Golaszewski
2018-03-23 13:04 ` Bartosz Golaszewski
2018-03-23 13:04 ` [PATCH v4 5/8] remoteproc: da8xx: add the missing retval check for clk_enable() Bartosz Golaszewski
2018-03-23 13:04 ` Bartosz Golaszewski
2018-03-23 13:04 ` Bartosz Golaszewski
2018-03-26 21:15 ` Suman Anna
2018-03-26 21:15 ` Suman Anna
2018-03-26 21:15 ` Suman Anna
2018-03-23 13:04 ` [PATCH v4 6/8] remoteproc: da8xx: prepare and unprepare the clock where needed Bartosz Golaszewski
2018-03-23 13:04 ` Bartosz Golaszewski
2018-03-26 21:19 ` Suman Anna
2018-03-26 21:19 ` Suman Anna
2018-03-26 21:19 ` Suman Anna
2018-03-26 21:19 ` Suman Anna
2018-03-23 13:04 ` [PATCH v4 7/8] remoteproc: da8xx: use the reset framework Bartosz Golaszewski
2018-03-23 13:04 ` Bartosz Golaszewski
2018-03-26 21:28 ` Suman Anna
2018-03-26 21:28 ` Suman Anna
2018-03-26 21:28 ` Suman Anna
2018-03-23 13:04 ` [PATCH v4 8/8] clk: davinci: kill davinci_clk_reset_assert/deassert() Bartosz Golaszewski
2018-03-23 13:04 ` Bartosz Golaszewski
2018-03-23 16:49 ` [PATCH v4 0/8] ARM: davinci: complete the conversion to using the reset framework Stephen Boyd
2018-03-23 16:49 ` Stephen Boyd
2018-03-23 16:49 ` Stephen Boyd
2018-03-23 16:55 ` Bartosz Golaszewski [this message]
2018-03-23 16:55 ` Bartosz Golaszewski
2018-03-23 17:08 ` Stephen Boyd
2018-03-23 17:08 ` Stephen Boyd
2018-03-23 17:08 ` Stephen Boyd
2018-03-23 17:16 ` Bartosz Golaszewski
2018-03-23 17:16 ` Bartosz Golaszewski
2018-03-24 0:30 ` Suman Anna
2018-03-24 0:30 ` Suman Anna
2018-03-24 0:30 ` Suman Anna
2018-03-24 0:30 ` Suman Anna
2018-03-27 0:42 ` Suman Anna
2018-03-27 0:42 ` Suman Anna
2018-03-27 0:42 ` Suman Anna
2018-03-27 0:42 ` Suman Anna
2018-03-27 5:24 ` Sekhar Nori
2018-03-27 5:24 ` Sekhar Nori
2018-03-27 5:24 ` Sekhar Nori
2018-03-27 5:24 ` Sekhar Nori
2018-03-28 22:44 ` Suman Anna
2018-03-28 22:44 ` Suman Anna
2018-03-28 22:44 ` Suman Anna
2018-03-27 6:09 ` Sekhar Nori
2018-03-27 6:09 ` Sekhar Nori
2018-03-27 6:09 ` Sekhar Nori
2018-03-27 6:09 ` Sekhar Nori
2018-03-27 9:23 ` Philipp Zabel
2018-03-27 9:23 ` Philipp Zabel
2018-03-27 9:23 ` Philipp Zabel
2018-03-27 9:29 ` Bartosz Golaszewski
2018-03-27 9:29 ` Bartosz Golaszewski
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='CAMRc=MfEebDk4D=t-ybRgbn+HaY7RUfOFCDAf9H8F3cZRchJmA@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=bgolaszewski@baylibre.com \
--cc=bjorn.andersson@linaro.org \
--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=nsekhar@ti.com \
--cc=ohad@wizery.com \
--cc=p.zabel@pengutronix.de \
--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 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.