All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: <linux-omap@vger.kernel.org>, <tony@atomide.com>
Cc: <linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/8] ARM: omap4/5: crypto support fixes
Date: Wed, 29 Apr 2020 17:29:54 +0300	[thread overview]
Message-ID: <20200429143002.5050-1-t-kristo@ti.com> (raw)

Hi,

This series fixes a couple of crypto data bugs for omap4/5. It also adds
support for crypto accelerators for omap5; the data for these is just
basically copied over from omap4.

OMAP5 currently appears to be running out of available DMA channels,
SPI/MMC are allocating a huge number of channels permanently in boot and
there are only 32 of them available in total. To mitigate the issue
partly, I have left the DES node disabled by default to save two
channels, if someone needs DES support, it can be easily enabled.
However, it might be useful to actually disable some of the SPI/MMC
nodes to save on the number of channels and to avoid running into any
problems.

-Tero


--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

WARNING: multiple messages have this Message-ID (diff)
From: Tero Kristo <t-kristo@ti.com>
To: <linux-omap@vger.kernel.org>, <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] ARM: omap4/5: crypto support fixes
Date: Wed, 29 Apr 2020 17:29:54 +0300	[thread overview]
Message-ID: <20200429143002.5050-1-t-kristo@ti.com> (raw)

Hi,

This series fixes a couple of crypto data bugs for omap4/5. It also adds
support for crypto accelerators for omap5; the data for these is just
basically copied over from omap4.

OMAP5 currently appears to be running out of available DMA channels,
SPI/MMC are allocating a huge number of channels permanently in boot and
there are only 32 of them available in total. To mitigate the issue
partly, I have left the DES node disabled by default to save two
channels, if someone needs DES support, it can be easily enabled.
However, it might be useful to actually disable some of the SPI/MMC
nodes to save on the number of channels and to avoid running into any
problems.

-Tero


--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2020-04-29 14:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29 14:29 Tero Kristo [this message]
2020-04-29 14:29 ` [PATCH 0/8] ARM: omap4/5: crypto support fixes Tero Kristo
2020-04-29 14:29 ` [PATCH 1/8] ARM: dts: omap4: fix node names for the l4_cm clkctrl nodes Tero Kristo
2020-04-29 14:29   ` Tero Kristo
2020-04-29 22:07   ` Tony Lindgren
2020-04-29 22:07     ` Tony Lindgren
2020-04-30  4:55     ` Tero Kristo
2020-04-30  4:55       ` Tero Kristo
2020-04-30  8:34       ` Tero Kristo
2020-04-30  8:34         ` Tero Kristo
2020-04-30 20:25         ` Tony Lindgren
2020-04-30 20:25           ` Tony Lindgren
2020-05-05 18:21           ` Tony Lindgren
2020-05-05 18:21             ` Tony Lindgren
2020-04-29 14:29 ` [PATCH 2/8] ARM: dts: omap5: " Tero Kristo
2020-04-29 14:29   ` Tero Kristo
2020-04-29 14:29 ` [PATCH 3/8] ARM: dts: omap5: add aes1 entry Tero Kristo
2020-04-29 14:29   ` Tero Kristo
2020-04-29 14:29 ` [PATCH 4/8] ARM: dts: omap5: add aes2 entry Tero Kristo
2020-04-29 14:29   ` Tero Kristo
2020-04-29 14:29 ` [PATCH 5/8] ARM: dts: omap5: add SHA crypto accelerator node Tero Kristo
2020-04-29 14:29   ` Tero Kristo
2020-04-29 14:30 ` [PATCH 6/8] ARM: dts: omap5: add DES " Tero Kristo
2020-04-29 14:30   ` Tero Kristo
2020-04-29 14:30 ` [PATCH 7/8] ARM: OMAP4: Make L4SEC clock domain SWSUP only Tero Kristo
2020-04-29 14:30   ` Tero Kristo
2020-04-29 14:30 ` [PATCH 8/8] ARM: OMAP5: " Tero Kristo
2020-04-29 14:30   ` Tero Kristo

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=20200429143002.5050-1-t-kristo@ti.com \
    --to=t-kristo@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --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 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.