drivers/soc/litex: support 32-bit subregisters, 64-bit CPUs
v4 cover drivers/soc/litex: support 32-bit subregisters, 64-bit CPUs
This series expands on commit 22447a99c97e ("drivers/soc/litex: add LiteX SoC Controller driver"), adding support for handling both 8- and 32-bit LiteX CSR (MMIO) subregisters, on both 32- and 64-bit CPUs.
Notes v4:
- improved "eloquence" of some 3/3 commit blurb paragraphs
- fixed instance of "disgusting" comment style :)
- litex_[get|set]_reg() now using size_t for 'reg_size' argument
- slightly tighter shift calculation in litex_set_reg()
Notes v3:
- split into smaller, more self-explanatory patches
- more detailed commit blurb for "main payload" (3/3) patch
- eliminate compiler warning on 32-bit architectures
Notes v2:
- fix typo (s/u32/u64/) in litex_read64().
Notes v1:
- LITEX_SUBREG_SIZE now provided by Kconfig.
- it's not LITEX_REG_SIZE, but rather LITEX_SUBREG_ALIGN!
- move litex_[get|set]_reg() to include/linux/litex.h and mark them as "static inline";
- redo litex_[read|write][8|16|32|64]() using litex_[get|set]_reg() (compiler should produce code as efficient as hardcoded shifts, but also automatically matching LITEX_SUBREG_SIZE).
Gabriel Somlo (3):
drivers/soc/litex: move generic accessors to litex.h drivers/soc/litex: separate MMIO from subregister offset calculation drivers/soc/litex: support 32-bit subregisters, 64-bit CPUs
drivers/soc/litex/Kconfig | 12 +++ drivers/soc/litex/litex_soc_ctrl.c | 76 +-------------- include/linux/litex.h | 151 +++++++++++++++++++---------- 3 files changed, 115 insertions(+), 124 deletions(-)
Signature · 1 line
2.26.2
PATCH v4 1/3 drivers/soc/litex: move generic accessors to litex.h
Move generic LiteX CSR (MMIO) register accessors to litex.h and declare them as "static inline", in preparation for supporting 32-bit CSR subregisters and 64-bit CPUs.
NOTE: this is a non-functional change.
--- drivers/soc/litex/litex_soc_ctrl.c | 73 ----------------------------- include/linux/litex.h | 74 ++++++++++++++++++++++++++++-- 2 files changed, 69 insertions(+), 78 deletions(-)
drivers/soc/litex/litex_soc_ctrl.c +0 -73
@@ -16,79 +16,6 @@#include <linux/errno.h> #include <linux/io.h> -/* -* LiteX SoC Generator, depending on the configuration, can split a single -* logical CSR (Control&Status Register) into a series of consecutive physical -* registers. -* -* For example, in the configuration with 8-bit CSR Bus, 32-bit aligned (the -* default one for 32-bit CPUs) a 32-bit logical CSR will be generated as four -* 32-bit physical registers, each one containing one byte of meaningful data. -* -* For details see: https://github.com/enjoy-digital/litex/wiki/CSR-Bus -* -* The purpose of `litex_set_reg`/`litex_get_reg` is to implement the logic -* of writing to/reading from the LiteX CSR in a single place that can be -* then reused by all LiteX drivers. -*/ - -/** -* litex_set_reg() - Writes the value to the LiteX CSR (Control&Status Register) -* @reg: Address of the CSR -* @reg_size: The width of the CSR expressed in the number of bytes -* @val: Value to be written to the CSR -* -* In the currently supported LiteX configuration (8-bit CSR Bus, 32-bit aligned), -* a 32-bit LiteX CSR is generated as 4 consecutive 32-bit physical registers, -* each one containing one byte of meaningful data. -* -* This function splits a single possibly multi-byte write into a series of -* single-byte writes with a proper offset. -*/ -void litex_set_reg (void __iomem *reg,unsigned long reg_size, -unsigned long val) -{ -unsigned long shifted_data, shift, i; - -for (i =0 ; i < reg_size; ++i) { - shift = ((reg_size - i -1 ) *LITEX_SUBREG_SIZE_BIT ); - shifted_data = val >> shift; - -WRITE_LITEX_SUBREGISTER (shifted_data, reg, i); - } -} -EXPORT_SYMBOL_GPL (litex_set_reg); - -/** -* litex_get_reg() - Reads the value of the LiteX CSR (Control&Status Register) -* @reg: Address of the CSR -* @reg_size: The width of the CSR expressed in the number of bytes -* -* Return: Value read from the CSR -* -* In the currently supported LiteX configuration (8-bit CSR Bus, 32-bit aligned), -* a 32-bit LiteX CSR is generated as 4 consecutive 32-bit physical registers, -* each one containing one byte of meaningful data. -* -* This function generates a series of single-byte reads with a proper offset -* and joins their results into a single multi-byte value. -*/ -unsigned long litex_get_reg (void __iomem *reg,unsigned long reg_size) -{ -unsigned long shifted_data, shift, i; -unsigned long result =0 ; - -for (i =0 ; i < reg_size; ++i) { - shifted_data =READ_LITEX_SUBREGISTER (reg, i); - - shift = ((reg_size - i -1 ) *LITEX_SUBREG_SIZE_BIT ); - result |= (shifted_data << shift); - } - -return result; -} -EXPORT_SYMBOL_GPL (litex_get_reg); -#define SCRATCH_REG_OFF 0x04#define SCRATCH_REG_VALUE 0x12345678#define SCRATCH_TEST_VALUE 0xdeadbeef
include/linux/litex.h +69 -5
87 lines not on this page · raw message
Signature · 1 line
2.26.2
PATCH v4 2/3 drivers/soc/litex: separate MMIO from subregister offset calculation
In reply to Gabriel SomloSeparate MMIO (read/write) access into _[read|write]_litex_subregister() static inline functions, leaving existing "READ|WRITE" macros to handle calculation of the subregister offset only.
NOTE: this is a non-functional change.
--- include/linux/litex.h | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-)
include/linux/litex.h +14 -2
@@ -24,11 +24,23 @@#define LITEX_SUBREG_SIZE 0x1#define LITEX_SUBREG_SIZE_BIT (LITEX_SUBREG_SIZE * 8) +static inline void _write_litex_subregister (u32 val,void __iomem *addr) +{ +writel ((u32 __force )cpu_to_le32 (val), addr); +} + +static inline u32 _read_litex_subregister (void __iomem *addr) +{ +return le32_to_cpu ((__le32 __force )readl (addr)); +} +#define WRITE_LITEX_SUBREGISTER (val, base_offset, subreg_id) \ - writel((u32 __force)cpu_to_le32(val), base_offset + (LITEX_REG_SIZE * subreg_id)) + _write_litex_subregister(val, (base_offset) + \ + LITEX_REG_SIZE * (subreg_id))#define READ_LITEX_SUBREGISTER (base_offset, subreg_id) \ - le32_to_cpu((__le32 __force)readl(base_offset + (LITEX_REG_SIZE * subreg_id))) + _read_litex_subregister((base_offset) + \ + LITEX_REG_SIZE * (subreg_id))/* * LiteX SoC Generator, depending on the configuration, can split a single
Signature · 1 line
2.26.2
PATCH v4 3/3 drivers/soc/litex: support 32-bit subregisters, 64-bit CPUs
In reply to Gabriel SomloUpstream LiteX now defaults to using 32-bit CSR subregisters (see https://github.com/enjoy-digital/litex/commit/a2b71fde).
This patch expands on commit 22447a99c97e ("drivers/soc/litex: add LiteX SoC Controller driver"), adding support for handling both 8- and 32-bit LiteX CSR (MMIO) subregisters, as determined by the LITEX_SUBREG_SIZE Kconfig option.
NOTE that while LITEX_SUBREG_SIZE could theoretically be a device tree property, defining it as a compile-time constant allows for much better optimization of the resulting code. This is further supported by the low expected usefulness of deploying the same kernel across LiteX SoCs built with different CSR-Bus data widths.
The constant LITEX_REG_SIZE is renamed to the more descriptive LITEX_SUBREG_ALIGN (LiteX CSR subregisters are located at 32-bit aligned MMIO addresses).
Finally, the litex_[read|write][8|16|32|64]() accessors are redefined in terms of litex_[get|set]_reg(), which, after compiler optimization, will result in code as efficient as hardcoded shifts, but with the added benefit of automatically matching the appropriate LITEX_SUBREG_SIZE.
NOTE that litex_[get|set]_reg() nominally operate on 64-bit data, but that will also be optimized by the compiler in situations where narrower data is used from a call site.
--- drivers/soc/litex/Kconfig | 12 +++ drivers/soc/litex/litex_soc_ctrl.c | 3 +- include/linux/litex.h | 141 ++++++++++++----------------- 3 files changed, 72 insertions(+), 84 deletions(-)
drivers/soc/litex/Kconfig +12 -0
@@ -16,4 +16,16 @@ config LITEX_SOC_CONTROLLER All drivers that use functions from litex.h must depend on LITEX. +config LITEX_SUBREG_SIZE + int "Size of a LiteX CSR subregister, in bytes" + depends on LITEX + range 1 4 + default 4 + help + LiteX MMIO registers (referred to as Configuration and Status + registers, or CSRs) are spread across adjacent 8- or 32-bit + subregisters, located at 32-bit aligned MMIO addresses. Use + this to select the appropriate size (1 or 4 bytes) matching + your particular LiteX build. + endmenu
drivers/soc/litex/litex_soc_ctrl.c +2 -1
@@ -58,7 +58,8 @@ static int litex_check_csr_access(void __iomem *reg_addr)/* restore original value of the SCRATCH register */ litex_write32 (reg_addr +SCRATCH_REG_OFF ,SCRATCH_REG_VALUE ); -pr_info ("LiteX SoC Controller driver initialized" ); +pr_info ("LiteX SoC Controller driver initialized: subreg:%d, align:%d" , +LITEX_SUBREG_SIZE ,LITEX_SUBREG_ALIGN );return 0 ; }
include/linux/litex.h +58 -83
214 lines not on this page · raw message
Signature · 1 line
2.26.2
Quoted 27 lines · Gabriel Somlo
This series expands on commit
22447a99c97e("drivers/soc/litex: add LiteX SoC Controller driver"), adding support for handling both 8- and 32-bit LiteX CSR (MMIO) subregisters, on both 32- and 64-bit CPUs.Notes v4:
- improved "eloquence" of some 3/3 commit blurb paragraphs
- fixed instance of "disgusting" comment style :)
- litex_[get|set]_reg() now usingsize_tfor 'reg_size' argument
- slightly tighter shift calculation inlitex_set_reg()Notes v3:
- split into smaller, more self-explanatory patches
- more detailed commit blurb for "main payload" (3/3) patch
- eliminate compiler warning on 32-bit architecturesNotes v2:
- fix typo (s/u32/u64/) inlitex_read64().Notes v1:
-LITEX_SUBREG_SIZEnow provided byKconfig.
- it's notLITEX_REG_SIZE, but ratherLITEX_SUBREG_ALIGN!
- move litex_[get|set]_reg() toinclude/linux/litex.hand mark them as "static inline";
- redo litex_[read|write][8|16|32|64]() using litex_[get|set]_reg() (compiler should produce code as efficient as hardcoded shifts, but also automatically matchingLITEX_SUBREG_SIZE).
Quoted 4 lines
Gabriel Somlo (3):
drivers/soc/litex: move generic accessors tolitex.hdrivers/soc/litex: separate MMIO from subregister offset calculationdrivers/soc/litex: support 32-bit subregisters, 64-bit CPUs
Thanks, this look good to me right now. I will wait for other reviewers to chime in over the next week or two after the holidays.
Some minor things:
- It's customary to add "Changes since xx" on each patch after "---",
See: https://kernelnewbies.org/PatchTipsAndTricks
- Did you run your patches through "./scripts/checkpatch.pl"?
- Did you use "./scripts/get_maintainer.pl" to create the cc list? I usually
run: git send-email --to linux-kernel --cc-cmd ./scripts/get_maintainer.pl ... From your cc list it seems you did, but maybe did it manually. (I setup .get_maintainer.conf with --no-rolestats for this to work)
- In general check out:
https://www.kernel.org/doc/html/latest/process/submit-checklist.html
-Stafford
Quoted 8 lines
drivers/soc/litex/Kconfig | 12 +++ drivers/soc/litex/litex_soc_ctrl.c | 76 +-------------- include/linux/litex.h | 151 +++++++++++++++++++---------- 3 files changed, 115 insertions(+), 124 deletions(-)Signature · 1 line
2.26.2