2022-02-17 05:30:40 +08:00
|
|
|
/*
|
|
|
|
|
* Copyright 2022 NXP
|
|
|
|
|
*
|
|
|
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#ifndef ZEPHYR_SUBSYS_SD_SDMMC_PRIV_H_
|
|
|
|
|
#define ZEPHYR_SUBSYS_SD_SDMMC_PRIV_H_
|
|
|
|
|
|
includes: prefer <zephyr/kernel.h> over <zephyr/zephyr.h>
As of today <zephyr/zephyr.h> is 100% equivalent to <zephyr/kernel.h>.
This patch proposes to then include <zephyr/kernel.h> instead of
<zephyr/zephyr.h> since it is more clear that you are including the
Kernel APIs and (probably) nothing else. <zephyr/zephyr.h> sounds like a
catch-all header that may be confusing. Most applications need to
include a bunch of other things to compile, e.g. driver headers or
subsystem headers like BT, logging, etc.
The idea of a catch-all header in Zephyr is probably not feasible
anyway. Reason is that Zephyr is not a library, like it could be for
example `libpython`. Zephyr provides many utilities nowadays: a kernel,
drivers, subsystems, etc and things will likely grow. A catch-all header
would be massive, difficult to keep up-to-date. It is also likely that
an application will only build a small subset. Note that subsystem-level
headers may use a catch-all approach to make things easier, though.
NOTE: This patch is **NOT** removing the header, just removing its usage
in-tree. I'd advocate for its deprecation (add a #warning on it), but I
understand many people will have concerns.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
2022-08-25 15:58:46 +08:00
|
|
|
#include <zephyr/kernel.h>
|
2022-02-17 05:30:40 +08:00
|
|
|
#include <zephyr/sd/sd.h>
|
|
|
|
|
|
|
|
|
|
int sdmmc_card_init(struct sd_card *card);
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#endif /* ZEPHYR_SUBSYS_SD_SDMMC_PRIV_H_ */
|