Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Topping D10s DAC auto standby?
#31
(12-21-2023, 12:22 PM)Nutul Wrote:
(12-21-2023, 10:17 AM)Falco Wrote: And tested with the following code I can switch the USB2 ports off (and my topping D10s then also switches off)


Code:
sudo uhubctl -l 1-1 -a 0


And to switch back on again

Code:
sudo uhubctl -l 1-1 -a 1
After switching off and on again, my D10s comes back up fine again. Now to see if an easy switch can be made, or even an additional command when music stops and starts again...

One remark, I tested a RPi4B which has an USB2 and an USB3 hub. The catch is that the network port is connected to the USB3 hub so if you turn that off, you cannot turn back on again. I have my RPi with moOde connected via wifi and that did not give issues. So connect any dac to the USB2 port when using this approach, but I believe that's the advise anyway.

Is it also possible to just switch on/off the Topping, by means of "1-1.4" instead of the hub-wise "1-1"?
Just asking

It seems not to be possible due to RPi hardware limitations
https://github.com/mvp/uhubctl#raspberry...-specified
Reply
#32
(12-21-2023, 12:55 PM)Falco Wrote: It seems not to be possible due to RPi hardware limitations

Yes, I see, all ports are wired together...

Then I think it should work on all Pi models before model 4 with
Code:
sudo uhubctl -l 1-1 -p 2 -a 0/1

and on the model 4 with just
Code:
sudo uhubctl -l 1-1 -a 0/1

What do you think?
Reply
#33
(12-21-2023, 01:09 PM)Nutul Wrote:
(12-21-2023, 12:55 PM)Falco Wrote: It seems not to be possible due to RPi hardware limitations

Yes, I see, all ports are wired together...

Then I think it should work on all Pi models before model 4 with
Code:
sudo uhubctl -l 1-1 -p 2 -a 0/1

and on the model 4 with just
Code:
sudo uhubctl -l 1-1 -a 0/1

What do you think?

Yes I agree, with the remark that on the RPi4 you should connect your usb DAC to one of the black USB2 ports
Reply
#34
(12-21-2023, 01:11 PM)Falco Wrote: Yes I agree, with the remark that on the RPi4 you should connect your usb DAC to one of the black USB2 ports

Yes.
Now, the "only" problem I see for a RPi3 for example, is that you will have the DAC and possibly an external SSD connected...
Switching the DAC off will also power the disc off...
(on the Pi4 you may just connect the DAC to the 2.0 ports, and the disc to the 3.0 ones and you're done)
Reply
#35
(12-21-2023, 01:31 PM)Nutul Wrote:
(12-21-2023, 01:11 PM)Falco Wrote: Yes I agree, with the remark that on the RPi4 you should connect your usb DAC to one of the black USB2 ports

Yes.
Now, the "only" problem I see for a RPi3 for example, is that you will have the DAC and possibly an external SSD connected...
Switching the DAC off will also power the disc off...
(on the Pi4 you may just connect the DAC to the 2.0 ports, and the disc to the 3.0 ones and you're done)

Indeed, would be yet another argument to use a RPi4 for moOde, for the ones using an USB powered DAC that is. But I guess the actual power use benefit is rather small, with my topping D10s the main benefit is to shutdown the display.
Reply
#36
So the answer to my earlier question is no, you can't control individual USB ports and the specifics depend on the RPi model. 

For folks like me, who are using most or all of the available USB ports, were we to want to use uhubctl or similar, we'd have to deploy an external hub.  Not the end of the world, certainly, but unfortunate.

Thankfully, I don't have any peripherals for which I need this level of control but your results are good to know for those who do.

Regards,
Kent
Reply
#37
Thank you all for bringing information about this, this below worked for me on a raspberry 5 / topping dac.

I'm not sure if it suspends my other devices, an SSD and a FLIRC usb, probably, but so far it's not been an issue.

This is added in /etc/rc.local for a 15 minutes delay before port being suspended.

Code:
echo 900000 | sudo tee /sys/bus/usb/devices/1-2/power/autosuspend_delay_ms
echo auto | sudo tee /sys/bus/usb/devices/1-2/power/control
Reply
#38
(11-17-2024, 10:48 AM)lelobster Wrote: Thank you all for bringing information about this, this below worked for me on a raspberry 5 / topping dac.

I'm not sure if it suspends my other devices, an SSD and a FLIRC usb, probably, but so far it's not been an issue.

This is added in /etc/rc.local for a 15 minutes delay before port being suspended.

Code:
echo 900000 | sudo tee /sys/bus/usb/devices/1-2/power/autosuspend_delay_ms
echo auto | sudo tee /sys/bus/usb/devices/1-2/power/control

Thanks for this method, world that work for a RPI 4 as well?
And suspending turns your topping off? And it counts back to life when you start playing?
Because that procedure would be more convenient then mine...
Reply
#39
(11-17-2024, 02:08 PM)Falco Wrote:
(11-17-2024, 10:48 AM)lelobster Wrote: Thank you all for bringing information about this, this below worked for me on a raspberry 5 / topping dac.

I'm not sure if it suspends my other devices, an SSD and a FLIRC usb, probably, but so far it's not been an issue.

This is added in /etc/rc.local for a 15 minutes delay before port being suspended.

Code:
echo 900000 | sudo tee /sys/bus/usb/devices/1-2/power/autosuspend_delay_ms
echo auto | sudo tee /sys/bus/usb/devices/1-2/power/control

Thanks for this method, world that work for a RPI 4 as well?
And suspending turns your topping off? And it counts back to life when you start playing?
Because that procedure would be more convenient then mine...

The E70 DAC goes to standby a few seconds after and it goes live if I start playing, pretty convenient yes, but I don't know about rpi 4.

The DAC has an autostandby option that I turned on, I think I remember that D90 or D90S had that autostandby by default.

Maybe this can help about rpi 4: https://github.com/mvp/uhubctl#linux-usb-permissions
Reply


Forum Jump: