Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Suman Anna <s-anna@ti.com>
To:     Herbert Xu <herbert@gondor.apana.org.au>,
        "David S. Miller" <davem@davemloft.net>
CC:     Deepak Saxena <dsaxena@plexity.net>,
        Tero Kristo <kristo@kernel.org>, Keerthy <j-keerthy@ti.com>,
        Gowtham Tammana <g-tammana@ti.com>,
        Vaibhav Gupta <v_gupta@ti.com>, <linux-crypto@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>, Suman Anna <s-anna@ti.com>
Subject: [PATCH 0/6] Misc. SA2UL fixes/cleanups
Date:   Fri, 14 May 2021 11:12:40 -0500
Message-ID: <20210514161246.22517-1-s-anna@ti.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain
Precedence: bulk

Hi All,

The following series includes various fixes for multiple minor
cleanup issues on failure paths in the TI K3 SA2UL Crypto driver.
The patches are all based on top of 5.13-rc1.

Patch 1 is the only non SA2UL patch, and allows the OMAP RNG driver
to be built for K3 platforms and probed properly when SA2UL is
selected, and the SA2UL driver is probed (the rng device is a child
of the sa2ul device).

regards
Suman

Suman Anna (6):
  hwrng: omap - Enable driver for TI K3 family
  crypto: sa2ul - Fix leaks on failure paths with sa_dma_init()
  crypto: sa2ul - Fix pm_runtime enable in sa_ul_probe()
  crypto: sa2ul - Use of_device_get_match_data() helper
  crypto: sa2ul - Use devm_platform_ioremap_resource()
  crypto: sa2ul - Remove child devices in remove

 drivers/char/hw_random/Kconfig |  2 +-
 drivers/crypto/sa2ul.c         | 46 ++++++++++++++++++----------------
 2 files changed, 25 insertions(+), 23 deletions(-)

-- 
2.30.1