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
heat_ has joined #armlinux
heat has quit [Remote host closed the connection]
heat_ is now known as heat
jclsn has quit [Quit: WeeChat 4.3.2]
hanetzer has quit [Ping timeout: 264 seconds]
hanetzer has joined #armlinux
System_Error has quit [Remote host closed the connection]
rvalue has quit [Ping timeout: 256 seconds]
rvalue has joined #armlinux
punit has quit [Remote host closed the connection]
sally has quit [Remote host closed the connection]
heat has quit [Ping timeout: 264 seconds]
sally has joined #armlinux
lain6141 has quit [Read error: Connection reset by peer]
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #armlinux
pg12 has quit [Remote host closed the connection]
pg12 has joined #armlinux
nsaenz has joined #armlinux
CrashTestDummy has quit [Quit: Leaving]
System_Error has joined #armlinux
System_Error has quit [Remote host closed the connection]
System_Error has joined #armlinux
rvalue has quit [Ping timeout: 255 seconds]
sszy has joined #armlinux
dliviu has quit [Quit: Going away]
dliviu has joined #armlinux
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #armlinux
rvalue has joined #armlinux
apritzel has joined #armlinux
<mvaittin>
conchuod: Good question :) Unfortunately, I've no answer for you - but I guess I can see if I find one from the company ;)
<Xogium>
mvaittin: wrong nick ?
<mvaittin>
Xogium: why so?
<mvaittin>
Oh, I understand your question about the nick when I look at the chat history :) But no, my reply really was for conchuod
<conchuod>
mvaittin: Thanks
* ukleinek
also wondered about the context
<mvaittin>
Well, we need to go a bit back on time :) - "<conchuod> mvaittin: is a dh2228fv a product Rohm ever sold, or is it likely a typo of bh2228fv?"
<conchuod>
I've been wondering about that device for a while. the spidev driver binds to it but google gives me no results for it other than kernel patches or advice about spidev.
headless has joined #armlinux
gclement has quit [Ping timeout: 268 seconds]
gclement has joined #armlinux
System_Error has quit [Remote host closed the connection]
prabhakalad has quit [Read error: Connection reset by peer]
System_Error has joined #armlinux
<mvaittin>
I sent a question to the HQ - but it may take a while to get an answer... A while can be anything from seconds to never ;)
prabhakalad has joined #armlinux
dliviu has quit [Quit: Going away]
<mvaittin>
But I suspect you might be right. It's not really rare that ROHM would create an IC which is only ever given for one customer, and never mentioned in any public documents - but it'd be quite a coincidence that the full model number including trailing 'fv' was same for two products.
<mvaittin>
Still, I can't say anything for sure myself
dliviu has joined #armlinux
<mvaittin>
I got following reply from the HQ: "All ROHM general purpose IC should be named as started from "B", and so it may be typo.
<mvaittin>
And BH2228FV is listed as 8bit DAC with SPI I/F, then I believe that it should be typo"
<mvaittin>
Still, to be on a safe side one could ask from someone who has worked on boards that have this IC in the dts
<mvaittin>
With a bit of luck someone could even see the IC on board and what has been printed on it ;)
<Xogium>
my bad ;)
hanetzer has quit [Read error: Connection reset by peer]
<conchuod>
I think mripard was the one that added it, like 15 years ago or so.
<conchuod>
And I suspect that most boards with that in the dts are just abuse of it, since you can't put spidev in your dts.
<conchuod>
I dunno, javierm_ maybe you made it worse since if people pick a random compatible to avoid the error they could lose their userspace control iff a driver appears.
<conchuod>
Obviously what we'd like is for people to document their devices and add them, but why do that when you can pretend you have that rohm device :)
<javierm_>
conchuod: yeah...
<mvaittin>
I think I saw a comment somewhere about an use-case where a board has an SPI-port which can be populated with a device by user.
<mvaittin>
That'd might warrant use of linux,spidev ?
headless has quit [Quit: Konversation terminated!]
robmur01 has quit [Read error: Connection reset by peer]
<mvaittin>
javierm_: I suppose so. Still, if we have a thing like 'SPI-port' in HW, then I don't see it so wrong to describe it as 'spidev'. But yeah, I have no strong experience or opinion on that :) Still, I feel almost anything is better than a "company,device-which-does-not-exists-on-the-board". Almost.
<mvaittin>
Sure the "company,device-which-does-not-exist-anywhere" can be considered even worse ;)
<javierm_>
mvaittin: yeah...
System_Error has joined #armlinux
mvaittin has quit [Ping timeout: 256 seconds]
<broonie>
You should describe the thing that's connected, not the port. Or invent the connector binding we all want...
heat has joined #armlinux
rgallaispou has quit [Quit: WeeChat 4.3.3]
balrog has quit [Quit: Bye]
balrog has joined #armlinux
jclsn has joined #armlinux
Grimler has joined #armlinux
rfs613 has quit [Quit: restart]
rfs613 has joined #armlinux
psydroid2 has joined #armlinux
psydroid2 has quit [Client Quit]
psydroid2 has joined #armlinux
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #armlinux
headless has joined #armlinux
misanthropos has quit [Read error: Connection reset by peer]
gclement has quit [Ping timeout: 268 seconds]
misanthropos has joined #armlinux
prabhakalad has quit [Ping timeout: 268 seconds]
Livio has joined #armlinux
frieder has quit [Remote host closed the connection]
<maz>
robher: regarding this PASemi regression: I think the new implementation of interrupt-map parsing is slightly more strict than it was before, so we fail earlier and never evaluate the !match condition.
Livio has quit [Ping timeout: 252 seconds]
dmart has quit [Quit: leaving]
<robher>
maz: Thanks for the heads up.
<robher>
maz: I may have a dump from the last time nemo broke...
<maz>
robher: potential workaround on the list, but I'd like to see the DT to be sure.
<maz>
robher: I decided to forget everything about it...
<robher>
maz: best I can tell, the interrupt-map in pxp node is crap. IIRC, this was the platform that broke when we changed how interrupt-controller and interrupt-map in one node behaved. There's no way to translate <0x9 0x1> with interrupt-map in .../pci@11/pci@12 which appears to be the ATA node.
apritzel has quit [Ping timeout: 252 seconds]
lain6141 has quit [Read error: Connection reset by peer]