linux-wpan.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Vincent <simon.vincent@xsilon.com>
To: Alan Ott <alan@signal11.us>, linux-wpan@vger.kernel.org
Subject: Re: [PATCH linux-wpan v3] ieee802154: mrf24j40: Add support for MRF24J40MC
Date: Mon, 06 Oct 2014 10:41:52 +0100	[thread overview]
Message-ID: <543263E0.4060009@xsilon.com> (raw)
In-Reply-To: <5431B934.9050304@signal11.us>


On 05/10/14 22:33, Alan Ott wrote:
> On 10/02/2014 05:55 AM, Simon Vincent wrote:
>> The MRF24J40MC module has an external amplifier which should be
>> enabled. The TX power has to be lowered to meet FCC regs.
>>
>> Signed-off-by: Simon Vincent <simon.vincent@xsilon.com>
>> ---
>> v2 -> v3:
>> * Added extra code comments and removed check of spi return values.
>>
>>   drivers/net/ieee802154/mrf24j40.c | 32 
>> ++++++++++++++++++++++++++++++--
>>   1 file changed, 30 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/net/ieee802154/mrf24j40.c 
>> b/drivers/net/ieee802154/mrf24j40.c
>> index 07e0b88..ff3ca07 100644
>> --- a/drivers/net/ieee802154/mrf24j40.c
>> +++ b/drivers/net/ieee802154/mrf24j40.c
>> @@ -43,6 +43,8 @@
>>   #define REG_TXSTBL   0x2E  /* TX Stabilization */
>>   #define REG_INTSTAT  0x31  /* Interrupt Status */
>>   #define REG_INTCON   0x32  /* Interrupt Control */
>> +#define REG_GPIO     0x33  /* GPIO */
>> +#define REG_TRISGPIO 0x34  /* GPIO direction */
>>   #define REG_RFCTL    0x36  /* RF Control Mode Register */
>>   #define REG_BBREG1   0x39  /* Baseband Registers */
>>   #define REG_BBREG2   0x3A  /* */
>> @@ -63,6 +65,7 @@
>>   #define REG_SLPCON1    0x220
>>   #define REG_WAKETIMEL  0x222  /* Wake-up Time Match Value Low */
>>   #define REG_WAKETIMEH  0x223  /* Wake-up Time Match Value High */
>> +#define REG_TESTMODE   0x22F  /* Test mode */
>>   #define REG_RX_FIFO    0x300  /* Receive FIFO */
>>
>>   /* Device configuration: Only channels 11-26 on page 0 are 
>> supported. */
>> @@ -75,6 +78,8 @@
>>   #define RX_FIFO_SIZE 144 /* From datasheet */
>>   #define SET_CHANNEL_DELAY_US 192 /* From datasheet */
>>
>> +enum mrf24j40_modules { MRF24J40, MRF24J40MA, MRF24J40MC };
>> +
>>   /* Device Private Data */
>>   struct mrf24j40 {
>>       struct spi_device *spi;
>> @@ -691,6 +696,28 @@ static int mrf24j40_hw_init(struct mrf24j40 
>> *devrec)
>>       if (ret)
>>           goto err_ret;
>>
>> +    if (spi_get_device_id(devrec->spi)->driver_data == MRF24J40MC) {
>> +        /* Enable external amplifier.
>> +         * From MRF24J40MC datasheet section 1.3: Operation.
>> +         */
>> +        write_long_reg(devrec, REG_TESTMODE, &val);
>
> This compiles? I think you want read_*() here. I'm surprised the 
> write_*() compiles with a pointer parameter given the kernel's 
> warning/error settings.
>
Sorry I had picked up on this during testing but I must have sent the 
wrong patch. I have sent a v4 patch now with this corrected.

Simon

  reply	other threads:[~2014-10-06  9:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02  9:55 [PATCH linux-wpan v3] ieee802154: mrf24j40: Add support for MRF24J40MC Simon Vincent
2014-10-05 21:33 ` Alan Ott
2014-10-06  9:41   ` Simon Vincent [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-06  9:37 Simon Vincent

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=543263E0.4060009@xsilon.com \
    --to=simon.vincent@xsilon.com \
    --cc=alan@signal11.us \
    --cc=linux-wpan@vger.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;
as well as URLs for NNTP newsgroup(s).