From: Viresh Kumar <viresh.kumar@linaro.org> To: Cristian Marussi <cristian.marussi@arm.com> Cc: Sudeep Holla <sudeep.holla@arm.com>, Vincent Guittot <vincent.guittot@linaro.org>, Arnd Bergmann <arnd@arndb.de>, Jassi Brar <jassisinghbrar@gmail.com>, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] firmware: arm_scmi: Make scmi core independent of transport type Date: Tue, 10 Dec 2019 11:04:48 +0530 [thread overview] Message-ID: <20191210053448.ugjzbp2puzvnm37f@vireshk-i7> (raw) In-Reply-To: <71417ba8-b844-ac96-bcad-4bf48fa8b869@arm.com> On 09-12-19, 18:13, Cristian Marussi wrote: > On 29/11/2019 09:31, Viresh Kumar wrote: > > /** > > * struct scmi_info - Structure representing a SCMI instance > > * > > @@ -128,6 +109,7 @@ struct scmi_chan_info { > > struct scmi_info { > > struct device *dev; > > const struct scmi_desc *desc; > > + struct scmi_transport_ops *transport_ops; > > struct scmi_revision_info version; > > struct scmi_handle handle; > > struct scmi_xfers_info tx_minfo; > > @@ -138,7 +120,6 @@ struct scmi_info { > > int users; > > }; > > > > Could we add also the related @transport_ops in the above comment block ? Ah, I missed that. > > desc = of_device_get_match_data(dev); > > if (!desc) > > return -EINVAL; > > This scmi_desc struct descriptor is retrieved from of_match_table .data and points to > the driver-provided scmi_generic_desc > > static const struct scmi_desc scmi_generic_desc = { > .max_rx_timeout_ms = 30, /* We may increase this if required */ > .max_msg = 20, /* Limited by MBOX_TX_QUEUE_LEN */ > .max_msg_size = 128, > }; > > Is not this kind of information possibly (maybe partially) related to the selected > transport, and as such it should be also provided dynamically by the chosen transport > layer at probe time, like the transport_ops, instead of being hard-coded in > this driver ? I had my doubts about this thing and I missed checking it out. @Sudeep: Is this information completely mailbox specific ? Should I move it to mailbox.c here ? -- viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org> To: Cristian Marussi <cristian.marussi@arm.com> Cc: Arnd Bergmann <arnd@arndb.de>, Jassi Brar <jassisinghbrar@gmail.com>, linux-kernel@vger.kernel.org, Sudeep Holla <sudeep.holla@arm.com>, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] firmware: arm_scmi: Make scmi core independent of transport type Date: Tue, 10 Dec 2019 11:04:48 +0530 [thread overview] Message-ID: <20191210053448.ugjzbp2puzvnm37f@vireshk-i7> (raw) In-Reply-To: <71417ba8-b844-ac96-bcad-4bf48fa8b869@arm.com> On 09-12-19, 18:13, Cristian Marussi wrote: > On 29/11/2019 09:31, Viresh Kumar wrote: > > /** > > * struct scmi_info - Structure representing a SCMI instance > > * > > @@ -128,6 +109,7 @@ struct scmi_chan_info { > > struct scmi_info { > > struct device *dev; > > const struct scmi_desc *desc; > > + struct scmi_transport_ops *transport_ops; > > struct scmi_revision_info version; > > struct scmi_handle handle; > > struct scmi_xfers_info tx_minfo; > > @@ -138,7 +120,6 @@ struct scmi_info { > > int users; > > }; > > > > Could we add also the related @transport_ops in the above comment block ? Ah, I missed that. > > desc = of_device_get_match_data(dev); > > if (!desc) > > return -EINVAL; > > This scmi_desc struct descriptor is retrieved from of_match_table .data and points to > the driver-provided scmi_generic_desc > > static const struct scmi_desc scmi_generic_desc = { > .max_rx_timeout_ms = 30, /* We may increase this if required */ > .max_msg = 20, /* Limited by MBOX_TX_QUEUE_LEN */ > .max_msg_size = 128, > }; > > Is not this kind of information possibly (maybe partially) related to the selected > transport, and as such it should be also provided dynamically by the chosen transport > layer at probe time, like the transport_ops, instead of being hard-coded in > this driver ? I had my doubts about this thing and I missed checking it out. @Sudeep: Is this information completely mailbox specific ? Should I move it to mailbox.c here ? -- viresh _______________________________________________ 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-12-10 5:34 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-29 9:31 [PATCH] firmware: arm_scmi: Make scmi core independent of transport type Viresh Kumar 2019-11-29 9:31 ` Viresh Kumar 2019-12-03 12:00 ` Sudeep Holla 2019-12-03 12:00 ` Sudeep Holla 2019-12-10 10:18 ` Viresh Kumar 2019-12-10 10:18 ` Viresh Kumar 2019-12-09 18:13 ` Cristian Marussi 2019-12-09 18:13 ` Cristian Marussi 2019-12-10 5:34 ` Viresh Kumar [this message] 2019-12-10 5:34 ` Viresh Kumar 2019-12-10 18:46 ` Sudeep Holla 2019-12-10 18:46 ` Sudeep Holla 2019-12-11 2:43 ` Viresh Kumar 2019-12-11 2:43 ` Viresh Kumar 2019-12-31 2:50 ` Peng Fan 2019-12-31 2:50 ` Peng Fan 2019-12-31 12:22 ` Sudeep Holla 2019-12-31 12:22 ` Sudeep Holla 2019-12-31 20:09 ` Jassi Brar 2019-12-31 20:09 ` Jassi Brar 2020-01-06 11:00 ` Sudeep Holla 2020-01-06 11:00 ` Sudeep Holla 2020-01-09 8:18 ` Arnd Bergmann 2020-01-09 8:18 ` Arnd Bergmann 2020-01-09 9:16 ` Viresh Kumar 2020-01-09 9:16 ` Viresh Kumar 2020-01-10 12:22 ` Sudeep Holla 2020-01-10 12:22 ` Sudeep Holla 2020-01-09 9:34 ` Viresh Kumar 2020-01-09 9:34 ` Viresh Kumar 2020-01-09 10:15 ` Arnd Bergmann 2020-01-09 10:15 ` Arnd Bergmann 2020-01-10 12:27 ` Sudeep Holla 2020-01-10 12:27 ` Sudeep Holla 2020-01-13 6:45 ` Peng Fan 2020-01-13 6:45 ` Peng Fan 2020-01-10 12:31 ` Sudeep Holla 2020-01-10 12:31 ` Sudeep Holla
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=20191210053448.ugjzbp2puzvnm37f@vireshk-i7 \ --to=viresh.kumar@linaro.org \ --cc=arnd@arndb.de \ --cc=cristian.marussi@arm.com \ --cc=jassisinghbrar@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=sudeep.holla@arm.com \ --cc=vincent.guittot@linaro.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.