Eric Lee / smarc-fsl-linux-kernel

09 Jun, 2017

1 commit

  • 80c2a5df3   MLK-14482-2: dma: imx-sdma: add virt-dma support ... Browse Code »

    This patch cherry-pick the blow patch from v4.1.y, and resove
    conflicts.

    commit 70805e9da3fd25eebf0e141a5cda48fba310c5f5
    Author: Robin Gong
    Date: Mon Aug 17 16:04:48 2015 +0800

    MLK-11358-3: dma: imx-sdma: add virt-dma support

    Old sdma can't support multi instances, because next transfer will return
    error if the last transfer not done(sdmac->status == DMA_IN_PROGRESS). virt
    dma is a common framework for versus dma drivers, and it's support multi
    instances, driver can dynamicly alloc description and add it to list which
    will be handled in the last sdma transfer done later.

    Another advantage of this patch is to clean up the constrain of max bd numer:
    --#define NUM_BD (int)(PAGE_SIZE / sizeof(struct sdma_buffer_descriptor))
    in other words, now sdma driver can support any length data now.

    Meanwhile, remove sdma_load_context() in prep_* everytime, since it can do
    only once in config channel.

    Signed-off-by: Robin Gong

    Signed-off-by: Robin Gong

    Robin Gong
     

23 Feb, 2017

2 commits

18 Oct, 2016

1 commit

  • d66197610   dmaengine: mmp_tdma: add missing select GENERIC_ALLOCATOR in Kconfig ... Browse Code »

    There are some compilation errors when CONFIG_MMP_TDMA is enabled and
    CONFIG_GENERIC_ALLOCATOR is disabled:

    drivers/built-in.o: In function `mmp_tdma_prep_dma_cyclic':
    mmp_tdma.c:(.text+0x7890e): undefined reference to `gen_pool_dma_alloc'
    drivers/built-in.o: In function `mmp_tdma_free_chan_resources':
    mmp_tdma.c:(.text+0x78aca): undefined reference to `gen_pool_free'
    drivers/built-in.o: In function `mmp_tdma_probe':
    mmp_tdma.c:(.text+0x78ea8): undefined reference to `of_gen_pool_get'

    This commit fix this problem by selecting GENERIC_ALLOCATOR when
    CONFIG_MMP_TDMA is enabled.

    Signed-off-by: Jérémy Lefaure
    Signed-off-by: Vinod Koul

    Jérémy Lefaure
     

03 Oct, 2016

1 commit

28 Sep, 2016

3 commits

27 Sep, 2016

14 commits

31 Aug, 2016

1 commit

16 Jul, 2016

1 commit

12 Jul, 2016

1 commit

  • 19a340b1a   dmaengine: mv_xor_v2: new driver ... Browse Code »

    The new mv_xor_v2 driver supports the XOR engines found in the 64-bits
    ARM from Marvell of the Armada 7K and Armada 8K family. This XOR
    engine is a completely new hardware block, entirely different from the
    one used on previous Marvell Armada platforms, which use the existing
    mv_xor driver.

    Signed-off-by: Thomas Petazzoni
    Signed-off-by: Vinod Koul

    Thomas Petazzoni
     

08 Jul, 2016

2 commits

17 May, 2016

2 commits

13 May, 2016

1 commit

  • f46b19579   dmaengine: tegra-adma: Add support for Tegra210 ADMA ... Browse Code »

    Add support for the Tegra210 Audio DMA controller that is used for
    transferring data between system memory and the Audio sub-system.
    The driver only supports cyclic transfers because this is being solely
    used for audio.

    This driver is based upon the work by Dara Ramesh .

    Signed-off-by: Jon Hunter
    Signed-off-by: Vinod Koul

    Jon Hunter
     

03 May, 2016

1 commit

  • c39290a1f   dmaengine: mv_xor: Allow selecting mv_xor for mvebu only compatible SoC ... Browse Code »

    Armada 3700 SoC uses the mv_xor driver but don't select anymore the
    PLAT_ORION symbol. This commit extends the dependency of the mv_xor
    driver to the more modern SoCs only compatible with ARCH_MVEBU, which
    allows using it with the Armada 3700 SoC.

    In the same time it also add the COMPILE_TEST dependency allowing a wider
    test coverage.

    Signed-off-by: Gregory CLEMENT
    Signed-off-by: Vinod Koul

    Gregory CLEMENT
     

06 Apr, 2016

1 commit

  • b72db4005   dmaengine: vdma: Add 64 bit addressing support to the driver ... Browse Code »

    This VDMA is a soft ip, which can be programmed to support
    32 bit addressing or greater than 32 bit addressing.

    When the VDMA ip is configured for 32 bit address space
    the buffer address is specified by a single register
    (0x5C for MM2S and 0xAC for S2MM channel).

    When the VDMA core is configured for an address space greater
    than 32 then each buffer address is specified by a combination of
    two registers.

    The first register specifies the LSB 32 bits of address,
    while the next register specifies the MSB 32 bits of address.

    For example, 5Ch will specify the LSB 32 bits while 60h will
    specify the MSB 32 bits of the first start address.
    So we need to program two registers at a time.

    This patch adds the 64 bit addressing support to the vdma driver.

    Signed-off-by: Anurag Kumar Vulisha
    Signed-off-by: Kedareswara rao Appana
    Signed-off-by: Vinod Koul

    Kedareswara rao Appana
     

14 Mar, 2016

1 commit

11 Mar, 2016

1 commit

22 Feb, 2016

1 commit

18 Jan, 2016

1 commit

  • a016af2e7   Merge tag 'sound-4.5-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound ... Browse Code »

    Pull sound updates from Takashi Iwai:
    "We've had quite busy weeks in this cycle. Looking at ALSA core, the
    significant changes are a few fixes wrt timer and sequencer ioctls
    that have been revealed by fuzzer recently. Other than that, ASoC
    core got a few updates about DAI link handling, but these are rather
    straightforward refactoring.

    In drivers scene, ASoC received quite lots of new drivers in addition
    to bunch of updates for still ongoing Intel Skylake support and
    topology API. HD-audio gained a new HDMI/DP hotplug notification via
    component. FireWire got a pile of code refactoring/updates with
    SCS.1x driver integration.

    More highlights are shown below.

    [ NOTE: this contains also many commits for DRM. This is due to the
    pull of drm stable branch into sound tree, as the base of i915 audio
    component work for HD-audio. The highlights below don't contain
    these DRM changes, as these are supposed to be pulled via drm tree
    in anyway sooner or later. ]

    Core:
    - Handful fixes to harden ALSA timer and sequencer ioctls against
    races reported by syzkaller fuzzer
    - Irq description string can be unique to each card; only for
    HD-audio for now

    ASoC:
    - Conversion of the array of DAI links to a list for supporting
    dynamically adding and removing DAI links
    - Topology API enhancements to make everything more component based
    and being able to specify PCM links via topology
    - Some more fixes for the topology code, though it is still not final
    and ready for enabling in production; we really need to get to the
    point where that can be done
    - A pile of changes for Intel SkyLake drivers which hopefully deliver
    some useful initial functionality for systems with this chipset,
    though there is more work still to come
    - Lots of new features and cleanups for the Renesas drivers
    - ANC support for WM5110
    - New drivers: Imagination Technologies IPs, Atmel class D speaker,
    Cirrus CS47L24 and WM1831, Dialog DA7128, Realtek RT5659 and
    RT56156, Rockchip RK3036, TI PC3168A, and AMD ACP
    - Rename PCM1792a driver to be generic pcm179x

    HD-Audio:
    - Use audio component for i915 HDMI/DP hotplug handling
    - On-demand binding with i915 driver
    - bdl_pos_adj parameter adjustment for Baytrail controllers
    - Enable power_save_node for CX20722; this shouldn't lead to
    regression, hopefully
    - Kabylake HDMI/DP codec support
    - Quirks for Lenovo E50-80, Dell Latitude E-series, and other Dell
    machines
    - A few code refactoring

    FireWire:
    - Lots of code cleanup and refactoring
    - Integrate the support of SCS.1x devices into snd-oxfw driver;
    snd-scs1x driver is obsoleted

    USB-audio:
    - Fix possible NULL dereference at disconnection
    - A regression fix for Native Instruments devices

    Misc:
    - A few code cleanups of fm801 driver"

    * tag 'sound-4.5-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound: (722 commits)
    ALSA: timer: Code cleanup
    ALSA: timer: Harden slave timer list handling
    ALSA: hda - Add fixup for Dell Latitidue E6540
    ALSA: timer: Fix race among timer ioctls
    ALSA: hda - add codec support for Kabylake display audio codec
    ALSA: timer: Fix double unlink of active_list
    ALSA: usb-audio: Fix mixer ctl regression of Native Instrument devices
    ALSA: hda - fix the headset mic detection problem for a Dell laptop
    ALSA: hda - Fix white noise on Dell Latitude E5550
    ALSA: hda_intel: add card number to irq description
    ALSA: seq: Fix race at timer setup and close
    ALSA: seq: Fix missing NULL check at remove_events ioctl
    ALSA: usb-audio: Avoid calling usb_autopm_put_interface() at disconnect
    ASoC: hdac_hdmi: remove unused hdac_hdmi_query_pin_connlist
    ASoC: AMD: Add missing include file
    ALSA: hda - Fixup inverted internal mic for Lenovo E50-80
    ALSA: usb: Add native DSD support for Oppo HA-1
    ASoC: Make aux_dev more like a generic component
    ASoC: bcm2835: cleanup includes by ordering them alphabetically
    ASoC: AMD: Manage ACP 2.x SRAM banks power
    ...

    Linus Torvalds
     

21 Nov, 2015

1 commit

  • 9bdca822c   ASoC: samsung: pass filter function as pointer ... Browse Code »

    As we are now passing the filter data as pointers to the drivers,
    we can take the final step and also pass the filter function the
    same way. I'm keeping this change separate, as there it's less
    obvious that this is a net win.

    Upsides of this are:

    - The ASoC drivers are completely independent from the DMA engine
    implementation, which simplifies the Kconfig logic and in theory
    allows the same sound drivers to be built in a kernel that supports
    different kinds of dmaengine drivers.

    - Consistency with other subsystems and drivers

    On the other hand, we have a few downsides:

    - The s3c24xx-dma driver now needs to be built-in for the ac97 platform
    device to be instantiated on s3c2440.

    - samsung_dmaengine_pcm_config cannot be marked 'const' any more
    because the filter function pointer needs to be set at runtime.
    This is safe as long we don't have multiple different DMA engines
    in thet same system at runtime, but is nonetheless ugly.

    Signed-off-by: Arnd Bergmann
    Reviewed-by: Krzysztof Kozlowski
    Signed-off-by: Mark Brown

    Arnd Bergmann
     

16 Nov, 2015

1 commit

31 Oct, 2015

1 commit

27 Oct, 2015

1 commit