All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robertino Benis <robertino.benis@intel.com>
To: ofono@ofono.org
Subject: Re: [RFC] ifxmodem: integrating new kernel-space MUX driver
Date: Thu, 03 Feb 2011 16:06:33 -0800	[thread overview]
Message-ID: <1296777993.5027.7.camel@think03> (raw)
In-Reply-To: <1296558001.1520.262.camel@aeonflux>

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

Hi Marcel,

> I am doing just a basic review here to get things going into the right
> direction.

I'll try to hash this out a bit, so maybe there won't many patch
re-submissions... 

> > +	gboolean use_ofono_mux;
> 
> This is the thing I'd rather not do. We can just have a second GPRS
> context driver. Not sure about the naming, but one could be "ifxmodem"
> and the other "ifxmodem-internal" or similar. Maybe someone comes up
> with some better names.

We had little internal discussion about this. We would like to use the
same gprs context driver instead, just as proposed. however, if you
insist on another gprs context driver ... Let me know what you think.

> > +	char if_name[IF_NAMESIZE];
> 
> This should not be needed. You can just reference the stack variable.

Ok.

> > +
> > +#define GSMIOC_ENABLE_NET       _IOW('G', 2, struct gsm_netconfig)
> > +#define GSMIOC_DISABLE_NET      _IO('G', 3)
> > +
> 
> This should be in drivers/ifxmodem/gsmmux.h and be a literal copy from
> what the kernel has. Check STE and how it does it for CAIF.

Ok, I'll pull gsmmux.h into patch submission. 

> >  	chat = g_at_chat_get_slave(gcd->chat);
> > @@ -475,6 +549,10 @@ static void ifx_gprs_context_remove(struct ofono_gprs_context *gc)
> >  		g_at_chat_resume(gcd->chat);
> >  	}
> >  
> > +	if (gcd->state != STATE_IDLE && gcd->use_ofono_mux == FALSE) {
> > +		g_at_chat_resume(gcd->chat);
> > +	}
> > +
> 
> What is this trying to fix? Either it is a general bug or not. Seems
> more like a general bug that we tie rawip existence with the state.

It was just resuming chat when kernel mux was used.


> Check if remove() will be actually ever called without calling
> deactivate() first. It might be well that this is an oversight on my
> part.

I'll test this. 

> > +	int ret;
> 
> As a general rule I prefer err as variable name.

Sure.

> > +		ofono_error("Failed to get configuration on n_gsm multiplexer: %d", ret);
> > +		goto error;
> 
> You forgot to restore the line discipline here.

Right, I'll inject this into the patch in those places where we can have
error... and watch for re-base.

There is updated patch in the works for MUX itself, as you know, once
it's in the kernel, I'll resubmit updated patch. 

Thanks,
-- r.




      reply	other threads:[~2011-02-04  0:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01  3:49 [RFC] ifxmodem: integrating new kernel-space MUX driver Robertino Benis
2011-02-01 11:00 ` Marcel Holtmann
2011-02-04  0:06   ` Robertino Benis [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=1296777993.5027.7.camel@think03 \
    --to=robertino.benis@intel.com \
    --cc=ofono@ofono.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 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.