All of lore.kernel.org
 help / color / mirror / Atom feed
From: monstr@monstr.eu (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] ARM: zynq: Add OCM controller driver
Date: Wed, 05 Nov 2014 09:36:28 +0100	[thread overview]
Message-ID: <5459E18C.1030502@monstr.eu> (raw)
In-Reply-To: <e65e39088e0f571ee4905172f2f6c84dbc037805.1412599051.git.michal.simek@xilinx.com>

Hi Arnd and Olof,

On 10/06/2014 02:38 PM, Michal Simek wrote:
> The driver provide memory allocator which can
> be used by others drivers to allocate memory inside OCM.
> All location for 64kB blocks are supported
> and driver is trying to allocate the largest continuous
> block of memory.
> 
> Checking mpcore addressing filterring is not done here
> but could be added in future.
> 
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> ---
> 
> Changes in v3:
> - Move OCM to drivers/soc
> - Update year
> - Extract DTS node to be able to apply it out of driver
> - Remove generic allocator enabling
> - Extract SLCR part
> - Use const in of_device_id
> - OCM->OCMC
> - Use ocmc-1.0 compatible string
> 
> Changes in v2:
> - Change compatibility string to be in xilinx format
> - Fix kernel-doc format
> 
> For everybody on-chip SRAM driver "mmio-sram"
> is missing parity IRQ handling not sure how to write
> in generic way and also the memory layout
> can be changed at run time (not currently supported by this driver)
> 
> smp-sram trampoline allocation can be used from mmio-sram
> and size allocated via DT but currently no reason for using
> it.
> 
> Creating mmio-sram node with setting at run time based on current setting
> is possible but it won't look good.
> One way how to do it is here
> "ARM: mvebu: Add quirk for i2c for the OpenBlocks AX3-4 board"
> (sha1: 85e618a1be2b2092318178d1d66bdad49cbbeeeb)
> but creating nodes at run-time or changing compact strings
> will be just more hacky code.
> 
> ---
>  .../bindings/arm/zynq/xlnx,zynq-ocmc.txt           |  17 ++
>  drivers/soc/Makefile                               |   1 +
>  drivers/soc/zynq/Makefile                          |   1 +
>  drivers/soc/zynq/zynq_ocmc.c                       | 246 +++++++++++++++++++++
>  4 files changed, 265 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/arm/zynq/xlnx,zynq-ocmc.txt
>  create mode 100644 drivers/soc/zynq/Makefile
>  create mode 100644 drivers/soc/zynq/zynq_ocmc.c
> 

Can you please review this OCM patch?
I would like to move it when I know how I should handle that slcr connection
and reserving trampoline size.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141105/c1ea3b22/attachment.sig>

      parent reply	other threads:[~2014-11-05  8:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06 12:38 [PATCH v3 1/2] ARM: zynq: Add OCM controller driver Michal Simek
2014-10-06 12:38 ` Michal Simek
2014-10-06 12:38 ` Michal Simek
2014-10-06 12:38 ` [PATCH v3 2/2] ARM: zynq: DT: Add OCM controller node Michal Simek
2014-10-06 12:38   ` Michal Simek
2014-10-06 16:04 ` [PATCH v3 1/2] ARM: zynq: Add OCM controller driver Sören Brinkmann
2014-10-06 16:04   ` Sören Brinkmann
2014-10-06 16:04   ` Sören Brinkmann
2014-11-05  8:36 ` Michal Simek [this message]

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=5459E18C.1030502@monstr.eu \
    --to=monstr@monstr.eu \
    --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 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.