linux-toradex.git/drivers/s390/char/Makefile, branch master

s390/tape: Consolidate tape config options and modules

2026-02-05T12:02:48+00:00

The tape device driver only supports 3490E devices on Virtual Tape Server
(VTS). There is no point in keeping separated options and modules for
different device types and general hardware support. Consolidate the tape
config option into a single option, which enables the complete tape support
with one singular module called 'tape_s390'. The corresponding module entry
points are adapted and consolidate in tape_init() and tape_exit()
respectively in tape_core.c

The current module author and descriptions of the individual tape
modules are outdated and haven't been changed for quite some time.
Change it to a more generic description that is in line with the
corresponding supported s390 architecture for the single tape module.

Signed-off-by: Jan Höppner 
Signed-off-by: Heiko Carstens

s390/tape: Rename tape_34xx.c to tape_3490.c

2026-02-04T07:31:30+00:00

The driver now exclusively supports 3490 tape devices, given support for
3480 tape devices has been removed. Update the device driver name, its
source file name, and change any occurrences of "34xx/34XX" to "3490" in
the source code and comments.

Signed-off-by: Jan Höppner 
Reviewed-by: Jens Remus 
Signed-off-by: Heiko Carstens

s390/tape: Remove support for 3590/3592 models

2026-02-04T07:31:29+00:00

Physical 3590/3592 tape models are not supported anymore for a very long
time. The Virtual Tape Server (VTS) emulates and presents only 3490E
models to the host. This is the only supported model and storage server.

Remove the entire code base for 3590/3592 models as it can be considered
dead code for quite some time already.

Signed-off-by: Jan Höppner 
Reviewed-by: Jens Remus 
Signed-off-by: Heiko Carstens

s390/sclp: Move memory hotplug code for better modularity

2025-08-20T14:38:23+00:00

To improve readability and prepare for future extensions, move the
memory hotplug code to a separate file. In addtion to it, add required
headers in sclp_mem.c and remove unnecessary headers in sclp_cmd.c

Acked-by: Heiko Carstens 
Signed-off-by: Sumanth Korikkar 
Signed-off-by: Alexander Gordeev

s390/ap: modularize ap bus

2024-04-09T15:29:56+00:00

There is no hard requirement to have the ap bus statically in the
kernel, so add an option to compile it as module.

Cc: Tony Krowiak 
Cc: Halil Pasic 
Signed-off-by: Holger Dengler 
Reviewed-by: Harald Freudenberger 
Reviewed-by: Anthony Krowiak 
Signed-off-by: Alexander Gordeev

s390/tty3270: rename to con3270

2023-01-09T13:33:56+00:00

Rename the driver file to con3270 to be in sync with con3215.c.
This removes CONFIG_TN3270_TTY, it is now always build if CONFIG_TN3270
is enabled.

Signed-off-by: Sven Schnelle 
Acked-by: Heiko Carstens 
Tested-by: Niklas Schnelle 
Signed-off-by: Heiko Carstens

s390/3270: unify con3270 + tty3270

2023-01-09T13:33:56+00:00

There were two flavours of 3270 drivers: con3270, which provides a
console driver, and tty3270 providing a tty driver. A user could switch
with PF3 between the two views. While this sounds nice, it's a bit
annoying: If the user enters a command which triggers a kernel message,
he always has to switch back and forth to see the message. Unify both
views to have kernel messages and tty in one screen, like it is on almost
all other platforms. This also has the nice side effect of removing a lot
of duplicate code.

Signed-off-by: Sven Schnelle 
Acked-by: Heiko Carstens 
Tested-by: Niklas Schnelle 
Signed-off-by: Heiko Carstens

drivers/s390/char: Add Ultravisor io device

2022-05-20T14:38:35+00:00

This patch adds a new miscdevice to expose some Ultravisor functions
to userspace. Userspace can send IOCTLs to the uvdevice that will then
emit a corresponding Ultravisor Call and hands the result over to
userspace. The uvdevice is available if the Ultravisor Call facility is
present.
Userspace can call the Retrieve Attestation Measurement
Ultravisor Call using IOCTLs on the uvdevice.

The uvdevice will do some sanity checks first.
Then, copy the request data to kernel space, build the UVCB,
perform the UV call, and copy the result back to userspace.

Signed-off-by: Steffen Eiden 
Reviewed-by: Janosch Frank 
Reviewed-by: Claudio Imbrenda 
Link: https://lore.kernel.org/kvm/20220516113335.338212-1-seiden@linux.ibm.com/
Message-Id: <20220516113335.338212-1-seiden@linux.ibm.com>
Signed-off-by: Janosch Frank  (whitespace and  tristate fixes, pick)

s390/sclp: Add support for SCLP AP adapter config/deconfig

2020-10-07T19:50:00+00:00

Add support for AP bus adapter config and deconfig to the sclp
core code. The code is statically build into the kernel when
ZCRYPT is configured either as module or with static support.

This is the base functionality for having configure/deconfigure
support in the AP bus and card code. Another patch will exploit
this soon.

Signed-off-by: Harald Freudenberger 
Suggested-by: Pierre Morel 
Signed-off-by: Vasily Gorbik

s390: clean .bss before running uncompressed kernel

2019-08-21T10:58:52+00:00

Clean uncompressed kernel .bss section in the startup code before
the uncompressed kernel is executed. At this point of time initrd and
certificates have been already rescued. Uncompressed kernel .bss size
is known from vmlinux_info. It is also taken into consideration during
uncompressed kernel positioning by kaslr (so it is safe to clean it).

With that uncompressed kernel is starting with .bss section zeroed and
no .bss section usage restrictions apply. Which makes chkbss checks for
uncompressed kernel objects obsolete and they can be removed.

early_nobss.c is also not needed anymore. Parts of it which are still
relevant are moved to early.c. Kasan initialization code is now called
directly from head64 (early.c is instrumented and should not be
executed before kasan shadow memory is set up).

Reviewed-by: Philipp Rudo 
Signed-off-by: Vasily Gorbik