On Mon, Jul 01, 2024 at 09:13:50AM -0600, Jeffrey Hugo wrote:
> On 6/30/2024 8:12 PM, Slark Xiao wrote:
> > For SDX72 MBIM mode, it starts data mux id from 112 instead of 0.
> > This would lead to device can't ping outside successfully.
> > Also MBIM side would report "bad packet session (112)".In order to
> > fix this issue, we decide to use the device name of MHI controller
> > to do a match in client driver side. Then client driver could set
> > a corresponding mux_id value for this MHI product.
> >
> > Signed-off-by: Slark Xiao <slark_xiao@xxxxxxx>
> > +++ b/include/linux/mhi.h
> > @@ -289,6 +289,7 @@ struct mhi_controller_config {
> > };
> > /**
> > + * @name: device name of the MHI controller
>
> This needs to be below the next line
>
If this is the only comment of the whole series, I will fix it up while
applying. Otherwise, fix it while sending next revision.
With that,
Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@xxxxxxxxxx>
- Mani
> > * struct mhi_controller - Master MHI controller structure
> > * @cntrl_dev: Pointer to the struct device of physical bus acting as the MHI
> > * controller (required)
> > @@ -367,6 +368,7 @@ struct mhi_controller_config {
> > * they can be populated depending on the usecase.
> > */
> > struct mhi_controller {
> > + const char *name;
> > struct device *cntrl_dev;
> > struct mhi_device *mhi_dev;
> > struct dentry *debugfs_dentry;
>
--
மணிவண்ணன் சதாசிவம்
