From: Matt Flax <flatmax@flatmax.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
alsa-devel@alsa-project.org, llvm@lists.linux.dev,
kbuild-all@lists.01.org, broonie@kernel.org
Subject: Re: [PATCH v2] ASoC: codecs: add uspport for the TI SRC4392 codec
Date: Wed, 17 Aug 2022 15:44:33 +1000 [thread overview]
Message-ID: <f8439531-897a-c25a-688b-be01290b006d@flatmax.com> (raw)
In-Reply-To: <YvvbKry5FVFbNdcI@dev-arch.thelio-3990X>
On 17/8/22 04:00, Nathan Chancellor wrote:
>> 265 /* set the PLL for the digital receiver */
>> 266 switch (src4xxx->mclk_hz) {
>> 267 case 24576000:
>> 268 pj = 0x22;
>> 269 jd = 0x00;
>> 270 d = 0x00;
>> 271 break;
>> 272 case 22579200:
>> 273 pj = 0x22;
>> 274 jd = 0x1b;
>> 275 d = 0xa3;
>> 276 break;
>> > 277 default:
>> 278 /* don't error out here,
>> 279 * other parts of the chip are still functional
>> 280 */
>> 281 dev_info(component->dev,
>> 282 "Couldn't set the RCV PLL as this master clock rate is unknown\n");
> In the final commit, there is a 'break' here. Should it be a 'return 0'
> instead? Or should there be a different fix for these warnings?
The data sheet for the src4392 doesn't list defaults for these registers
(loaded with pj, jd and d). The actual state of these registers is not
known until we load them with something, arbitrary or not.
{ SRC4XXX_RCV_PLL_0F, 0x00 }, /* not spec. in the datasheet */
{ SRC4XXX_RCV_PLL_10, 0xff }, /* not spec. in the datasheet */
{ SRC4XXX_RCV_PLL_11, 0xff }, /* not spec. in the datasheet */
The state of DIR PLL registers aren't important if the user doesn't
specify a known mclk frequency. The implication is that the DIR will
not function, however that is already implied by the user lacking to
specify a known mclk frequency.
The other functions on the chip (port A/B I2S, SRC, DIT, etc) will
behave as per usual, only the DIR will be dysfunctional.
>> 283 }
>> 284 ret = regmap_write(src4xxx->regmap, SRC4XXX_RCV_PLL_0F, pj);
>> 285 if (ret < 0)
>> 286 dev_err(component->dev,
>> 287 "Failed to update PLL register 0x%x\n",
>> 288 SRC4XXX_RCV_PLL_0F);
>> > 289 ret = regmap_write(src4xxx->regmap, SRC4XXX_RCV_PLL_10, jd);
>> 290 if (ret < 0)
>> 291 dev_err(component->dev,
>> 292 "Failed to update PLL register 0x%x\n",
>> 293 SRC4XXX_RCV_PLL_10);
>> > 294 ret = regmap_write(src4xxx->regmap, SRC4XXX_RCV_PLL_11, d);
>> 295 if (ret < 0)
>> 296 dev_err(component->dev,
>> 297 "Failed to update PLL register 0x%x\n",
>> 298 SRC4XXX_RCV_PLL_11);
>>
> Cheers,
> Nathan
next prev parent reply other threads:[~2022-08-17 5:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220808214028.2502801-1-flatmax@flatmax.com>
2022-08-09 1:49 ` [PATCH v2] ASoC: codecs: add uspport for the TI SRC4392 codec kernel test robot
2022-08-16 18:00 ` Nathan Chancellor
2022-08-17 5:44 ` Matt Flax [this message]
2022-08-17 15:45 ` Nathan Chancellor
2022-08-22 18:09 ` Mark Brown
2022-08-22 18:32 ` Nathan Chancellor
2022-08-17 16:21 ` Mark Brown
2022-08-17 17:23 ` Nathan Chancellor
2022-08-18 11:44 ` Mark Brown
2022-08-09 8:25 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f8439531-897a-c25a-688b-be01290b006d@flatmax.com \
--to=flatmax@flatmax.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox