linux-kernel - RE: [PATCH] ARM: s3x24xx: Fix gpiochip

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 25 Nov 2010 16:15:08 +0900
From:	Kukjin Kim <kgene.kim@...sung.com>
To:	'Vasily Khoruzhick' <anarsoul@...il.com>,
	'Lars-Peter Clausen' <lars@...afoo.de>
Cc:	linux-arm-kernel@...ts.infradead.org,
	'Ben Dooks' <ben-linux@...ff.org>,
	'Marek Belisko' <marek.belisko@...n-nandra.com>,
	linux-kernel@...r.kernel.org
Subject: RE: [PATCH] ARM: s3x24xx: Fix gpiochip_add complaining.

Vasily Khoruzhick wrote:
> 
> On Friday 19 November 2010 12:42:02 Lars-Peter Clausen wrote:
> > Hi
> >
Hi all,

> > Well it actually causes problems on systems with external gpio
expanders,
> > because now the additional banks will take up the space which was meant
> > for the gpio expander chip and peripherals connected to it wont be
> > accessible.
> 
> Ok, but it would be nice to see some runtime soc-type detection for
gpiolib.

Yeah, I agree. We need to check SoC type for it during booting...

> s3c2410/s3c2440/s3c2442 doesn't differ too much (actually, they're same in
> gpiopart, s3c2410 lacks some gpiobanks that s3c244[0,2] have, and
difference
> in pull-up/pull-down on s3c2440 and s3c2442).
> I think it's not good to make artificial restrictions for building single
> binary kernel for these socs.
> 
> > I sent a patch[1] about this some time ago, but I guess it was never
> > applied...

Maybe you missed my e-mail...or..I missed?...anyway...
Could you please re-send it so that can get the patch via e-mail?

> 
> Try pinging Ben or Kukjin :)
> 
Thanks...

Basically, I'd like to keep single binary for S3C24XX, maybe Ben also agree
with this. But also there is some side effects, i.e., according to
mach-s3c2410/Makefile.boot, zreladdr is different. But only selected
0x30108000 as zreladdr when build time because selected CONFIG_PM_H1940 with
s3c2410_defconfig if there is no changes kernel configuration. This is just
simple example. Maybe There are many similar examples.

Hmm...anyway, we need to sort it out with keeping S3C24XX single binary.
Will think some method for this...

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@...sung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/