forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge series "Add Renesas RPC-IF support" from Sergei Shtylyov <serge…
…i.shtylyov@cogentembedded.com>: Hello! Here's a set of 2 patches against Linus' repo. Renesas Reduced Pin Count Interface (RPC-IF) allows a SPI flash or HyperFlash connected to the SoC to be accessed via the external address space read mode or the manual mode. The memory controller driver for RPC-IF registers either SPI or HyperFLash subdevice, depending on the contents of the device tree subnode; it also provides the abstract "back end" API that can be used by the "front end" SPI/MTD drivers to talk to the real hardware... Based on the original patch by Mason Yang <masonccyang@mxic.com.tw>. [1/2] dt-bindings: memory: document Renesas RPC-IF bindings [2/2] memory: add Renesas RPC-IF driver MBR, Sergei
- Loading branch information
Showing
5 changed files
with
788 additions
and
0 deletions.
There are no files selected for viewing
88 changes: 88 additions & 0 deletions
88
Documentation/devicetree/bindings/memory-controllers/renesas,rpc-if.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,88 @@ | ||
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) | ||
%YAML 1.2 | ||
--- | ||
$id: http://devicetree.org/schemas/memory-controllers/renesas,rpc-if.yaml# | ||
$schema: http://devicetree.org/meta-schemas/core.yaml# | ||
|
||
title: Renesas Reduced Pin Count Interface (RPC-IF) | ||
|
||
maintainers: | ||
- Sergei Shtylyov <sergei.shtylyov@gmail.com> | ||
|
||
description: | | ||
Renesas RPC-IF allows a SPI flash or HyperFlash connected to the SoC to | ||
be accessed via the external address space read mode or the manual mode. | ||
The flash chip itself should be represented by a subnode of the RPC-IF node. | ||
The flash interface is selected based on the "compatible" property of this | ||
subnode: | ||
- if it contains "jedec,spi-nor", then SPI is used; | ||
- if it contains "cfi-flash", then HyperFlash is used. | ||
allOf: | ||
- $ref: "/schemas/spi/spi-controller.yaml#" | ||
|
||
properties: | ||
compatible: | ||
items: | ||
- enum: | ||
- renesas,r8a77970-rpc-if # R-Car V3M | ||
- renesas,r8a77980-rpc-if # R-Car V3H | ||
- renesas,r8a77995-rpc-if # R-Car D3 | ||
- const: renesas,rcar-gen3-rpc-if # a generic R-Car gen3 device | ||
|
||
reg: | ||
items: | ||
- description: RPC-IF registers | ||
- description: direct mapping read mode area | ||
- description: write buffer area | ||
|
||
reg-names: | ||
items: | ||
- const: regs | ||
- const: dirmap | ||
- const: wbuf | ||
|
||
clocks: | ||
maxItems: 1 | ||
|
||
power-domains: | ||
maxItems: 1 | ||
|
||
resets: | ||
maxItems: 1 | ||
|
||
patternProperties: | ||
"flash@[0-9a-f]+$": | ||
type: object | ||
properties: | ||
compatible: | ||
enum: | ||
- cfi-flash | ||
- jedec,spi-nor | ||
|
||
examples: | ||
- | | ||
#include <dt-bindings/clock/renesas-cpg-mssr.h> | ||
#include <dt-bindings/power/r8a77995-sysc.h> | ||
spi@ee200000 { | ||
compatible = "renesas,r8a77995-rpc-if", "renesas,rcar-gen3-rpc-if"; | ||
reg = <0xee200000 0x200>, | ||
<0x08000000 0x4000000>, | ||
<0xee208000 0x100>; | ||
reg-names = "regs", "dirmap", "wbuf"; | ||
clocks = <&cpg CPG_MOD 917>; | ||
power-domains = <&sysc R8A77995_PD_ALWAYS_ON>; | ||
resets = <&cpg 917>; | ||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
flash@0 { | ||
compatible = "jedec,spi-nor"; | ||
reg = <0>; | ||
spi-max-frequency = <40000000>; | ||
spi-tx-bus-width = <1>; | ||
spi-rx-bus-width = <1>; | ||
}; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.