On 2020-02-10 13:26, Mark Brown wrote:
On Mon, Feb 10, 2020 at 10:45:16AM -0500, Adam Serbinski wrote:
On 2020-02-10 08:36, Mark Brown wrote:
> This would seem like an excellent thing to put in the driver for the
> baseband or bluetooth.
The value that must be set to this control is not available to the
bluetooth
driver. It originates from the bluetooth stack in userspace, typically
either blueZ or fluoride, as a result of a negotiation between the two
devices participating in the HFP call.
To repeat my comment on another patch in the series there should still
be some representation of the DAI for this device in the kernel.
Respectfully, I'm not sure I understand what it is that you are
suggesting.
Is it your intention to suggest that instead of adding controls to the
machine driver, I should instead write a codec driver to contain those
controls?
Or is it your intention to suggest that something within the kernel is
already aware of the rate to be set, and it is that which should set the
rate rather than a control?
