[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <s5hmuu8r9fm.wl-tiwai@suse.de>
Date: Mon, 30 Jul 2018 18:10:37 +0200
From: Takashi Iwai <tiwai@...e.de>
To: Jorge <jorge.sanjuan@...ethink.co.uk>
Cc: alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/4] ALSA: usb-audio: Initial Power Domain support
On Mon, 30 Jul 2018 18:05:47 +0200,
Jorge wrote:
>
>
>
> On 30/07/18 14:03, Takashi Iwai wrote:
> > On Mon, 30 Jul 2018 11:23:33 +0200,
> > Jorge Sanjuan wrote:
> >>
> >> diff --git a/include/linux/usb/audio-v3.h b/include/linux/usb/audio-v3.h
> >> index 334bfa6dfb47..786e5939d831 100644
> >> --- a/include/linux/usb/audio-v3.h
> >> +++ b/include/linux/usb/audio-v3.h
> >> @@ -447,4 +447,8 @@ struct uac3_interrupt_data_msg {
> >> /* BADD sample rate is always fixed to 48kHz */
> >> #define UAC3_BADD_SAMPLING_RATE 48000
> >>
> >> +/* BADD power domains recovery times */
> >> +#define UAC3_BADD_PD_RECOVER_D1D0 0x0258
> >> +#define UAC3_BADD_PD_RECOVER_D2D0 0x1770
> >
> > Please put the unit for these values. I guess they don't need to be
> > hex?
> >
>
> Hi!
>
> The BADD spec defines these inferred values as hex (see section 6.2.2.13
> of the spec). Should we keep them as per spec to avoid confusion? I'll
> update comment there with the units (50 us increments).
Well, if they were defined in hex, it makes sense to keep the raw
values as is. But it'd be also helpful to give a comment showing the
actual usecs.
thanks,
Takashi
Powered by blists - more mailing lists