All of lore.kernel.org
 help / color / mirror / Atom feed
From: Youngmin Nam <ym0914-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: kgene-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	k.kozlowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
	linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] spi: s3c64xx: Get fifosize via device tree
Date: Sun, 14 Feb 2016 15:28:30 +0900	[thread overview]
Message-ID: <56C01E8E.6090107@gmail.com> (raw)
In-Reply-To: <20160209161036.GI13270-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>

Hello Mark.
Thank you for your review.
Please ignore previous mail that I sent to you.
I sent this mail without CC-ing. I resend including CC list.

On 2016년 02월 10일 01:10, Mark Brown wrote:
> On Wed, Feb 10, 2016 at 12:26:25AM +0900, Youngmin Nam wrote:
> 
>> SPI driver on some SoCs only differ in the fifosize of each
>> SPI channel. It is useless to duplicate the s3c64xx_spi_port_config structure
>> or create a compatible name for such a change.
> 
> I disagree that it is useless to do this, it means that if we realize
> later that there is some other difference between the implementations
> then we have the information in the DT to handle this without needing 
> to update the ABI.
> 

To clarify, let me check that I understood.
Do you mean we can fix fifosize of each SPI channel with DT handling
if there is difference on this fifosize with driver code?

If I understand your words correctly, let me modify commit messages. 

>> +Optional SoC Specific properties:
>> +
>> +- samsung,spi-fifosize: The fifo size supported by the SPI channel
>> +
>> +
> 
> In units of...?  FIFO sizes do get quoted in both words and bytes so it
> seems good to be clear.
> 

"samsung,spi-fifosize = <64>" means 64 bytes of fifosize.
Let me add the units as bytes.

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

  parent reply	other threads:[~2016-02-14  6:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 15:26 [PATCH] spi: s3c64xx: Get fifosize via device tree Youngmin Nam
2016-02-09 16:10 ` Mark Brown
     [not found]   ` <20160209161036.GI13270-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-02-14  6:28     ` Youngmin Nam [this message]
2016-02-15 18:04       ` Mark Brown
     [not found] ` <1455031585-11113-1-git-send-email-ym0914-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-14  7:01   ` Krzysztof Kozlowski
     [not found]     ` <56C02634.8020204-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2016-02-14  8:13       ` Youngmin Nam
2016-02-14  8:31         ` Krzysztof Kozlowski
2016-02-14 13:22           ` Youngmin Nam
     [not found]             ` <56C07F7C.5030907-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-14 14:31               ` Krzysztof Kozlowski

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=56C01E8E.6090107@gmail.com \
    --to=ym0914-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=k.kozlowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
    --cc=kgene-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@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 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.