Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Thomas Perrot <thomas.perrot@bootlin.com>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, hemantk@codeaurora.org,
	aleksander@aleksander.es
Subject: Re: [PATCH] bus: mhi: pci_generic: Introduce Sierra EM919X support
Date: Tue, 23 Nov 2021 09:05:44 +0100	[thread overview]
Message-ID: <163e5d068983030d1e879ce3321766aeb38aeed7.camel@bootlin.com> (raw)
In-Reply-To: <20211122153922.GB83834@thinkpad>

[-- Attachment #1: Type: text/plain, Size: 2385 bytes --]

Hi Mani,

On Mon, 2021-11-22 at 21:09 +0530, Manivannan Sadhasivam wrote:
> On Mon, Nov 22, 2021 at 12:11:35PM +0100, Thomas Perrot wrote:
> > Add support for EM919X modems, this modem series is based on SDX55
> > qcom chip.
> > 
> > Tested-by: Aleksander Morgado <aleksander@aleksander.es>
> > Signed-off-by: Thomas Perrot <thomas.perrot@bootlin.com>
> > ---
> >  drivers/bus/mhi/pci_generic.c | 43
> > +++++++++++++++++++++++++++++++++++
> >  1 file changed, 43 insertions(+)
> > 
> > diff --git a/drivers/bus/mhi/pci_generic.c
> > b/drivers/bus/mhi/pci_generic.c
> > index 59a4896a8030..076a951fd587 100644
> > --- a/drivers/bus/mhi/pci_generic.c
> > +++ b/drivers/bus/mhi/pci_generic.c
> > @@ -403,7 +403,50 @@ static const struct mhi_pci_dev_info
> > mhi_mv31_info = {
> >         .dma_data_width = 32,
> >  };
> >  
> > +static const struct mhi_channel_config
> > mhi_sierra_em919x_channels[] = {
> > +       MHI_CHANNEL_CONFIG_UL_SBL(2, "SAHARA", 32, 0),
> > +       MHI_CHANNEL_CONFIG_DL_SBL(3, "SAHARA", 256, 0),
> > +       MHI_CHANNEL_CONFIG_UL(4, "DIAG", 32, 0),
> > +       MHI_CHANNEL_CONFIG_DL(5, "DIAG", 32, 0),
> 
> DIAG generally uses a dedicated event ring.
> 
> > +       MHI_CHANNEL_CONFIG_UL(12, "MBIM", 128, 0),
> > +       MHI_CHANNEL_CONFIG_DL(13, "MBIM", 128, 0),
> > +       MHI_CHANNEL_CONFIG_UL(14, "QMI", 32, 0),
> > +       MHI_CHANNEL_CONFIG_DL(15, "QMI", 32, 0),
> > +       MHI_CHANNEL_CONFIG_UL(32, "DUN", 32, 0),
> > +       MHI_CHANNEL_CONFIG_DL(33, "DUN", 32, 0),
> > +       MHI_CHANNEL_CONFIG_HW_UL(100, "IP_HW0", 512, 1),
> > +       MHI_CHANNEL_CONFIG_HW_DL(101, "IP_HW0", 512, 2),
> > +};
> > +
> > +static struct mhi_event_config modem_sierra_em919x_mhi_events[] =
> > {
> > +       /* first ring is control+data and DIAG ring */
> > +       MHI_EVENT_CONFIG_CTRL(0, 2048),
> 
> I think you can just split control+data and diag events as like other
> modems.
> If there is a requirement, please mention in commit description.
> 

Thank you, I will submit a v2 that notify, in commit description, that
is a requirement.

Best regards,
Thomas

> Rest LGTM.
> 
> Thanks,
> Mani

-- 
Thomas Perrot, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      reply	other threads:[~2021-11-23  8:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 11:11 [PATCH] bus: mhi: pci_generic: Introduce Sierra EM919X support Thomas Perrot
2021-11-22 15:39 ` Manivannan Sadhasivam
2021-11-23  8:05   ` Thomas Perrot [this message]

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=163e5d068983030d1e879ce3321766aeb38aeed7.camel@bootlin.com \
    --to=thomas.perrot@bootlin.com \
    --cc=aleksander@aleksander.es \
    --cc=hemantk@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=mani@kernel.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox