From: Alex Elder <elder@linaro.org> To: Bjorn Andersson <bjorn.andersson@linaro.org> Cc: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>, arnd@arndb.de, david.brown@linaro.org, agross@kernel.org, davem@davemloft.net, ilias.apalodimas@linaro.org, cpratapa@codeaurora.org, syadagir@codeaurora.org, evgreen@chromium.org, benchan@google.com, ejcaruso@google.com, netdev@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/8] net: qualcomm: rmnet: fix struct rmnet_map_header Date: Tue, 21 May 2019 06:03:58 -0500 [thread overview] Message-ID: <25b1d768-d492-08a7-b1ab-d3d022b01bc9@linaro.org> (raw) In-Reply-To: <20190521030712.GY2085@tuxbook-pro> On 5/20/19 10:07 PM, Bjorn Andersson wrote: > On Mon 20 May 19:30 PDT 2019, Alex Elder wrote: > >> On 5/20/19 8:32 PM, Subash Abhinov Kasiviswanathan wrote: >>>> >>>> If you are telling me that the command/data flag resides at bit >>>> 7 of the first byte, I will update the field masks in a later >>>> patch in this series to reflect that. >>>> >>> >>> Higher order bit is Command / Data. >> >> So what this means is that to get the command/data bit we use: >> >> first_byte & 0x80 >> >> If that is correct I will remove this patch from the series and >> will update the subsequent patches so bit 7 is the command bit, >> bit 6 is reserved, and bits 0-5 are the pad length. >> >> I will post a v2 of the series with these changes, and will >> incorporate Bjorn's "Reviewed-by". >> > > But didn't you say that your testing show that the current bit order is > wrong? I did say that, but it seems I may have been misinterpreting what the documentation said, namely that "bit 0" in the network data stream is actually the high-order bit in the first byte. I did definitely see that bit 7 (0x80) in the first byte was the one selected by the "cd_bit" C bit-field originally, and I believed that was wrong. The other thing I can say is that I never see that bit set in my use of the rmnet driver for IPA. On top of that, the pad_len value is 0. Given that, either bit order works, because the whole first byte is 0 either way. So it turns out the testing I am able to do is not adequate to verify the change. I am hoping that Subash has an environment in which QMAP commands (with the appropriate bit set) are actually used. I'm going to wait a bit for him to confirm that, but at this time my plan is to do as I said above--remove this patch and adjust the ones that follow accordingly. -Alex > I still like the cleanup, if nothing else just to clarify and clearly > document the actual content of this header. > > Regards, > Bjorn >
WARNING: multiple messages have this Message-ID (diff)
From: Alex Elder <elder@linaro.org> To: Bjorn Andersson <bjorn.andersson@linaro.org> Cc: syadagir@codeaurora.org, ejcaruso@google.com, arnd@arndb.de, netdev@vger.kernel.org, ilias.apalodimas@linaro.org, linux-kernel@vger.kernel.org, evgreen@chromium.org, david.brown@linaro.org, agross@kernel.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>, davem@davemloft.net, cpratapa@codeaurora.org, benchan@google.com Subject: Re: [PATCH 1/8] net: qualcomm: rmnet: fix struct rmnet_map_header Date: Tue, 21 May 2019 06:03:58 -0500 [thread overview] Message-ID: <25b1d768-d492-08a7-b1ab-d3d022b01bc9@linaro.org> (raw) In-Reply-To: <20190521030712.GY2085@tuxbook-pro> On 5/20/19 10:07 PM, Bjorn Andersson wrote: > On Mon 20 May 19:30 PDT 2019, Alex Elder wrote: > >> On 5/20/19 8:32 PM, Subash Abhinov Kasiviswanathan wrote: >>>> >>>> If you are telling me that the command/data flag resides at bit >>>> 7 of the first byte, I will update the field masks in a later >>>> patch in this series to reflect that. >>>> >>> >>> Higher order bit is Command / Data. >> >> So what this means is that to get the command/data bit we use: >> >> first_byte & 0x80 >> >> If that is correct I will remove this patch from the series and >> will update the subsequent patches so bit 7 is the command bit, >> bit 6 is reserved, and bits 0-5 are the pad length. >> >> I will post a v2 of the series with these changes, and will >> incorporate Bjorn's "Reviewed-by". >> > > But didn't you say that your testing show that the current bit order is > wrong? I did say that, but it seems I may have been misinterpreting what the documentation said, namely that "bit 0" in the network data stream is actually the high-order bit in the first byte. I did definitely see that bit 7 (0x80) in the first byte was the one selected by the "cd_bit" C bit-field originally, and I believed that was wrong. The other thing I can say is that I never see that bit set in my use of the rmnet driver for IPA. On top of that, the pad_len value is 0. Given that, either bit order works, because the whole first byte is 0 either way. So it turns out the testing I am able to do is not adequate to verify the change. I am hoping that Subash has an environment in which QMAP commands (with the appropriate bit set) are actually used. I'm going to wait a bit for him to confirm that, but at this time my plan is to do as I said above--remove this patch and adjust the ones that follow accordingly. -Alex > I still like the cleanup, if nothing else just to clarify and clearly > document the actual content of this header. > > Regards, > Bjorn > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-05-21 11:04 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-20 13:53 [PATCH 0/8] net: introduce "include/linux/if_rmnet.h" Alex Elder 2019-05-20 13:53 ` Alex Elder 2019-05-20 13:53 ` [PATCH 1/8] net: qualcomm: rmnet: fix struct rmnet_map_header Alex Elder 2019-05-20 13:53 ` Alex Elder 2019-05-20 15:38 ` Bjorn Andersson 2019-05-20 15:38 ` Bjorn Andersson 2019-05-20 20:11 ` Subash Abhinov Kasiviswanathan 2019-05-20 20:11 ` Subash Abhinov Kasiviswanathan 2019-05-20 21:23 ` Alex Elder 2019-05-20 21:23 ` Alex Elder 2019-05-21 1:32 ` Subash Abhinov Kasiviswanathan 2019-05-21 1:32 ` Subash Abhinov Kasiviswanathan 2019-05-21 2:30 ` Alex Elder 2019-05-21 2:30 ` Alex Elder 2019-05-21 3:07 ` Bjorn Andersson 2019-05-21 3:07 ` Bjorn Andersson 2019-05-21 11:03 ` Alex Elder [this message] 2019-05-21 11:03 ` Alex Elder 2019-05-20 13:53 ` [PATCH 2/8] net: qualcomm: rmnet: kill RMNET_MAP_GET_*() accessor macros Alex Elder 2019-05-20 13:53 ` Alex Elder 2019-05-20 15:41 ` Bjorn Andersson 2019-05-20 15:41 ` Bjorn Andersson 2019-05-20 13:53 ` [PATCH 3/8] net: qualcomm: rmnet: use field masks instead of C bit-fields Alex Elder 2019-05-20 13:53 ` Alex Elder 2019-05-20 15:43 ` Bjorn Andersson 2019-05-20 15:43 ` Bjorn Andersson 2019-05-20 13:53 ` [PATCH 4/8] net: qualcomm: rmnet: don't use C bit-fields in rmnet checksum header Alex Elder 2019-05-20 13:53 ` Alex Elder 2019-05-20 15:49 ` Bjorn Andersson 2019-05-20 15:49 ` Bjorn Andersson 2019-05-20 13:53 ` [PATCH 5/8] net: qualcomm: rmnet: don't use C bit-fields in rmnet checksum trailer Alex Elder 2019-05-20 13:53 ` Alex Elder 2019-05-20 17:17 ` Bjorn Andersson 2019-05-20 17:17 ` Bjorn Andersson 2019-05-20 13:53 ` [PATCH 6/8] net: qualcomm: rmnet: get rid of a variable in rmnet_map_ipv4_ul_csum_header() Alex Elder 2019-05-20 13:53 ` Alex Elder 2019-05-20 17:17 ` Bjorn Andersson 2019-05-20 17:17 ` Bjorn Andersson 2019-05-20 13:53 ` [PATCH 7/8] net: qualcomm: rmnet: mark endianness of struct rmnet_map_dl_csum_trailer fields Alex Elder 2019-05-20 13:53 ` Alex Elder 2019-05-20 17:17 ` Bjorn Andersson 2019-05-20 17:17 ` Bjorn Andersson 2019-05-20 13:53 ` [PATCH 8/8] net: introduce "include/linux/if_rmnet.h" Alex Elder 2019-05-20 13:53 ` Alex Elder 2019-05-20 17:18 ` Bjorn Andersson 2019-05-20 17:18 ` Bjorn Andersson 2019-05-20 18:00 ` [PATCH 0/8] " Alex Elder 2019-05-20 18:00 ` Alex Elder
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=25b1d768-d492-08a7-b1ab-d3d022b01bc9@linaro.org \ --to=elder@linaro.org \ --cc=agross@kernel.org \ --cc=arnd@arndb.de \ --cc=benchan@google.com \ --cc=bjorn.andersson@linaro.org \ --cc=cpratapa@codeaurora.org \ --cc=davem@davemloft.net \ --cc=david.brown@linaro.org \ --cc=ejcaruso@google.com \ --cc=evgreen@chromium.org \ --cc=ilias.apalodimas@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=subashab@codeaurora.org \ --cc=syadagir@codeaurora.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.