narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
sputnik_ has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
Barada has joined #linux-amlogic
Barada has quit [Client Quit]
Barada has joined #linux-amlogic
Barada has quit [Quit: Barada]
Barada has joined #linux-amlogic
ndufresne has quit [Ping timeout: 256 seconds]
ndufresne has joined #linux-amlogic
yann has quit [Ping timeout: 245 seconds]
cosm has quit [Ping timeout: 260 seconds]
cosm has joined #linux-amlogic
ldevulder has joined #linux-amlogic
sputnik__ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 268 seconds]
yann has joined #linux-amlogic
sputnik__ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Client Quit]
sputnik_ has joined #linux-amlogic
<narmstrong> The_Coolest: hi, not much overhead but gpio bitbanging will never be efficient using the gpio framework
<narmstrong> The_Coolest: by the way, why don’t you use the kernel gpio bitbanging helpers to i2c and spi ???
<narmstrong> and why bitbanging ? The aml SoCs have plenty of i2c interfaces
sputnik_ has quit [Remote host closed the connection]
ldevulder has quit [Ping timeout: 268 seconds]
ldevulder has joined #linux-amlogic
ldevulder has quit [Ping timeout: 255 seconds]
ldevulder has joined #linux-amlogic
Barada has quit [Quit: Barada]
<The_Coolest> narmstrong>> Hmm. I think I looked at those helpers, they won't do what I need because they use DTB definitions.
<The_Coolest> And bitbanging because most of the hardware the code will be running on won't have the display connected to a SPI\I2C port
chewitt has joined #linux-amlogic
<narmstrong> The_Coolest: question, is this for mainline Linux ? 5 lines of DT vs 500k lines of possible buggy custom code ? These helpers has been written to avoid needing to rewrite them again and are bug-free ;-)
jakogut_ has joined #linux-amlogic
jakogut_ has quit [Remote host closed the connection]
jakogut_ has joined #linux-amlogic
yann has quit [Ping timeout: 244 seconds]
jakogut_ has quit [Read error: Connection reset by peer]
jakogut_ has joined #linux-amlogic
jakogut_ has quit [Ping timeout: 240 seconds]
The_Coolest has quit [Ping timeout: 256 seconds]
The_Coolest has joined #linux-amlogic
<The_Coolest> Can't do it in DT because the whole point of my driver is to be easily configurable, rather than having to maintain a bunch of DTBs.
<The_Coolest> that came out wrong.
<The_Coolest> The point is for the driver to work on any Amlogic S905\S912 tv box/SBC. Be easy to configure, and not require maintaining a bunch of DTBs - as we already tried that bit.
<The_Coolest> We're also looking at possibly adding support for other platforms too.
<The_Coolest> Currently we're building against 3.14 kernel
<The_Coolest> narmstrong ^
yann has joined #linux-amlogic
trem has joined #linux-amlogic
vagrantc has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
Guest35713 has quit [Ping timeout: 276 seconds]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Client Quit]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
mag has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
trem has quit [Quit: Leaving]
mag has quit [Ping timeout: 240 seconds]
mag has joined #linux-amlogic
sputnik__ has joined #linux-amlogic
mastertheknife has quit [Ping timeout: 240 seconds]
mastertheknife has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 260 seconds]