ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Tokamak has joined #armlinux
alpernebbi has quit [Ping timeout: 264 seconds]
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
alpernebbi has joined #armlinux
Tokamak has joined #armlinux
Tokamak has quit [Client Quit]
naoki has joined #armlinux
heat has quit [Ping timeout: 260 seconds]
nexalam_ has joined #armlinux
nexalam__ has quit [Ping timeout: 260 seconds]
macromorgan has quit [Read error: Connection reset by peer]
macromorgan has joined #armlinux
apritzel has joined #armlinux
macromorgan has quit [Read error: Connection reset by peer]
macromorgan has joined #armlinux
biju has joined #armlinux
apritzel has quit [Ping timeout: 246 seconds]
monstr has joined #armlinux
biju has quit [Quit: Client closed]
guillaume_g has joined #armlinux
biju has joined #armlinux
elastic_dog has quit [Ping timeout: 264 seconds]
elastic_dog has joined #armlinux
prabhakarlad has joined #armlinux
elastic_dog has quit [Client Quit]
elastic_dog has joined #armlinux
sszy has joined #armlinux
viorel_suman has joined #armlinux
Pali has joined #armlinux
headless has joined #armlinux
Pali has quit [Ping timeout: 246 seconds]
luispm has joined #armlinux
apritzel_ has joined #armlinux
prabhakarlad95 has joined #armlinux
prabhakarlad has quit [Ping timeout: 252 seconds]
heat has joined #armlinux
cbeznea has joined #armlinux
headless has quit [Quit: Konversation terminated!]
plappermaul has joined #armlinux
torez has joined #armlinux
Amit_T has joined #armlinux
apritzel_ is now known as apritzel
biju has quit [Quit: Client closed]
heat_ has joined #armlinux
heat has quit [Ping timeout: 250 seconds]
biju has joined #armlinux
Amit_T has quit [Ping timeout: 268 seconds]
monstr has quit [Remote host closed the connection]
rfried has quit [Quit: The Lounge - https://thelounge.github.io]
rfried has joined #armlinux
Amit_T has joined #armlinux
apritzel_ has joined #armlinux
apritzel_ has left #armlinux [#armlinux]
apritzel_ has joined #armlinux
apritzel has quit [Ping timeout: 252 seconds]
plappermaul has quit [Quit: Client closed]
tachoknight has joined #armlinux
headless has joined #armlinux
<hanetzer> is there any instruction in the arm isa that says 'stop here and wait for debugger'? b . seems to funk up in my situation
psydroid has joined #armlinux
<clever> hanetzer: i think there is one that immediately drops into the debugger, typically used for software breakpoints
<clever> what is `b .` not doing right?
<hanetzer> halting is a pain, sometimes it 'doesn't take'. might have to do with the fact its a dual core proc.
<apritzel_> hanetzer: there is "hlt", that should take you into external (JTAG) debuggers, and triggers an exception if none is connected
* hanetzer notes
<clever> i think hlt is what is used by software breakpoints?
<clever> and the software debugger can also catch it, so ptrace may use that
<apritzel_> I think "brk" is more for the software debugger case
headless has quit [Quit: Konversation terminated!]
Pali has joined #armlinux
prabhakarlad95 has quit [Quit: Client closed]
sszy has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
prabhakarlad has joined #armlinux
<macromorgan> are there any good IRC channels for i2c questions? I'm trying to port a BSP driver to mainline and want to redo some functions with kernel provided macros. Problem is, I have no idea what the current driver is doing (it's just a bunch of raw read/write calls now).
guillaume_g has quit [Quit: Konversation terminated!]
viorel_suman has quit [Quit: WeeChat 3.5]
<ukleinek> macromorgan: ask your BSP vendor?
<macromorgan> that's... yeah, probably not going to work. http://www.hynitron.com/
<macromorgan> I did email them though, so far radio silence
<ukleinek> macromorgan: is there a mainline driver?
<macromorgan> no
<broonie> Often it's easier to go to the datasheet and start from scratch.
alpernebbi has quit [Ping timeout: 264 seconds]
amitk has quit [Quit: leaving]
<ukleinek> ..ooOO(if you have a datasheet)
<macromorgan> I've taken the very ugly BSP driver and so far changed everything I could to devm based functions, replaced their non-standard devicetree parsing with the standard ones, and stripped a bunch of other stuff too
Lucanis0 has joined #armlinux
Lucanis0 has quit [Changing host]
Lucanis0 has joined #armlinux
amitk has joined #armlinux
<macromorgan> closest thing I have this this: https://www.buydisplay.com/download/ic/CST340%20DataSheet%20V2.3.pdf
Amit_T has quit [Ping timeout: 268 seconds]
<macromorgan> but of course those registers don't make sense for an i2c device
<broonie> Why not?
<macromorgan> ultimately I'm just wondering if I see a i2c_master_send(client, buf, 2) and I know the buf is buf[0] = 0xd1 and buf[1] = 0x01, what is it doing? Sending a value of 0x01 to address 0xd1?
<ukleinek> ..ooOO(ah, this is a i2c device, up to know I thought that's about a i2c controller)
<ukleinek> no, it sends two bytes to the address defined by client
Lucanis has quit [Ping timeout: 244 seconds]
alpernebbi has joined #armlinux
<macromorgan> okay, so i2c_master_send doesn't necessarily mean it's writing to a specific register, it's just sending 2 bytes?
<broonie> Yes, I2C is just a byte stream in both directions.
<broonie> Any meaning is assigned by the device.
<macromorgan> ...so I'm guessing this driver is a poor candidate for regmap then :-(
<macromorgan> okay, thanks
<ukleinek> usually there is a register model though, the most usual is that sending these two bytes sets the register at address 0xd1 to 0x1
amitk has quit [Ping timeout: 265 seconds]
<broonie> Perhaps, perhaps not. It depends what the device does.
<macromorgan> touchscreen
<broonie> Right, but in terms of how it structures the control interface.
<ukleinek> broonie: ack, that's why I used "usually"
<macromorgan> okay, have to assume register based access might not be viable, that helps at least.
<ukleinek> macromorgan: "touchscreen" is a bit like answering "my car is red" on "usually cars have their steering wheel on the left side, in UK it's on the right".
<macromorgan> yeah, in over my head but never let that stop me before
<broonie> Look at regmap-i2c.c - it will cope with anything where the interface is some number of bits of register address followed by zero or more padding bits then some number of n bit registers.
apritzel_ has quit [Ping timeout: 252 seconds]
Amit_T has joined #armlinux
zkrx has quit []
luispm has quit [Quit: Leaving]
Tokamak has joined #armlinux
Tokamak has quit [Read error: Connection reset by peer]
Tokamak has joined #armlinux
plappermaul has joined #armlinux
zkrx has joined #armlinux
headless has joined #armlinux
zkrx has quit [Ping timeout: 246 seconds]
zkrx has joined #armlinux
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zkrx has quit []
Lucanis0 has quit [Quit: Leaving]
Lucanis has joined #armlinux
torez has quit [Remote host closed the connection]
Tokamak has joined #armlinux
headless has quit [Ping timeout: 244 seconds]
headless has joined #armlinux
plappermaul has quit [Quit: Client closed]
apritzel has joined #armlinux
zkrx has joined #armlinux
Amit_T has quit [Quit: Leaving]
zkrx has quit [Ping timeout: 246 seconds]
zkrx has joined #armlinux
<hanetzer> heh... I recently did a combo approach. modeled the soc in qemu and ran the bsp driver in it, had qemu log the io operations
<hanetzer> re: bsp uggo drivers
<hanetzer> I should look into regmap stuff more. the rtc on the soc I'm tinkering is a bit weird
Tokamak has quit [Read error: Connection reset by peer]
Tokamak has joined #armlinux
apritzel_ has joined #armlinux
heat_ has quit [Remote host closed the connection]
heat has joined #armlinux
apritzel_ has quit [Ping timeout: 246 seconds]
headless has quit [Quit: Konversation terminated!]
heat_ has joined #armlinux
heat has quit [Read error: Connection reset by peer]
Pali has quit [Ping timeout: 246 seconds]