From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/4] mfd: add basic Super I/O chip helpers
Date: Mon, 14 Oct 2019 15:18:47 +0200 [thread overview]
Message-ID: <20191014131847.z7hvwp2p2qlee57s@pengutronix.de> (raw)
In-Reply-To: <20191011162753.17100-1-a.fatoum@pengutronix.de>
On Fri, Oct 11, 2019 at 06:27:50PM +0200, Ahmad Fatoum wrote:
> Super I/O chips are ICs common to x86 that are used for interfacing
> to low-bandwidth peripherals. They often contain serial ports, watchdog
> timers and hardware monitoring units.
>
> They are usually addressable via one of two I/O port pairs, either
> 0x2e-0x2f or 0x4e-0x4f, but they don't typically respond to reads from
> their range unless a device-specific 'password' has been poked in.
> After this is done, they are read and written in the same manner however.
>
> On Linux, these devices aren't subject to any device/driver model.
> Each driver for some function (e.g. watchdog or GPIO) duplicates the
> device probe in the module_init and board-specific configuration
> is handled via module parameters.
>
> Lets do it a bit fancier in barebox and add a helper to register chips
> and a regmap for the control and configuration registers as well as a
> helper to register child devices for each function contained within the
> Super I/O chip.
> Board-specific configuration, e.g. which pin to use as a watchdog reset,
> can then be realized using barebox device-specific parameters.
>
> The regmap will be more of a debugging aid, however.
> For ease of porting from Linux, it's expected that access to the
> I/O ports won't happen via the regmap. For this reason, the new
> <superio.h> header offers functions to read/write these chips' registers
> as well.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-10-14 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 16:27 Ahmad Fatoum
2019-10-11 16:27 ` [PATCH 2/4] mfd: superio: add Fintek MFD driver Ahmad Fatoum
2019-10-11 16:27 ` [PATCH 3/4] watchdog: add support for Fintek F718xx and, F818xx Super I/O Ahmad Fatoum
2019-10-14 12:39 ` Sascha Hauer
2019-10-14 12:47 ` [PATCH] fixup! " Ahmad Fatoum
2019-10-11 16:27 ` [PATCH 4/4] mfd: superio: add base SMSC MFD driver Ahmad Fatoum
2019-10-14 13:18 ` Sascha Hauer [this message]
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=20191014131847.z7hvwp2p2qlee57s@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@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