From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <robherring2@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, alan@linux.intel.com,
linux-serial@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] tty/serial: atmel_serial: add device tree support
Date: Tue, 11 Oct 2011 18:04:51 +0200 [thread overview]
Message-ID: <4E946923.1010202@atmel.com> (raw)
In-Reply-To: <20111004165520.GB10919@ponder.secretlab.ca>
On 10/04/2011 06:55 PM, Grant Likely :
> On Tue, Oct 04, 2011 at 08:08:27AM -0500, Rob Herring wrote:
>> Nicolas,
>>
>> On 10/04/2011 03:18 AM, Nicolas Ferre wrote:
>>> On 10/04/2011 03:58 AM, Rob Herring :
>>>> On 10/03/2011 04:51 AM, Nicolas Ferre wrote:
>>>>> +Optional properties:
>>>>> +- atmel,use-dma-rx: use of PDC or DMA for receiving data
>>>>> +- atmel,use-dma-tx: use of PDC or DMA for transmitting data
>>>>
>>>> Is this an internal DMA or separate DMA controller? If the latter, these
>>>> should be phandles to a DMA channel/request.
>>>
>>> Well, for now it relies on PDC (looks like an internal DMA). There is no
>>> notion of channel/request so I think it is appropriate to keep it like this.
>>>
>>
>> Okay. Although, this is a bit of Linux creeping into DT. DT should
>> describe the h/w. You should really be describing whether the h/w
>> supports DMA or not rather than whether you want to use DMA or not.
>> Since DMA support is really tied to the SOC rather than board, you could
>> just use the compatible string to distinguish platforms that support DMA
>> or not. So what is determining this setting? Is it purely user choice?
>
> It is okay for a binding to still requires config properties like this
> to state if the DMA can be used, even if compatible is enough to
> distinquish. However, you're right to bring it up. It is a design
> choice that should be made thoughtfully.
Grant, Rob,
Thanks for your inputs.
I would like to keep this binding to allow the user to choose the way he
likes to use integrated DMA.
I plan to resend a patch series about this serial driver once I will be
able to propose a rs485 binding.
Cheers,
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] tty/serial: atmel_serial: add device tree support
Date: Tue, 11 Oct 2011 18:04:51 +0200 [thread overview]
Message-ID: <4E946923.1010202@atmel.com> (raw)
In-Reply-To: <20111004165520.GB10919@ponder.secretlab.ca>
On 10/04/2011 06:55 PM, Grant Likely :
> On Tue, Oct 04, 2011 at 08:08:27AM -0500, Rob Herring wrote:
>> Nicolas,
>>
>> On 10/04/2011 03:18 AM, Nicolas Ferre wrote:
>>> On 10/04/2011 03:58 AM, Rob Herring :
>>>> On 10/03/2011 04:51 AM, Nicolas Ferre wrote:
>>>>> +Optional properties:
>>>>> +- atmel,use-dma-rx: use of PDC or DMA for receiving data
>>>>> +- atmel,use-dma-tx: use of PDC or DMA for transmitting data
>>>>
>>>> Is this an internal DMA or separate DMA controller? If the latter, these
>>>> should be phandles to a DMA channel/request.
>>>
>>> Well, for now it relies on PDC (looks like an internal DMA). There is no
>>> notion of channel/request so I think it is appropriate to keep it like this.
>>>
>>
>> Okay. Although, this is a bit of Linux creeping into DT. DT should
>> describe the h/w. You should really be describing whether the h/w
>> supports DMA or not rather than whether you want to use DMA or not.
>> Since DMA support is really tied to the SOC rather than board, you could
>> just use the compatible string to distinguish platforms that support DMA
>> or not. So what is determining this setting? Is it purely user choice?
>
> It is okay for a binding to still requires config properties like this
> to state if the DMA can be used, even if compatible is enough to
> distinquish. However, you're right to bring it up. It is a design
> choice that should be made thoughtfully.
Grant, Rob,
Thanks for your inputs.
I would like to keep this binding to allow the user to choose the way he
likes to use integrated DMA.
I plan to resend a patch series about this serial driver once I will be
able to propose a rs485 binding.
Cheers,
--
Nicolas Ferre
next prev parent reply other threads:[~2011-10-11 16:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 9:51 [RFC PATCH] tty/serial: atmel_serial: add device tree support Nicolas Ferre
2011-10-03 9:51 ` Nicolas Ferre
2011-10-03 9:51 ` Nicolas Ferre
2011-10-04 1:58 ` Rob Herring
2011-10-04 1:58 ` Rob Herring
2011-10-04 8:18 ` Nicolas Ferre
2011-10-04 8:18 ` Nicolas Ferre
2011-10-04 8:18 ` Nicolas Ferre
2011-10-04 13:08 ` Rob Herring
2011-10-04 13:08 ` Rob Herring
2011-10-04 16:55 ` Grant Likely
2011-10-04 16:55 ` Grant Likely
2011-10-11 16:04 ` Nicolas Ferre [this message]
2011-10-11 16:04 ` Nicolas Ferre
2011-10-04 16:52 ` Grant Likely
2011-10-04 16:52 ` Grant Likely
2011-10-12 15:35 ` Nicolas Ferre
2011-10-12 15:35 ` Nicolas Ferre
2011-10-12 15:35 ` Nicolas Ferre
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=4E946923.1010202@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=alan@linux.intel.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robherring2@gmail.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 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.