From: Kishon Vijay Abraham I <kishon@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Paul Walmsley <paul@pwsan.com>,
bhelgaas@google.com, richardcochran@gmail.com, s-anna@ti.com,
Russell King <linux@arm.linux.org.uk>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, bcousson@baylibre.com,
nsekhar@ti.com
Subject: Re: [PATCH 0/3] omap: hwmod: add default reset handling support
Date: Tue, 9 Feb 2016 10:43:22 +0530 [thread overview]
Message-ID: <56B97572.6080100@ti.com> (raw)
In-Reply-To: <20160208204446.GC19432@atomide.com>
Hi Tony,
On Tuesday 09 February 2016 02:14 AM, Tony Lindgren wrote:
> Hi Kishon,
>
> * Kishon Vijay Abraham I <kishon@ti.com> [160208 03:13]:
>> Add a new hwmod flag to indicate custom reset handling and use it
>> for devices that require custom reset handling (like dsp, ipu, iva).
>>
>> Tested PCIe on dra7-evm and dra72-evm.
>> I need help in testing DSP, IPU, IVA, PRU, GFX, M3 in other platforms.
>> Or a way to test these cores to see if reset is not broken. Suman?
>>
>> I'll post this series once again after performing these tests.
>
> Do we also still need to patch something in the pcie driver too
> or can all that be left out now?
With this series changes in PCIe driver is not required at all.
Thanks
Kishon
>
> Regards,
>
> Tony
>
>
>> Paul Walmsley (3):
>> ARM: omap2+: omap_hwmod: introduce hwmod flag for custom reset
>> handling
>> ARM: OMAP2+: hwmod: use HWMOD_CUSTOM_HARDRESET for custom reset
>> handling
>> ARM: OMAP2+: hwmod: Add default reset handling
>>
>> arch/arm/mach-omap2/omap_hwmod.c | 16 +++++++++++-----
>> arch/arm/mach-omap2/omap_hwmod.h | 12 ++++++++++++
>> arch/arm/mach-omap2/omap_hwmod_2420_data.c | 2 ++
>> arch/arm/mach-omap2/omap_hwmod_2430_data.c | 1 +
>> .../mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c | 2 ++
>> arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 1 +
>> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 3 +++
>> arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 1 +
>> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 6 ++++++
>> arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 2 ++
>> 10 files changed, 41 insertions(+), 5 deletions(-)
>>
>> --
>> 1.7.9.5
>>
next prev parent reply other threads:[~2016-02-09 5:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 11:12 [PATCH 0/3] omap: hwmod: add default reset handling support Kishon Vijay Abraham I
2016-02-08 11:12 ` [PATCH 1/3] ARM: omap2+: omap_hwmod: introduce hwmod flag for custom reset handling Kishon Vijay Abraham I
2016-02-08 11:12 ` [RFT PATCH 2/3] ARM: OMAP2+: hwmod: use HWMOD_CUSTOM_HARDRESET " Kishon Vijay Abraham I
2016-02-08 11:12 ` [PATCH 3/3] ARM: OMAP2+: hwmod: Add default " Kishon Vijay Abraham I
2016-02-08 20:44 ` [PATCH 0/3] omap: hwmod: add default reset handling support Tony Lindgren
2016-02-09 5:13 ` Kishon Vijay Abraham I [this message]
2016-02-09 15:58 ` Tony Lindgren
2016-02-08 21:07 ` Suman Anna
2016-02-09 5:17 ` Kishon Vijay Abraham I
2016-02-09 17:44 ` Suman Anna
2016-02-09 20:19 ` Dave Gerlach
2016-02-09 21:34 ` Paul Walmsley
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=56B97572.6080100@ti.com \
--to=kishon@ti.com \
--cc=bcousson@baylibre.com \
--cc=bhelgaas@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nsekhar@ti.com \
--cc=paul@pwsan.com \
--cc=richardcochran@gmail.com \
--cc=s-anna@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).