| Message ID | 20230414103941.39566-1-CTLIN0@nuvoton.com |
|---|---|
| State | Accepted |
| Commit | c26c5921e1a770e6c092c4d25dea19052bdfddab |
| Headers | show |
| Series | [1/2] ASoC: dt-bindings: nau8825: Add delay control for input path | expand |
On Fri, Apr 14, 2023 at 02:34:19PM +0200, Krzysztof Kozlowski wrote: > On 14/04/2023 12:39, David Lin wrote: > > + - nuvoton,adc-delay-ms: Delay (in ms) to make input path stable and avoid pop noise. The > > + default value is 125 and range between 125 to 500 ms. > Convert the binding to DT Schema first. That seems disproportionate for such a trivial change.
On 14/04/2023 15:58, Krzysztof Kozlowski wrote: > On 14/04/2023 15:46, Mark Brown wrote: >> On Fri, Apr 14, 2023 at 02:34:19PM +0200, Krzysztof Kozlowski wrote: >>> On 14/04/2023 12:39, David Lin wrote: >> >>>> + - nuvoton,adc-delay-ms: Delay (in ms) to make input path stable and avoid pop noise. The >>>> + default value is 125 and range between 125 to 500 ms. >> >>> Convert the binding to DT Schema first. >> >> That seems disproportionate for such a trivial change. > > What is the difference between: > 1. Adding 2 or 3 new properties to TXT file without converting the file > to DT Schema, > > 2. Adding 1 property in 2022 Sep. Then adding one more property now. > Then adding another property in 3 months. > > I don't see. > > Every time the excuse is the same - it is just one property, so let's > add it. Since this is second property, after we started enforcing DT > schema, I don't think my request is disproportionate. > BTW, the change from September was also sent to mailing lists ignoring Devicetree entirely. This does not help here, because now it looks like a pattern. Best regards, Krzysztof
On Fri, 14 Apr 2023 18:39:42 +0800, David Lin wrote: > Change the original fixed delay to the assignment from property. It will make > more flexible to different platforms for avoiding pop noise at the beginning > of recording. > > Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/2] ASoC: dt-bindings: nau8825: Add delay control for input path commit: c26c5921e1a770e6c092c4d25dea19052bdfddab [2/2] ASoC: nau8825: Add delay control for input path commit: fc0b096c92918c2ba4d76411ea763fdeb2ef6b0d All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark
On Fri, Apr 14, 2023 at 03:58:06PM +0200, Krzysztof Kozlowski wrote: > On 14/04/2023 15:46, Mark Brown wrote: > > That seems disproportionate for such a trivial change. > What is the difference between: > 1. Adding 2 or 3 new properties to TXT file without converting the file > to DT Schema, > 2. Adding 1 property in 2022 Sep. Then adding one more property now. > Then adding another property in 3 months. > I don't see. Me either, but I also don't see an issue with this situation. If someone wants to convert to schema they'll get round to it, meanwhile the code isn't held up by that process. > Every time the excuse is the same - it is just one property, so let's > add it. Since this is second property, after we started enforcing DT > schema, I don't think my request is disproportionate. > I think my request is reasonable. The schema conversion patches are very often disproportionately hard work, there's a lot of poorly communicated rules beyond whatever the tools actually check for.
On 4/15/2023 12:38 AM, Mark Brown wrote: > On Fri, Apr 14, 2023 at 03:58:06PM +0200, Krzysztof Kozlowski wrote: >> On 14/04/2023 15:46, Mark Brown wrote: >>> That seems disproportionate for such a trivial change. >> What is the difference between: >> 1. Adding 2 or 3 new properties to TXT file without converting the file >> to DT Schema, >> 2. Adding 1 property in 2022 Sep. Then adding one more property now. >> Then adding another property in 3 months. >> I don't see. > Me either, but I also don't see an issue with this situation. If > someone wants to convert to schema they'll get round to it, meanwhile > the code isn't held up by that process. > >> Every time the excuse is the same - it is just one property, so let's >> add it. Since this is second property, after we started enforcing DT >> schema, I don't think my request is disproportionate. >> I think my request is reasonable. > The schema conversion patches are very often disproportionately hard > work, there's a lot of poorly communicated rules beyond whatever the > tools actually check for. Thanks to the comments from Krzysztof Kozlowski and Mark. We will plan to gradually convert all txt files of codec driver of Nuvoton to yaml format.
diff --git a/Documentation/devicetree/bindings/sound/nau8825.txt b/Documentation/devicetree/bindings/sound/nau8825.txt index cb861aca8d40..a9c34526f4cb 100644 --- a/Documentation/devicetree/bindings/sound/nau8825.txt +++ b/Documentation/devicetree/bindings/sound/nau8825.txt @@ -74,6 +74,9 @@ Optional properties: - nuvoton,adcout-drive-strong: make the drive strength of ADCOUT IO PIN strong if set. Otherwise, the drive keeps normal strength. + - nuvoton,adc-delay-ms: Delay (in ms) to make input path stable and avoid pop noise. The + default value is 125 and range between 125 to 500 ms. + - clocks: list of phandle and clock specifier pairs according to common clock bindings for the clocks described in clock-names - clock-names: should include "mclk" for the MCLK master clock
Change the original fixed delay to the assignment from property. It will make more flexible to different platforms for avoiding pop noise at the beginning of recording. Signed-off-by: David Lin <CTLIN0@nuvoton.com> --- Documentation/devicetree/bindings/sound/nau8825.txt | 3 +++ 1 file changed, 3 insertions(+)