From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/7] mips: ath79: Use uniform header for reset
Date: Sun, 22 May 2016 13:32:26 +0200 [thread overview]
Message-ID: <574198CA.5020506@denx.de> (raw)
In-Reply-To: <BLU436-SMTP1114C1277313C47B9422ADBFF4D0@phx.gbl>
On 05/22/2016 01:29 PM, Wills Wang wrote:
>
>
> On 05/22/2016 07:08 PM, Marek Vasut wrote:
>> On 05/22/2016 05:59 AM, Wills Wang wrote:
>>> Collect all reset operation on platform and move them into a uniform
>>> header
>>>
>>> Signed-off-by: Wills Wang <wills.wang@live.com>
>>> ---
>>>
>>> arch/mips/mach-ath79/include/mach/ath79.h | 3 ---
>>> arch/mips/mach-ath79/include/mach/reset.h | 2 ++
>>> board/tplink/wdr4300/wdr4300.c | 1 +
>>> 3 files changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/arch/mips/mach-ath79/include/mach/ath79.h
>>> b/arch/mips/mach-ath79/include/mach/ath79.h
>>> index 17af082..18d1e26 100644
>>> --- a/arch/mips/mach-ath79/include/mach/ath79.h
>>> +++ b/arch/mips/mach-ath79/include/mach/ath79.h
>>> @@ -140,9 +140,6 @@ static inline int soc_is_qca956x(void)
>>> return soc_is_tp9343() || soc_is_qca9561();
>>> }
>>> -int ath79_eth_reset(void);
>>> -int ath79_usb_reset(void);
>>> -
>>> void ar934x_pll_init(const u16 cpu_mhz, const u16 ddr_mhz, const
>>> u16 ahb_mhz);
>>> void ar934x_ddr_init(const u16 cpu_mhz, const u16 ddr_mhz, const
>>> u16 ahb_mhz);
>>> diff --git a/arch/mips/mach-ath79/include/mach/reset.h
>>> b/arch/mips/mach-ath79/include/mach/reset.h
>>> index c383bfe..7721e1d 100644
>>> --- a/arch/mips/mach-ath79/include/mach/reset.h
>>> +++ b/arch/mips/mach-ath79/include/mach/reset.h
>>> @@ -10,5 +10,7 @@
>>> #include <linux/types.h>
>>> u32 get_bootstrap(void);
>>> +int ath79_eth_reset(void);
>>> +int ath79_usb_reset(void);
>> By moving the prototype into reset.h :
>> - New functions are added to a file which can be almost removed
>> - You need to include two headers now
>>
>> So drop this patch and instead focus on getting rid of reset.h
> You mean we should use a header "ath79.h" for all?
Yes, having one header per function makes no sense and ath79.h already
has multiple function prototypes in it.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-05-22 11:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1463889595-15333-1-git-send-email-wills.wang@live.com>
2016-05-22 3:59 ` [U-Boot] [PATCH V2 2/7] mips: ath79: ar933x: Fix ethernet PHY mismatch Wills Wang
2016-05-22 11:05 ` Marek Vasut
2016-05-22 11:20 ` Wills Wang
2016-05-25 23:29 ` Daniel Schwierzeck
2016-05-22 3:59 ` [U-Boot] [PATCH 3/7] mips: ath79: Use uniform header for reset Wills Wang
2016-05-22 11:08 ` Marek Vasut
2016-05-22 11:29 ` Wills Wang
2016-05-22 11:32 ` Marek Vasut [this message]
2016-05-30 10:10 ` Daniel Schwierzeck
2016-05-22 3:59 ` [U-Boot] [PATCH 4/7] mips: ath79: Rename get_bootstrap into ath79_get_bootstrap Wills Wang
2016-05-22 11:09 ` Marek Vasut
2016-05-22 3:59 ` [U-Boot] [PATCH 5/7] mips: ath79: Unify DDR initialization entry for ar934x Wills Wang
2016-05-22 11:13 ` Marek Vasut
2016-05-22 11:35 ` Wills Wang
2016-05-22 12:23 ` Marek Vasut
2016-05-22 3:59 ` [U-Boot] [PATCH 6/7] mips: ath79: Unify PLL initialization entry Wills Wang
2016-05-22 11:14 ` Marek Vasut
2016-05-22 3:59 ` [U-Boot] [PATCH 7/7] mips: ath79: ap121: Enable ethernet Wills Wang
2016-05-22 11:14 ` Marek Vasut
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=574198CA.5020506@denx.de \
--to=marex@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox