Eric Lee / smarc-fsl-linux-kernel

06 Oct, 2020

1 commit

22 Sep, 2020

1 commit

11 Sep, 2020

1 commit

  • 375e2c352   ALSA: rockchip_i2s: fix a possible divide-by-zero bug in rockchip_i2s_hw_params() ... Browse Code »

    The variable bclk_rate is checked in:
    if (bclk_rate && mclk_rate % bclk_rate)

    This indicates that bclk_rate can be zero.
    If so, a divide-by-zero bug will occur:
    div_bclk = mclk_rate / bclk_rate;

    To fix this possible bug, the function returns -EINVAL when bclk_rate is
    zero.

    Signed-off-by: Tuo Li
    Link: https://lore.kernel.org/r/TY2PR04MB4029799E60A5BCAAD5B7B5BBB8280@TY2PR04MB4029.apcprd04.prod.outlook.com
    Signed-off-by: Mark Brown

    Tuo Li
     

24 Aug, 2020

1 commit

  • df561f668   treewide: Use fallthrough pseudo-keyword ... Browse Code »

    Replace the existing /* fall through */ comments and its variants with
    the new pseudo-keyword macro fallthrough[1]. Also, remove unnecessary
    fall-through markings when it is the case.

    [1] https://www.kernel.org/doc/html/v5.7/process/deprecated.html?highlight=fallthrough#implicit-switch-case-fall-through

    Signed-off-by: Gustavo A. R. Silva

    Gustavo A. R. Silva
     

31 Jul, 2020

1 commit

  • d0508b4f1   ASoC: rk3399_gru_sound: Add DAPM pins, kcontrols for jack detection ... Browse Code »

    PulseAudio (and perhaps other userspace utilities) can not detect any
    jack for rk3399_gru_sound as the driver doesn't expose related Jack
    kcontrols.

    This patch adds two DAPM pins to the headset jack, where the
    snd_soc_card_jack_new() call automatically creates "Headphones Jack" and
    "Headset Mic Jack" kcontrols from them.

    With an appropriate ALSA UCM config specifying JackControl fields for
    the "Headphones" and "Headset" (mic) devices, PulseAudio can detect
    plug/unplug events for both of them after this patch.

    Signed-off-by: Alper Nebi Yasak
    Link: https://lore.kernel.org/r/20200721182709.6895-1-alpernebiyasak@gmail.com
    Signed-off-by: Mark Brown

    Alper Nebi Yasak
     

24 Jul, 2020

1 commit

14 Jul, 2020

1 commit

01 Jul, 2020

1 commit

  • 1eb96c198   ASoC: rockchip: add format and rate constraints on rk3399 ... Browse Code »

    S8 and S24 formats does not work on this machine driver so force to use
    S16_LE instead.

    In addition, add constraint to limit the max value of rate because the
    rate higher than 96000(172000, 192000) is not stable either.

    Signed-off-by: Yu-Hsuan Hsu
    Link: https://lore.kernel.org/r/20200630091615.4020059-1-yuhsuan@chromium.org
    Signed-off-by: Mark Brown

    Yu-Hsuan Hsu
     

19 Jun, 2020

1 commit

  • f141a4221   ASoC: rockchip: Fix a reference count leak. ... Browse Code »

    Calling pm_runtime_get_sync increments the counter even in case of
    failure, causing incorrect ref count if pm_runtime_put is not called in
    error handling paths. Call pm_runtime_put if pm_runtime_get_sync fails.

    Fixes: fc05a5b22253 ("ASoC: rockchip: add support for pdm controller")
    Signed-off-by: Qiushi Wu
    Reviewed-by: Heiko Stuebner
    Link: https://lore.kernel.org/r/20200613205158.27296-1-wu000273@umn.edu
    Signed-off-by: Mark Brown

    Qiushi Wu
     

27 Mar, 2020

1 commit

07 Nov, 2019

1 commit

29 Oct, 2019

2 commits

  • bf2f64ea6   ASoC: rockchip_max98090: Add HDMI jack support ... Browse Code »

    In machine driver, create a jack and let hdmi-codec report jack status.

    Signed-off-by: Cheng-Yi Chiang
    Link: https://lore.kernel.org/r/20191028071930.145899-5-cychiang@chromium.org
    Signed-off-by: Mark Brown

    Cheng-Yi Chiang
     
  • 05b754f5f   ASoC: rockchip_max98090: Optionally support HDMI use case ... Browse Code »

    Support three different use cases with rockchip_max98090 driver.

    The three use cases:
    - max98090 only: Current usage, where HDMI link is missing.
    - HDMI only: Needed use case for veyron_mickey board.
    - max98090 + HDMI: Ideal use case for veyron_jerry, veyron_minnie..etc.

    The presence of max98090 is determined by the presence of
    rockchip,audio-codec device property.

    The presence of HDMI is determined by the presence of
    rockchip,hdmi-codec device property.

    Create different sound card based on the configuration.
    Note that we keep max98090 only usage for backward compatibility.

    Signed-off-by: Cheng-Yi Chiang
    Link: https://lore.kernel.org/r/20191028071930.145899-4-cychiang@chromium.org
    Signed-off-by: Mark Brown

    Cheng-Yi Chiang
     

28 Oct, 2019

1 commit

  • 07c1b73e2   ASoC: rockchip: rockchip_max98090: Enable SHDN to fix headset detection ... Browse Code »

    max98090 spec states that chip needs to be in turned-on state to supply
    mic bias. Enable SHDN dapm widget along with MICBIAS widget to
    actually turn on mic bias for proper headset button detection.
    This is similar to cht_ti_jack_event in
    sound/soc/intel/boards/cht_bsw_max98090_ti.c.

    Note that due to ts3a227e reports the jack event right away before the
    notifier is registered, if headset is plugged on boot, headset button
    will not get detected until headset is unplugged and plugged. This is
    still an issue to be fixed.

    Signed-off-by: Cheng-Yi Chiang
    Link: https://lore.kernel.org/r/20191028095229.99438-1-cychiang@chromium.org
    Signed-off-by: Mark Brown

    Cheng-Yi Chiang
     

03 Oct, 2019

1 commit

  • b1e620e7d   ASoc: rockchip: i2s: Fix RPM imbalance ... Browse Code »

    If rockchip_pcm_platform_register() fails, e.g. upon deferring to wait
    for an absent DMA channel, we return without disabling RPM, which makes
    subsequent re-probe attempts scream with errors about the unbalanced
    enable. Don't do that.

    Fixes: ebb75c0bdba2 ("ASoC: rockchip: i2s: Adjust devm usage")
    Signed-off-by: Robin Murphy
    Link: https://lore.kernel.org/r/bcb12a849a05437fb18372bc7536c649b94bdf07.1570029862.git.robin.murphy@arm.com
    Signed-off-by: Mark Brown

    Robin Murphy
     

18 Sep, 2019

1 commit

  • 4feaab05d   Merge tag 'leds-for-5.4-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/j.… ... Browse Code »

    …anaszewski/linux-leds

    Pull LED updates from Jacek Anaszewski:
    "In this cycle we've finally managed to contribute the patch set
    sorting out LED naming issues. Besides that there are many changes
    scattered among various LED class drivers and triggers.

    LED naming related improvements:

    - add new 'function' and 'color' fwnode properties and deprecate
    'label' property which has been frequently abused for conveying
    vendor specific names that have been available in sysfs anyway

    - introduce a set of standard LED_FUNCTION* definitions

    - introduce a set of standard LED_COLOR_ID* definitions

    - add a new {devm_}led_classdev_register_ext() API with the
    capability of automatic LED name composition basing on the
    properties available in the passed fwnode; the function is
    backwards compatible in a sense that it uses 'label' data, if
    present in the fwnode, for creating LED name

    - add tools/leds/get_led_device_info.sh script for retrieving LED
    vendor, product and bus names, if applicable; it also performs
    basic validation of an LED name

    - update following drivers and their DT bindings to use the new LED
    registration API:

    - leds-an30259a, leds-gpio, leds-as3645a, leds-aat1290, leds-cr0014114,
    leds-lm3601x, leds-lm3692x, leds-lp8860, leds-lt3593, leds-sc27xx-blt

    Other LED class improvements:

    - replace {devm_}led_classdev_register() macros with inlines

    - allow to call led_classdev_unregister() unconditionally

    - switch to use fwnode instead of be stuck with OF one

    LED triggers improvements:

    - led-triggers:
    - fix dereferencing of null pointer
    - fix a memory leak bug

    - ledtrig-gpio:
    - GPIO 0 is valid

    Drop superseeded apu2/3 support from leds-apu since for apu2+ a newer,
    more complete driver exists, based on a generic driver for the AMD
    SOCs gpio-controller, supporting LEDs as well other devices:

    - drop profile field from priv data

    - drop iosize field from priv data

    - drop enum_apu_led_platform_types

    - drop superseeded apu2/3 led support

    - add pr_fmt prefix for better log output

    - fix error message on probing failure

    Other misc fixes and improvements to existing LED class drivers:

    - leds-ns2, leds-max77650:
    - add of_node_put() before return

    - leds-pwm, leds-is31fl32xx:
    - use struct_size() helper

    - leds-lm3697, leds-lm36274, leds-lm3532:
    - switch to use fwnode_property_count_uXX()

    - leds-lm3532:
    - fix brightness control for i2c mode
    - change the define for the fs current register
    - fixes for the driver for stability
    - add full scale current configuration
    - dt: Add property for full scale current.
    - avoid potentially unpaired regulator calls
    - move static keyword to the front of declarations
    - fix optional led-max-microamp prop error handling

    - leds-max77650:
    - add of_node_put() before return
    - add MODULE_ALIAS()
    - Switch to fwnode property API

    - leds-as3645a:
    - fix misuse of strlcpy

    - leds-netxbig:
    - add of_node_put() in netxbig_leds_get_of_pdata()
    - remove legacy board-file support

    - leds-is31fl319x:
    - simplify getting the adapter of a client

    - leds-ti-lmu-common:
    - fix coccinelle issue
    - move static keyword to the front of declaration

    - leds-syscon:
    - use resource managed variant of device register

    - leds-ktd2692:
    - fix a typo in the name of a constant

    - leds-lp5562:
    - allow firmware files up to the maximum length

    - leds-an30259a:
    - fix typo

    - leds-pca953x:
    - include the right header"

    * tag 'leds-for-5.4-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds: (72 commits)
    leds: lm3532: Fix optional led-max-microamp prop error handling
    led: triggers: Fix dereferencing of null pointer
    leds: ti-lmu-common: Move static keyword to the front of declaration
    leds: lm3532: Move static keyword to the front of declarations
    leds: trigger: gpio: GPIO 0 is valid
    leds: pwm: Use struct_size() helper
    leds: is31fl32xx: Use struct_size() helper
    leds: ti-lmu-common: Fix coccinelle issue in TI LMU
    leds: lm3532: Avoid potentially unpaired regulator calls
    leds: syscon: Use resource managed variant of device register
    leds: Replace {devm_}led_classdev_register() macros with inlines
    leds: Allow to call led_classdev_unregister() unconditionally
    leds: lm3532: Add full scale current configuration
    dt: lm3532: Add property for full scale current.
    leds: lm3532: Fixes for the driver for stability
    leds: lm3532: Change the define for the fs current register
    leds: lm3532: Fix brightness control for i2c mode
    leds: Switch to use fwnode instead of be stuck with OF one
    leds: max77650: Switch to fwnode property API
    led: triggers: Fix a memory leak bug
    ...

    Linus Torvalds
     

09 Sep, 2019

1 commit

  • f1879d7b9   ASoC: rockchip: ignore 0Hz sysclk ... Browse Code »

    This patch ignores sysclk setting if it is 0Hz.

    Some codecs treat 0Hz sysclk as signal of applying no constraints.
    This driver does not have such feature but current implementation
    outputs 'Failed to set mclk' error message if machine driver sets
    0Hz sysclk to this driver.

    Signed-off-by: Katsuhiro Suzuki
    Link: https://lore.kernel.org/r/20190907174332.19586-1-katsuhiro@katsuster.net
    Signed-off-by: Mark Brown

    Katsuhiro Suzuki
     

21 Aug, 2019

1 commit

13 Aug, 2019

1 commit

  • 7188f656c   ASoC: rockchip: rockchip_max98090: Set period size to 240 ... Browse Code »

    From stress testing of arecord, we found that period size
    greater than ~900 will bring pl330 to DYING state and
    can not recover within 100 iterations.
    The result is that arecord will stuck and get I/O error,
    and issue can not be recovered until reboot.

    This issue does not happen when period size is small.
    Set constraint of period size to 240 to prevent such issue.
    With the constraint, there will be no issue after 2000 iterations.

    We can revert this patch once the root cause is found
    in rockchip's pl330 implementation.

    Signed-off-by: Cheng-Yi Chiang
    Link: https://lore.kernel.org/r/20190813074430.191791-1-cychiang@chromium.org
    Signed-off-by: Mark Brown

    Cheng-Yi Chiang
     

10 Aug, 2019

1 commit

30 Jul, 2019

1 commit

  • cfba5de9b   drivers: Introduce device lookup variants by of_node ... Browse Code »

    Introduce wrappers for {bus/driver/class}_find_device() to
    locate devices by its of_node.

    Cc: Maarten Lankhorst
    Cc: Maxime Ripard
    Cc: dri-devel@lists.freedesktop.org
    Cc: David Airlie
    Cc: Daniel Vetter
    Cc: devicetree@vger.kernel.org
    Cc: Florian Fainelli
    Cc: Frank Rowand
    Cc: Heiko Stuebner
    Cc: Liam Girdwood
    Cc: linux-i2c@vger.kernel.org
    Cc: linux-rockchip@lists.infradead.org
    Cc: linux-spi@vger.kernel.org
    Cc: Mathieu Poirier
    Cc: Rob Herring
    Cc: Srinivas Kandagatla
    Cc: Takashi Iwai
    Cc: Alan Tull
    Cc: linux-fpga@vger.kernel.org
    Cc: Peter Rosin
    Cc: Florian Fainelli
    Cc: Heiner Kallweit
    Cc: "David S. Miller"
    Cc: Andrew Lunn
    Cc: Liam Girdwood
    Cc: "Rafael J. Wysocki"
    Cc: Thor Thayer
    Cc: Jiri Slaby
    Cc: Andrew Lunn
    Cc: Peter Rosin
    Signed-off-by: Suzuki K Poulose
    Acked-by: Lee Jones
    Acked-by: Wolfram Sang # I2C part
    Acked-by: Moritz Fischer # For FPGA part
    Acked-by: Mark Brown
    Link: https://lore.kernel.org/r/20190723221838.12024-3-suzuki.poulose@arm.com
    Signed-off-by: Greg Kroah-Hartman

    Suzuki K Poulose
     

26 Jul, 2019

2 commits

  • 3b46a67af   Merge branch 'asoc-5.3' into asoc-5.4 Browse Code »
    Mark Brown
     
  • 789e162a6   ASoC: rockchip: Fix mono capture ... Browse Code »

    This reverts commit db51707b9c9aeedd310ebce60f15d5bb006567e0.
    Revert "ASoC: rockchip: i2s: Support mono capture"

    Previous discussion in

    https://patchwork.kernel.org/patch/10147153/

    explains the issue of the patch.
    While device is configured as 1-ch, hardware is still
    generating a 2-ch stream.
    When user space reads the data and assumes it is a 1-ch stream,
    the rate will be slower by 2x.

    Revert the change so 1-ch is not supported.
    User space can selectively take one channel data out of two channel
    if 1-ch is preferred.
    Currently, both channels record identical data.

    Signed-off-by: Cheng-Yi Chiang
    Link: https://lore.kernel.org/r/20190726044202.26866-1-cychiang@chromium.org
    Signed-off-by: Mark Brown

    Cheng-Yi Chiang
     

22 Jul, 2019

2 commits

  • 4aefb7387   ASoC: rockchip-max98090: Remove MICBIAS as supply of input pin IN34 ... Browse Code »

    Commit ec0d23b295b9 ("ASoC: rockchip-max98090: Fix the Headset Mic
    route.") moved the MICBIAS widget to supply Headset Mic but forget to
    remove the MICBIAS widget to supply IN34 which is not really needed, so
    remove that path so we have:

    IN34
    Link: https://lore.kernel.org/r/20190719180558.11459-1-enric.balletbo@collabora.com
    Signed-off-by: Mark Brown

    Enric Balletbo i Serra
     
  • f86621cd6   SoC: rockchip: rockchip_max98090: Enable MICBIAS for headset keypress detection ... Browse Code »

    The TS3A227E says that the headset keypress detection needs the MICBIAS
    power in order to report the key events to ensure proper operation
    The headset keypress detection needs the MICBIAS power in order to report
    the key events all the time as long as MIC is present. So MICBIAS pin
    is forced on when a MICROPHONE is detected.

    On Veyron Minnie I observed that if the MICBIAS power is not present and
    the key press detection is activated (just because it is enabled when you
    insert a headset), it randomly reports a keypress on insert.
    E.g. (KEY_PLAYPAUSE)

    Event: (SW_HEADPHONE_INSERT), value 1
    Event: (SW_MICROPHONE_INSERT), value 1
    Event: -------------- SYN_REPORT ------------
    Event: (KEY_PLAYPAUSE), value 1

    Userspace thinks that KEY_PLAYPAUSE is pressed and produces the annoying
    effect that the media player starts a play/pause loop.

    Note that, although most of the time the key reported is the one
    associated with BTN_0, not always this is true. On my tests I also saw
    different keys reported

    Signed-off-by: Enric Balletbo i Serra
    Link: https://lore.kernel.org/r/20190719173929.24065-1-enric.balletbo@collabora.com
    Signed-off-by: Mark Brown

    Enric Balletbo i Serra
     

13 Jul, 2019

1 commit

  • f632a8170   Merge tag 'driver-core-5.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core ... Browse Code »

    Pull driver core and debugfs updates from Greg KH:
    "Here is the "big" driver core and debugfs changes for 5.3-rc1

    It's a lot of different patches, all across the tree due to some api
    changes and lots of debugfs cleanups.

    Other than the debugfs cleanups, in this set of changes we have:

    - bus iteration function cleanups

    - scripts/get_abi.pl tool to display and parse Documentation/ABI
    entries in a simple way

    - cleanups to Documenatation/ABI/ entries to make them parse easier
    due to typos and other minor things

    - default_attrs use for some ktype users

    - driver model documentation file conversions to .rst

    - compressed firmware file loading

    - deferred probe fixes

    All of these have been in linux-next for a while, with a bunch of
    merge issues that Stephen has been patient with me for"

    * tag 'driver-core-5.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core: (102 commits)
    debugfs: make error message a bit more verbose
    orangefs: fix build warning from debugfs cleanup patch
    ubifs: fix build warning after debugfs cleanup patch
    driver: core: Allow subsystems to continue deferring probe
    drivers: base: cacheinfo: Ensure cpu hotplug work is done before Intel RDT
    arch_topology: Remove error messages on out-of-memory conditions
    lib: notifier-error-inject: no need to check return value of debugfs_create functions
    swiotlb: no need to check return value of debugfs_create functions
    ceph: no need to check return value of debugfs_create functions
    sunrpc: no need to check return value of debugfs_create functions
    ubifs: no need to check return value of debugfs_create functions
    orangefs: no need to check return value of debugfs_create functions
    nfsd: no need to check return value of debugfs_create functions
    lib: 842: no need to check return value of debugfs_create functions
    debugfs: provide pr_fmt() macro
    debugfs: log errors when something goes wrong
    drivers: s390/cio: Fix compilation warning about const qualifiers
    drivers: Add generic helper to match by of_node
    driver_find_device: Unify the match function with class_find_device()
    bus_find_device: Unify the match callback with class_find_device
    ...

    Linus Torvalds
     

28 Jun, 2019

4 commits

  • 6c10da54f   ASoC: rockchip: rk3399_gru_sound: consider CPU-Platform possibility ... Browse Code »

    commit 961fb3c206dc ("ASoC: rockchip: rk3399_gru_sound: don't select
    unnecessary Platform")

    Current ALSA SoC avoid to add duplicate component to rtd,
    and this driver was selecting CPU component as Platform component.
    Thus, above patch removed Platform settings from this driver,
    because it assumed these are same component.

    But, some CPU driver is using generic DMAEngine, in such case, both
    CPU component and Platform component will have same of_node/name.
    In other words, there are some components which are different but
    have same of_node/name.

    In such case, Card driver definitely need to select Platform even
    though it is same as CPU.
    It is depends on CPU driver, but is difficult to know it from Card driver.
    This patch reverts above patch.

    Fixes: commit 961fb3c206dc ("ASoC: rockchip: rk3399_gru_sound: don't select unnecessary Platform")
    Signed-off-by: Kuninori Morimoto
    Signed-off-by: Mark Brown

    Kuninori Morimoto
     
  • f94d7b6e6   ASoC: rockchip: rockchip_rt5645: consider CPU-Platform possibility ... Browse Code »

    commit 27a37973a6f1 ("ASoC: rockchip: rockchip_rt5645: don't select
    unnecessary Platform")

    Current ALSA SoC avoid to add duplicate component to rtd,
    and this driver was selecting CPU component as Platform component.
    Thus, above patch removed Platform settings from this driver,
    because it assumed these are same component.

    But, some CPU driver is using generic DMAEngine, in such case, both
    CPU component and Platform component will have same of_node/name.
    In other words, there are some components which are different but
    have same of_node/name.

    In such case, Card driver definitely need to select Platform even
    though it is same as CPU.
    It is depends on CPU driver, but is difficult to know it from Card driver.
    This patch reverts above patch.

    Fixes: commit 27a37973a6f1 ("ASoC: rockchip: rockchip_rt5645: don't select unnecessary Platform")
    Signed-off-by: Kuninori Morimoto
    Signed-off-by: Mark Brown

    Kuninori Morimoto
     
  • 5554af40e   ASoC: rockchip: rockchip_max98090: consider CPU-Platform possibility ... Browse Code »

    commit 7df405ae5895 ("ASoC: rockchip: rockchip_max98090: don't select
    unnecessary Platform")

    Current ALSA SoC avoid to add duplicate component to rtd,
    and this driver was selecting CPU component as Platform component.
    Thus, above patch removed Platform settings from this driver,
    because it assumed these are same component.

    But, some CPU driver is using generic DMAEngine, in such case, both
    CPU component and Platform component will have same of_node/name.
    In other words, there are some components which are different but
    have same of_node/name.

    In such case, Card driver definitely need to select Platform even
    though it is same as CPU.
    It is depends on CPU driver, but is difficult to know it from Card driver.
    This patch reverts above patch.

    Fixes: commit 7df405ae5895 ("ASoC: rockchip: rockchip_max98090: don't select unnecessary Platform")
    Signed-off-by: Kuninori Morimoto
    Signed-off-by: Mark Brown

    Kuninori Morimoto
     
  • 418e12fca   ASoC: rockchip: rk3288_hdmi_analog: consider CPU-Platform possibility ... Browse Code »

    commit 9c21e82c165c ("ASoC: rockchip: rk3288_hdmi_analog: don't select
    unnecessary Platform")

    Current ALSA SoC avoid to add duplicate component to rtd,
    and this driver was selecting CPU component as Platform component.
    Thus, above patch removed Platform settings from this driver,
    because it assumed these are same component.

    But, some CPU driver is using generic DMAEngine, in such case, both
    CPU component and Platform component will have same of_node/name.
    In other words, there are some components which are different but
    have same of_node/name.

    In such case, Card driver definitely need to select Platform even
    though it is same as CPU.
    It is depends on CPU driver, but is difficult to know it from Card driver.
    This patch reverts above patch.

    Fixes: commit 9c21e82c165c ("ASoC: rockchip: rk3288_hdmi_analog: don't select unnecessary Platform")
    Signed-off-by: Kuninori Morimoto
    Signed-off-by: Mark Brown

    Kuninori Morimoto
     

26 Jun, 2019

1 commit

25 Jun, 2019

1 commit

  • 30b233b1c   ASoC: rk3399_gru_sound: Support 32, 44.1 and 88.2 kHz sample rates ... Browse Code »

    According to the datasheet the max98357a also supports 32, 44.1 and
    88.2 kHz sample rate. This support was also introduced recently by
    commit fdf34366d324 ("ASoC: max98357a: add missing supported rates").

    Actually the machine driver validates the supported sample rates but
    this is not really needed because the component driver can all apply
    whatever constraints are needed and do their own validation. So, remove
    the checks from the machine driver as are not needed at all. This way,
    we also support 32, 44.1 and 88.2 kHz sample rates and we get rid of the
    errors like the below.

    rk3399-gru-sound sound: rockchip_sound_max98357a_hw_params() doesn't support this sample rate: 44100
    rk3399-gru-sound sound: ASoC: machine hw_params failed: -22

    Signed-off-by: Enric Balletbo i Serra
    Signed-off-by: Mark Brown

    Enric Balletbo i Serra
     

24 Jun, 2019

1 commit

  • 418e3ea15   bus_find_device: Unify the match callback with class_find_device ... Browse Code »

    There is an arbitrary difference between the prototypes of
    bus_find_device() and class_find_device() preventing their callers
    from passing the same pair of data and match() arguments to both of
    them, which is the const qualifier used in the prototype of
    class_find_device(). If that qualifier is also used in the
    bus_find_device() prototype, it will be possible to pass the same
    match() callback function to both bus_find_device() and
    class_find_device(), which will allow some optimizations to be made in
    order to avoid code duplication going forward. Also with that, constify
    the "data" parameter as it is passed as a const to the match function.

    For this reason, change the prototype of bus_find_device() to match
    the prototype of class_find_device() and adjust its callers to use the
    const qualifier in accordance with the new prototype of it.

    Cc: Alexander Shishkin
    Cc: Andrew Lunn
    Cc: Andreas Noever
    Cc: Arnd Bergmann
    Cc: Bjorn Helgaas
    Cc: Corey Minyard
    Cc: Christian Borntraeger
    Cc: David Kershner
    Cc: "David S. Miller"
    Cc: David Airlie
    Cc: Felipe Balbi
    Cc: Frank Rowand
    Cc: Grygorii Strashko
    Cc: Harald Freudenberger
    Cc: Hartmut Knaack
    Cc: Heiko Stuebner
    Cc: Jason Gunthorpe
    Cc: Jonathan Cameron
    Cc: "James E.J. Bottomley"
    Cc: Len Brown
    Cc: Mark Brown
    Cc: Michael Ellerman
    Cc: Michael Jamet
    Cc: "Martin K. Petersen"
    Cc: Peter Oberparleiter
    Cc: Sebastian Ott
    Cc: Srinivas Kandagatla
    Cc: Yehezkel Bernat
    Cc: rafael@kernel.org
    Acked-by: Corey Minyard
    Acked-by: David Kershner
    Acked-by: Mark Brown
    Acked-by: Rafael J. Wysocki
    Acked-by: Srinivas Kandagatla
    Acked-by: Wolfram Sang # for the I2C parts
    Acked-by: Rob Herring
    Signed-off-by: Suzuki K Poulose
    Signed-off-by: Greg Kroah-Hartman

    Suzuki K Poulose
     

19 Jun, 2019

5 commits

17 Jun, 2019

1 commit

  • 41d92e0c8   ASoC: rockchip: pdm: select CONFIG_RATIONAL ... Browse Code »

    Without this, we get a link error:

    sound/soc/rockchip/rockchip_pdm.o: In function `rockchip_pdm_hw_params':
    rockchip_pdm.c:(.text+0x754): undefined reference to `rational_best_approximation'

    Fixes: 624e8e00acaf ("ASoC: rockchip: pdm: fixup pdm fractional div")
    Signed-off-by: Arnd Bergmann
    Signed-off-by: Mark Brown

    Arnd Bergmann
     

07 Jun, 2019

1 commit