devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
	Michal Simek
	<michal.simek-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
Cc: "Anurag Kumar Vulisha"
	<anuragku-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
	"Rob Herring" <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	"Sören Brinkmann"
	<soren.brinkmann-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
	"pawel.moll-5wv7dgnIgG8@public.gmane.org"
	<pawel.moll-5wv7dgnIgG8@public.gmane.org>,
	"mark.rutland-5wv7dgnIgG8@public.gmane.org"
	<mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	"ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org"
	<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
	"galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org"
	<galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
	"tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
	<tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-ide-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-ide-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"Anirudha Sarangi"
	<anirudh-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
	"Srikanth Vemula"
	<svemula-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
	"Punnaiah Choudary Kalluri"
	<punnaia-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
Subject: Re: [RFC PATCH] drivers: ata: Read Rx water mark value from device-tree
Date: Wed, 2 Mar 2016 12:51:44 +0100	[thread overview]
Message-ID: <56D6D3D0.9030408@xilinx.com> (raw)
In-Reply-To: <1798710.nJonRpmlxx@wuerfel>

On 2.3.2016 12:42, Arnd Bergmann wrote:
> On Wednesday 02 March 2016 10:27:51 Michal Simek wrote:
>>
>> No problem with default value in driver. Something has to be setup.
>> Reset value based on reg spec I was checking is 0x20. Based on our
>> testing we saw some issues that's why 0x40 was setup as default value.
>> There is a need to be able to configure this value for example for
>> testing different values that's why I think module parameter should be
>> the right way to go.
> 
> I don't object to the module parameter, but I don't understand how important
> that kind of testing is to normal users. Who would set it, aside from
> the person writing that driver to come up with the correct default?
> 
>> If this should be DT parameters there should be different ceva IP which
>> allows different fifo size and different watermark level to be setup by
>> user.
>>
>> What do you think? Does it sound reasonable.
> 
> Having a property for the actual hardware fifo size once you get
> different implementations seems like the correct approach, but it's
> moot as long as all implementations are hardwired to 128 entries.

yep right now and we don't know what can happen in future. I just wanted
to point to example where this property can be specified or wired to
particular compatible string.

Anurag: Please make it as module parameter instead of DT parameter.

Thanks,
Michal

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2016-03-02 11:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20 13:18 [RFC PATCH] drivers: ata: Read Rx water mark value from device-tree Anurag Kumar Vulisha
2016-02-20 22:34 ` Arnd Bergmann
2016-02-22 10:53   ` Anurag Kumar Vulisha
2016-02-22 15:19     ` Arnd Bergmann
2016-02-23  5:58       ` Anurag Kumar Vulisha
2016-02-23 10:20         ` Arnd Bergmann
2016-02-23 15:29           ` Anurag Kumar Vulisha
     [not found]             ` <3802E9A6666DF54886E2B9CBF743BA9825E0117F-4lKfpRxZ5enZMOc0yg5rMog+Gb3gawCHQz34XiSyOiE@public.gmane.org>
2016-02-23 19:29               ` Rob Herring
2016-02-26 13:48                 ` Anurag Kumar Vulisha
2016-03-02  5:53                 ` Anurag Kumar Vulisha
2016-03-02  8:05                   ` Michal Simek
2016-03-02  9:11                     ` Arnd Bergmann
2016-03-02  9:27                       ` Michal Simek
2016-03-02 11:42                         ` Arnd Bergmann
2016-03-02 11:51                           ` Michal Simek [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=56D6D3D0.9030408@xilinx.com \
    --to=michal.simek-gjffaj9ahvfqt0dzr+alfa@public.gmane.org \
    --cc=anirudh-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    --cc=anuragku-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
    --cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
    --cc=linux-ide-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
    --cc=punnaia-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    --cc=robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=soren.brinkmann-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    --cc=svemula-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    --cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).