Skip to content

Enable Hifiberry DAC with VC4 driver #68

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
joaodriessen opened this issue Nov 2, 2016 · 8 comments
Closed

Enable Hifiberry DAC with VC4 driver #68

joaodriessen opened this issue Nov 2, 2016 · 8 comments

Comments

@joaodriessen
Copy link

This is a support related question, so I apologise for posting it here, but I could not find relevant documentation on this.

running the 4.4.28 kernel on archlinuxarm.

enabling the VC4 driver (dtoverlay=vc4-kms-v3d) I no longer get audio from my DAC (dtoverlay=hifiberry-dacplus).
Is there a way to use you video driver in conjunction with the digital analog converter from HifiBerry?

@anholt
Copy link
Owner

anholt commented Nov 2, 2016

My best bet would be that something went wrong in your config.txt setup. I don't know of any way that vc4 should interact with non-HDMI audio.

@joaodriessen
Copy link
Author

joaodriessen commented Nov 2, 2016

The hardware is not being recognised by my system when I enable the video driver.

for reference, my config.txt, (maybe I screwed something up):

#hdmi_group=1
#hdmi_mode=4
#disable_overscan=1
#framebuffer_depth=32
#gpu_mem=256
dtoverlay=hifiberry-dacplus

avoid_warnings=2
dtoverlay=vc4-kms-v3d

@schnitzeltony
Copy link

On Wed, Nov 2, 2016 at 9:07 PM, Joao Driessen [email protected]
wrote:

The hardware is not being recognised by my system when I enable the video
driver.

for reference, my config.txt, (maybe I screwed something up):
See /boot/overlays/README for all available options

#hdmi_group=1
#hdmi_mode=4
#disable_overscan=1
#framebuffer_depth=32
#gpu_mem=256
dtoverlay=hifiberry-dacplus

avoid_warnings=2
dtoverlay=vc4-kms-v3d

I have same problem with a very similar config.txt:

dtoverlay=hifiberry-dacplus

Enable VC4 Graphics

dtoverlay=vc4-kms-v3d,cma-256

My kernel is

git://github.com/raspberrypi/linux.git
branch=rpi-4.4.y
commit 1c8b82b (should be quite recent
4.4.27)

I attached journalctl extract - see attachment. Seems i2s wants memory
already allocated. Checked hifiberry-dacplus.dts: i2s is required by
hifiberry.

I think this is more an issue for https://github.com/raspberrypi/linux.
Shall I open an issue there?

Ah one thing - (my environment does not boot without vc4 overlay):
@*joaodriessen
https://github.com/joaodriessen *is that correct that hifiberry works
fine for you in case vc4 is not enabled?

@joaodriessen
Copy link
Author

Yes, as long as I don't enable Eric Anholt's driver, the hifiberry DAC+ works.

@schnitzeltony
Copy link

n Wed, Nov 2, 2016 at 10:52 PM, Joao Driessen [email protected]
wrote:

Yes, as long as I don't enable Eric Anholt's driver, the hifiberry DAC+
works.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#68 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACc-L74i70WrNLqofib8D8nyCGaZlg_Oks5q6QY2gaJpZM4Km9jS
.

I think this is same as raspberrypi#1420 -
w can close this one

@joaodriessen
Copy link
Author

would prefer to leave this issue open here so people who have the same issue find it and can follow the cookiecrumbs to raspberrypi#1420 and raspberrypi#1231

@joaodriessen
Copy link
Author

joaodriessen commented Nov 6, 2016

using "vc4-fkms-v3d" the HifiBerry DAC will work on kernel 4.4
But I can't get any graphics acceleration going on with this setting yet, and can't say if that's due to my system setup or that it's not ready yet, I have no idea how to properly set this one up.

@anholt
Copy link
Owner

anholt commented Jan 26, 2017

There's not much I can do for 4.4 if they're not taking the i2s clock backport. Downstream 4.9 has cprman on by default now, so closing this.

@anholt anholt closed this as completed Jan 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants