1. 09 Mar, 2019 1 commit
    • Qiang Yu's avatar
      drm/lima: driver for ARM Mali4xx GPUs · f6858923
      Qiang Yu authored
      - Mali 4xx GPUs have two kinds of processors GP and PP. GP is for
        OpenGL vertex shader processing and PP is for fragment shader
        processing. Each processor has its own MMU so prcessors work in
        virtual address space.
      - There's only one GP but multiple PP (max 4 for mali 400 and 8
        for mali 450) in the same mali 4xx GPU. All PPs are grouped
        togather to handle a single fragment shader task divided by
        FB output tiled pixels. Mali 400 user space driver is
        responsible for assign target tiled pixels to each PP, but mali
        450 has a HW module called DLBU to dynamically balance each
        PP's load.
      - User space driver allocate buffer object and map into GPU
        virtual address space, upload command stream and draw data with
        CPU mmap of the buffer object, then submit task to GP/PP with
        a register frame indicating where is the command stream and misc
      - There's no command stream validation/relocation due to each user
        process has its own GPU virtual address space. GP/PP's MMU switch
        virtual address space before running two tasks from different
        user process. Error or evil user space code just get MMU fault
        or GP/PP error IRQ, then the HW/SW will be recovered.
      - Use GEM+shmem for MM. Currently just alloc and pin memory when
        gem object creation. GPU vm map of the buffer is also done in
        the alloc stage in kernel space. We may delay the memory
        allocation and real GPU vm map to command submission stage in the
        furture as improvement.
      - Use drm_sched for GPU task schedule. Each OpenGL context should
        have a lima context object in the kernel to distinguish tasks
        from different user. drm_sched gets task from each lima context
        in a fair way.
      mesa driver can be found here before upstreamed:
      - add comments for in_sync
      - fix ctx free miss mutex unlock
      - remove lima_fence_ops with default value
      - move fence slab create to device probe
      - check pad ioctl args to be zero
      - add comments for user/kernel interface
      - fix comments by checkpatch.pl
      - export gp/pp version to userspace
      - rebase on drm-misc-next
      - use get param interface to get info
      - separate context create/free ioctl
      - remove unused max sched task param
      - update copyright time
      - use xarray instead of idr
      - stop using drmP.h
      - fix comments from kbuild robot
      - restrict supported arch to tested ones
      - fix syscall argument check
      - fix job finish fence leak since kernel 5.0
      - use drm syncobj to replace native fence
      - move buffer object GPU va map into kernel
      - reserve syscall argument space for future info
      - remove kernel gem modifier
      - switch TTM back to GEM+shmem MM
      - use time based io poll
      - use whole register name
      - adopt gem reservation obj integration
      - use drm_timeout_abs_to_jiffies
      Cc: Eric Anholt <eric@anholt.net>
      Cc: Rob Herring <robh@kernel.org>
      Cc: Christian König <ckoenig.leichtzumerken@gmail.com>
      Cc: Daniel Vetter <daniel@ffwll.ch>
      Cc: Alex Deucher <alexdeucher@gmail.com>
      Cc: Sam Ravnborg <sam@ravnborg.org>
      Cc: Rob Clark <robdclark@gmail.com>
      Signed-off-by: Andreas Baierl's avatarAndreas Baierl <ichgeh@imkreisrum.de>
      Signed-off-by: Erico Nunes's avatarErico Nunes <nunes.erico@gmail.com>
      Signed-off-by: Heiko Stuebner's avatarHeiko Stuebner <heiko@sntech.de>
      Signed-off-by: Marek Vasut's avatarMarek Vasut <marex@denx.de>
      Signed-off-by: Neil Armstrong's avatarNeil Armstrong <narmstrong@baylibre.com>
      Signed-off-by: Simon Shields's avatarSimon Shields <simon@lineageos.org>
      Signed-off-by: Vasily Khoruzhick's avatarVasily Khoruzhick <anarsoul@gmail.com>
      Signed-off-by: Qiang Yu's avatarQiang Yu <yuq825@gmail.com>
  2. 08 Mar, 2019 4 commits
  3. 07 Mar, 2019 6 commits
  4. 06 Mar, 2019 3 commits
  5. 05 Mar, 2019 9 commits
  6. 04 Mar, 2019 9 commits
  7. 02 Mar, 2019 3 commits
    • Andrew Lunn's avatar
      net: dsa: mv88e6xxx: Fix statistics on mv88e6161 · a6da21bb
      Andrew Lunn authored
      Despite what the datesheet says, the silicon implements the older way
      of snapshoting the statistics. Change the op.
      Reported-by: Chris.Healy@zii.aero
      Tested-by: Chris.Healy@zii.aero
      Fixes: 0ac64c39 ("net: dsa: mv88e6xxx: mv88e6161 uses mv88e6320 stats snapshot")
      Signed-off-by: default avatarAndrew Lunn <andrew@lunn.ch>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    • Jiri Benc's avatar
      geneve: correctly handle ipv6.disable module parameter · cf1c9ccb
      Jiri Benc authored
      When IPv6 is compiled but disabled at runtime, geneve_sock_add returns
      -EAFNOSUPPORT. For metadata based tunnels, this causes failure of the whole
      operation of bringing up the tunnel.
      Ignore failure of IPv6 socket creation for metadata based tunnels caused by
      IPv6 not being available.
      This is the same fix as what commit d074bf96 ("vxlan: correctly handle
      ipv6.disable module parameter") is doing for vxlan.
      Note there's also commit c0a47e44 ("geneve: should not call rt6_lookup()
      when ipv6 was disabled") which fixes a similar issue but for regular
      tunnels, while this patch is needed for metadata based tunnels.
      Signed-off-by: default avatarJiri Benc <jbenc@redhat.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    • Heiner Kallweit's avatar
      net: dsa: mv88e6xxx: prevent interrupt storm caused by mv88e6390x_port_set_cmode · ed8fe202
      Heiner Kallweit authored
      When debugging another issue I faced an interrupt storm in this
      driver (88E6390, port 9 in SGMII mode), consisting of alternating
      link-up / link-down interrupts. Analysis showed that the driver
      wanted to set a cmode that was set already. But so far
      mv88e6390x_port_set_cmode() doesn't check this and powers down
      SERDES, what causes the link to break, and eventually results in
      the described interrupt storm.
      Fix this by checking whether the cmode actually changes. We want
      that the very first call to mv88e6390x_port_set_cmode() always
      configures the registers, therefore initialize port.cmode with
      a value that is different from any supported cmode value.
      We have to take care that we only init the ports cmode once
      chip->info->num_ports is set.
      - add small helper and init the number of actual ports only
      Fixes: 364e9d77 ("net: dsa: mv88e6xxx: Power on/off SERDES on cmode change")
      Signed-off-by: default avatarHeiner Kallweit <hkallweit1@gmail.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  8. 01 Mar, 2019 5 commits