linux-toradex.git/Documentation/driver-api/firmware, branch v5.17-rc4

docs: driver-api: firmware: fallback-mechanisms: Fix rendering of bullet point

2020-09-08T11:32:06+00:00

Without this patch, the "Firmware is not accessible [...]" line is
rendered in bold, which does not seem intentional.

Signed-off-by: Jonathan Neuschäfer 
Link: https://lore.kernel.org/r/20200905184131.1280337-1-j.neuschaefer@gmx.net
Signed-off-by: Greg Kroah-Hartman

Documentation/driver-api: firmware/request_firmware: drop doubled word

2020-07-10T12:58:01+00:00

Drop the doubled word "call".

Signed-off-by: Randy Dunlap 
Cc: Jonathan Corbet 
Cc: linux-doc@vger.kernel.org
Acked-by: Luis Chamberlain 
Link: https://lore.kernel.org/r/20200704034502.17199-6-rdunlap@infradead.org
Signed-off-by: Greg Kroah-Hartman

Documentation/driver-api: firmware/direct-fs-lookup: drop doubled word

2020-07-10T12:58:01+00:00

Drop the doubled word "firmware".

Signed-off-by: Randy Dunlap 
Cc: Jonathan Corbet 
Cc: linux-doc@vger.kernel.org
Acked-by: Luis Chamberlain 
Link: https://lore.kernel.org/r/20200704034502.17199-5-rdunlap@infradead.org
Signed-off-by: Greg Kroah-Hartman

Documentation/driver-api: firmware/firmware_cache: drop doubled word

2020-07-10T12:58:00+00:00

Drop the doubled word "if".

Signed-off-by: Randy Dunlap 
Cc: Jonathan Corbet 
Cc: linux-doc@vger.kernel.org
Acked-by: Luis Chamberlain 
Link: https://lore.kernel.org/r/20200704034502.17199-4-rdunlap@infradead.org
Signed-off-by: Greg Kroah-Hartman

Documentation/driver-api: firmware/built-in-fw: drop doubled word

2020-07-10T12:58:00+00:00

Drop the doubled word "for".

Signed-off-by: Randy Dunlap 
Cc: Jonathan Corbet 
Cc: linux-doc@vger.kernel.org
Acked-by: Luis Chamberlain 
Link: https://lore.kernel.org/r/20200704034502.17199-3-rdunlap@infradead.org
Signed-off-by: Greg Kroah-Hartman

Merge branch 'efi-core-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

2020-03-30T23:13:08+00:00

Pull EFI updates from Ingo Molnar:
 "The EFI changes in this cycle are much larger than usual, for two
  (positive) reasons:

   - The GRUB project is showing signs of life again, resulting in the
     introduction of the generic Linux/UEFI boot protocol, instead of
     x86 specific hacks which are increasingly difficult to maintain.
     There's hope that all future extensions will now go through that
     boot protocol.

   - Preparatory work for RISC-V EFI support.

  The main changes are:

   - Boot time GDT handling changes

   - Simplify handling of EFI properties table on arm64

   - Generic EFI stub cleanups, to improve command line handling, file
     I/O, memory allocation, etc.

   - Introduce a generic initrd loading method based on calling back
     into the firmware, instead of relying on the x86 EFI handover
     protocol or device tree.

   - Introduce a mixed mode boot method that does not rely on the x86
     EFI handover protocol either, and could potentially be adopted by
     other architectures (if another one ever surfaces where one
     execution mode is a superset of another)

   - Clean up the contents of 'struct efi', and move out everything that
     doesn't need to be stored there.

   - Incorporate support for UEFI spec v2.8A changes that permit
     firmware implementations to return EFI_UNSUPPORTED from UEFI
     runtime services at OS runtime, and expose a mask of which ones are
     supported or unsupported via a configuration table.

   - Partial fix for the lack of by-VA cache maintenance in the
     decompressor on 32-bit ARM.

   - Changes to load device firmware from EFI boot service memory
     regions

   - Various documentation updates and minor code cleanups and fixes"

* 'efi-core-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (114 commits)
  efi/libstub/arm: Fix spurious message that an initrd was loaded
  efi/libstub/arm64: Avoid image_base value from efi_loaded_image
  partitions/efi: Fix partition name parsing in GUID partition entry
  efi/x86: Fix cast of image argument
  efi/libstub/x86: Use ULONG_MAX as upper bound for all allocations
  efi: Fix a mistype in comments mentioning efivar_entry_iter_begin()
  efi/libstub: Avoid linking libstub/lib-ksyms.o into vmlinux
  efi/x86: Preserve %ebx correctly in efi_set_virtual_address_map()
  efi/x86: Ignore the memory attributes table on i386
  efi/x86: Don't relocate the kernel unless necessary
  efi/x86: Remove extra headroom for setup block
  efi/x86: Add kernel preferred address to PE header
  efi/x86: Decompress at start of PE image load address
  x86/boot/compressed/32: Save the output address instead of recalculating it
  efi/libstub/x86: Deal with exit() boot service returning
  x86/boot: Use unsigned comparison for addresses
  efi/x86: Avoid using code32_start
  efi/x86: Make efi32_pe_entry() more readable
  efi/x86: Respect 32-bit ABI in efi32_pe_entry()
  efi/x86: Annotate the LOADED_IMAGE_PROTOCOL_GUID with SYM_DATA
  ...

firmware: Add new platform fallback mechanism and firmware_request_platform()

2020-03-20T13:54:04+00:00

In some cases the platform's main firmware (e.g. the UEFI fw) may contain
an embedded copy of device firmware which needs to be (re)loaded into the
peripheral. Normally such firmware would be part of linux-firmware, but in
some cases this is not feasible, for 2 reasons:

1) The firmware is customized for a specific use-case of the chipset / use
with a specific hardware model, so we cannot have a single firmware file
for the chipset. E.g. touchscreen controller firmwares are compiled
specifically for the hardware model they are used with, as they are
calibrated for a specific model digitizer.

2) Despite repeated attempts we have failed to get permission to
redistribute the firmware. This is especially a problem with customized
firmwares, these get created by the chip vendor for a specific ODM and the
copyright may partially belong with the ODM, so the chip vendor cannot
give a blanket permission to distribute these.

This commit adds a new platform fallback mechanism to the firmware loader
which will try to lookup a device fw copy embedded in the platform's main
firmware if direct filesystem lookup fails.

Drivers which need such embedded fw copies can enable this fallback
mechanism by using the new firmware_request_platform() function.

Note that for now this is only supported on EFI platforms and even on
these platforms firmware_fallback_platform() only works if
CONFIG_EFI_EMBEDDED_FIRMWARE is enabled (this gets selected by drivers
which need this), in all other cases firmware_fallback_platform() simply
always returns -ENOENT.

Reported-by: Dave Olsthoorn 
Suggested-by: Peter Jones 
Acked-by: Luis Chamberlain 
Signed-off-by: Hans de Goede 
Link: https://lore.kernel.org/r/20200115163554.101315-5-hdegoede@redhat.com
Signed-off-by: Greg Kroah-Hartman

efi/libstub: Add libstub/mem.c to the documentation tree

2020-03-08T08:58:13+00:00

Let the description of the efi/libstub/mem.c functions appear in the kernel
API documentation in the following chapters:

    The Linux driver implementer’s API guide
        Linux Firmware API
            UEFI Support
                UEFI stub library functions

Acked-by: Jonathan Corbet 
Signed-off-by: Heinrich Schuchardt 
Signed-off-by: Ard Biesheuvel 
Signed-off-by: Ingo Molnar 
Link: https://lore.kernel.org/r/20200221035832.144960-1-xypron.glpk@gmx.de
Link: https://lore.kernel.org/r/20200308080859.21568-9-ardb@kernel.org

docs: Fix a misdirected kerneldoc directive

2019-05-24T20:31:50+00:00

The stratix10 service layer documentation tried to include a kerneldoc
comments for a nonexistent struct; leading to a "no structured comments
found" message.  Switch it to stratix10_svc_command_config_type, which
appears at that spot in the sequence and was not included.

Signed-off-by: Jonathan Corbet

Documentation: driver-api: add stratix10 service layer

2018-11-26T19:15:07+00:00

Add Intel Stratix10 service layer driver document

Signed-off-by: Richard Gong 
Signed-off-by: Alan Tull 
Signed-off-by: Greg Kroah-Hartman