[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e3ebba30-65ec-183a-eb91-c5147c28441d@linux.intel.com>
Date: Wed, 26 Oct 2022 15:14:10 -0500
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
vkoul@...nel.org, yung-chuan.liao@...ux.intel.com
Cc: andersson@...nel.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, sanyog.r.kale@...el.com,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: [PATCH 6/6] soundwire: qcom: add support for v1.7 Soundwire
Controller
> @@ -1582,6 +1597,7 @@ static const struct of_device_id qcom_swrm_of_match[] = {
> { .compatible = "qcom,soundwire-v1.3.0", .data = &swrm_v1_3_data },
> { .compatible = "qcom,soundwire-v1.5.1", .data = &swrm_v1_5_data },
> { .compatible = "qcom,soundwire-v1.6.0", .data = &swrm_v1_6_data },
> + { .compatible = "qcom,soundwire-v1.7.0", .data = &swrm_v1_5_data },
is this line intentional, it looks odd that 1.7 is compatible with 1.5,
but 1.6 isn't?
Powered by blists - more mailing lists