linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s-anna@ti.com (Suman Anna)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Cleanup legacy OMAP IOMMU device creation
Date: Thu, 22 Oct 2015 12:15:55 -0500	[thread overview]
Message-ID: <562919CB.1000606@ti.com> (raw)
In-Reply-To: <1442447302-5246-1-git-send-email-s-anna@ti.com>

Hi Tony,

On 09/16/2015 06:48 PM, Suman Anna wrote:
> Hi Tony,
> 
> The following series removes the legacy platform device creation
> logic for OMAP IOMMU devices. I will cleanup the legacy support
> from the OMAP IOMMU driver in a subsequent merge window after
> this series makes it to mainline.
> 
> Patches are based on 4.3-rc1 + the OMAP3 ISP instantiation cleanup
> patch [1]. All the patches need to be picked up sequentially,
> otherwise a NULL pointer dereference crash might be seen on OMAP3
> legacy boots as the dev attribute structure is deferenced directly
> in mach-omap2/omap-iommu.c during platform data creation. Also, the
> last patch removes the structure definition altogether, so will
> cause build issues if picked separately from the hwmod cleanup
> patches.
> 
> I do not have any boards where I can still perform a legacy-style
> boot, so patches verified using DT-boot only.
> 
> regards
> Suman
> 
> [1] https://patchwork.kernel.org/patch/6806891/
> 
> Suman Anna (4):
>   ARM: OMAP2+: Remove legacy device instantiation of IOMMUs
>   ARM: OMAP3: hwmod data: Remove legacy IOMMU data
>   ARM: OMAP4: hwmod data: Remove legacy IOMMU attr and addrs
>   ARM: OMAP2+: Remove omap_mmu_dev_attr structure

Ping on this series. You should be able to pick up atleast patch 1 if
not picking all, now that the OMAP3 ISP cleanup patch is staged in your
omap-for-4.4/cleanup branch.

Thanks
Suman

> 
>  arch/arm/mach-omap2/omap-iommu.c           | 66 ------------------------------
>  arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 42 -------------------
>  arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 31 --------------
>  include/linux/platform_data/iommu-omap.h   |  9 ----
>  4 files changed, 148 deletions(-)
>  delete mode 100644 arch/arm/mach-omap2/omap-iommu.c
> 

  parent reply	other threads:[~2015-10-22 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16 23:48 [PATCH 0/4] Cleanup legacy OMAP IOMMU device creation Suman Anna
2015-09-16 23:48 ` [PATCH 1/4] ARM: OMAP2+: Remove legacy device instantiation of IOMMUs Suman Anna
2015-09-16 23:48 ` [PATCH 2/4] ARM: OMAP3: hwmod data: Remove legacy IOMMU data Suman Anna
2015-09-16 23:48 ` [PATCH 3/4] ARM: OMAP4: hwmod data: Remove legacy IOMMU attr and addrs Suman Anna
2015-09-16 23:48 ` [PATCH 4/4] ARM: OMAP2+: Remove omap_mmu_dev_attr structure Suman Anna
2015-10-22 17:15 ` Suman Anna [this message]
2015-11-30 18:34   ` [PATCH 0/4] Cleanup legacy OMAP IOMMU device creation Tony Lindgren

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=562919CB.1000606@ti.com \
    --to=s-anna@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).