From: s-anna@ti•com (Suman Anna)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/3] omap: hwmod: add default reset handling support
Date: Mon, 8 Feb 2016 15:07:08 -0600 [thread overview]
Message-ID: <56B9037C.2050203@ti.com> (raw)
In-Reply-To: <1454929941-23949-1-git-send-email-kishon@ti.com>
On 02/08/2016 05:12 AM, Kishon Vijay Abraham I wrote:
> 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 won't be able to test this week, and have requested Dave to check on
wkup_m3_rproc driver atleast. I see one potential issue (see my commment
on the other thread), but can confirm that only after testing.
Have you tested multiple probe/removal sequences? Can you check the
return status on the _hardreset_deassert call with your PCIe driver,
believe even that one would return an error on multiple probes.
regards
Suman
>
> I'll post this series once again after performing these tests.
>
> 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(-)
>
next prev parent reply other threads:[~2016-02-08 21:07 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
2016-02-09 15:58 ` Tony Lindgren
2016-02-08 21:07 ` Suman Anna [this message]
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=56B9037C.2050203@ti.com \
--to=s-anna@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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