netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: stefano babic <stefano.babic@babic.homelinux.org>
To: sjur.brandeland@stericsson.com
Cc: netdev@vger.kernel.org, randy.dunlap@oracle.com,
	kim.xx.lilliestierna@stericsson.com,
	christian.bejram@stericsson.com,
	daniel.martensson@stericsson.com
Subject: Re: [RFC PATCH v3  2/8] CAIF Protocol Stack
Date: Wed, 09 Dec 2009 01:18:52 +0100	[thread overview]
Message-ID: <4B1EECEC.5080903@babic.homelinux.org> (raw)
In-Reply-To: <1259593252-2493-3-git-send-email-sjur.brandeland@stericsson.com>

sjur.brandeland@stericsson.com wrote:
> diff --git a/include/net/caif/generic/caif_layer.h b/include/net/caif/generic/caif_layer.h

> +enum caif_ctrlcmd {
> +	/** Flow Control is OFF, transmit function should stop sending data */
> +	CAIF_CTRLCMD_FLOW_OFF_IND = 0,
> +	/** Flow Control is ON, transmit function can start sending data */
> +	CAIF_CTRLCMD_FLOW_ON_IND = 1,
> +	/** Remote end modem has decided to close down channel */
> +	CAIF_CTRLCMD_REMOTE_SHUTDOWN_IND = 5,

Not really important, but is there some reason to not put them in order ?


> diff --git a/include/net/caif/generic/cfcnfg.h b/include/net/caif/generic/cfcnfg.h
> +/** Physical preference - HW Abstraction */
> +enum cfcnfg_phy_preference {
> +	/** Default physical interface */
> +	CFPHYPREF_UNSPECIFIED = 0xa0,
> +	/** Default physical interface for low-latency traffic */
> +	CFPHYPREF_LOW_LAT = 0xd0,
> +	/** Default physical interface for high-bandwidth traffic */
> +	CFPHYPREF_HIGH_BW = 0xe0,
> +	/** \b TEST \b ONLY Loopback interface simulating modem responses */
> +	CFPHYPREF_LOOP = 0x70,
> +	/** \b TEST \b ONLY Raw loopback interface */
> +	CFPHYPREF_RAW_LOOP = 0x80
> +};

Different context, but preferences have always the same values. Could we
remove the duplicates ?

> +/** Configuration parameters for a physical layer (e.g. serial) */
> +struct cfcnfg_phy_param {
> +	int foo;
> +};

This structure is obsolete and can be safely dropped.

> +/**
> + * These variable is used as a global flag, in order to configure padding on SPI communication.
> + * NOTE: This is not a fully future-proof solution.
> + */

I understand that the padding is due to the fact that a lot of spi
controller can send only words and not bytes. However, this is very
processor specific. Probably when you will add the SPI layer you will
need to add a way to set up this issue.

Stefano

-- 
stefano <stefano.babic@babic.homelinux.org>
GPG Key: 0x55814DDE
Fingerprint 4E85 2A66 4CBA 497A 2A7B D3BF 5973 F216 5581 4DDE

  parent reply	other threads:[~2009-12-09  0:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 15:00 [RFC PATCH v3 0/8] CAIF Protocol Stack sjur.brandeland
2009-11-30 15:00 ` [RFC PATCH v3 1/8] " sjur.brandeland
2009-11-30 15:00   ` [RFC PATCH v3 2/8] " sjur.brandeland
2009-11-30 15:00     ` [RFC PATCH v3 3/8] " sjur.brandeland
2009-11-30 15:00       ` [RFC PATCH v3 4/8] " sjur.brandeland
2009-11-30 15:00         ` [RFC PATCH v3 5/8] " sjur.brandeland
2009-11-30 15:00           ` [RFC PATCH v3 6/8] " sjur.brandeland
2009-11-30 15:00             ` [RFC PATCH v3 7/8] " sjur.brandeland
2009-11-30 15:00               ` [RFC PATCH v3 8/8] " sjur.brandeland
2009-12-15 17:12               ` [RFC PATCH v3 7/8] " stefano babic
2009-11-30 16:41           ` [RFC PATCH v3 5/8] " Randy Dunlap
2009-12-10 13:05             ` Sjur Brændeland
2009-12-10 16:44               ` Randy Dunlap
2009-12-15 16:47         ` [RFC PATCH v3 4/8] " stefano babic
2009-12-16 16:16           ` Sjur Brændeland
2009-12-15 16:00       ` [RFC PATCH v3 3/8] " stefano babic
2009-12-16 16:15         ` Sjur Brændeland
2009-12-09  0:18     ` stefano babic [this message]
2009-12-10 11:20       ` [RFC PATCH v3 2/8] " Sjur Brændeland
2009-12-08 23:42   ` [RFC PATCH v3 1/8] " stefano babic
2009-12-10 11:11     ` Sjur Brændeland
2009-11-30 16:08 ` [RFC PATCH v3 0/8] " Patrick McHardy
2009-11-30 18:26   ` Sjur Brændeland
2009-12-02 17:02 ` Stefano Babic
2009-12-03 17:49   ` Sjur Brændeland

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=4B1EECEC.5080903@babic.homelinux.org \
    --to=stefano.babic@babic.homelinux.org \
    --cc=christian.bejram@stericsson.com \
    --cc=daniel.martensson@stericsson.com \
    --cc=kim.xx.lilliestierna@stericsson.com \
    --cc=netdev@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sjur.brandeland@stericsson.com \
    /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;
as well as URLs for NNTP newsgroup(s).