From: alan@linux.intel.com (Alan Cox)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 02/14] ARM : SAMSUNG : Add RS485 support.
Date: Tue, 1 Nov 2011 12:18:51 +0000 [thread overview]
Message-ID: <20111101121851.7d393277@bob.linux.org.uk> (raw)
In-Reply-To: <1319255194-4799-1-git-send-email-paul.s.schilling@gmail.com>
> +config SAMSUNG_HAS_RS485
> + bool "Enable RS485 support for Samsung"
> + depends on SERIAL_SAMSUNG && (MACH_CONDOR2440 ||
> MACH_CONDOR2416 || MACH_MINI2440)
> + default y if (MACH_CONDOR2440 || MACH_CONDOR2416)
> + default n if (MACH_MINI2440)
There really needs to be more ARM thinking about doing this sort of
stuff at runtime. If you can detect the board type at runtime then you
need to be moving towards kicking board specifics out of the depends,
and treating it as an "include support for this, if the board has it"
so you can move towards less build time only configuration.
> +/* FIXME */
> + #if 0
> + if (last_state != en) {
> +
So this doesn't look ready to submit either...
> + if ((utrstat & S3C2410_UTRSTAT_TXE) ? 1 : 0) {
> + if (cfg->gpio_transmit_en > -1) {
> +
> gpio_set_value(cfg->gpio_transmit_en, 0);
> + }
Lots of excess brackets (see CodingStyle) - removing a few of the
excess ones would make it easier to read later.
The later bits become a real mess of ifdefs - much not your fault, the
combination of your ifdefs and existing lack of design push it beyond
ugly and really want addressing.
next prev parent reply other threads:[~2011-11-01 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <samsung_rs485>
2011-10-22 3:46 ` [PATCH 02/14] ARM : SAMSUNG : Add RS485 support Paul Schilling
2011-10-22 13:47 ` Russell King - ARM Linux
2011-10-23 17:12 ` Paul Schilling
2011-10-23 20:20 ` Russell King - ARM Linux
2011-11-01 12:18 ` Alan Cox [this message]
2011-11-01 14:57 ` Paul Schilling
2011-11-01 19:12 ` Paul Schilling
2011-11-01 19:22 ` Paul Schilling
2011-11-01 19:55 ` Alan Cox
2011-11-04 10:18 ` Nicolas Ferre
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=20111101121851.7d393277@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.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).