**** BEGIN LOGGING AT Sun Mar 24 02:59:57 2019
Mar 24 15:05:21 <shreeya> @zmatt: your spi0.dtsi file worked for me :)
Mar 24 15:05:38 <shreeya> But I am getting a kernel oops
Mar 24 15:05:59 <shreeya> Which I am not sure if it related to my connection to the beaglebone
Mar 24 15:06:30 <shreeya> https://www.pastiebin.com/5c979ba3d8b4a#&togetherjs=Ih2sAelRBK
Mar 24 15:06:59 <shreeya> Above are the log messages
Mar 24 15:07:32 <zmatt> I mean, the first line says fairly explicitly what the problem is
Mar 24 15:07:40 <shreeya> Yes
Mar 24 15:07:54 <zmatt> be sure to disable cape-universal
Mar 24 15:08:22 <zmatt> actually
Mar 24 15:08:23 <zmatt> hmm
Mar 24 15:09:23 <zmatt> also, could you use a less annoying paste site next time
Mar 24 15:09:46 <shreeya> Hmmm yeah enable_uboot_cape_universal=1
Mar 24 15:10:03 <shreeya> It is enabled in uEnv.txt
Mar 24 15:10:16 <shreeya> 8:39 PM <zmatt> also, could you use a less annoying paste site next time
Mar 24 15:10:21 <shreeya> Sorry about this
Mar 24 15:10:21 <zmatt> I feel like I'm missing part of the log
Mar 24 15:10:32 <zmatt> the first three lines look like an unrelated warning
Mar 24 15:10:52 <zmatt> while the remaining lines look like the last part of a kernel oops, with the important part missing
Mar 24 15:10:58 <shreeya> This is the output of dmesg | grep spi
Mar 24 15:11:20 <zmatt> well by doing so you filtered out the actual error
Mar 24 15:11:50 <zmatt> please just pastebin the whole kernel log
Mar 24 15:12:01 <shreeya> Okay let me send you the whole kernel log
Mar 24 15:12:24 <zmatt> (using... well basically any paste site other than this one :P
Mar 24 15:12:58 <zmatt> seeing other people's cursors moving around is rather distracting
Mar 24 15:16:31 <shreeya> Yes
Mar 24 15:16:53 <shreeya> https://gist.github.com/crazoes/c9736765008264284112b87d461af82d
Mar 24 15:17:00 <shreeya> Here it is
Mar 24 15:17:30 <shreeya> Kernel null pointer dereference
Mar 24 15:18:31 <zmatt> did you name your device 'channel@0' ?
Mar 24 15:18:42 <shreeya> Does that matter?
Mar 24 15:18:47 <zmatt> or is this some old version of cape-universal?
Mar 24 15:18:55 <zmatt> I'm trying to determine which device is giving the error here
Mar 24 15:19:07 <shreeya> I didn't change it to adt7516
Mar 24 15:19:27 <shreeya> I just changed the compatible name
Mar 24 15:20:15 <shreeya> Btw cape universal was enabled
Mar 24 15:22:14 <zmatt> so, you probably need to disable cape-universal.  but regardless of what, the kernel oops is still a bug in the kernel or this driver
Mar 24 15:22:26 <shreeya> Okay
Mar 24 15:22:45 <shreeya> This is what I wanted to know
Mar 24 15:23:08 <shreeya> I am implementing regmap support for this driver
Mar 24 15:23:21 <shreeya> So maybe there is some.problem with my code
Mar 24 15:23:25 <zmatt> I'm also a bit confused that it says failed to create SPI device, yet still ends up loading and probing your driver
Mar 24 15:24:13 <shreeya> The driver sends 3 pulses down the CS line
Mar 24 15:24:25 <shreeya> To switch from i2c to spi
Mar 24 15:24:25 <zmatt> unless that error is about the device added by cape-universal, and the kernel oops is unrelated to it
Mar 24 15:24:49 <zmatt> but that's easy to verify: just disable cape-universal and check if it still happens
Mar 24 15:24:58 <shreeya> Yes
Mar 24 15:25:29 <shreeya> So while it is writing to send 3 pulses down
Mar 24 15:25:43 <shreeya> This kernel oops is generated
Mar 24 15:27:34 <shreeya> https://github.com/crazoes/adt7316/blob/master/drivers/staging/iio/addac/adt7316-spi.c#L112
Mar 24 15:32:00 <zmatt> based on the traceback, it seems it crashes here: https://github.com/crazoes/adt7316/blob/master/drivers/spi/spi.c#L3160   which may be consistent with 'struct spi_device *spi' being NULL
Mar 24 15:32:57 <shreeya> Hmmm
Mar 24 15:33:22 <shreeya> I also tried to disable cape universal
Mar 24 15:33:48 <shreeya> But the problem is not related to it (as you said)
Mar 24 15:34:45 <zmatt> in that case, as a side note, you may want update your overlays package since current versions of cape-universal do not declare a device named 'channel@0'
Mar 24 15:36:08 <shreeya> Okay
Mar 24 15:36:12 <shreeya> Will do that
Mar 24 15:36:28 <shreeya> Sorry, I gave you the link of old code
Mar 24 15:36:40 <shreeya> Here is the updated one with regmap
Mar 24 15:37:10 <shreeya> https://github.com/crazoes/adt7316/blob/new_iio/drivers/staging/iio/addac/adt7316-spi.c#L41
Mar 24 15:37:30 <zmatt> I'm a bit confused really, since I don't see it being changed from channel@0 to spi0channel@0 in the git history of the cape-universal overlay... it looks like it's always been spi0channel@0, weird
Mar 24 15:37:32 <shreeya> spi_write function is calling spi_sync
Mar 24 15:40:28 <zmatt> I don't really know anything about regmap so I'm not sure what you're doing wrong
Mar 24 15:40:37 <shreeya> Okay
Mar 24 15:40:45 <shreeya> Let us just leave that
Mar 24 15:40:50 <zmatt> obviously spi_dev isn't NULL at the start of your probe function, since then it would crash on spi_dev->max_speed_hz
Mar 24 15:41:23 <zmatt> but it appears to be NULL inside adt7316_regmap_spi_write().  you could try to confirm that using a WARN_ON(spi_dev == NULL) there or so
Mar 24 15:42:09 <zmatt> why exactly is this context-pointer supposed to be spi_dev ?
Mar 24 15:42:46 <zmatt> actually it might also be not NULL, but just the wrong pointer (causing the error somewhere further down the chain)
Mar 24 15:44:40 <zmatt> hmm, "This function should generally not be called directly, it should be called by bus-specific init functions."
Mar 24 15:45:13 <zmatt> why are you not using devm_regmap_init_spi ?
Mar 24 15:47:25 <shreeya> I haven't looked at init_spi
Mar 24 15:47:37 <shreeya> Maybe that can be my mistake
Mar 24 15:47:59 <shreeya> Context is used as a client
Mar 24 15:48:12 <shreeya> Just a different name given in regmap
Mar 24 15:48:38 <zmatt> hm, maybe it assumes a specific format.. not sure.  like I said, I've never done anything with regmap
Mar 24 15:49:04 <shreeya> Oh yed
Mar 24 15:49:09 <shreeya> Yes*
Mar 24 15:49:13 <zmatt> why are you passing &spi_dev->device as context though? that's not guaranteed to be the same pointer as spi_dev
Mar 24 15:49:21 <zmatt> if your want your context to be spi_dev, just pass spi_dev
Mar 24 15:49:27 <shreeya> I have used devm_regmap_init_i2c
Mar 24 15:49:34 <shreeya> In i2c file
Mar 24 15:49:50 <shreeya> But I haven't used init_spi for spi file
Mar 24 15:50:20 <shreeya> Stupid of me :(
Mar 24 15:51:09 <zmatt> anyway, regardless of what's causing the crash, it just seems to be a bug in your driver as far as I can tell
Mar 24 15:51:17 <shreeya> Yes
Mar 24 15:51:23 <zmatt> so I wish you good luck with debugging :)
Mar 24 15:51:32 <shreeya> Thanks :)
Mar 24 16:33:41 <shreeya> @zmatt: just FYI I used devm_regmap_init instead of devm_regmap_init_spi because I also wanted to pass the regmap bus with it. But init_spi only takes two arguments i.e.  device and config.
Mar 24 16:34:22 <shreeya> And ultimately devm_regmap_init_spi calls devm_regmap_init into it
Mar 24 19:55:05 <shreeya> @zmatt: I just solved the driver bug
Mar 24 19:55:16 <shreeya> But I am still getting the following
Mar 24 19:55:58 <shreeya> https://www.irccloud.com/pastebin/vt5y6mQi
Mar 24 19:56:41 <shreeya> If you want I'll send you the whole kernel log
Mar 24 19:57:12 <shreeya> And I think I have the latest code of your repo
Mar 24 19:57:53 <zmatt> I'm more interested in your /boot/uEnv.txt
Mar 24 19:58:06 <shreeya> Okk
Mar 24 19:59:00 <zmatt> (with "overlays package" earlier i meant the bb-cape-overlays debian package)
Mar 24 19:59:24 <zmatt> although if you have this error with cape-universal disabled, then the problem is something else
Mar 24 19:59:44 <zmatt> this kinda looks like you have another overlay enabled for spi
Mar 24 20:02:41 <shreeya> Sorry if I have made any silly mistake here
Mar 24 20:02:52 <shreeya> I have used overlays for the first time
Mar 24 20:03:12 <zmatt> if you share your /boot/uEnv.txt, I can check
Mar 24 20:07:24 <shreeya> https://gist.github.com/crazoes/26c8a8feaaa70f596fe252b69ee12c2c
Mar 24 20:07:28 <shreeya> Here it is
Mar 24 20:08:26 <zmatt> hm, weird
Mar 24 20:08:36 <zmatt> can you pastebin your overlay?
Mar 24 20:09:03 <shreeya> I was trying to do that
Mar 24 20:09:13 <shreeya> But it wasn't happening
Mar 24 20:09:16 <shreeya> Let me try
Mar 24 20:12:01 <shreeya> https://www.irccloud.com/pastebin/34EhZKEe
Mar 24 20:12:27 <shreeya> Sorry
Mar 24 20:12:30 <shreeya> Wrong file
Mar 24 20:13:46 <shreeya> https://www.irccloud.com/pastebin/0al2ewz9
Mar 24 20:14:14 <shreeya> Here it is ^
Mar 24 20:15:27 <zmatt> o.O  okay then I have no idea where the device it's complaining about is coming from
Mar 24 20:16:22 <zmatt> it looks like somehow another overlay is being applied or something, except you haven't enable any in your /boot/uEnv.txt
Mar 24 20:17:00 <shreeya> Maybe I have connected wrong pins?
Mar 24 20:17:15 <zmatt> this is a DT issue, not a hardware issue
Mar 24 20:17:20 <zmatt> and it's not an issue in your overlay
Mar 24 20:17:40 <shreeya> Ok
Mar 24 20:18:05 <zmatt> something is declaring another spi device conflicting with yours, and I don't know what
Mar 24 20:18:52 <shreeya> There has been a lot of problems with this device because there is a microcontroller in between
Mar 24 20:19:42 <shreeya> Do you have anything that you want me to try?
Mar 24 20:19:47 <zmatt> note that there's nothing going wrong with your device, those error messages should not have any adverse effect on the functionality of your device
Mar 24 20:20:02 <zmatt> I suspect this is actually something bogus in the base dts or something
Mar 24 20:20:17 <zmatt> for now I suggest you just ignore those three lines
Mar 24 20:20:33 <shreeya> Okay
Mar 24 20:20:45 <shreeya> So I can continue with the driver development
Mar 24 20:20:47 <shreeya> ?
Mar 24 20:21:00 <shreeya> Without having to worry about these?
Mar 24 20:21:01 <zmatt> yes, this shouldn't cause any problems for you
Mar 24 20:21:29 <shreeya> Okay thanks for your time and efforts :)
Mar 24 20:21:33 <zmatt> the device that failed is not your device
Mar 24 20:21:58 <shreeya> Okay
Mar 24 22:21:00 <jibbsmcgee> need some help with the beaglebone blue
Mar 24 22:22:41 <jibbsmcgee> I want to make a vaccum robot
Mar 24 22:27:19 <zmatt> tip: if you want help with something, it helps to actually ask a question / explain your problem.  (and have patience, plenty of knowledgable people here, but they may only occasionally glance at chat, so it can sometimes take quite a while to get a response)
Mar 24 22:43:54 <zmatt> or not
Mar 24 22:48:09 <set_> I know. Use a motor!
Mar 24 22:48:47 <set_> Oh. Dang. He left. That is too bad. I bet he/she could have learned some stuff about the BBB and motors.
Mar 24 22:49:51 <set_> Supreme suction is not easy on those vacuums.
Mar 24 22:59:56 <mawk> hi set_
Mar 24 23:00:17 <mawk> I'm busy doing javascript since a few weeks
Mar 24 23:00:21 <mawk> I don't like it
Mar 24 23:00:30 <mawk> but I hate it less than before starting
Mar 24 23:00:44 <mawk> my hate went from -oo hate points to -10000 hate points
Mar 24 23:00:55 <zmatt> lol
Mar 24 23:01:00 <zmatt> javascript is pretty bad
Mar 24 23:01:11 <mawk> yeah
Mar 24 23:01:20 <set_> It is not easy.
Mar 24 23:01:21 <mawk> it has modern language features next to horrible quirks
Mar 24 23:01:25 <mawk> it has a taste of unfinished
Mar 24 23:01:30 <mawk> but the syntax is okay overall, coming from C
Mar 24 23:01:36 <zmatt> a lot of legacy mistakes
Mar 24 23:01:38 <mawk> yeah
Mar 24 23:01:50 <mawk> I'm doing a chrome extension so don't care too much about legacy browsers
Mar 24 23:01:55 <mawk> I can use modules, async functions, etc
Mar 24 23:02:02 <mawk> I can unleash my creativity
Mar 24 23:02:13 <mawk> but still
Mar 24 23:02:15 <zmatt> sure they added lots of nice things, but it also has core problems that aren't easily fixable
Mar 24 23:02:17 <mawk> yeah
Mar 24 23:03:26 <zmatt> they have fortunately fixed some braindeadness.. e.g. thank god we have 'let' and 'const' now, given the bizarre behaviour of 'var' :P
Mar 24 23:03:38 <mawk> yeah
Mar 24 23:04:11 <mawk> what were they thinking with their var
Mar 24 23:04:34 <mawk> I can't think of any legit usecase
Mar 24 23:04:41 <mawk> of having names defined before their values
Mar 24 23:04:52 <set_> "easy" set up most likely to declare stuff.
Mar 24 23:05:18 <set_> So, starters like me can understand what it is exactly I need to use.
Mar 24 23:05:26 <zmatt> set_: ???
Mar 24 23:05:30 <set_> Yes?
Mar 24 23:05:34 <mawk> almost every other language have "lexical scoping"
Mar 24 23:05:40 <mawk> you don't refer to names before their definitions
Mar 24 23:05:44 <set_> Oh.
Mar 24 23:05:56 <mawk> but javascript thought it would be an interesting feature to not do that
Mar 24 23:06:23 <mawk> it's akin to isset in php
Mar 24 23:06:33 <set_> so like var = taco is not cool?
Mar 24 23:06:39 <zmatt> mawk: note that even with 'let' there are still magical bits, e.g. a closure can use variables that are declared in an enclosing scope *after* the closure is created but before the closure is invoked
Mar 24 23:06:54 <zmatt> set_: simple rule: don't use 'var', at all, ever
Mar 24 23:07:00 <mawk> lol
Mar 24 23:07:03 <set_> Fine. I used to like var.
Mar 24 23:07:16 <mawk> it's interchangeable with "let" for the purposes you were using it for
Mar 24 23:07:20 <zmatt> set_: in basically any situation you can replace it with 'let' and all will be fine
Mar 24 23:07:20 <set_> var = "contact_page";
Mar 24 23:07:24 <mawk> and if it breaks your code, your code was probably wrong
Mar 24 23:07:27 <set_> Oh.
Mar 24 23:07:33 <zmatt> set_: ehh, you're missing a variable name
Mar 24 23:07:39 <set_> Oh. Right!
Mar 24 23:07:52 <mawk> also maybe you can use as a rule to put const instead of let, and if it doesn't work you replace by let
Mar 24 23:07:52 <set_> var j = "contact_page";
Mar 24 23:08:03 <mawk> this is the braindead version, if you're smart enough you can just figure what is const and what is not
Mar 24 23:08:03 <zmatt> let j = "contact_page";
Mar 24 23:08:14 <set_> Aw!
Mar 24 23:08:45 <set_> Okay. I have not kept up w/ JavaScript in some time (ever). I get tid bits here and there but nothing concrete in my language usage.
Mar 24 23:09:14 <set_> I guess I can use let j = "SuperDuper"; for now on if I use it ever.
Mar 24 23:09:39 <set_> I barely use it w/ HTML stuff too. I should learn to use it more.
Mar 24 23:10:02 <set_> It creates nice structure.
Mar 24 23:11:24 <mawk> there are some annoying trends in the web dev currently
Mar 24 23:11:33 <mawk> I figured I would just use vanilla js and that's all
Mar 24 23:11:37 <mawk> no jquery, no whatever
Mar 24 23:11:44 <mawk> just bootstrap for the design because I'm terrible at design
Mar 24 23:12:21 <set_> bootstrap makes for nice pages.
Mar 24 23:13:14 <set_> I used this set up I found on w3schools.com, one of their templates for use, to make this webpage. It came out nice. Big and Bright!
Mar 24 23:15:18 <mawk> my thing looks like this: https://pix.watch/tF9kQT/jyrTBH.png
Mar 24 23:18:55 <mawk> several pages and popups and whatnot
Mar 24 23:30:14 <mawk> I've got a synchronization problem
Mar 24 23:30:18 <mawk> this is so annoying to debug
Mar 24 23:30:22 <mawk> over several pages
Mar 25 01:43:16 <set_> GPS!
Mar 25 01:43:38 <set_> Now...onto real time. Yikes!
**** ENDING LOGGING AT Mon Mar 25 03:00:06 2019