Commit e18d6152 authored by Paolo Bonzini's avatar Paolo Bonzini
Browse files

Merge tag 'kvm-riscv-6.1-1' of https://github.com/kvm-riscv/linux into HEAD 

KVM/riscv changes for 6.1

- Improved instruction encoding infrastructure for
  instructions not yet supported by binutils
- Svinval support for both KVM Host and KVM Guest
- Zihintpause support for KVM Guest
- Zicbom support for KVM Guest
- Record number of signal exits as a VCPU stat
- Use generic guest entry infrastructure
parents fe4d9e4a b60ca697

Documentation/devicetree/bindings/dma/moxa,moxart-dma.txt

+2 −2
Original line number Diff line number Diff line
@@ -34,8 +34,8 @@ Example: 
Use specific request line passing from dma

For example, MMC request line is 5



	sdhci: sdhci@98e00000 {

		compatible = "moxa,moxart-sdhci";

	mmc: mmc@98e00000 {

		compatible = "moxa,moxart-mmc";

		reg = <0x98e00000 0x5C>;

		interrupts = <5 0>;

		clocks = <&clk_apb>;

Documentation/devicetree/bindings/memory-controllers/fsl/imx8m-ddrc.yaml

+1 −1
Original line number Diff line number Diff line
@@ -7,7 +7,7 @@ $schema: http://devicetree.org/meta-schemas/core.yaml# 
title: i.MX8M DDR Controller



maintainers:

  - Leonard Crestez <leonard.crestez@nxp.com>

  - Peng Fan <peng.fan@nxp.com>



description:

  The DDRC block is integrated in i.MX8M for interfacing with DDR based

Documentation/devicetree/bindings/opp/opp-v2-kryo-cpu.yaml

+1 −0
Original line number Diff line number Diff line
@@ -40,6 +40,7 @@ properties: 
patternProperties:

  '^opp-?[0-9]+$':

    type: object

    additionalProperties: false



    properties:

      opp-hz: true

Documentation/devicetree/bindings/opp/opp-v2-qcom-level.yaml

+1 −0
Original line number Diff line number Diff line
@@ -19,6 +19,7 @@ properties: 
patternProperties:

  '^opp-?[0-9]+$':

    type: object

    additionalProperties: false



    properties:

      opp-level: true

Documentation/i2c/dev-interface.rst

+1 −1
Original line number Diff line number Diff line
@@ -148,7 +148,7 @@ You can do plain I2C transactions by using read(2) and write(2) calls. 
You do not need to pass the address byte; instead, set it through

ioctl I2C_SLAVE before you try to access the device.



You can do SMBus level transactions (see documentation file smbus-protocol

You can do SMBus level transactions (see documentation file smbus-protocol.rst

for details) through the following functions::



  __s32 i2c_smbus_write_quick(int file, __u8 value);