Go to advanced search

by HiassofT
Wed Feb 28, 2018 2:41 pm
Forum: Device Tree
Topic: Possibility for multiple instances of LIRC?
Replies: 41
Views: 13821

Re: Possibility for multiple instances of LIRC?

Hmmm this seems to work fine here on RPi2. config.txt: dtoverlay=gpio-ir,gpio_pin=17 dtoverlay=gpio-ir-tx,gpio_pin=18 Terminal 1: root@raspbian:~# ir-keytable -s rc1 -p rc5 -t Protocols changed to rc-5 Testing events. Please, press CTRL-C to abort. 1519828026.219516: event type EV_MSC(0x04): scancod...
by HiassofT
Wed Feb 28, 2018 10:23 am
Forum: Device Tree
Topic: Possibility for multiple instances of LIRC?
Replies: 41
Views: 13821

Re: Possibility for multiple instances of LIRC?

When you run ir-keytable -t you may have to specify the protocol, eg use "ir-keytable -p rc5 -t". When you run mode2 it'll disable all in-kernel decoders. If you run "ir-keytable" it'll show which decoders are available and which ones are enabled. eg: # ir-keytable Found /sys/class/rc/rc0/ (/dev/inp...
by HiassofT
Tue Feb 27, 2018 10:00 am
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 926
Views: 480457

Re: STICKY: The I2S sound thread.

Ok. I hooked up the i2c lines, but am having issues seeing the device. I posted the issue in this thread... https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=206443 Any idea why I can see the USBi, but not the 1701? I2C address 0x34 seems to be correct. I2C uses 7bit address followed by a bit...
by HiassofT
Tue Feb 27, 2018 9:36 am
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 926
Views: 480457

Re: STICKY: The I2S sound thread.

When I do a playback open (snd_pcm_open) with "plughw:0,0" as the card name, and 48000 as speed, I can get alsa to open OK with 32,24 and 16 bits (though the hardware driver outputs only to 24 bits as mentioned in an earlier post) However, when I try an open using "dmix" as the card name, 32 an 24 ...
by HiassofT
Mon Feb 26, 2018 1:32 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 926
Views: 480457

Re: STICKY: The I2S sound thread.

From a quick glance the DT overlay looks OK to me.

But, as I wrote before, setup ADAU1701 to be controlled via I2C, hook up the I2C lines and allow the driver to control ADAU1701 via I2C like the driver expects it.

so long,

Hias
by HiassofT
Sun Feb 25, 2018 3:01 pm
Forum: HATs and other add-ons
Topic: Iqaudio DAC + and shutdown hardware button problem.
Replies: 2
Views: 908

Re: Iqaudio DAC + and shutdown hardware button problem.

IQaudio DAC only uses very few GPIOs (I2S, I2C, plus GPIO22 for mute on the DAC+) but you managed to pick one of the important, used ones (pin 5 is I2C clock line). Use eg pin 7 (GPIO4) instead, that one should be unused IIIRC

so long,

Hias
by HiassofT
Sun Feb 25, 2018 12:44 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 926
Views: 480457

Re: STICKY: The I2S sound thread.

You also have to add the adau1701 codec to devicetree so that the module is loaded and you can reference the codec in the simple-card fragment. Of course you also have to connect the I2C lines and use the correct I2C address in the fragment - plus maybe add the reset, pll, ... gpio properties so tha...
by HiassofT
Fri Feb 23, 2018 6:00 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 926
Views: 480457

Re: STICKY: The I2S sound thread.

Note that the generic spdif drivers used in the dual overlay only support 16 and 24 bit mode - you can check eg with aplay -v, if you play 32bit data plughw will automatically convert that to S24_LE. If you want 32bit output you need to use a codec driver that actually supports S32_LE mode, then the...
by HiassofT
Fri Feb 23, 2018 12:56 pm
Forum: Device Tree
Topic: Possibility for multiple instances of LIRC?
Replies: 41
Views: 13821

Re: Possibility for multiple instances of LIRC?

Ah, no. As I wrote before IrCOMM has nothing to do - and can't work with - infrared remote drivers. IrCOMM is designed to be used with IRDA ports, which the RPi doesn't have. Also IRDA uses a completely different way to transmit data than infrared remotes. Infrared remotes typically send bursts of I...
by HiassofT
Fri Feb 23, 2018 12:32 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 926
Views: 480457

Re: STICKY: The I2S sound thread.

When using RPi in I2S slave mode (i.e. codec is clock master) the most important thing is that you correctly reference and configure your codec in the devicetree. When you did that you just have to add the bitclock-master and frame-master properties like in the superaudioboard overlay. For details a...
by HiassofT
Tue Feb 20, 2018 10:03 am
Forum: Device Tree
Topic: Possibility for multiple instances of LIRC?
Replies: 41
Views: 13821

Re: Possibility for multiple instances of LIRC?

If you mean the ircomm protocol driver in the kernel - this has nothing to do with infrared remotes. The ircomm protocol emulates a serial port on IRDA interfaces. $ cat drivers/staging/irda/net/ircomm/Kconfig config IRCOMM tristate "IrCOMM protocol" depends on IRDA && TTY help Say Y here if you wan...
by HiassofT
Mon Feb 19, 2018 10:03 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 926
Views: 480457

Re: STICKY: The I2S sound thread.

Yes, RPi works fine in slave mode - quite a lot of soundcards use such a setup. Configuring RPi as I2S slave is easy, with simple-audio-card you just point the bitclock-master and frameclock-master properties to the codec. See for example this recently added overlay: https://github.com/raspberrypi/l...
by HiassofT
Sun Feb 18, 2018 1:13 am
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 926
Views: 480457

Re: STICKY: The I2S sound thread.

I'd recommend using a oscillator to drive MCLK and use the codec in master mode - this should work just fine. bcm2835 doesn't support MCLK output and using a fractional divider or MASH as a clock source for the codec isn't a good idea - best thing you could do is to generate a clock that's derived b...
by HiassofT
Fri Feb 16, 2018 9:13 am
Forum: Raspbian
Topic: GPIO IR remote
Replies: 22
Views: 16263

Re: GPIO IR remote

Odd that changing /etc/rc_maps.cfg didn't work, but this could be a bug in the ir-keytable version of Debian - we ran into a similar issue last year, and it's fixed in the latest upstream versions. But since the official hauppauge keymap worked for you there's an easy solution that doesn't involve i...
by HiassofT
Thu Feb 15, 2018 10:51 pm
Forum: Raspbian
Topic: GPIO IR remote
Replies: 22
Views: 16263

Re: GPIO IR remote

One minor but important correction - the debian package with ir-keytable is ir-keytable, not v4l-utils (the latter is for ir-ctl and other stuff). I've edited my post above and fixed my mistake.

so long,

Hias
by HiassofT
Thu Feb 15, 2018 8:55 pm
Forum: Raspbian
Topic: GPIO IR remote
Replies: 22
Views: 16263

Re: GPIO IR remote

Rough outline: - use dtoverlay=gpio-ir to activate the kernel drvier (make sure you DON'T use lirc_rpi) - apt-get install v4l-utils ir-keytable to get ir-keytable - if necessary change the IR remote settings (protocol, scancodes) via /etc/rc_maps.cfg and/or custom keymaps in /etc/rc_keymaps - apt-ge...
by HiassofT
Thu Feb 15, 2018 2:55 pm
Forum: Device Tree
Topic: Possibility for multiple instances of LIRC?
Replies: 41
Views: 13821

Re: Possibility for multiple instances of LIRC?

To make it easier to use multiple gpio-ir instances the overlays ( gpio-ir and gpio-ir-tx ) now use the magic "reg" property to prevent name clashes. Thanks a lot, this is a really nice feature! (although personally I have no use for multiple IR receivers/transmitters it will certainly be helpful f...
by HiassofT
Thu Feb 15, 2018 1:19 pm
Forum: Device Tree
Topic: Possibility for multiple instances of LIRC?
Replies: 41
Views: 13821

Re: Possibility for multiple instances of LIRC?

If you want to use lircd (the userspace program) you have to start separate instances for each /dev/lircX device. lirc_dev was a combined receiver and transmitter, but with gpio-ir-receiver / gpio-ir-tx these are now separate. Depending on what you exactly want to do you maybe can get away without u...
by HiassofT
Wed Feb 14, 2018 2:03 pm
Forum: Device Tree
Topic: Possibility for multiple instances of LIRC?
Replies: 41
Views: 13821

Re: Possibility for multiple instances of LIRC?

I'd recomment switching to kernel 4.14 which includes the upstream gpio-ir-tx and pwm-ir-tx drivers in addition to the gpio-ir-receiver driver. Then use a DT overlay like this to create multiple receiver and transmitter instances: /dts-v1/; /plugin/; / { compatible = "brcm,bcm2708"; fragment@0 { tar...
by HiassofT
Thu Feb 01, 2018 12:58 pm
Forum: Raspbian
Topic: ALSA microphone volume configuration
Replies: 2
Views: 11839

Re: ALSA microphone volume configuration

Testing softvol with the following .asoundrc worked fine with my Cirrus Logic audio card: pcm.softvol { type softvol slave.pcm "plughw:RPiCirrus" control.name "Softmaster" control.card RPiCirrus min_dB -10.0 max_dB 50.0 } You don't need mmap_emul (bcm2835-i2s supports mmap) and restricting channel/f...
by HiassofT
Sat Jan 27, 2018 3:00 pm
Forum: Advanced users
Topic: Moving Linux kernel to 4.14
Replies: 161
Views: 90349

Re: Moving Linux kernel to 4.14

FYI: Eric Anholt held a rather interesting talk about VC4 driver development a this week's linux.conf.au. It's up here on youtube: https://www.youtube.com/watch?v=hNeq-iG9pfc

so long,

Hias
by HiassofT
Wed Jan 24, 2018 9:23 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 926
Views: 480457

Re: STICKY: The I2S sound thread.

Rerouting the I2S GPIOs the way you'd like it doesn't work. bcm2835 doesn't support every function on every GPIO - actually only very limited options are available. A detailed table of possible configurations and ALT function numbers is available here: https://elinux.org/RPi_BCM2835_GPIOs This means...
by HiassofT
Mon Jan 22, 2018 10:37 am
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 926
Views: 480457

Re: STICKY: The I2S sound thread.

that actually explains what I see. I see on the analyzer that the incoming bit clock may be stepping too fast every now and then, is there a way to enforce to wait for the next frame clock (happy to patch the code for myself) because I currenlty can't influence the clock source. Page 121 of the "bc...
by HiassofT
Sun Jan 21, 2018 10:26 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: Raspberry PI2 I2S ADC
Replies: 6
Views: 5235

Re: Raspberry PI2 I2S ADC

If found support codec. Build kernel with this how to https://www.raspberrypi.org/documentation/linux/kernel/building.md And ... what next step? Create a devicetree overlay to enable the ADC/DAC. Easiest way to do this is via the simple-audio-card driver. Here's a recently added overlay that you ca...
by HiassofT
Fri Jan 19, 2018 11:00 am
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 926
Views: 480457

Re: STICKY: The I2S sound thread.

In slave mode bcm2835 only uses the externally supplied clocks. The I2S block runs in an independent clock domain, either clocked by the PCM clock or externally via BCLK input - in slave mode the PCM clock isn't even set up. In slave mode it's important that you setup the frame length parameters cor...

Go to advanced search