All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <p.yadav@ti.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/3] mem: spi-mem: define spi_mem_default_supports_op
Date: Tue, 19 Jan 2021 17:36:00 +0530	[thread overview]
Message-ID: <20210119120558.ga3trinnpd6hxbcm@ti.com> (raw)
In-Reply-To: <20210118235256.29748-2-matt@traverse.com.au>

Hi Matthew,

> Subject: [PATCH 1/3] mem: spi-mem: define spi_mem_default_supports_op

Nitpick: You are declaring spi_mem_default_supports_op() here. It is 
already defined.

On 18/01/21 11:52PM, Mathew McBride wrote:
> spi_mem_default_supports_op is used internally by controller
> drivers to verify operation semantics are correct.
> 
> Signed-off-by: Mathew McBride <matt@traverse.com.au>
> ---
>  include/spi-mem.h | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/include/spi-mem.h b/include/spi-mem.h
> index ca0f55c8fd..92c640dabe 100644
> --- a/include/spi-mem.h
> +++ b/include/spi-mem.h
> @@ -216,6 +216,10 @@ int spi_controller_dma_map_mem_op_data(struct spi_controller *ctlr,
>  void spi_controller_dma_unmap_mem_op_data(struct spi_controller *ctlr,
>  					  const struct spi_mem_op *op,
>  					  struct sg_table *sg);
> +
> +bool spi_mem_default_supports_op(struct spi_mem *mem,
> +				 const struct spi_mem_op *op);
> +

This block of code was imported verbatim from the Linux driver and then 
wrapped around with a #ifndef __UBOOT__ to avoid compilation errors. So 
it will never get "enabled" in U-Boot ever. No driver can use the 
prototypes you have added.

And I tested this by applying your patch series and building the 
fsl_qspi driver using ls1012aqds_qspi_defconfig. Sure enough, the 
compiler reported "implicit declaration of function 
spi_mem_default_supports_op". Strangely, the linker did not complain and 
went through without errors. Not sure which function it would end up 
linking there.

Move the declaration outside this ifdef, right beside where
spi_mem_supports_op() is declared. No need to have the variant below. It 
is safe to assume CONFIG_SPI_MEM is enabled if spi-mem.h is included.

>  #else
>  static inline int
>  spi_controller_dma_map_mem_op_data(struct spi_controller *ctlr,
> @@ -231,6 +235,12 @@ spi_controller_dma_unmap_mem_op_data(struct spi_controller *ctlr,
>  				     struct sg_table *sg)
>  {
>  }
> +
> +bool spi_mem_default_supports_op(struct spi_mem *mem,
> +				 const struct spi_mem_op *op)
> +{
> +	return false;
> +}
>  #endif /* CONFIG_SPI_MEM */
>  #endif /* __UBOOT__ */
>  
> -- 
> 2.30.0
> 

-- 
Regards,
Pratyush Yadav
Texas Instruments India

  reply	other threads:[~2021-01-19 12:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 23:52 [PATCH 0/3] Fixes for SPI-NAND issues on LS1088A Mathew McBride
2021-01-18 23:52 ` [PATCH 1/3] mem: spi-mem: define spi_mem_default_supports_op Mathew McBride
2021-01-19 12:06   ` Pratyush Yadav [this message]
2021-01-25  4:00     ` Mathew McBride
2021-01-18 23:52 ` [PATCH 2/3] spi: fsl_qspi: Ensure width is respected in spi-mem operations Mathew McBride
2021-01-18 23:52 ` [PATCH 3/3] spi: fsl_qspi: apply the same settings for LS1088 as LS208x Mathew McBride
2021-01-25  3:55 ` [PATCH v2 0/3] Fixes for SPI-NAND issues on LS1088A Mathew McBride
2021-01-25  3:55 ` [PATCH v2 1/3] mem: spi-mem: add declaration for spi_mem_default_supports_op Mathew McBride
2021-01-25  8:50   ` Pratyush Yadav
2021-01-25  3:55 ` [PATCH v2 2/3] spi: fsl_qspi: Ensure width is respected in spi-mem operations Mathew McBride
2021-01-25  3:55 ` [PATCH v2 3/3] spi: fsl_qspi: apply the same settings for LS1088 as LS208x Mathew McBride

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=20210119120558.ga3trinnpd6hxbcm@ti.com \
    --to=p.yadav@ti.com \
    --cc=u-boot@lists.denx.de \
    /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.